From: Ted Ts'o <tytso@mit.edu>
To: "Yury V. Zaytsev" <yury@shurup.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/1 v2 RESEND] mke2fs: check that auto-detected blocksize <= sys_page_size
Date: Thu, 15 Sep 2011 23:11:48 -0400 [thread overview]
Message-ID: <20110916031148.GP28181@thunk.org> (raw)
In-Reply-To: <1312966123.4477.99.camel@newpride>
On Wed, Aug 10, 2011 at 10:48:43AM +0200, Yury V. Zaytsev wrote:
> Block size can be specified manually via the -b option or deduced
> automatically. Unfortunately, the check that it is still smaller than
> the system page size is only performed right after the command line
> options are parsed.
>
> Therefore, if buggy or inappropriately installed/configured hardware
> hints that larger block sizes have to be used, mkfs will silently create
> a file system which can not be mounted on the system in question.
>
> By moving the check beyond the last assignment to blocksize it is now
> ensured, that mkfs will issue a warning even if inappropriate blocksize
> was auto-detected.
>
> The new behavior can be easily tested, by exporting the following
> variables before running mkfs:
>
> export MKE2FS_DEVICE_SECTSIZE=8192
> export MKE2FS_DEVICE_PHYS_SECTSIZE=8192
>
> Signed-off-by: Yury V. Zaytsev <yury@shurup.com>
> Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Thanks, I've merged this into the next branch. Apologies for the delay.
- Ted
prev parent reply other threads:[~2011-09-16 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 8:48 [PATCH 1/1 v2 RESEND] mke2fs: check that auto-detected blocksize <= sys_page_size Yury V. Zaytsev
2011-09-16 3:11 ` Ted Ts'o [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=20110916031148.GP28181@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=yury@shurup.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.