public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: Jens Axboe <axboe@kernel.dk>
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>,
	"Kenneth R. Crudup" <kenny@panix.com>
Subject: Re: Write I/O queue hangup at random on recent Linus' kernels
Date: Sat, 27 Nov 2021 16:11:31 -0800 (PST)	[thread overview]
Message-ID: <b549b4ce-4156-eaab-a146-1fa52f51b642@panix.com> (raw)
In-Reply-To: <a4d728c2-703d-66be-bffd-3bfde0fddf41@kernel.dk>


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.

	-Kenny

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA

  reply	other threads:[~2021-11-28  0:13 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 [this message]
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=b549b4ce-4156-eaab-a146-1fa52f51b642@panix.com \
    --to=kenny@panix.com \
    --cc=axboe@kernel.dk \
    --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