From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [git pull] vfs.git: poll annotations
Date: Wed, 31 Jan 2018 03:13:00 +0000 [thread overview]
Message-ID: <20180131031300.GE29051@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFz8UL883+rj0nYsU_gtX6jLhriPGncDb1XDteEu817HRQ@mail.gmail.com>
On Tue, Jan 30, 2018 at 06:21:37PM -0800, Linus Torvalds wrote:
> On Tue, Jan 30, 2018 at 10:39 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > Introduces a __bitwise type for POLL... bitmap, propagates
> > the annotations through the tree.
>
> Ok, I'm not entirely happy with this.
>
> I don't think the mangle/demangle_poll() stuff should be in the uapi
> headers, and it really worries me that we use the same names - with
> different values - for the kernel and user versions of the POLLxyz
> macros.
I'm not happy with that either, but the alternative would be to
rename almost every instance of POLL... in the tree. All of them
except for poll.h, actually. And then keep playing whack-a-mole
for resurfacing POLL... in drivers.
Sure, we can do that, but at least let's do that as a single
search-and-replace job in -rc1. Too many conflicts otherwise.
No need to invent KPOLLIN et.al. - we have perfectly usable
EPOLLIN and friends.
A bit of a problem in places like
mask & POLLOUT ? "POLLOUT" : "",
but it's not too terrible. I'll experiment a bit - should be able to
post a script to run.
As for the place for mangle/demangle... where would you prefer them?
next prev parent reply other threads:[~2018-01-31 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:39 [git pull] vfs.git: poll annotations Al Viro
2018-01-31 2:21 ` Linus Torvalds
2018-01-31 3:13 ` Al Viro [this message]
2018-01-31 3:19 ` Linus Torvalds
2018-01-31 4:46 ` Al Viro
2018-01-31 17:50 ` Al Viro
2018-02-01 22:00 ` Al Viro
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=20180131031300.GE29051@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).