From: Hannes Reinecke <hare@suse.de>
To: Johannes Thumshirn <jthumshirn@suse.de>, Jens Axboe <axboe@fb.com>
Cc: Linux Block Layer Mailinglist <linux-block@vger.kernel.org>,
Linux FSDEVEL Mailinglist <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: bio: ensure newly added bio flags don't override BVEC_POOL_IDX
Date: Wed, 3 Apr 2019 14:03:27 +0200 [thread overview]
Message-ID: <2a5adb69-1df4-ce19-b8c6-518ce1346133@suse.de> (raw)
In-Reply-To: <20190403091519.13376-1-jthumshirn@suse.de>
On 4/3/19 11:15 AM, Johannes Thumshirn wrote:
> With the introduction of BIO_NO_PAGE_REF we've used up all available bits
> in bio::bi_flags.
>
> Convert the defines of the flags to an enum and add a BUILD_BUG_ON() call
> to make sure no-one adds a new one and thus overrides the BVEC_POOL_IDX
> causing crashes.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
>
> ---
> This used to be part of my bio patchset but as it's a) not clear why we
> end up calling bio_put() on the on-stack bio and b) the needed prep patch
> for the fix introduces a regression, I've decided to sent this patch out
> as it's valid on it's own.
>
> I dropped Hannes' and Christoph's R-b though, as the context changed.
> ---
> block/bio.c | 3 +++
> include/linux/blk_types.h | 29 ++++++++++++++++-------------
> 2 files changed, 19 insertions(+), 13 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-04-03 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 9:15 [PATCH] block: bio: ensure newly added bio flags don't override BVEC_POOL_IDX Johannes Thumshirn
2019-04-03 9:57 ` Ming Lei
2019-04-03 12:03 ` Hannes Reinecke [this message]
2019-04-03 15:34 ` Bart Van Assche
2019-04-03 19:50 ` Christoph Hellwig
2019-04-04 15:31 ` Jens Axboe
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=2a5adb69-1df4-ce19-b8c6-518ce1346133@suse.de \
--to=hare@suse.de \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).