All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Pankaj Raghav <p.raghav@samsung.com>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: javier.gonz@samsung.com, Damien.LeMoal@wdc.com,
	mcgrof@kernel.org, pankydev8@gmail.com
Subject: Re: [f2fs-dev] [PATCH v2] libf2fs: don't allow mkfs / fsck on non power-of-2 zoned devices
Date: Wed, 20 Apr 2022 18:45:15 +0800	[thread overview]
Message-ID: <8b1c2c4e-4769-67d1-42b9-42d2d1d0871d@kernel.org> (raw)
In-Reply-To: <20220413122940.133981-1-p.raghav@samsung.com>

On 2022/4/13 20:29, Pankaj Raghav wrote:
> From: Luis Chamberlain <mcgrof@kernel.org>
> 
> f2fs currently only work with zoned storage devices with a zone
> size which is a power of 2 (PO2). So check if a non-power of 2
> zoned device is found, and if so disallow its use. This prevents
> users from incorrectly using these devices.
> 
> This is a non-issue today given today's kernel does not allow NPO2
> zoned devices to exist as a block device. But NPO2 zoned devices do exist
> so proactively put a stop-gap measure in place to prevent it from being
> incorrectly used.
> 
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>

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

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2022-04-20 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220413122941eucas1p1ec05e8e8dfe2baf451fcb549d60fda35@eucas1p1.samsung.com>
2022-04-13 12:29 ` [f2fs-dev] [PATCH v2] libf2fs: don't allow mkfs / fsck on non power-of-2 zoned devices Pankaj Raghav
2022-04-13 17:03   ` Jaegeuk Kim
2022-04-13 17:53     ` Pankaj Raghav
2022-04-13 19:45       ` Jaegeuk Kim
2022-04-19  8:02         ` Pankaj Raghav
2022-04-19 23:07           ` Jaegeuk Kim
2022-04-20  6:48             ` Pankaj Raghav
2022-04-20  8:30             ` Pankaj Raghav
2022-04-20 10:45   ` Chao Yu [this message]

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=8b1c2c4e-4769-67d1-42b9-42d2d1d0871d@kernel.org \
    --to=chao@kernel.org \
    --cc=Damien.LeMoal@wdc.com \
    --cc=javier.gonz@samsung.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=pankydev8@gmail.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 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.