From: Linus Torvalds <[email protected]>
To: Jens Axboe <[email protected]>,
"Eric W. Biederman" <[email protected]>,
Oleg Nesterov <[email protected]>,
Al Viro <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring fixes for 5.15-rc3
Date: Sat, 25 Sep 2021 16:05:07 -0700 [thread overview]
Message-ID: <CAHk-=whi3UxvY1C1LQNCO9d2xzX5A69qfzNGbBVGpRE_6gv=9Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Sat, Sep 25, 2021 at 1:32 PM Jens Axboe <[email protected]> wrote:
>
> - io-wq core dump exit fix (me)
Hmm.
That one strikes me as odd.
I get the feeling that if the io_uring thread needs to have that
signal_group_exit() test, something is wrong in signal-land.
It's basically a "fatal signal has been sent to another thread", and I
really get the feeling that "fatal_signal_pending()" should just be
modified to handle that case too.
Because what about a number of other situations where we have that
"killable" logic (ie "stop waiting for locks or IO if you're just
going to get killed anyway" - things like lock_page_killable() and
friends)
Adding Eric, Oleg and Al to the participants, so that somebody else can pipe up.
That piping up may quite possibly be to just tell me I'm being stupid,
and that this is just a result of some io_uring thread thing, and
nobody else has this problem.
It's commit 87c169665578 ("io-wq: ensure we exit if thread group is
exiting") in my tree.
Comments?
Linus
next prev parent reply other threads:[~2021-09-25 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 20:32 [GIT PULL] io_uring fixes for 5.15-rc3 Jens Axboe
2021-09-25 23:05 ` Linus Torvalds [this message]
2021-09-26 1:20 ` Jens Axboe
2021-09-27 13:51 ` Eric W. Biederman
2021-09-27 14:29 ` Jens Axboe
2021-09-27 14:59 ` Jens Axboe
2021-09-27 15:13 ` Eric W. Biederman
2021-09-27 15:41 ` Jens Axboe
2021-09-27 15:52 ` Eric W. Biederman
2021-09-27 16:03 ` Jens Axboe
2021-09-26 4:31 ` Eric W. Biederman
2021-09-25 23:05 ` 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='CAHk-=whi3UxvY1C1LQNCO9d2xzX5A69qfzNGbBVGpRE_6gv=9Q@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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