public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: daejun7.park@samsung.com,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"daehojeong@google.com" <daehojeong@google.com>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Seokhwan Kim <sukka.kim@samsung.com>,
	Dongjin Kim <dongjin_.kim@samsung.com>,
	Yonggil Song <yonggil.song@samsung.com>,
	Jaeyoon Choi <j_yoon.choi@samsung.com>,
	Nayeon Kim <nayeoni.kim@samsung.com>,
	Siwoo Jung <siu.jung@samsung.com>
Subject: Re: (2) [PATCH] f2fs: fix null reference error when checking end of zone
Date: Thu, 4 Jul 2024 17:32:23 +0800	[thread overview]
Message-ID: <5c312ebb-a202-45e5-a82b-7b7c3f080d67@kernel.org> (raw)
In-Reply-To: <20240704075521epcms2p49cc9985b6624e4e1129907e883fbc1d9@epcms2p4>

On 2024/7/4 15:55, Daejun Park wrote:
> Hi Chao Yu,
>>   
>> --------- Original Message ---------
>> Sender : Chao Yu <chao@kernel.org>
>> Date : 2024-07-04 16:16 (GMT+9)
>> Title : Re: [PATCH] f2fs: fix null reference error when checking end of zone
>>   
>> On 2024/7/4 9:01, Daejun Park wrote:
>>> This patch fixes a potentially null pointer being accessed by
>>> is_end_zone_blkaddr() that checks the last block of a zone
>>> when f2fs is mounted as a single device.
>>
>> blkzoned feature depends on multiple device feature? One regular
>> device and one seq-zone device?
> 
> According to mkfs.f2fs, if there are a sufficient number of
> conventional zones, a single zoned device can be used.

Correct.

Anyway, the code looks clean.

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

> 
> Thanks,
> Daejun
> 
>>
>> Thanks,
>>
>>>
>>> Fixes: e067dc3c6b9c ("f2fs: maintain six open zones for zoned devices")
>>> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
>>> ---
>>>    fs/f2fs/data.c 4 +++-
>>>    1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>>> index b6dcb3bcaef7..1aa7eefa659c 100644
>>> --- a/fs/f2fs/data.c
>>> +++ b/fs/f2fs/data.c
>>> @@ -925,6 +925,7 @@ int f2fs_merge_page_bio(struct f2fs_io_info *fio)
>>>    #ifdef CONFIG_BLK_DEV_ZONED
>>>    static bool is_end_zone_blkaddr(struct f2fs_sb_info *sbi, block_t blkaddr)
>>>    {
>>> +        struct block_device *bdev = sbi->sb->s_bdev;
>>>             int devi = 0;
>>>   
>>>             if (f2fs_is_multi_device(sbi)) {
>>> @@ -935,8 +936,9 @@ static bool is_end_zone_blkaddr(struct f2fs_sb_info *sbi, block_t blkaddr)
>>>                             return false;
>>>                     }
>>>                     blkaddr -= FDEV(devi).start_blk;
>>> +                bdev = FDEV(devi).bdev;
>>>             }
>>> -        return bdev_is_zoned(FDEV(devi).bdev) &&
>>> +        return bdev_is_zoned(bdev) &&
>>>                     f2fs_blkz_is_seq(sbi, devi, blkaddr) &&
>>>                     (blkaddr % sbi->blocks_per_blkz == sbi->blocks_per_blkz - 1);
>>>    }

  reply	other threads:[~2024-07-04  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240704010121epcms2p4cff8b25d976d4a1b820ba18f1eb5aa90@epcms2p4>
2024-07-04  1:01 ` [PATCH] f2fs: fix null reference error when checking end of zone Daejun Park
2024-07-04  6:26   ` Markus Elfring
2024-07-04  7:15   ` Chao Yu
2024-07-04  7:55     ` Daejun Park
2024-07-04  9:32       ` Chao Yu [this message]
2024-07-09 22:20     ` [f2fs-dev] " Daeho Jeong
2024-07-15 14:40   ` patchwork-bot+f2fs

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=5c312ebb-a202-45e5-a82b-7b7c3f080d67@kernel.org \
    --to=chao@kernel.org \
    --cc=daehojeong@google.com \
    --cc=daejun7.park@samsung.com \
    --cc=dongjin_.kim@samsung.com \
    --cc=j_yoon.choi@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nayeoni.kim@samsung.com \
    --cc=siu.jung@samsung.com \
    --cc=sukka.kim@samsung.com \
    --cc=yonggil.song@samsung.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