linux-kernel - Re: [GIT PULL] ext4 bug fixes for 4.2-rc2

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] [day] [month] [year] [list]

Message-ID: <55A106EE.3050204@web.de>
Date:	Sat, 11 Jul 2015 14:07:10 +0200
From:	Jörg-Volker Peetz <jvpeetz@....de>
To:	Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: [GIT PULL] ext4 bug fixes for 4.2-rc2

Theodore Ts'o wrote on 07/05/2015 23:53:
> The following changes since commit a2fd66d069d86d793e9d39d4079b96f46d13f237:
> 
>   ext4: set lazytime on remount if MS_LAZYTIME is set by mount (2015-06-23 11:03:54 -0400)
> 
<snip>

Hi Ted,

I'm testing this patch and "ext4: set lazytime on remount if MS_LAZYTIME is set
by mount" on top of stable kernel 4.1.2.

So far no problems with lazytime enabled. Thanks for that :-)

But remounting with mount version 2.26.2 sucks. As promised, lazytime can be
enabled. But disabling it or trying to switch between atime, relatime, and
noatime doesn't work.

Starting from

# grep sda /proc/mounts
/dev/sda2 /home ext4 rw,lazytime,noatime,nobarrier,errors=remount-ro 0 0

some strace output:

# strace -o /tmp/st mount -o remount,nolazytime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x2152780, MS_MGC_VAL|MS_REMOUNT|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,relatime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1543780, MS_REMOUNT|MS_RELATIME|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,atime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1534780, MS_MGC_VAL|MS_REMOUNT,
"nobarrier,errors=remount-ro") = 0

The contents of /proc/mounts isn't changed by all this :-(

Or should I contact the util-linux developers?

-- 
Regards,
Jörg.

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