From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: reject zero length in bio_add_page()
Date: Mon, 16 Mar 2026 09:29:52 -0700 [thread overview]
Message-ID: <abgwAPMckUrmsnUx@infradead.org> (raw)
In-Reply-To: <f3db373bad065ae6251892acd15993f5dd56dfe1.1773368732.git.wqu@suse.com>
I'm a bit worried about adding more an more checks, but this seems like
an actually useful one.
On Fri, Mar 13, 2026 at 12:55:55PM +1030, Qu Wenruo wrote:
> [BUG]
However this [TAG] style commit message is a bit weird. Can you
rewrite it like a normal kernel commit message?
next prev parent reply other threads:[~2026-03-16 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 2:25 [PATCH] block: reject zero length in bio_add_page() Qu Wenruo
2026-03-16 16:29 ` Christoph Hellwig [this message]
2026-03-16 20:44 ` Qu Wenruo
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=abgwAPMckUrmsnUx@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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