From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] mke2fs: prompt for user verification for "-S"
Date: Fri, 19 Jun 2015 21:38:18 -0400 [thread overview]
Message-ID: <20150620013818.GC29480@thunk.org> (raw)
In-Reply-To: <1432334588-18387-1-git-send-email-adilger@dilger.ca>
On Fri, May 22, 2015 at 04:43:08PM -0600, Andreas Dilger wrote:
> Prompt for user verification before rewriting the filesystem
> superblocks using the "-S" (super-only) option. This should
> not normally be used at all, so adding the extra verification
> will probably save a few user filesystems in the future. Since
> this is something that should only be done in rare cases under
> user supervision, wait for user input rather than proceeding
> automatically after a timeout.
>
> Update the mke2fs man page to more fully explain the many
> dangers of this option.
>
> Signed-off-by: Andreas Dilger <adilger@dilger.ca>
Applied, thanks.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
prev parent reply other threads:[~2015-06-20 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 22:43 [PATCH] mke2fs: prompt for user verification for "-S" Andreas Dilger
2015-06-20 1:38 ` Theodore 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=20150620013818.GC29480@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).