From: Jon DeVree <nuxi@vault24.org>
To: linux-fsdevel@vger.kernel.org
Subject: [BUG] 2038 warning is not printed with new mount API
Date: Sun, 1 Dec 2024 22:57:59 -0500 [thread overview]
Message-ID: <Z00wR_eFKZvxFJFW@feynman.vault24.org> (raw)
When using the old mount API, the linux kernel displays a warning for
filesystems that lack support for timestamps after 2038. This same
warning does not display when using the new mount API
(fsopen/fsconfig/fsmount)
util-linux 2.39 and higher use the new mount API when available which
means the warning is effectively invisible for distributions with the
newer util-linux.
I noticed this after upgrading a box from Debian Bookworm to Trixie, but
its also reproducible with stock upstream kernels.
From a box running a vanilla 6.1 kernel:
With util-linux 2.38.1 (old mount API)
[11526.615241] loop0: detected capacity change from 0 to 6291456
[11526.618049] XFS (loop0): Mounting V5 Filesystem
[11526.621376] XFS (loop0): Ending clean mount
[11526.621600] xfs filesystem being mounted at /mnt supports timestamps until 2038 (0x7fffffff)
[11530.275460] XFS (loop0): Unmounting Filesystem
With util-linux 2.39.4 (new mount API)
[11544.063381] loop0: detected capacity change from 0 to 6291456
[11544.066295] XFS (loop0): Mounting V5 Filesystem
[11544.069596] XFS (loop0): Ending clean mount
[11545.527687] XFS (loop0): Unmounting Filesystem
With util-linux 2.40.2 (new mount API)
[11550.718647] loop0: detected capacity change from 0 to 6291456
[11550.722105] XFS (loop0): Mounting V5 Filesystem
[11550.725297] XFS (loop0): Ending clean mount
[11552.009042] XFS (loop0): Unmounting Filesystem
All of them were mounting the same filesystem image that was created
with: mkfs.xfs -m bigtime=0
If play games with seccomp to hide the new mount APIs from util-linux,
it will fall back to the old mount API and the warning prints again.
--
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).
next reply other threads:[~2024-12-02 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 3:57 Jon DeVree [this message]
2024-12-02 11:55 ` [BUG] 2038 warning is not printed with new mount API Christian Brauner
2024-12-02 14:46 ` Jon DeVree
2024-12-03 5:12 ` Dave Chinner
2024-12-03 9:19 ` Christian Brauner
2024-12-03 11:06 ` Karel Zak
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=Z00wR_eFKZvxFJFW@feynman.vault24.org \
--to=nuxi@vault24.org \
--cc=linux-fsdevel@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