linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>,
	Jeff Layton <jlayton@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Eric Biggers <ebiggers@google.com>
Subject: filesystem being remounted supports timestamps until 2038
Date: Fri, 20 Dec 2019 18:02:54 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.21.99999.375.1912201332260.21037@trent.utfs.org> (raw)

Hello,

I noticed the following messages in my dmesg:

 xfs filesystem being remounted at /mnt/disk supports imestamps until 2038 (0x7fffffff)

These messages get printed over and over again because /mnt/disk is 
usually a read-only mount that is remounted (rw) a couple of times a day 
for backup purposes.

I see that these messages have been introduced with f8b92ba67c5d ("mount: 
Add mount warning for impending timestamp expiry") resp. 0ecee6699064 
("fix use-after-free of mount in mnt_warn_timestamp_expiry()") and I was 
wondering if there is any chance to either adjust this to pr_debug (but 
then it would still show up in dmesg, right?) or to only warn once when 
it's mounted, but not on re-mount?

Thanks,
Christian.
-- 
BOFH excuse #83:

Support staff hung over, send aspirin and come back LATER.

             reply	other threads:[~2019-12-21  2:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21  2:02 Christian Kujau [this message]
2019-12-27  1:54 ` [PATCH] Re: filesystem being remounted supports timestamps until 2038 Christian Kujau
2019-12-28 19:51   ` Deepa Dinamani
2019-12-29 18:01   ` Linus Torvalds
2020-01-04 23:51     ` Christian Kujau
2020-06-24  0:26       ` Christian Kujau
2022-01-27 21:49         ` Salvatore Bonaccorso

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=alpine.DEB.2.21.99999.375.1912201332260.21037@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=deepa.kernel@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jlayton@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).