From: Keith Busch <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Andrew Marshall <[email protected]>,
[email protected]
Subject: Re: PROBLEM: io_uring hang causing uninterruptible sleep state on 6.6.59
Date: Sun, 3 Nov 2024 17:01:48 -0700 [thread overview]
Message-ID: <ZygO7O1Pm5lYbNkP@kbusch-mbp> (raw)
In-Reply-To: <[email protected]>
On Sun, Nov 03, 2024 at 04:53:27PM -0700, Jens Axboe wrote:
> On 11/3/24 4:47 PM, Andrew Marshall wrote:
> > I identified f4ce3b5d26ce149e77e6b8e8f2058aa80e5b034e as the likely
> > problematic commit simply by browsing git log. As indicated above;
> > reverting that atop 6.6.59 results in success. Since it is passing on
> > 6.11.6, I suspect there is some missing backport to 6.6.x, or some
> > other semantic merge conflict. Unfortunately I do not have a compact,
> > minimal reproducer, but can provide my large one (it is testing a
> > larger build process in a VM) if needed?there are some additional
> > details in the above-linked downstream bug report, though. I hope that
> > having identified the problematic commit is enough for someone with
> > more context to go off of. Happy to provide more information if
> > needed.
>
> Don't worry about not having a reproducer, having the backport commit
> pin pointed will do just fine. I'll take a look at this.
I think stable is missing:
6b231248e97fc3 ("io_uring: consolidate overflow flushing")
next prev parent reply other threads:[~2024-11-04 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 23:47 PROBLEM: io_uring hang causing uninterruptible sleep state on 6.6.59 Andrew Marshall
2024-11-03 23:53 ` Jens Axboe
2024-11-03 23:58 ` Jens Axboe
2024-11-04 0:01 ` Keith Busch [this message]
2024-11-04 0:06 ` Jens Axboe
2024-11-04 2:38 ` Stable backport (was "Re: PROBLEM: io_uring hang causing uninterruptible sleep state on 6.6.59") Jens Axboe
2024-11-04 4:25 ` Andrew Marshall
2024-11-04 13:17 ` Andrew Marshall
2024-11-04 15:58 ` Jens Axboe
2024-11-06 6:05 ` Greg Kroah-Hartman
2024-11-06 14:11 ` Jens Axboe
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=ZygO7O1Pm5lYbNkP@kbusch-mbp \
[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