linux-kernel - Re: ubifs: noatime support?

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: <1996634.ggXeMYieCh@blindfold>
Date:   Thu, 18 Jan 2018 21:44:33 +0100
From:   Richard Weinberger <richard@....at>
To:     Pavel Machek <pavel@....cz>
Cc:     kernel list <linux-kernel@...r.kernel.org>, dedekind1@...il.com,
        adrian.hunter@...el.com, linux-mtd@...ts.infradead.org,
        linux-fsdevel@...r.kernel.org
Subject: Re: ubifs: noatime support?

Pavel,

Am Donnerstag, 18. Januar 2018, 20:30:15 CET schrieb Pavel Machek:
> Hi!
> 
> Ubifs seems to have atime support these days:
> 
>           sb->s_flags |= SB_ACTIVE;
> #ifndef CONFIG_UBIFS_ATIME_SUPPORT
>           sb->s_flags |= SB_NOATIME;
> #else
>           ubifs_msg(c, "full atime support is enabled.");
> #endif
> 
> Which can be configured at compile-time, but no option to disable it
> at runtime. What is going on there?
> 
> UBIFS: parse noatime
> UBIFS error (ubi1:0 pid 94): ubifs_parse_options.constprop.5:
> unrecognized mount option "noatime" e
> mount: mounting ubi1:log_volume on /mnt/log failed: Invalid argument

Filesystems don't parse the "noatime" string, it is job of the mount tool to 
translate it to the MS_NOATIME mount flag.

Thanks,
//richard