io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Langlois <olivier@trillion01.com>
To: Jens Axboe <axboe@kernel.dk>, Dave Chinner <david@fromorbit.com>
Cc: io-uring <io-uring@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [5.15-rc1 regression] io_uring: fsstress hangs in do_coredump() on exit
Date: Thu, 23 Sep 2021 10:05:51 -0400	[thread overview]
Message-ID: <a9f88c7d9b7ac119431a343bda10da251ef7f57e.camel@trillion01.com> (raw)
In-Reply-To: <6d46951b-a7b3-0feb-3af0-aaa8ec87b87a@kernel.dk>

On Tue, 2021-09-21 at 15:41 -0600, Jens Axboe wrote:
> > 
> > Cleaned up so it compiles and the tests run properly again. But
> > playing whack-a-mole with signals seems kinda fragile. I was
> > pointed
> > to this patchset by another dev on #xfs overnight who saw the same
> > hangs that also fixed the hang:
> 
> It seems sane to me - exit if there's a fatal signal, or doing core
> dump. Don't think there should be other conditions.
> 
> > https://lore.kernel.org/lkml/cover.1629655338.git.olivier@trillion0
> > 1.com/
> > 
> > It was posted about a month ago and I don't see any response to it
> > on the lists...
> 
> That's been a long discussion, but it's a different topic really. Yes
> it's signals, but it's not this particular issue. It'll happen to
> work
> around this issue, as it cancels everything post core dumping.
> 
I am glad to see that my patch is still on your radar.

I was starting to wonder if it did somehow slip in a floor crack or if
I did omit to do something justifying that noone is reviewing it.

I guess that everyone has been crazy busy like mad men in the last few
weeks...



      reply	other threads:[~2021-09-23 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  6:40 [5.15-rc1 regression] io_uring: fsstress hangs in do_coredump() on exit Dave Chinner
2021-09-21 13:25 ` Jens Axboe
2021-09-21 14:19   ` Jens Axboe
2021-09-21 21:35     ` Dave Chinner
2021-09-21 21:41       ` Jens Axboe
2021-09-23 14:05         ` Olivier Langlois [this message]

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=a9f88c7d9b7ac119431a343bda10da251ef7f57e.camel@trillion01.com \
    --to=olivier@trillion01.com \
    --cc=axboe@kernel.dk \
    --cc=david@fromorbit.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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).