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: Sat, 18 Oct 2014 19:45:28 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Miklos Szeredi <miklos@...redi.hu> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Maxim Patlasov <mpatlasov@...allels.com>, Anand Avati <avati@...ster.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Michael j Theall <mtheall@...ibm.com>, fuse-devel <fuse-devel@...ts.sourceforge.net> Subject: Re: [PATCH 0/5] fuse: handle release synchronously (v4) On Sat, Oct 18, 2014 at 07:24:54PM +0100, Al Viro wrote: > On Sat, Oct 18, 2014 at 08:01:13PM +0200, Miklos Szeredi wrote: > > > And what you don't get is that there's a deep difference between those > > and the /proc file access case. > > > > And the difference is that one is done because of an explicit action > > by the holder of the open file. And the other is done by some random > > process doing non-invasive examination of the holder of the open-file. > > Such as ls -l /proc/*/fd/*? That will give you the same transient EBUSY > from umount, if it hits the right moment... stat -L /proc/*/fd/*, that is... -- 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