From: Jens Axboe <axboe@kernel.dk>
To: "Kenneth R. Crudup" <kenny@panix.com>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-nvme@lists.infradead.org,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: Write I/O queue hangup at random on recent Linus' kernels
Date: Fri, 26 Nov 2021 11:41:22 -0700 [thread overview]
Message-ID: <a4d728c2-703d-66be-bffd-3bfde0fddf41@kernel.dk> (raw)
In-Reply-To: <1ff86d55-f39d-f88b-b8d-b6dfbd2f1b19@panix.com>
On 11/26/21 11:20 AM, Kenneth R. Crudup wrote:
>
> On Fri, 26 Nov 2021, Jens Axboe wrote:
>
>> I'd just do what you usually do, that's usually the best way to gain
>> confidence in the fix.
> ...
>> That said, I'm pretty confident in the fix,
>
> OK, then I'll just continue my normal workflow.
Sounds good.
> ... but am I the first report of this you've seen? (I sometimes wonder how many
> people use the master branch as a daily driver; an -rc went out a couple of
> weeks ago that had a commit that broke suspend that manifested right away.)
https://lore.kernel.org/linux-block/20211126095352.bkbrvtgfcmfj3wkj@shindev/
There's another here from today. But this particular window has a pretty
narrow window, which often means that most people won't hit it, while the
people that do hit it all the time...
--
Jens Axboe
next prev parent reply other threads:[~2021-11-26 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 21:05 Write I/O queue hangup at random on recent Linus' kernels Kenneth R. Crudup
2021-11-23 23:23 ` Kenneth R. Crudup
2021-11-23 23:27 ` Jens Axboe
2021-11-23 23:35 ` Kenneth R. Crudup
2021-11-25 21:05 ` Kenneth R. Crudup
2021-11-25 21:07 ` Jens Axboe
2021-11-25 21:11 ` Kenneth R. Crudup
2021-11-26 16:53 ` Jens Axboe
2021-11-26 17:09 ` Kenneth R. Crudup
2021-11-26 17:58 ` Kenneth R. Crudup
2021-11-26 18:10 ` Jens Axboe
2021-11-26 18:20 ` Kenneth R. Crudup
2021-11-26 18:41 ` Jens Axboe [this message]
2021-11-28 0:11 ` Kenneth R. Crudup
2021-11-28 14:50 ` Jens Axboe
2021-12-02 15:13 ` Kenneth R. Crudup
2021-12-02 15:37 ` Kenneth R. Crudup
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=a4d728c2-703d-66be-bffd-3bfde0fddf41@kernel.dk \
--to=axboe@kernel.dk \
--cc=kenny@panix.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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