lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 30 Jun 2012 00:04:36 -0700
From:	Tejun Heo <>
To:	Al Viro <>
Cc:	Li Zefan <>, shyju pv <>,
	"" <>,
	"" <>,
	Sanil kumar <>,
	Masanari Iida <>
Subject: Re: 3.5-rc3: BUG: Dentry still in use (1) [unmount of cgroup cgroup]

Hello, Al.

On Fri, Jun 29, 2012 at 11:47 PM, Al Viro <> wrote:
> On Sat, Jun 30, 2012 at 02:13:02PM +0800, Li Zefan wrote:
>> So it's bad to have dentry refcnts dangling after umount.
> No shit.  Yes, it is bad.  What on the Earth is cgroup code doing with
> those?  And what could it possibly want to do with dentry reference
> after the filesystem has been shut down, assuming it could hold one
> in the first place?

cgroup interface code was copied from sysfs back when it was
piggybacking internal data structures to dentries, so, unfortunately,
sysfs is still using dentries to manage internal data structures and
propagates internal refs to dentry refs. There seem to be several
places where dentry ref is held w/o active super ref triggering BUG on
umount. Longer term, it should be updated to share sysfs code, I


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists