From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Chaitanya Kulkarni <kch@nvidia.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, dm-devel@redhat.com,
Song Liu <song@kernel.org>,
linux-raid@vger.kernel.org, Mike Snitzer <snitzer@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Dave Kleikamp <shaggy@kernel.org>,
jfs-discussion@lists.sourceforge.net, cluster-devel@redhat.com,
Bob Peterson <rpeterso@redhat.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
gouha7@uniontech.com,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: [PATCH v7 02/20] drbd: use __bio_add_page to add page to bio
Date: Wed, 31 May 2023 04:50:25 -0700 [thread overview]
Message-ID: <435007afac14f3766455559059d21843771fae53.1685532726.git.johannes.thumshirn@wdc.com> (raw)
In-Reply-To: <cover.1685532726.git.johannes.thumshirn@wdc.com>
The drbd code only adds a single page to a newly created bio. So use
__bio_add_page() to add the page which is guaranteed to succeed in this
case.
This brings us closer to marking bio_add_page() as __must_check.
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
---
drivers/block/drbd/drbd_bitmap.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/drbd/drbd_bitmap.c b/drivers/block/drbd/drbd_bitmap.c
index 6ac8c54b44c7..85ca000a0564 100644
--- a/drivers/block/drbd/drbd_bitmap.c
+++ b/drivers/block/drbd/drbd_bitmap.c
@@ -1043,9 +1043,7 @@ static void bm_page_io_async(struct drbd_bm_aio_ctx *ctx, int page_nr) __must_ho
bio = bio_alloc_bioset(device->ldev->md_bdev, 1, op, GFP_NOIO,
&drbd_md_io_bio_set);
bio->bi_iter.bi_sector = on_disk_sector;
- /* bio_add_page of a single page to an empty bio will always succeed,
- * according to api. Do we want to assert that? */
- bio_add_page(bio, page, len, 0);
+ __bio_add_page(bio, page, len, 0);
bio->bi_private = ctx;
bio->bi_end_io = drbd_bm_endio;
--
2.40.1
next prev parent reply other threads:[~2023-05-31 11:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:50 [PATCH v7 00/20] bio: check return values of bio_add_page Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 01/20] swap: use __bio_add_page to add page to bio Johannes Thumshirn
2023-05-31 11:50 ` Johannes Thumshirn [this message]
2023-05-31 11:50 ` [PATCH v7 03/20] dm: dm-zoned: use __bio_add_page for adding single metadata page Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 04/20] fs: buffer: use __bio_add_page to add single page to bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 05/20] md: use __bio_add_page to add single page Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 06/20] md: raid5-log: " Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 07/20] md: raid5: use __bio_add_page to add single page to new bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 08/20] jfs: logmgr: use __bio_add_page to add single page to bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 09/20] gfs2: use __bio_add_page for adding " Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 10/20] zonefs: " Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 11/20] zram: " Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 12/20] floppy: " Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 13/20] md: check for failure when adding pages in alloc_behind_master_bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 14/20] md: raid1: use __bio_add_page for adding single page to bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 15/20] md: raid1: check if adding pages to resync bio fails Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 16/20] dm-crypt: use __bio_add_page to add single page to clone bio Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 17/20] block: mark bio_add_page as __must_check Johannes Thumshirn
2023-05-31 12:32 ` Christoph Hellwig
2023-05-31 11:50 ` [PATCH v7 18/20] block: add bio_add_folio_nofail Johannes Thumshirn
2023-05-31 12:32 ` Christoph Hellwig
2023-05-31 11:50 ` [PATCH v7 19/20] fs: iomap: use bio_add_folio_nofail where possible Johannes Thumshirn
2023-05-31 11:50 ` [PATCH v7 20/20] block: mark bio_add_folio as __must_check Johannes Thumshirn
2023-05-31 12:34 ` Christoph Hellwig
2023-05-31 15:50 ` [PATCH v7 00/20] bio: check return values of bio_add_page 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=435007afac14f3766455559059d21843771fae53.1685532726.git.johannes.thumshirn@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=cluster-devel@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=gouha7@uniontech.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=rpeterso@redhat.com \
--cc=shaggy@kernel.org \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=willy@infradead.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).