Linux filesystem development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Benjamin LaHaise <bcrl@kvack.org>,
	linux-aio@kvack.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ramji Jiyani <ramjiyani@google.com>,
	Christoph Hellwig <hch@lst.de>, Oleg Nesterov <oleg@redhat.com>,
	Jens Axboe <axboe@kernel.dk>, Martijn Coenen <maco@android.com>,
	Xie Yongji <xieyongji@bytedance.com>
Subject: Re: [GIT PULL] aio poll fixes for 5.16-rc5
Date: Fri, 10 Dec 2021 15:00:36 -0800	[thread overview]
Message-ID: <YbPcFIUFYmEueuXX@sol.localdomain> (raw)
In-Reply-To: <CAHk-=wh5X0iQ7dDY1joBj0eoZ65rbMb4-v0ewirN1teY8VD=8A@mail.gmail.com>

On Fri, Dec 10, 2021 at 02:18:12PM -0800, Linus Torvalds wrote:
> On Fri, Dec 10, 2021 at 10:33 AM Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > This has been tested with the libaio test suite, as well as with test
> > programs I wrote that reproduce the first two bugs.  I am sending this
> > pull request myself as no one seems to be maintaining this code.
> 
> Pulled.
> 
> The "nobody really maintains or cares about epoll/aio" makes me wonder
> if we should just remove the "if EXPERT" from the config options we
> have on them, and start encouraging people to perhaps not even build
> that code any more?
> 
> Because I'm sure we have users of it, but maybe they are few enough
> that saying "don't enable this feature unless you need it" is the
> right thing to do...

Isn't epoll more commonly used than aio?  Either way, removing 'if EXPERT' from
both would make sense, so that they aren't forced on just because someone didn't
set CONFIG_EXPERT.  I think that a lot of people have these options enabled but
don't need them.  Android used to be in that boat for CONFIG_AIO (i.e. it wasn't
needed but was sometimes enabled anyway, maybe due to !CONFIG_EXPERT).
Unfortunately Android has started depending on CONFIG_AIO, so it seems Android
will need to keep it set, but I think most other Linux systems don't need it.

- Eric

  reply	other threads:[~2021-12-10 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 18:32 [GIT PULL] aio poll fixes for 5.16-rc5 Eric Biggers
2021-12-10 22:18 ` Linus Torvalds
2021-12-10 23:00   ` Eric Biggers [this message]
2021-12-11  0:45     ` Theodore Y. Ts'o
2021-12-13  7:23       ` Christoph Hellwig
2021-12-10 22:46 ` pr-tracker-bot

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=YbPcFIUFYmEueuXX@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bcrl@kvack.org \
    --cc=hch@lst.de \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=oleg@redhat.com \
    --cc=ramjiyani@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xieyongji@bytedance.com \
    /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