linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Enzo Matsumiya <ematsumiya@suse.de>
To: Julian Sikorski <belegdol@gmail.com>
Cc: Paulo Alcantara <pc@cjr.nz>,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	CIFS <linux-cifs@vger.kernel.org>
Subject: Re: kernel-5.18.8 breaks cifs mounts
Date: Thu, 30 Jun 2022 17:32:07 -0300	[thread overview]
Message-ID: <20220630203207.ewmdgnzzjauofgru@cyberdelia> (raw)
In-Reply-To: <4c28c2f8-cda6-d9b4-d80f-1ffa3a3be14c@gmail.com>

On 06/30, Julian Sikorski wrote:
>>>Openmediavault 6.0.30 running on top of armbian bullseye. The samba
>>>package version is 4.13.13+dfsg-1~deb11u3.

[ ... ]

>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.

It's possible that server is not discarding/ignoring SMB2_NETNAME_NEGOTIATE_CONTEXT_ID
negotiate context as it should, and rather treating it as an error. 

I took a quick look in SLE15-SP3 samba 4.15 code and I didn't spot any
obvious mishandling there (it seems it's not supported yet). Also I
couldn't reproduce the issue with that server.

Maybe it's possible it's a vendor modification?


Cheers,

Enzo

  reply	other threads:[~2022-06-30 20:32 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
2022-06-30 20:32             ` Enzo Matsumiya [this message]
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=20220630203207.ewmdgnzzjauofgru@cyberdelia \
    --to=ematsumiya@suse.de \
    --cc=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).