diff options
| author | Andi Kleen <andi@firstfloor.org> | 2009-04-19 18:40:43 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-19 10:46:47 -0700 |
| commit | 613cbe3d4870429bf2e816d4bbe3146d157ee5c1 (patch) | |
| tree | 52031a08d45201164ca6b8a126b3a0c4af2ecb43 /include/linux/seccomp.h | |
| parent | ff54250a0ebab7f90a5f848a0ba63f999830c872 (diff) | |
| download | kernel_samsung_espresso10-613cbe3d4870429bf2e816d4bbe3146d157ee5c1.zip kernel_samsung_espresso10-613cbe3d4870429bf2e816d4bbe3146d157ee5c1.tar.gz kernel_samsung_espresso10-613cbe3d4870429bf2e816d4bbe3146d157ee5c1.tar.bz2 | |
Don't set relatime when noatime is specified
Since commit 0a1c01c9477602ee8b44548a9405b2c1d587b5a2 ("Make relatime
default") when a file system is mounted explicitely with noatime it gets
both the MNT_RELATIME and MNT_NOATIME bits set.
This shows up like this in /proc/mounts:
/dev/xxx /yyy ext3 rw,noatime,relatime,errors=continue,data=writeback 0 0
That looks strange. The VFS uses noatime in this case, but both flags
are set. So it's more a cosmetic issue, but still better to fix.
Cc: mjg@redhat.com
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/seccomp.h')
0 files changed, 0 insertions, 0 deletions