From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arthur Marsh <arthur.marsh@internode.on.net>
Subject: VFAT mounting / sharing issue after: d_path: make 'prepend()' fill up the buffer exactly on overflow
Date: Mon, 13 Sep 2021 23:46:31 +0930 [thread overview]
Message-ID: <ad3d1354-59d6-2f1a-adf9-e09644ce9769@internode.on.net> (raw)
Hi,
On recent kernels a VFAT filesystem mounted on my i686 system started
behaving weirdly:
The /etc/fstab entry was:
UUID=7417-5AFF /victoria vfat
defaults,uid=65534,gid=65534,umask=000 0 2
After boot-up the filesystem had previously been mounted as:
# mount|grep vic
/dev/sdb6 on /victoria type vfat
(rw,relatime,uid=65534,gid=65534,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,
iocharset=utf8,shortname=mixed,errors=remount-ro)
On more recent kernels after the boot-up I saw the mount name truncated:
# mount|grep vic
/dev/sda6 on /vict type vfat
(rw,relatime,uid=65534,gid=65534,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,
iocharset=utf8,shortname=mixed,errors=remount-ro)
I could cd to /victoria and access the filesystem locally, but samba
sharing of the filesystem failed.
After a long git-bisect session I found the commit that caused it:
commit b0cfcdd9b9672ea90642f33d6c0dd8516553adf2
Author: Linus Torvalds @linux-foundation.org>
Date: Fri Jul 16 14:01:12 2021 -0700
d_path: make 'prepend()' fill up the buffer exactly on overflow
Reverting the commit resolved the issue, including on kernel 5.15.0-rc1
I'm at a loss as to why the patch caused the problem with the reported
mount name and samba sharing.
Build was on i686 using gcc-11 and:
make -j2 menuconfig bindeb-pkg
I'm happy to supply .config and run tests.
Arthur.
reply other threads:[~2021-09-13 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ad3d1354-59d6-2f1a-adf9-e09644ce9769@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®