From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jonas Gorski <jonas.gorski@gmail.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: Why is CONFIG_FHANDLE an option??
Date: Fri, 10 Jun 2011 23:58:35 +0100 [thread overview]
Message-ID: <20110610225835.GC11521@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1106110040370.21722@swampdragon.chaosbits.net>
On Sat, Jun 11, 2011 at 12:42:50AM +0200, Jesper Juhl wrote:
> Yes, I'm aware of that. Doesn't mean we have to make things worse.
> Just because we've had optional syscalls in the past doesn't mean we have
> to add more, nor that the existing ones were a good idea. IMHO they should
> be removed as options and just included unconditionally - not too late to
> correct this...
There's fanotify in that pile. Consider that bright idea *strongly* NAKed.
next prev parent reply other threads:[~2011-06-10 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 22:14 Why is CONFIG_FHANDLE an option?? Jesper Juhl
2011-06-10 22:39 ` Al Viro
2011-06-10 22:38 ` Jesper Juhl
2011-06-10 22:47 ` Al Viro
2011-06-10 22:42 ` Jesper Juhl
2011-06-10 22:58 ` Al Viro [this message]
2011-06-10 23:10 ` Alexey Dobriyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110610225835.GC11521@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jj@chaosbits.net \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.