All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Steve French <sfrench@samba.org>
Cc: Kim Scarborough <kim@scarborough.kim>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: [Regression] Bug 216881 - CIFS 1.0 mounts fail with "VFS: bogus file nlink value 0"
Date: Fri, 6 Jan 2023 10:49:48 +0100	[thread overview]
Message-ID: <a1081b61-c066-153d-2ec3-1f86ce68c0e6@leemhuis.info> (raw)

Hi, this is your Linux kernel regression tracker.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216881 :

>  Kim Scarborough 2023-01-04 07:00:50 UTC
> 
> An SMB mount to a Windows XP machine in my fstab no longer works. It last worked with 6.0.9. fstab line:
> 
> //server/D /remote/server/D cifs noauto,_netdev,username=example,password=example,uid=1000,vers=1.0,nomultichannel 0 0
> 
> When I attempt to mount this now, I get the following error:
> 
> mount error(20): Not a directory
> 
> dmesg shows:
> 
> CIFS: VFS: bogus file nlink value 0

See the ticket for more details.

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.0..v6.1
https://bugzilla.kernel.org/show_bug.cgi?id=216881
#regzbot title: cifs: cifs 1.0 mounts fail with "VFS: bogus file nlink
value 0"
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

                 reply	other threads:[~2023-01-06  9:49 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=a1081b61-c066-153d-2ec3-1f86ce68c0e6@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=kim@scarborough.kim \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sfrench@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.