From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org
Subject: Re: [PATCH] f2fs: don't reopen the main block device in f2fs_scan_devices
Date: Tue, 11 Jul 2023 09:17:57 -0700 [thread overview]
Message-ID: <ZK2AtW9hLjqpbaPW@google.com> (raw)
In-Reply-To: <20230711050101.GA19128@lst.de>
On 07/11, Christoph Hellwig wrote:
> I think that's because it doesn't look at sbi->s_ndevs in
> destroy_device_list. Let's try the variant below, which also fixes
> the buildbot warning for non-zoned configfs:
Thanks. At a glance, this looks better. Let me give it a try.
>
> ---
> >From 645d8dceaa97b6ee73be067495b111b15b187498 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Fri, 7 Jul 2023 10:31:49 +0200
> Subject: f2fs: don't reopen the main block device in f2fs_scan_devices
>
> f2fs_scan_devices reopens the main device since the very beginning, which
> has always been useless, and also means that we don't pass the right
> holder for the reopen, which now leads to a warning as the core super.c
> holder ops aren't passed in for the reopen.
>
> Fixes: 3c62be17d4f5 ("f2fs: support multiple devices")
> Fixes: 0718afd47f70 ("block: introduce holder ops")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-flush.c | 2 +-
> fs/f2fs/super.c | 20 ++++++++------------
> 2 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index ca31163da00a55..30883beb750a59 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1561,7 +1561,8 @@ static void destroy_device_list(struct f2fs_sb_info *sbi)
> int i;
>
> for (i = 0; i < sbi->s_ndevs; i++) {
> - blkdev_put(FDEV(i).bdev, sbi->sb->s_type);
> + if (i > 0)
> + blkdev_put(FDEV(i).bdev, sbi->sb->s_type);
> #ifdef CONFIG_BLK_DEV_ZONED
> kvfree(FDEV(i).blkz_seq);
> #endif
> @@ -4190,16 +4191,12 @@ static int f2fs_scan_devices(struct f2fs_sb_info *sbi)
> sbi->aligned_blksize = true;
>
> for (i = 0; i < max_devices; i++) {
> -
> - if (i > 0 && !RDEV(i).path[0])
> + if (i == 0)
> + FDEV(0).bdev = sbi->sb->s_bdev;
> + else if (!RDEV(i).path[0])
> break;
>
> - if (max_devices == 1) {
> - /* Single zoned block device mount */
> - FDEV(0).bdev =
> - blkdev_get_by_dev(sbi->sb->s_bdev->bd_dev, mode,
> - sbi->sb->s_type, NULL);
> - } else {
> + if (max_devices > 1) {
> /* Multi-device mount */
> memcpy(FDEV(i).path, RDEV(i).path, MAX_PATH_LEN);
> FDEV(i).total_segments =
> @@ -4215,10 +4212,9 @@ static int f2fs_scan_devices(struct f2fs_sb_info *sbi)
> FDEV(i).end_blk = FDEV(i).start_blk +
> (FDEV(i).total_segments <<
> sbi->log_blocks_per_seg) - 1;
> + FDEV(i).bdev = blkdev_get_by_path(FDEV(i).path,
> + mode, sbi->sb->s_type, NULL);
> }
> - FDEV(i).bdev = blkdev_get_by_path(FDEV(i).path, mode,
> - sbi->sb->s_type,
> - NULL);
> }
> if (IS_ERR(FDEV(i).bdev))
> return PTR_ERR(FDEV(i).bdev);
> --
> 2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't reopen the main block device in f2fs_scan_devices
Date: Tue, 11 Jul 2023 09:17:57 -0700 [thread overview]
Message-ID: <ZK2AtW9hLjqpbaPW@google.com> (raw)
In-Reply-To: <20230711050101.GA19128@lst.de>
On 07/11, Christoph Hellwig wrote:
> I think that's because it doesn't look at sbi->s_ndevs in
> destroy_device_list. Let's try the variant below, which also fixes
> the buildbot warning for non-zoned configfs:
Thanks. At a glance, this looks better. Let me give it a try.
>
> ---
> >From 645d8dceaa97b6ee73be067495b111b15b187498 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Fri, 7 Jul 2023 10:31:49 +0200
> Subject: f2fs: don't reopen the main block device in f2fs_scan_devices
>
> f2fs_scan_devices reopens the main device since the very beginning, which
> has always been useless, and also means that we don't pass the right
> holder for the reopen, which now leads to a warning as the core super.c
> holder ops aren't passed in for the reopen.
>
> Fixes: 3c62be17d4f5 ("f2fs: support multiple devices")
> Fixes: 0718afd47f70 ("block: introduce holder ops")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-flush.c | 2 +-
> fs/f2fs/super.c | 20 ++++++++------------
> 2 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index ca31163da00a55..30883beb750a59 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1561,7 +1561,8 @@ static void destroy_device_list(struct f2fs_sb_info *sbi)
> int i;
>
> for (i = 0; i < sbi->s_ndevs; i++) {
> - blkdev_put(FDEV(i).bdev, sbi->sb->s_type);
> + if (i > 0)
> + blkdev_put(FDEV(i).bdev, sbi->sb->s_type);
> #ifdef CONFIG_BLK_DEV_ZONED
> kvfree(FDEV(i).blkz_seq);
> #endif
> @@ -4190,16 +4191,12 @@ static int f2fs_scan_devices(struct f2fs_sb_info *sbi)
> sbi->aligned_blksize = true;
>
> for (i = 0; i < max_devices; i++) {
> -
> - if (i > 0 && !RDEV(i).path[0])
> + if (i == 0)
> + FDEV(0).bdev = sbi->sb->s_bdev;
> + else if (!RDEV(i).path[0])
> break;
>
> - if (max_devices == 1) {
> - /* Single zoned block device mount */
> - FDEV(0).bdev =
> - blkdev_get_by_dev(sbi->sb->s_bdev->bd_dev, mode,
> - sbi->sb->s_type, NULL);
> - } else {
> + if (max_devices > 1) {
> /* Multi-device mount */
> memcpy(FDEV(i).path, RDEV(i).path, MAX_PATH_LEN);
> FDEV(i).total_segments =
> @@ -4215,10 +4212,9 @@ static int f2fs_scan_devices(struct f2fs_sb_info *sbi)
> FDEV(i).end_blk = FDEV(i).start_blk +
> (FDEV(i).total_segments <<
> sbi->log_blocks_per_seg) - 1;
> + FDEV(i).bdev = blkdev_get_by_path(FDEV(i).path,
> + mode, sbi->sb->s_type, NULL);
> }
> - FDEV(i).bdev = blkdev_get_by_path(FDEV(i).path, mode,
> - sbi->sb->s_type,
> - NULL);
> }
> if (IS_ERR(FDEV(i).bdev))
> return PTR_ERR(FDEV(i).bdev);
> --
> 2.39.2
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-07-11 16:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 9:40 [PATCH] f2fs: don't reopen the main block device in f2fs_scan_devices Christoph Hellwig
2023-07-07 9:40 ` [f2fs-dev] " Christoph Hellwig
2023-07-10 21:22 ` Jaegeuk Kim
2023-07-10 21:22 ` [f2fs-dev] " Jaegeuk Kim
2023-07-10 23:51 ` Damien Le Moal
2023-07-10 23:51 ` [f2fs-dev] " Damien Le Moal
2023-07-11 1:52 ` Jaegeuk Kim
2023-07-11 1:52 ` [f2fs-dev] " Jaegeuk Kim
2023-07-11 2:00 ` Damien Le Moal
2023-07-11 2:00 ` [f2fs-dev] " Damien Le Moal
2023-07-11 5:01 ` Christoph Hellwig
2023-07-11 5:01 ` [f2fs-dev] " Christoph Hellwig
2023-07-11 6:19 ` Hannes Reinecke
2023-07-11 6:19 ` [f2fs-dev] " Hannes Reinecke
2023-07-11 6:22 ` Christoph Hellwig
2023-07-11 6:22 ` [f2fs-dev] " Christoph Hellwig
2023-07-11 16:17 ` Jaegeuk Kim [this message]
2023-07-11 16:17 ` Jaegeuk Kim
2023-07-17 15:16 ` Chao Yu
2023-07-17 15:16 ` [f2fs-dev] " Chao Yu
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=ZK2AtW9hLjqpbaPW@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.