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: <20081129125607.55d70063.akpm@linux-foundation.org>
Date:	Sat, 29 Nov 2008 12:56:07 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Matthew Garrett <mjg@...hat.com>,
	Jamie Lokier <jamie@...reable.org>,
	J?rn Engel <joern@...fs.org>,
	Christoph Hellwig <hch@...radead.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	mingo@...hat.com, val.henson@...il.com
Subject: Re: [PATCH v2 2/2] relatime: Allow making relatime the default
 behaviour

On Sat, 29 Nov 2008 13:38:57 -0700 Matthew Wilcox <matthew@....cx> wrote:

> On Sat, Nov 29, 2008 at 12:32:20PM -0800, Andrew Morton wrote:
> > The standard, usual, expected way of modifying a filesystem's behaviour
> > is via mount options.  This is also quite flexible.
> > 
> > Is there some extraordinary reason why the standard interface is not to
> > be used here?
> 
> Because it would have to be managed (and consulted) per ... what?
> vfsmount?  superblock?

Per superblock, of course.

> This is featuritis gone MAD.

No it isn't - it's the expected and standard behaviour.  We have all
the kernel infrastructure and userspace tools in place for doing it
this way.

Modifying the behaviour of all filesystems with a single knob is a
weird thing to do.

MNT_RELATIME itself is already per-superblock.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ