linux-ext4 - Re: tune2fs and setting noatime as a default mount options

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: <54009D31.70703@redhat.com>
Date:	Fri, 29 Aug 2014 10:33:05 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Tomasz Chmielewski <mangoo@...g.org>, linux-ext4@...r.kernel.org
Subject: Re: tune2fs and setting noatime as a default mount options

On 8/28/14, 5:12 PM, Tomasz Chmielewski wrote:
> I'd like to set noatime as a default mount option for a filesystem:
> 
> # tune2fs -o noatime /dev/sdb1
> tune2fs 1.42.9 (4-Feb-2014)
> Invalid mount option set: noatime

Right, the manpage doesn't list that as supported under "-o".

> Is there a reason why noatime can't be set as a default mount option? Thinking of all these USB connected devices where it would be handy.

I haven't looked, but I'm guessing it's because noatime is a vfs-level switch, and by the time the ext4 superblock is getting read and processed during mount, that chance has passed.

Just to keep things complicated and confusing ;) there's a different mechanism to do this as well:

# tune2fs -E mount_opts=noatime /dev/sdc1

which succeeds; however, this fails to be parsed at mount time:

[  118.384020] EXT4-fs (sdc1): failed to parse options in superblock: noatime

for the same reasons, I guess.  The documentation could certainly be better...

-Eric
--
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