After adding "C=1 CF=-D__CHECK_ENDIAN__" to my build script, sparse produced the following warning: kernel/audit_tree.c:222:13: warning: context imbalance in 'untag_chunk' - unexpected unlock It looks like a confused parser to me, because the locks appear to balance properly from my review. It doesn't say which lock triggered the warning, hash_lock, or entry->lock. The hash_lock is locked on call and returns in the same state. entry->lock looks fine. The fsnotify marks look get/put balanced too. Is sparse spewing bogons, or am I? - RGB -- Richard Guy Briggs <rbriggs(a)redhat.com&gt; Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat Remote, Ottawa, Canada Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545