| 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, 28 Dec 2015 12:31:21 -0800 From: Greg Kroah-Hartman <greg@...ah.com> To: Rajat Jain <rajatxjain@...il.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-newbie@...r.kernel.org Subject: Re: debugfs_remove_recursive() while a file is in use by userspace On Mon, Dec 28, 2015 at 12:27:22PM -0800, Rajat Jain wrote: > Hi, > > I wanted to understand the behavior taken when a module calls > debugfs_remove_recursive() on a directory, while files under that > directory may still be in use by the userspace (for instance an > ongoing read / write operation). Bad things :( > Does the function wait > > (1) until all the currently executing file operation methods > (read/write/map etc) have returned? Nope. > OR > (2) until the user has given up all references (descriptors) to the > files under the directory (i.e. until release() method has been > called)? Nope. There are some patches on the mailing list that I need to review that hopefully should resolve this problem, as it's been known for a very long time. In short, just don't remove debugfs files unless your module is unloading, and all should be good as modules are never auto-unloaded. If you remove debugfs files when a device is removed, be careful. thanks, greg k-h -- 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