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: Thu, 23 Feb 2012 09:48:23 +0800 From: Ian Kent <raven@...maw.net> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>, autofs@...r.kernel.org, Thomas Meyer <thomas@...3r.de>, Al Viro <viro@...iv.linux.org.uk> Subject: Re: compat: autofs v5 packet size ambiguity - update On Wed, 2012-02-22 at 08:12 -0800, Linus Torvalds wrote: > On Wed, Feb 22, 2012 at 1:32 AM, Ian Kent <raven@...maw.net> wrote: > > > > Oh, DOH ... > > > > The process mounting the autofs mount is passing the pipe it will use > > for communication via a mount option so we can do this right in > > fill_super. > > No, we really cannot. Sorry, I think your wrong this time. > > The autofs "mount" is done by fork + execve("mount"). It's done like this when mounting things inside an already mounted indirect autofs mount or when mounting things on autofs direct mount triggers but, in version 5, mount(2) has always used to mount autofs file systems. Ian -- 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