From: Al Viro <viro@zeniv.linux.org.uk>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] mount: warn only once about timestamp range expiration
Date: Mon, 31 Jan 2022 02:52:53 +0000 [thread overview]
Message-ID: <YfdPBUYno5f0bTVk@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20220119202934.26495-1-ailiop@suse.com>
On Wed, Jan 19, 2022 at 09:29:34PM +0100, Anthony Iliopoulos wrote:
> 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].
Looks sane, except for the locking rules for ->s_iflags stores...
next prev parent reply other threads:[~2022-01-31 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 20:29 [PATCH RESEND] mount: warn only once about timestamp range expiration Anthony Iliopoulos
2022-01-20 7:25 ` Christoph Hellwig
2022-01-20 8:47 ` Christian Brauner
2022-01-20 18:03 ` Darrick J. Wong
2022-01-31 2:52 ` Al Viro [this message]
2022-02-07 22:10 ` Christian Kujau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfdPBUYno5f0bTVk@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ailiop@suse.com \
--cc=akpm@linux-foundation.org \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).