From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Paulo Alcantara <pc@manguebit.org>,
Linux Cifs <linux-cifs@vger.kernel.org>
Subject: [REGRESSION] in Linux 7.0: empty CIFS mount point with vers=1.0
Date: Thu, 16 Apr 2026 17:20:30 -0400 [thread overview]
Message-ID: <f758f4ff-4d54-4244-931d-38f469c3ff14@moonlit-rail.com> (raw)
A bit late to the party, sorry, I should have reported this in 7.0-rcX.
When mounting a CIFS share with vers=1.0, the mount "succeeds" (is added
to /proc/mounts) but the mountpoint is completely empty. Even "." and
".." are missing. Blindly accessing a known file results in "no such
file or directory".
Kernels 6.19 and below are not affected. Using vers=2.0 or vers=3.1.1
(etc) works fine, but "UNIX File Extensions" is still necessary for my
workload. (While "posix" extensions in vers=3.1.1 against Samba Stable
is getting better, it's not there yet, details on request.)
Example:
# ls -al /mnt/tmp
Total 8
drwxr-xr-x 2 root root 4096 Sep 25 2006 ./
drwxr-xr-x 12 root root 4096 Apr 11 03:32 ../
---------- 1 root root 0 Dec 22 2018 filesystem.not.mounted
# mount -t cifs -o vers=1.0,cred=.creds //Server/Share /mnt/tmp
# ls -al /mnt/tmp
Total 0
#
If Greg KH were reading this, I just know he'd say,
"can you bisect?" :-) OK, the winner of the bisect is:
> 4fc3a433c13944ee5766ec5b9bf6f1eb4d29b880 is the first bad commit
> commit 4fc3a433c13944ee5766ec5b9bf6f1eb4d29b880
> Author: Paulo Alcantara <pc@manguebit.org>
> Date: Mon Feb 23 13:34:35 2026 -0300
>
> smb: client: use atomic_t for mnt_cifs_flags
>
> Use atomic_t for cifs_sb_info::mnt_cifs_flags as it's currently
> accessed locklessly and may be changed concurrently in mount/remount
> and reconnect paths.
I added Paulo to the CC's.
Kris
next reply other threads:[~2026-04-16 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 21:20 Kris Karas (Bug Reporting) [this message]
2026-04-16 22:39 ` [REGRESSION] in Linux 7.0: empty CIFS mount point with vers=1.0 Paulo Alcantara
2026-04-17 0:51 ` Kris Karas (Bug Reporting)
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=f758f4ff-4d54-4244-931d-38f469c3ff14@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.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 read-only IMAP folder(s) and NNTP newsgroup(s).