linux-kernel - filesystem being remounted supports timestamps until 2038

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

Message-ID: <alpine.DEB.2.21.99999.375.1912201332260.21037@trent.utfs.org>
Date:   Fri, 20 Dec 2019 18:02:54 -0800 (PST)
From:   Christian Kujau <lists@...dbynature.de>
To:     Deepa Dinamani <deepa.kernel@...il.com>,
        Jeff Layton <jlayton@...nel.org>
cc:     LKML <linux-kernel@...r.kernel.org>,
        Eric Biggers <ebiggers@...gle.com>
Subject: filesystem being remounted supports timestamps until 2038

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.