From: Liu Song <liusong@linux.alibaba.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: avoid potential infinite loop in __blk_mq_alloc_request
Date: Tue, 9 Aug 2022 18:10:26 +0800 [thread overview]
Message-ID: <90938e46-a865-064c-493f-cf1016161156@linux.alibaba.com> (raw)
In-Reply-To: <YtrLYiJFlqL64voT@infradead.org>
> On Fri, Jul 22, 2022 at 04:15:49PM +0800, Liu Song wrote:
>> It is a reasonable approach to prevent abnormal alloc from going down,
>> but this is a very rare exception after all, and above modification is
>> checked
>> every alloc request, which seems to be a bit excessive overhead.
> Every allocation of a passthrough requests. Which isn't really the
> normal fast path.
Hi,
It is true that there is no possibility of triggering an infinite loop
in the current code,
but the necessary guard code should also exist without adding extra
overhead.
Thanks
prev parent reply other threads:[~2022-08-09 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 5:22 Liu Song
2022-07-22 5:33 ` Christoph Hellwig
2022-07-22 8:15 ` Liu Song
2022-07-22 16:08 ` Christoph Hellwig
2022-08-09 10:10 ` Liu Song [this message]
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=90938e46-a865-064c-493f-cf1016161156@linux.alibaba.com \
--to=liusong@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®