From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 211605] Re-mount XFS causes "noattr2 mount option is deprecated" warning
Date: Sun, 07 Feb 2021 23:01:29 +0000 [thread overview]
Message-ID: <bug-211605-201763-7XvPElabdR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211605-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211605
--- Comment #4 from Eric Sandeen (sandeen@sandeen.net) ---
On 2/7/21 4:15 PM, Dave Chinner wrote:
> On Sun, Feb 07, 2021 at 05:06:36AM +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=211605
>>
>> Bug ID: 211605
>> Summary: Re-mount XFS causes "noattr2 mount option is
>> deprecated" warning
>> Product: File System
>> Version: 2.5
>> Kernel Version: 5.10.13
>> Hardware: All
>> OS: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: low
>> Priority: P1
>> Component: XFS
>> Assignee: filesystem_xfs@kernel-bugs.kernel.org
>> Reporter: cuihao.leo@gmail.com
>> Regression: No
>>
...
> The kernel is warning about a mount option being specified that
> isn't even in the set emitted in /proc/mounts. Nor is it on your
> command line. Yet the kernel is warning about it, and that implies
> that mount has passed it to the kernel incorrectly.
I am confused about how "noattr2" showed up.
But we do still emit "attr2" in /proc/mounts, and a remount will complain
about /that/, so we do need to stop emitting deprecated options in
/proc/mounts.
# mount /dev/pmem0p1 /mnt/test
# grep pmem /proc/mounts
/dev/pmem0p1 /mnt/test xfs
rw,seclabel,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
# mount -o remount,ro /mnt/test
# dmesg | tail -n 1
[346311.064017] XFS: attr2 mount option is deprecated.
Pavel, can you fix this up, since your patch did the deprecations? I guess we
missed this on review.
Ideally the xfs(5) man page in xfsprogs should be updated as well to reflect
the
deprecated items.
-Eric
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-02-07 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 5:06 [Bug 211605] New: Re-mount XFS causes "noattr2 mount option is deprecated" warning bugzilla-daemon
2021-02-07 22:15 ` Dave Chinner
2021-02-07 22:53 ` Eric Sandeen
2021-02-07 23:18 ` Dave Chinner
2021-02-07 23:36 ` Eric Sandeen
2021-02-07 22:41 ` [Bug 211605] " bugzilla-daemon
2021-02-07 22:42 ` bugzilla-daemon
2021-02-07 22:56 ` bugzilla-daemon
2021-02-07 23:01 ` bugzilla-daemon [this message]
2021-02-07 23:06 ` bugzilla-daemon
2021-02-07 23:18 ` [Bug 211605] Re-mount XFS causes "attr2 " bugzilla-daemon
2021-02-07 23:36 ` bugzilla-daemon
2021-03-08 7:04 ` bugzilla-daemon
2021-03-08 15:07 ` bugzilla-daemon
2021-05-03 13:31 ` bugzilla-daemon
2021-05-03 13:35 ` bugzilla-daemon
2021-05-13 11:15 ` bugzilla-daemon
2021-05-13 13:22 ` bugzilla-daemon
2025-11-15 8:12 ` bugzilla-daemon
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=bug-211605-201763-7XvPElabdR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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