diff options
author | Anthony Iliopoulos <ailiop@suse.com> | 2022-03-22 14:39:22 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-03-22 15:57:01 -0700 |
commit | a128b054ce029554a4a52fc3abb8c1df8bafcaef (patch) | |
tree | 643bae30214c2a3cfc8ec68575174cce7a2a2117 /mm/mincore.c | |
parent | a88f2096d5a2d91179db5dd9aa8f60dc3df9bb3e (diff) | |
download | linux-stable-a128b054ce029554a4a52fc3abb8c1df8bafcaef.tar.gz linux-stable-a128b054ce029554a4a52fc3abb8c1df8bafcaef.tar.bz2 linux-stable-a128b054ce029554a4a52fc3abb8c1df8bafcaef.zip |
mount: warn only once about timestamp range expiration
Commit f8b92ba67c5d ("mount: Add mount warning for impending timestamp
expiry") introduced a mount warning regarding filesystem timestamp
limits, that is printed upon each writable mount or remount.
This can result in a lot of unnecessary messages in the kernel log in
setups where filesystems are being frequently remounted (or mounted
multiple times).
Avoid this by setting a superblock flag which indicates that the warning
has been emitted at least once for any particular mount, as suggested in
[1].
Link: https://lore.kernel.org/CAHk-=wim6VGnxQmjfK_tDg6fbHYKL4EFkmnTjVr9QnRqjDBAeA@mail.gmail.com/ [1]
Link: https://lkml.kernel.org/r/20220119202934.26495-1-ailiop@suse.com
Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/mincore.c')
0 files changed, 0 insertions, 0 deletions