From: Chengming Zhou <zhouchengming@bytedance.com>
To: Christoph Hellwig <hch@lst.de>, Chuck Lever III <chuck.lever@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>, Chuck Lever <cel@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH RFC] block: Revert 615939a2ae73
Date: Thu, 10 Aug 2023 11:42:50 +0800 [thread overview]
Message-ID: <86ce2299-ce42-c0bb-e577-9d23f8af494c@bytedance.com> (raw)
In-Reply-To: <20230809214913.GA9902@lst.de>
On 2023/8/10 05:49, Christoph Hellwig wrote:
> Oh well. I don't feel like we're going to find the root cause
> given that its late in the merge window and I'm running out of
> time I have to work due to the annual summer vacation. Unless
> someone like Chengming who knows the flush code pretty well
> feels like working with chuck on a few more iterations we'll
Hi,
No problem, I can work with Chuck to find the root cause if Chuck
has time too, since I still can't reproduce it by myself.
Maybe we should first find what's the status of the hang request?
I can write a Drgn script to find if any request hang in the queue.
Christoph, it would be very helpful if you share some thoughts
and directions.
> have to revert it. Which is going to be a very painful merge
> with Chengming's work in the for-6.6 branch.
>
Maybe we can revert it manually if we still fail since that commit
just let postflushes go to the normal I/O path, instead of going to
the flush state machine.
So I think it should be fine if we just delete that case?
Chuck, could you please help to check this change on block/for-next?
Thanks!
diff --git a/block/blk-flush.c b/block/blk-flush.c
index e73dc22d05c1..7ea3c00f40ce 100644
--- a/block/blk-flush.c
+++ b/block/blk-flush.c
@@ -442,17 +442,6 @@ bool blk_insert_flush(struct request *rq)
* Queue for normal execution.
*/
return false;
- case REQ_FSEQ_DATA | REQ_FSEQ_POSTFLUSH:
- /*
- * Initialize the flush fields and completion handler to trigger
- * the post flush, and then just pass the command on.
- */
- blk_rq_init_flush(rq);
- rq->flush.seq |= REQ_FSEQ_PREFLUSH;
- spin_lock_irq(&fq->mq_flush_lock);
- fq->flush_data_in_flight++;
- spin_unlock_irq(&fq->mq_flush_lock);
- return false;
default:
/*
* Mark the request as part of a flush sequence and submit it
next prev parent reply other threads:[~2023-08-10 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:08 [PATCH RFC] block: Revert 615939a2ae73 Chuck Lever
2023-08-09 15:51 ` Jens Axboe
2023-08-09 16:11 ` Christoph Hellwig
2023-08-09 16:26 ` Chuck Lever III
2023-08-09 21:49 ` Christoph Hellwig
2023-08-10 3:42 ` Chengming Zhou [this message]
2023-08-10 13:47 ` Chuck Lever III
2023-08-10 15:58 ` Christoph Hellwig
2023-08-10 16:02 ` Chuck Lever
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=86ce2299-ce42-c0bb-e577-9d23f8af494c@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=axboe@kernel.dk \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=linux-block@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