Re: [Cluster-devel] [PATCH v3 17/19] md: raid1: check if adding pages to resync bio fails

2023-04-19 Thread Song Liu
On Wed, Apr 19, 2023 at 7:11 AM Johannes Thumshirn  wrote:
>
> From: Johannes Thumshirn 
>
> Check if adding pages to resync bio fails and if bail out.
>
> As the comment above suggests this cannot happen, WARN if it actually
> happens.
>
> This way we can mark bio_add_pages as __must_check.
>
> Signed-off-by: Johannes Thumshirn 
> Reviewed-by: Damien Le Moal 

Acked-by: Song Liu 

Thanks!



[Cluster-devel] [PATCH v3 10/19] jfs: logmgr: use __bio_add_page to add single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The JFS IO code uses bio_add_page() to add a page to a newly created bio.
bio_add_page() can fail, but the return value is never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
Acked-by: Dave Kleikamp 
---
 fs/jfs/jfs_logmgr.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
index 695415cbfe98..15c645827dec 100644
--- a/fs/jfs/jfs_logmgr.c
+++ b/fs/jfs/jfs_logmgr.c
@@ -1974,7 +1974,7 @@ static int lbmRead(struct jfs_log * log, int pn, struct 
lbuf ** bpp)
 
bio = bio_alloc(log->bdev, 1, REQ_OP_READ, GFP_NOFS);
bio->bi_iter.bi_sector = bp->l_blkno << (log->l2bsize - 9);
-   bio_add_page(bio, bp->l_page, LOGPSIZE, bp->l_offset);
+   __bio_add_page(bio, bp->l_page, LOGPSIZE, bp->l_offset);
BUG_ON(bio->bi_iter.bi_size != LOGPSIZE);
 
bio->bi_end_io = lbmIODone;
@@ -2115,7 +2115,7 @@ static void lbmStartIO(struct lbuf * bp)
 
bio = bio_alloc(log->bdev, 1, REQ_OP_WRITE | REQ_SYNC, GFP_NOFS);
bio->bi_iter.bi_sector = bp->l_blkno << (log->l2bsize - 9);
-   bio_add_page(bio, bp->l_page, LOGPSIZE, bp->l_offset);
+   __bio_add_page(bio, bp->l_page, LOGPSIZE, bp->l_offset);
BUG_ON(bio->bi_iter.bi_size != LOGPSIZE);
 
bio->bi_end_io = lbmIODone;
-- 
2.39.2



[Cluster-devel] [PATCH v3 11/19] gfs: use __bio_add_page for adding single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The GFS superblock reading code uses bio_add_page() to add a page to a
newly created bio. bio_add_page() can fail, but the return value is never
checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 fs/gfs2/ops_fstype.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index 6de901c3b89b..e0cd0d43b12f 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -254,7 +254,7 @@ static int gfs2_read_super(struct gfs2_sbd *sdp, sector_t 
sector, int silent)
 
bio = bio_alloc(sb->s_bdev, 1, REQ_OP_READ | REQ_META, GFP_NOFS);
bio->bi_iter.bi_sector = sector * (sb->s_blocksize >> 9);
-   bio_add_page(bio, page, PAGE_SIZE, 0);
+   __bio_add_page(bio, page, PAGE_SIZE, 0);
 
bio->bi_end_io = end_bio_io_page;
bio->bi_private = page;
-- 
2.39.2



[Cluster-devel] [PATCH v3 13/19] zram: use __bio_add_page for adding single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The zram writeback code uses bio_add_page() to add a page to a newly
created bio. bio_add_page() can fail, but the return value is never
checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/block/zram/zram_drv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index aa490da3cef2..9179bd0f248c 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -760,7 +760,7 @@ static ssize_t writeback_store(struct device *dev,
 REQ_OP_WRITE | REQ_SYNC);
bio.bi_iter.bi_sector = blk_idx * (PAGE_SIZE >> 9);
 
-   bio_add_page(, bvec.bv_page, bvec.bv_len,
+   __bio_add_page(, bvec.bv_page, bvec.bv_len,
bvec.bv_offset);
/*
 * XXX: A single page IO would be inefficient for write
-- 
2.39.2



[Cluster-devel] [PATCH v3 17/19] md: raid1: check if adding pages to resync bio fails

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

Check if adding pages to resync bio fails and if bail out.

As the comment above suggests this cannot happen, WARN if it actually
happens.

This way we can mark bio_add_pages as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/md/raid1-10.c | 11 ++-
 drivers/md/raid10.c   | 20 ++--
 2 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/drivers/md/raid1-10.c b/drivers/md/raid1-10.c
index e61f6cad4e08..cd349e69ed77 100644
--- a/drivers/md/raid1-10.c
+++ b/drivers/md/raid1-10.c
@@ -101,11 +101,12 @@ static void md_bio_reset_resync_pages(struct bio *bio, 
struct resync_pages *rp,
struct page *page = resync_fetch_page(rp, idx);
int len = min_t(int, size, PAGE_SIZE);
 
-   /*
-* won't fail because the vec table is big
-* enough to hold all these pages
-*/
-   bio_add_page(bio, page, len, 0);
+   if (WARN_ON(!bio_add_page(bio, page, len, 0))) {
+   bio->bi_status = BLK_STS_RESOURCE;
+   bio_endio(bio);
+   return;
+   }
+
size -= len;
} while (idx++ < RESYNC_PAGES && size > 0);
 }
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 6c66357f92f5..59e52cf01569 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -3804,11 +3804,11 @@ static sector_t raid10_sync_request(struct mddev 
*mddev, sector_t sector_nr,
for (bio= biolist ; bio ; bio=bio->bi_next) {
struct resync_pages *rp = get_resync_pages(bio);
page = resync_fetch_page(rp, page_idx);
-   /*
-* won't fail because the vec table is big enough
-* to hold all these pages
-*/
-   bio_add_page(bio, page, len, 0);
+   if (WARN_ON(!bio_add_page(bio, page, len, 0))) {
+   bio->bi_status = BLK_STS_RESOURCE;
+   bio_endio(bio);
+   goto giveup;
+   }
}
nr_sectors += len>>9;
sector_nr += len>>9;
@@ -4985,11 +4985,11 @@ static sector_t reshape_request(struct mddev *mddev, 
sector_t sector_nr,
if (len > PAGE_SIZE)
len = PAGE_SIZE;
for (bio = blist; bio ; bio = bio->bi_next) {
-   /*
-* won't fail because the vec table is big enough
-* to hold all these pages
-*/
-   bio_add_page(bio, page, len, 0);
+   if (WARN_ON(!bio_add_page(bio, page, len, 0))) {
+   bio->bi_status = BLK_STS_RESOURCE;
+   bio_endio(bio);
+   return sectors_done;
+   }
}
sector_nr += len >> 9;
nr_sectors += len >> 9;
-- 
2.39.2



[Cluster-devel] [PATCH v3 01/19] swap: use __bio_add_page to add page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The swap 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.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 mm/page_io.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/mm/page_io.c b/mm/page_io.c
index 87b682d18850..684cd3c7b59b 100644
--- a/mm/page_io.c
+++ b/mm/page_io.c
@@ -338,7 +338,7 @@ static void swap_writepage_bdev_sync(struct page *page,
bio_init(, sis->bdev, , 1,
 REQ_OP_WRITE | REQ_SWAP | wbc_to_write_flags(wbc));
bio.bi_iter.bi_sector = swap_page_sector(page);
-   bio_add_page(, page, thp_size(page), 0);
+   __bio_add_page(, page, thp_size(page), 0);
 
bio_associate_blkg_from_page(, page);
count_swpout_vm_event(page);
@@ -360,7 +360,7 @@ static void swap_writepage_bdev_async(struct page *page,
GFP_NOIO);
bio->bi_iter.bi_sector = swap_page_sector(page);
bio->bi_end_io = end_swap_bio_write;
-   bio_add_page(bio, page, thp_size(page), 0);
+   __bio_add_page(bio, page, thp_size(page), 0);
 
bio_associate_blkg_from_page(bio, page);
count_swpout_vm_event(page);
@@ -468,7 +468,7 @@ static void swap_readpage_bdev_sync(struct page *page,
 
bio_init(, sis->bdev, , 1, REQ_OP_READ);
bio.bi_iter.bi_sector = swap_page_sector(page);
-   bio_add_page(, page, thp_size(page), 0);
+   __bio_add_page(, page, thp_size(page), 0);
/*
 * Keep this task valid during swap readpage because the oom killer may
 * attempt to access it in the page fault retry time check.
@@ -488,7 +488,7 @@ static void swap_readpage_bdev_async(struct page *page,
bio = bio_alloc(sis->bdev, 1, REQ_OP_READ, GFP_KERNEL);
bio->bi_iter.bi_sector = swap_page_sector(page);
bio->bi_end_io = end_swap_bio_read;
-   bio_add_page(bio, page, thp_size(page), 0);
+   __bio_add_page(bio, page, thp_size(page), 0);
count_vm_event(PSWPIN);
submit_bio(bio);
 }
-- 
2.39.2



[Cluster-devel] [PATCH v3 04/19] fs: buffer: use __bio_add_page to add single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The buffer_head submission code uses bio_add_page() to add a page to a
newly created bio. bio_add_page() can fail, but the return value is never
checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 fs/buffer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/buffer.c b/fs/buffer.c
index 9e1e2add541e..855dc41fe162 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -2733,7 +2733,7 @@ static void submit_bh_wbc(blk_opf_t opf, struct 
buffer_head *bh,
 
bio->bi_iter.bi_sector = bh->b_blocknr * (bh->b_size >> 9);
 
-   bio_add_page(bio, bh->b_page, bh->b_size, bh_offset(bh));
+   __bio_add_page(bio, bh->b_page, bh->b_size, bh_offset(bh));
BUG_ON(bio->bi_iter.bi_size != bh->b_size);
 
bio->bi_end_io = end_bio_bh_io_sync;
-- 
2.39.2



Re: [Cluster-devel] [PATCH v3 11/19] gfs: use __bio_add_page for adding single page to bio

2023-04-19 Thread Andreas Gruenbacher
On Wed, Apr 19, 2023 at 4:10 PM Johannes Thumshirn  wrote:
>
> From: Johannes Thumshirn 
>
> The GFS superblock reading code uses bio_add_page() to add a page to a
> newly created bio. bio_add_page() can fail, but the return value is never
> checked.

It's GFS2, not GFS, but otherwise this is obviously fine, thanks.

> Use __bio_add_page() as adding a single page to a newly created bio is
> guaranteed to succeed.
>
> This brings us a step closer to marking bio_add_page() as __must_check.
>
> Signed-off-by: Johannes Thumshirn 
> Reviewed-by: Damien Le Moal 

Reviewed-by: Andreas Gruenbacher 

> ---
>  fs/gfs2/ops_fstype.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> index 6de901c3b89b..e0cd0d43b12f 100644
> --- a/fs/gfs2/ops_fstype.c
> +++ b/fs/gfs2/ops_fstype.c
> @@ -254,7 +254,7 @@ static int gfs2_read_super(struct gfs2_sbd *sdp, sector_t 
> sector, int silent)
>
> bio = bio_alloc(sb->s_bdev, 1, REQ_OP_READ | REQ_META, GFP_NOFS);
> bio->bi_iter.bi_sector = sector * (sb->s_blocksize >> 9);
> -   bio_add_page(bio, page, PAGE_SIZE, 0);
> +   __bio_add_page(bio, page, PAGE_SIZE, 0);
>
> bio->bi_end_io = end_bio_io_page;
> bio->bi_private = page;
> --
> 2.39.2
>



[Cluster-devel] [PATCH v3 00/19] bio: check return values of bio_add_page

2023-04-19 Thread Johannes Thumshirn
We have two functions for adding a page to a bio, __bio_add_page() which is
used to add a single page to a freshly created bio and bio_add_page() which is
used to add a page to an existing bio.

While __bio_add_page() is expected to succeed, bio_add_page() can fail.

This series converts the callers of bio_add_page() which can easily use
__bio_add_page() to using it and checks the return of bio_add_page() for
callers that don't work on a freshly created bio.

Lastly it marks bio_add_page() as __must_check so we don't have to go again
and audit all callers.

NOTE: David already applied the two btrfs patches to his tree but I've left
them in the series to make the build bot happy.

Changes to v2:
- Removed 'wont fail' comments pointed out by Song

Changes to v1:
- Removed pointless comment pointed out by Willy
- Changed commit messages pointed out by Damien
- Colledted Damien's Reviews and Acks

Johannes Thumshirn (19):
  swap: use __bio_add_page to add page to bio
  drbd: use __bio_add_page to add page to bio
  dm: dm-zoned: use __bio_add_page for adding single metadata page
  fs: buffer: use __bio_add_page to add single page to bio
  md: use __bio_add_page to add single page
  md: raid5-log: use __bio_add_page to add single page
  md: raid5: use __bio_add_page to add single page to new bio
  btrfs: repair: use __bio_add_page for adding single page
  btrfs: raid56: use __bio_add_page to add single page
  jfs: logmgr: use __bio_add_page to add single page to bio
  gfs: use __bio_add_page for adding single page to bio
  zonefs: use __bio_add_page for adding single page to bio
  zram: use __bio_add_page for adding single page to bio
  floppy: use __bio_add_page for adding single page to bio
  md: check for failure when adding pages in alloc_behind_master_bio
  md: raid1: use __bio_add_page for adding single page to bio
  md: raid1: check if adding pages to resync bio fails
  dm-crypt: check if adding pages to clone bio fails
  block: mark bio_add_page as __must_check

 drivers/block/drbd/drbd_bitmap.c |  4 +---
 drivers/block/floppy.c   |  2 +-
 drivers/block/zram/zram_drv.c|  2 +-
 drivers/md/dm-crypt.c|  9 -
 drivers/md/dm-zoned-metadata.c   |  6 +++---
 drivers/md/md.c  |  4 ++--
 drivers/md/raid1-10.c| 11 ++-
 drivers/md/raid1.c   |  7 +--
 drivers/md/raid10.c  | 20 ++--
 drivers/md/raid5-cache.c |  2 +-
 drivers/md/raid5-ppl.c   |  4 ++--
 fs/btrfs/bio.c   |  2 +-
 fs/btrfs/raid56.c|  2 +-
 fs/buffer.c  |  2 +-
 fs/gfs2/ops_fstype.c |  2 +-
 fs/jfs/jfs_logmgr.c  |  4 ++--
 fs/zonefs/super.c|  2 +-
 include/linux/bio.h  |  2 +-
 mm/page_io.c |  8 
 19 files changed, 52 insertions(+), 43 deletions(-)


base-commit: af67688dca57999fd848f051eeea1d375ba546b2
-- 
2.39.2



[Cluster-devel] [PATCH v3 03/19] dm: dm-zoned: use __bio_add_page for adding single metadata page

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

dm-zoned uses bio_add_page() for adding a single page to a freshly created
metadata bio.

Use __bio_add_page() instead as adding a single page to a new bio is
always guaranteed to succeed.

This brings us a step closer to marking bio_add_page() __must_check

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/md/dm-zoned-metadata.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/md/dm-zoned-metadata.c b/drivers/md/dm-zoned-metadata.c
index cf9402064aba..8dbe102ab271 100644
--- a/drivers/md/dm-zoned-metadata.c
+++ b/drivers/md/dm-zoned-metadata.c
@@ -577,7 +577,7 @@ static struct dmz_mblock *dmz_get_mblock_slow(struct 
dmz_metadata *zmd,
bio->bi_iter.bi_sector = dmz_blk2sect(block);
bio->bi_private = mblk;
bio->bi_end_io = dmz_mblock_bio_end_io;
-   bio_add_page(bio, mblk->page, DMZ_BLOCK_SIZE, 0);
+   __bio_add_page(bio, mblk->page, DMZ_BLOCK_SIZE, 0);
submit_bio(bio);
 
return mblk;
@@ -728,7 +728,7 @@ static int dmz_write_mblock(struct dmz_metadata *zmd, 
struct dmz_mblock *mblk,
bio->bi_iter.bi_sector = dmz_blk2sect(block);
bio->bi_private = mblk;
bio->bi_end_io = dmz_mblock_bio_end_io;
-   bio_add_page(bio, mblk->page, DMZ_BLOCK_SIZE, 0);
+   __bio_add_page(bio, mblk->page, DMZ_BLOCK_SIZE, 0);
submit_bio(bio);
 
return 0;
@@ -752,7 +752,7 @@ static int dmz_rdwr_block(struct dmz_dev *dev, enum req_op 
op,
bio = bio_alloc(dev->bdev, 1, op | REQ_SYNC | REQ_META | REQ_PRIO,
GFP_NOIO);
bio->bi_iter.bi_sector = dmz_blk2sect(block);
-   bio_add_page(bio, page, DMZ_BLOCK_SIZE, 0);
+   __bio_add_page(bio, page, DMZ_BLOCK_SIZE, 0);
ret = submit_bio_wait(bio);
bio_put(bio);
 
-- 
2.39.2



[Cluster-devel] [PATCH v3 16/19] md: raid1: use __bio_add_page for adding single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The sync request code uses bio_add_page() to add a page to a newly created bio.
bio_add_page() can fail, but the return value is never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
Acked-by: Song Liu 
---
 drivers/md/raid1.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
index 8283ef177f6c..ff89839455ec 100644
--- a/drivers/md/raid1.c
+++ b/drivers/md/raid1.c
@@ -2917,7 +2917,7 @@ static sector_t raid1_sync_request(struct mddev *mddev, 
sector_t sector_nr,
 * won't fail because the vec table is big
 * enough to hold all these pages
 */
-   bio_add_page(bio, page, len, 0);
+   __bio_add_page(bio, page, len, 0);
}
}
nr_sectors += len>>9;
-- 
2.39.2



[Cluster-devel] [PATCH v3 18/19] dm-crypt: check if adding pages to clone bio fails

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

Check if adding pages to clone bio fails and if it does retry with
reclaim. This mirrors the behaviour of page allocation in
crypt_alloc_buffer().

This way we can mark bio_add_pages as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/md/dm-crypt.c | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index 3ba53dc3cc3f..19f7e087c6df 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -1693,7 +1693,14 @@ static struct bio *crypt_alloc_buffer(struct dm_crypt_io 
*io, unsigned int size)
 
len = (remaining_size > PAGE_SIZE) ? PAGE_SIZE : remaining_size;
 
-   bio_add_page(clone, page, len, 0);
+   if (!bio_add_page(clone, page, len, 0)) {
+   mempool_free(page, >page_pool);
+   crypt_free_buffer_pages(cc, clone);
+   bio_put(clone);
+   gfp_mask |= __GFP_DIRECT_RECLAIM;
+   goto retry;
+
+   }
 
remaining_size -= len;
}
-- 
2.39.2



[Cluster-devel] [PATCH v3 07/19] md: raid5: use __bio_add_page to add single page to new bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The raid5-ppl submission code uses bio_add_page() to add a page to a
newly created bio. bio_add_page() can fail, but the return value is never
checked. For adding consecutive pages, the return is actually checked and
a new bio is allocated if adding the page fails.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
Acked-by: Song Liu 
---
 drivers/md/raid5-ppl.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/md/raid5-ppl.c b/drivers/md/raid5-ppl.c
index e495939bb3e0..eaea57aee602 100644
--- a/drivers/md/raid5-ppl.c
+++ b/drivers/md/raid5-ppl.c
@@ -465,7 +465,7 @@ static void ppl_submit_iounit(struct ppl_io_unit *io)
 
bio->bi_end_io = ppl_log_endio;
bio->bi_iter.bi_sector = log->next_io_sector;
-   bio_add_page(bio, io->header_page, PAGE_SIZE, 0);
+   __bio_add_page(bio, io->header_page, PAGE_SIZE, 0);
 
pr_debug("%s: log->current_io_sector: %llu\n", __func__,
(unsigned long long)log->next_io_sector);
@@ -496,7 +496,7 @@ static void ppl_submit_iounit(struct ppl_io_unit *io)
   prev->bi_opf, GFP_NOIO,
   _conf->bs);
bio->bi_iter.bi_sector = bio_end_sector(prev);
-   bio_add_page(bio, sh->ppl_page, PAGE_SIZE, 0);
+   __bio_add_page(bio, sh->ppl_page, PAGE_SIZE, 0);
 
bio_chain(bio, prev);
ppl_submit_iounit_bio(io, prev);
-- 
2.39.2



[Cluster-devel] [PATCH v3 08/19] btrfs: repair: use __bio_add_page for adding single page

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The btrfs repair bio submission code uses bio_add_page() to add a page to
a newly created bio. bio_add_page() can fail, but the return value is
never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 fs/btrfs/bio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/btrfs/bio.c b/fs/btrfs/bio.c
index 726592868e9c..73220a219c91 100644
--- a/fs/btrfs/bio.c
+++ b/fs/btrfs/bio.c
@@ -224,7 +224,7 @@ static struct btrfs_failed_bio *repair_one_sector(struct 
btrfs_bio *failed_bbio,
repair_bio = bio_alloc_bioset(NULL, 1, REQ_OP_READ, GFP_NOFS,
  _repair_bioset);
repair_bio->bi_iter.bi_sector = failed_bbio->saved_iter.bi_sector;
-   bio_add_page(repair_bio, bv->bv_page, bv->bv_len, bv->bv_offset);
+   __bio_add_page(repair_bio, bv->bv_page, bv->bv_len, bv->bv_offset);
 
repair_bbio = btrfs_bio(repair_bio);
btrfs_bio_init(repair_bbio, failed_bbio->inode, NULL, fbio);
-- 
2.39.2



[Cluster-devel] [PATCH v3 09/19] btrfs: raid56: use __bio_add_page to add single page

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The btrfs raid58 sector submission code uses bio_add_page() to add a page
to a newly created bio. bio_add_page() can fail, but the return value is
never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 fs/btrfs/raid56.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
index 642828c1b299..c8173e003df6 100644
--- a/fs/btrfs/raid56.c
+++ b/fs/btrfs/raid56.c
@@ -1108,7 +1108,7 @@ static int rbio_add_io_sector(struct btrfs_raid_bio *rbio,
bio->bi_iter.bi_sector = disk_start >> 9;
bio->bi_private = rbio;
 
-   bio_add_page(bio, sector->page, sectorsize, sector->pgoff);
+   __bio_add_page(bio, sector->page, sectorsize, sector->pgoff);
bio_list_add(bio_list, bio);
return 0;
 }
-- 
2.39.2



[Cluster-devel] [PATCH v3 19/19] block: mark bio_add_page as __must_check

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

Now that all users of bio_add_page check for the return value, mark
bio_add_page as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 include/linux/bio.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/bio.h b/include/linux/bio.h
index d766be7152e1..0f8a8d7a6384 100644
--- a/include/linux/bio.h
+++ b/include/linux/bio.h
@@ -465,7 +465,7 @@ extern void bio_uninit(struct bio *);
 void bio_reset(struct bio *bio, struct block_device *bdev, blk_opf_t opf);
 void bio_chain(struct bio *, struct bio *);
 
-int bio_add_page(struct bio *, struct page *, unsigned len, unsigned off);
+int __must_check bio_add_page(struct bio *, struct page *, unsigned len, 
unsigned off);
 bool bio_add_folio(struct bio *, struct folio *, size_t len, size_t off);
 extern int bio_add_pc_page(struct request_queue *, struct bio *, struct page *,
   unsigned int, unsigned int);
-- 
2.39.2



[Cluster-devel] [PATCH v3 05/19] md: use __bio_add_page to add single page

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The md-raid superblock writing code uses bio_add_page() to add a page to a
newly created bio. bio_add_page() can fail, but the return value is never
checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-of_-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
Acked-by: Song Liu 
---
 drivers/md/md.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/md/md.c b/drivers/md/md.c
index 13321dbb5fbc..20b9cd7c2f39 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -958,7 +958,7 @@ void md_super_write(struct mddev *mddev, struct md_rdev 
*rdev,
atomic_inc(>nr_pending);
 
bio->bi_iter.bi_sector = sector;
-   bio_add_page(bio, page, size, 0);
+   __bio_add_page(bio, page, size, 0);
bio->bi_private = rdev;
bio->bi_end_io = super_written;
 
@@ -999,7 +999,7 @@ int sync_page_io(struct md_rdev *rdev, sector_t sector, int 
size,
bio.bi_iter.bi_sector = sector + rdev->new_data_offset;
else
bio.bi_iter.bi_sector = sector + rdev->data_offset;
-   bio_add_page(, page, size, 0);
+   __bio_add_page(, page, size, 0);
 
submit_bio_wait();
 
-- 
2.39.2



[Cluster-devel] [PATCH v3 02/19] drbd: use __bio_add_page to add page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

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.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 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 289876ffbc31..050154eb963d 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,
_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.39.2



[Cluster-devel] [PATCH v3 06/19] md: raid5-log: use __bio_add_page to add single page

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The raid5 log metadata submission code uses bio_add_page() to add a page
to a newly created bio. bio_add_page() can fail, but the return value is
never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
Acked-by: Song Liu 
---
 drivers/md/raid5-cache.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
index 46182b955aef..852b265c5db4 100644
--- a/drivers/md/raid5-cache.c
+++ b/drivers/md/raid5-cache.c
@@ -792,7 +792,7 @@ static struct r5l_io_unit *r5l_new_meta(struct r5l_log *log)
io->current_bio = r5l_bio_alloc(log);
io->current_bio->bi_end_io = r5l_log_endio;
io->current_bio->bi_private = io;
-   bio_add_page(io->current_bio, io->meta_page, PAGE_SIZE, 0);
+   __bio_add_page(io->current_bio, io->meta_page, PAGE_SIZE, 0);
 
r5_reserve_log_entry(log, io);
 
-- 
2.39.2



[Cluster-devel] [PATCH v3 15/19] md: check for failure when adding pages in alloc_behind_master_bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

alloc_behind_master_bio() can possibly add multiple pages to a bio, but it
is not checking for the return value of bio_add_page() if adding really
succeeded.

Check if the page adding succeeded and if not bail out.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/md/raid1.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
index 68a9e2d9985b..8283ef177f6c 100644
--- a/drivers/md/raid1.c
+++ b/drivers/md/raid1.c
@@ -1147,7 +1147,10 @@ static void alloc_behind_master_bio(struct r1bio *r1_bio,
if (unlikely(!page))
goto free_pages;
 
-   bio_add_page(behind_bio, page, len, 0);
+   if (!bio_add_page(behind_bio, page, len, 0)) {
+   free_page(page);
+   goto free_pages;
+   }
 
size -= len;
i++;
-- 
2.39.2



[Cluster-devel] [PATCH v3 12/19] zonefs: use __bio_add_page for adding single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The zonefs superblock reading code uses bio_add_page() to add a page to a
newly created bio. bio_add_page() can fail, but the return value is
never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Acked-by: Damien Le Moal 
---
 fs/zonefs/super.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
index 23b8b299c64e..9350221abfc5 100644
--- a/fs/zonefs/super.c
+++ b/fs/zonefs/super.c
@@ -1128,7 +1128,7 @@ static int zonefs_read_super(struct super_block *sb)
 
bio_init(, sb->s_bdev, _vec, 1, REQ_OP_READ);
bio.bi_iter.bi_sector = 0;
-   bio_add_page(, page, PAGE_SIZE, 0);
+   __bio_add_page(, page, PAGE_SIZE, 0);
 
ret = submit_bio_wait();
if (ret)
-- 
2.39.2



Re: [Cluster-devel] [PATCH v3 19/19] block: mark bio_add_page as __must_check

2023-04-19 Thread Johannes Thumshirn

On 19/04/2023 16:19, Matthew Wilcox wrote:

On Wed, Apr 19, 2023 at 04:09:29PM +0200, Johannes Thumshirn wrote:

Now that all users of bio_add_page check for the return value, mark
bio_add_page as __must_check.


Should probably add __must_check to bio_add_folio too?  If this is
really the way you want to go ... means we also need a
__bio_add_folio().


I admit I haven't thought of folios, mea culpa.

3 of the callers of bio_add_folio() don't check the return value:
$ git grep -E '\sbio_add_folio\b'
fs/iomap/buffered-io.c: bio_add_folio(ctx->bio, folio, plen, poff);
fs/iomap/buffered-io.c: bio_add_folio(, folio, plen, poff);
fs/iomap/buffered-io.c: bio_add_folio(wpc->ioend->io_bio, folio, 
len, poff);


But from a quick look they look OK to me.

Does that look reasonable to you:

diff --git a/block/bio.c b/block/bio.c
index fd11614bba4d..f3a3524b53e4 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -1138,6 +1138,14 @@ int bio_add_page(struct bio *bio, struct page *page,
 }
 EXPORT_SYMBOL(bio_add_page);

+void __bio_add_folio(struct bio *bio, struct folio *folio, size_t len,
+size_t off)
+{
+   WARN_ON_ONCE(len > UINT_MAX);
+   WARN_ON_ONCE(off > UINT_MAX);
+   __bio_add_page(bio, >page, len, off);
+}
+
 /**
  * bio_add_folio - Attempt to add part of a folio to a bio.
  * @bio: BIO to add to.


Byte,
Johannes



Re: [Cluster-devel] [PATCH v3 19/19] block: mark bio_add_page as __must_check

2023-04-19 Thread Matthew Wilcox
On Wed, Apr 19, 2023 at 04:09:29PM +0200, Johannes Thumshirn wrote:
> Now that all users of bio_add_page check for the return value, mark
> bio_add_page as __must_check.

Should probably add __must_check to bio_add_folio too?  If this is
really the way you want to go ... means we also need a
__bio_add_folio().



[Cluster-devel] [PATCH v3 14/19] floppy: use __bio_add_page for adding single page to bio

2023-04-19 Thread Johannes Thumshirn
From: Johannes Thumshirn 

The floppy code uses bio_add_page() to add a page to a newly created bio.
bio_add_page() can fail, but the return value is never checked.

Use __bio_add_page() as adding a single page to a newly created bio is
guaranteed to succeed.

This brings us a step closer to marking bio_add_page() as __must_check.

Signed-off-by: Johannes Thumshirn 
Reviewed-by: Damien Le Moal 
---
 drivers/block/floppy.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c
index 487840e3564d..6f46a30f7c36 100644
--- a/drivers/block/floppy.c
+++ b/drivers/block/floppy.c
@@ -4147,7 +4147,7 @@ static int __floppy_read_block_0(struct block_device 
*bdev, int drive)
cbdata.drive = drive;
 
bio_init(, bdev, _vec, 1, REQ_OP_READ);
-   bio_add_page(, page, block_size(bdev), 0);
+   __bio_add_page(, page, block_size(bdev), 0);
 
bio.bi_iter.bi_sector = 0;
bio.bi_flags |= (1 << BIO_QUIET);
-- 
2.39.2