From: Julian Sikorski <belegdol@gmail.com>
To: Paulo Alcantara <pc@cjr.nz>, ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: kernel-5.18.8 breaks cifs mounts
Date: Thu, 30 Jun 2022 21:12:02 +0200 [thread overview]
Message-ID: <4c28c2f8-cda6-d9b4-d80f-1ffa3a3be14c@gmail.com> (raw)
In-Reply-To: <87edz63t11.fsf@cjr.nz>
Am 30.06.22 um 20:28 schrieb Paulo Alcantara:
> Julian Sikorski <belegdol@gmail.com> writes:
>
>> Am 30.06.22 um 19:55 schrieb Paulo Alcantara:
>>> Julian Sikorski <belegdol@gmail.com> writes:
>>>
>>>> Not much is there:
>>>>
>>>> Jun 30 18:19:34 snowball3 kernel: CIFS: Attempting to mount
>>>> \\odroidxu4.local\julian
>>>>
>>>> Jun 30 18:19:34 snowball3 kernel: CIFS: VFS: cifs_mount failed w/return
>>>> code = -22
>>>>
>>>>
>>>> I tried reverting 16d5d91 as it was the only commit referencing smb, but
>>>> it did not help unfortunately.
>>>
>>> Could you please run
>>>
>>> echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
>>> echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
>>> echo 1 > /proc/fs/cifs/cifsFYI
>>> echo 1 > /sys/module/dns_resolver/parameters/debug
>>> dmesg --clear
>>> tcpdump -s 0 -w trace.pcap port 445 & pid=$!
>>> mount ...
>>> kill $pid
>>> dmesg > trace.log
>>>
>>> and then send trace.log and trace.pcap.
>>
>> Attached.
>>
>>>
>>> What SMB server and version?
>>
>> Openmediavault 6.0.30 running on top of armbian bullseye. The samba
>> package version is 4.13.13+dfsg-1~deb11u3.
>
> Thanks!
>
> So, it is failing very early during the negproto request:
>
> SMB2 302 Negotiate Protocol Request
> SMB2 143 Negotiate Protocol Response, Error: STATUS_INVALID_PARAMETER
>
> which seems related to these commits in v5.18.8
>
> 16d5d9100927 smb3: use netname when available on secondary channels
> ca83f50b43a0 smb3: fix empty netname context on secondary channels
>
> Have you tried reverting both in v5.18.8 to see if it works?
>
> I built v5.18.8 but couldn't reproduce it against w22 server, though.
Good catch! I only noticed
16d5d9100927 smb3: use netname when available on secondary channels
initally, and reverting it did not help. Reverting
ca83f50b43a0 smb3: fix empty netname context on secondary channels
makes the mounts work again.
Best regards,
Julian
next prev parent reply other threads:[~2022-06-30 19:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:47 kernel-5.18.8 breaks cifs mounts Julian Sikorski
2022-06-30 17:02 ` ronnie sahlberg
2022-06-30 17:41 ` Julian Sikorski
2022-06-30 17:55 ` Paulo Alcantara
2022-06-30 18:11 ` Julian Sikorski
2022-06-30 18:28 ` Paulo Alcantara
2022-06-30 19:12 ` Julian Sikorski [this message]
2022-06-30 20:32 ` Enzo Matsumiya
2022-07-04 8:12 ` Shyam Prasad N
2022-07-04 16:30 ` Julian Sikorski
[not found] ` <CAH2r5mtVwZggJ9Fi0zsK5hCci4uxee-kOSC3brb56xpb0_xn7w@mail.gmail.com>
[not found] ` <56afe80b-bf6a-2508-063a-7b091cdbbe0f@gmail.com>
[not found] ` <CAH2r5mvoyhZGjf_wgvjgmkCz=+2iDxCSpbyJ79NMtpE1Ecjdnw@mail.gmail.com>
[not found] ` <fccdb4af-697e-b7fc-6421-f16e9b35bb8e@samba.org>
2022-07-04 16:29 ` Julian Sikorski
2022-07-05 5:28 ` Shyam Prasad N
2022-07-05 10:55 ` Julian Sikorski
2022-07-06 11:18 ` Julian Sikorski
2022-07-12 4:36 ` Steve French
2022-07-13 21:25 ` Georg Müller
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=4c28c2f8-cda6-d9b4-d80f-1ffa3a3be14c@gmail.com \
--to=belegdol@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@cjr.nz \
--cc=ronniesahlberg@gmail.com \
/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 NNTP newsgroup(s).