public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
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: Sun, 28 Nov 2021 07:50:36 -0700	[thread overview]
Message-ID: <838c86fa-bb3d-6794-64fd-35b81c62bbb6@kernel.dk> (raw)
In-Reply-To: <b549b4ce-4156-eaab-a146-1fa52f51b642@panix.com>

On 11/27/21 5:11 PM, Kenneth R. Crudup wrote:
> 
> On Fri, 26 Nov 2021, Jens Axboe wrote:
> 
>>>> That said, I'm pretty confident in the fix,
> 
> Moot point kinda, as I see the fix in Linus' master, but yeah, it's
> working here.

Thanks for testing! I had a high level of confidence in that fix, and
wanted to flush it out before -rc3. But testing is always appreciated,
and thanks for the initial report as well.

-- 
Jens Axboe



  reply	other threads:[~2021-11-28 14:50 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
2021-11-28  0:11                 ` Kenneth R. Crudup
2021-11-28 14:50                   ` Jens Axboe [this message]
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=838c86fa-bb3d-6794-64fd-35b81c62bbb6@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