lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090821070252.GA17871@skywalker.linux.vnet.ibm.com>
Date:	Fri, 21 Aug 2009 12:32:52 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: RFC: guard against more "dangerous" userspace options

On Thu, Aug 20, 2009 at 09:48:08AM -0500, Eric Sandeen wrote:
> Aneesh Kumar K.V wrote:
> > 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
> 
> Better, or _safe_?  :)
> 
> No offense and I certainly appreciate that work.  If you feel it's
> robust enough now to safely unleash on users, I'll drop it from my list.  :)

I am interested in the test results. Getting more users to test would always
be nice. But it still would help to get a through review.


-aneesh
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ