From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Bob Peterson <rpeterso@redhat.com>,
"axboe @ kernel . dk" <axboe@kernel.dk>
Cc: "agruenba@redhat.com" <agruenba@redhat.com>,
"cluster-devel@redhat.com" <cluster-devel@redhat.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"hare@suse.de" <hare@suse.de>, "hch@lst.de" <hch@lst.de>,
"jfs-discussion@lists.sourceforge.net"
<jfs-discussion@lists.sourceforge.net>,
"kch@nvidia.com" <kch@nvidia.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"shaggy@kernel.org" <shaggy@kernel.org>,
"snitzer@kernel.org" <snitzer@kernel.org>,
"song@kernel.org" <song@kernel.org>,
"willy@infradead.org" <willy@infradead.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v5 09/20] gfs2: use __bio_add_page for adding single page to bio
Date: Tue, 2 May 2023 11:53:56 +0000 [thread overview]
Message-ID: <a8a8ee20-7783-e955-aef7-edb5a24aa0ae@wdc.com> (raw)
In-Reply-To: <5f3ddda1-2c7d-811c-ffd5-5fc237def2eb@redhat.com>
On 02.05.23 13:51, Bob Peterson wrote:
> On 5/2/23 6:19 AM, Johannes Thumshirn wrote:
>> The GFS2 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.
>>
>> Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>> Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>
>> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>> ---
>> 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 9af9ddb61ca0..cd962985b058 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;
> Hi Johannes,
>
> So...I see 6 different calls to bio_add_page() in gfs2.
> Why change this particular bio_add_page() to __bio_add_page() and not
> the other five?
>
Hi Bob,
Because all the others check the return value of bio_add_page(), only the
one converted doesn't. But it also doesn't need to as we're using
__bio_add_page() on a newly created bio.
next prev parent reply other threads:[~2023-05-02 14:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 10:19 [PATCH v5 00/20] bio: check return values of bio_add_page Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 01/20] swap: use __bio_add_page to add page to bio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 02/20] drbd: " Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 03/20] dm: dm-zoned: use __bio_add_page for adding single metadata page Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 04/20] fs: buffer: use __bio_add_page to add single page to bio Johannes Thumshirn
2023-05-30 5:41 ` gouhao
2023-05-30 6:02 ` gouhao
2023-05-02 10:19 ` [PATCH v5 05/20] md: use __bio_add_page to add single page Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 06/20] md: raid5-log: " Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 07/20] md: raid5: use __bio_add_page to add single page to new bio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 08/20] jfs: logmgr: use __bio_add_page to add single page to bio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 09/20] gfs2: use __bio_add_page for adding " Johannes Thumshirn
2023-05-02 11:51 ` Bob Peterson
2023-05-02 11:53 ` Johannes Thumshirn [this message]
2023-05-02 10:19 ` [PATCH v5 10/20] zonefs: " Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 11/20] zram: " Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 12/20] floppy: " Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 13/20] md: check for failure when adding pages in alloc_behind_master_bio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 14/20] md: raid1: use __bio_add_page for adding single page to bio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 15/20] md: raid1: check if adding pages to resync bio fails Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 16/20] dm-crypt: check if adding pages to clone " Johannes Thumshirn
2023-05-30 15:13 ` [dm-devel] " Mikulas Patocka
2023-05-30 15:49 ` Mike Snitzer
2023-05-30 19:43 ` Mikulas Patocka
2023-05-02 10:19 ` [PATCH v5 17/20] block: mark bio_add_page as __must_check Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 18/20] block: add __bio_add_folio Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 19/20] fs: iomap: use __bio_add_folio where possible Johannes Thumshirn
2023-05-02 10:19 ` [PATCH v5 20/20] block: mark bio_add_folio as __must_check Johannes Thumshirn
2023-05-05 8:09 ` [PATCH v5 00/20] bio: check return values of bio_add_page Johannes Thumshirn
2023-05-05 14:11 ` Jens Axboe
2023-05-24 10:04 ` Johannes Thumshirn
2023-05-24 15:02 ` Jens Axboe
2023-05-26 6:37 ` Johannes Thumshirn
2023-05-30 15:14 ` 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=a8a8ee20-7783-e955-aef7-edb5a24aa0ae@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=cluster-devel@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dm-devel@redhat.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=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