lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 7 Jan 2008 09:22:56 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Tejun Heo <htejun@...il.com> Cc: "Eric W. Biederman" <ebiederm@...ssion.com>, Gabor Gombas <gombasg@...aki.hu>, Dave Young <hidave.darkstar@...il.com>, linux-kernel@...r.kernel.org, bluez-devel@...ts.sourceforge.net, Greg KH <greg@...ah.com> Subject: Re: [Bluez-devel] Oops involving RFCOMM and sysfs On Mon, Jan 07, 2008 at 06:18:21PM +0900, Tejun Heo wrote: > Tejun Heo wrote: > > Eric W. Biederman wrote: > >>> That said, the mechanism is a bit too fragile. sysfs currently ensures > >>> that dentry/inode point to the associated sysfs_dirent. This is mainly > >>> remanent of conversion from previous VFS based implementation. I think > >>> the right thing to do here is to make sysfs behave like other proper > >>> distributed filesystems using d_revalidate. > >> Huh? We still need something like sysfs_get_dentry to find the dentries > >> for the rename or move operation. So we can call d_move. > > > > Ah... right. Thanks. :-) > > On the second thought, can't those too be dealt with d_revalidate? FVO "dealt with" as pleasant and efficient as using coarse whetstone to deal with caries. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists