From: Bart Van Assche <bvanassche@acm.org>
To: 刘喜鑫 <liuxixin@kylinos.cn>, linux-block <linux-block@vger.kernel.org>
Cc: axboe <axboe@kernel.dk>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 回复: Re: [PATCH v1] block/mq-deadline: hold elevator_lock in debugfs next_rq show
Date: Wed, 22 Jul 2026 18:02:47 -0700 [thread overview]
Message-ID: <625c8daa-832f-4b9b-ae9c-446a024493f0@acm.org> (raw)
In-Reply-To: <4gmvbeouu7qb-4gn345cmtdpg@nsmail8.2--kylin--1>
On 7/22/26 5:14 PM, 刘喜鑫 wrote:
> I have verified the patch.
Which patch has been verified? Your patch or my patch?
> yet locking with dd->lock does not take effect.
Is the above statement based on analysis of the source code or on
actual testing? In the latter case, please share the reproducer of the
crash and also the KASAN output triggered by my patch.
Thanks,
Bart.
parent reply other threads:[~2026-07-23 1:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4gmvbeouu7qb-4gn345cmtdpg@nsmail8.2--kylin--1>]
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=625c8daa-832f-4b9b-ae9c-446a024493f0@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxixin@kylinos.cn \
/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