From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: RFC: guard against more "dangerous" userspace options
Date: Thu, 20 Aug 2009 11:57:30 +0530 [thread overview]
Message-ID: <20090820062730.GA23232@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <4A81D7EC.2060706@redhat.com>
On Tue, Aug 11, 2009 at 03:43:24PM -0500, Eric Sandeen wrote:
> I'll keep it short and sweet:
>
> Can we add a consistent "--eatmydata" type of hurdle to jump over before
> people are allowed to use either the so-far-less-tested tools and/or
> options therein?
>
> I'm thinking of, so far:
......
> tune2fs -I <bigger>
I have sent patches which should make this better. Any chance to get that reviwed and
applied
-aneesh
next prev parent reply other threads:[~2009-08-20 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:43 RFC: guard against more "dangerous" userspace options Eric Sandeen
2009-08-20 6:27 ` Aneesh Kumar K.V [this message]
2009-08-20 14:48 ` Eric Sandeen
2009-08-21 7:02 ` Aneesh Kumar K.V
2009-08-21 14:40 ` Eric Sandeen
2009-08-21 16:08 ` Andreas Dilger
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=20090820062730.GA23232@skywalker.linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).