mount.cifs broken after update, advice?

mount.cifs broken after update, advice?

[Brian Caine]

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

Hey all,

So I recently updated my kernel and my previously-working CIFS
mountpoints are broken. The server hasn't changed.

I can successfully access it via smbclient. Only mount.cifs is broken.

On the server:

% /usr/local/sbin/smbd --version
Version 4.12.15

On the client:

$ mount.cifs --version
mount.cifs version: 6.15

$ smbclient --version
Version 4.16.2

$ uname -r
5.18.9-arch1-1

(I know it's not a vanilla kernel, so I wanted to ask for advice here
before making a bug report.)

As mentioned, smbclient still works:

$ smbclient -U brian //192.168.1.131/backup -c ls
Password for [WORKGROUP\brian]:
  .                                   D        0  Sat Apr 24 16:01:23 2021
  ..                                  D        0  Tue Dec  1 20:18:28 2020
  brian                               D        0  Sat Apr 24 16:09:46 2021

15119769681 blocks of size 1024. 12418540722 blocks available

This doesn't though:

# mount.cifs --verbose --verbose -o username=brian
//192.168.1.131/backup /tmp/foo
Password for brian@//192.168.1.131/backup:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and
kernel log messages (dmesg)

I attached my kernel output. Is there anything there that jumps out at
anyone? Any easy fixes or should I look into opening a bug report?
Anything else I can provide, just ask.

Thanks,
Brian

[-- Attachment #2: trace.log --]
[-- Type: text/x-log, Size: 3331 bytes --]

[177628.524701] device enp4s0 entered promiscuous mode
[177628.524722] audit: type=1700 audit(1657508205.654:2034): dev=enp4s0 prom=256 old_prom=0 auid=1000 uid=0 gid=0 ses=4
[177628.525000] audit: type=1300 audit(1657508205.654:2034): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=107 a2=1 a3=7ffccf6d1fd0 items=0 ppid=8236 pid=138099 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts9 ses=4 comm="tcpdump" exe="/usr/bin/tcpdump" key=(null)
[177628.525003] audit: type=1327 audit(1657508205.654:2034): proctitle=74637064756D70002D730030002D770074726163652E70636170
[177640.325043] CIFS: fs/cifs/fs_context.c: CIFS: parsing cifs mount option 'source'
[177640.325053] CIFS: fs/cifs/fs_context.c: CIFS: parsing cifs mount option 'ip'
[177640.325057] CIFS: fs/cifs/fs_context.c: CIFS: parsing cifs mount option 'unc'
[177640.325059] CIFS: fs/cifs/fs_context.c: CIFS: parsing cifs mount option 'user'
[177640.325061] CIFS: fs/cifs/fs_context.c: CIFS: parsing cifs mount option 'pass'
[177640.325064] CIFS: fs/cifs/cifsfs.c: Devname: \\192.168.1.131\backup flags: 0
[177640.325068] CIFS: fs/cifs/connect.c: Username: brian
[177640.325070] CIFS: fs/cifs/connect.c: file mode: 0755  dir mode: 0755
[177640.325073] CIFS: fs/cifs/connect.c: VFS: in mount_get_conns as Xid: 72 with uid: 0
[177640.325076] CIFS: fs/cifs/connect.c: UNC: \\192.168.1.131\backup
[177640.325080] CIFS: fs/cifs/connect.c: generic_ip_connect: connecting to 192.168.1.131:445
[177640.325090] CIFS: fs/cifs/connect.c: Socket created
[177640.325092] CIFS: fs/cifs/connect.c: sndbuf 16384 rcvbuf 131072 rcvtimeo 0x834
[177640.325724] CIFS: fs/cifs/connect.c: cifs_get_tcp_session: next dns resolution scheduled for 600 seconds in the future
[177640.325727] CIFS: fs/cifs/connect.c: VFS: in cifs_get_smb_ses as Xid: 73 with uid: 0
[177640.325729] CIFS: fs/cifs/connect.c: Existing smb sess not found
[177640.325728] CIFS: fs/cifs/connect.c: Demultiplex PID: 138111
[177640.325732] CIFS: fs/cifs/smb2pdu.c: Negotiate protocol
[177640.325738] CIFS: fs/cifs/transport.c: wait_for_free_credits: remove 1 credits total=0
[177640.325750] CIFS: fs/cifs/transport.c: Sending smb: smb_len=244
[177640.339376] CIFS: fs/cifs/connect.c: RFC1002 header 0x49
[177640.339381] CIFS: fs/cifs/smb2misc.c: SMB2 data length 0 offset 0
[177640.339382] CIFS: fs/cifs/smb2misc.c: SMB2 len 73
[177640.339385] CIFS: fs/cifs/smb2ops.c: smb2_add_credits: added 1 credits total=1
[177640.339395] CIFS: fs/cifs/transport.c: cifs_sync_mid_result: cmd=0 mid=0 state=4
[177640.339399] CIFS: fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc000000d to POSIX err -22
[177640.339403] CIFS: fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release
[177640.339406] CIFS: fs/cifs/connect.c: VFS: leaving cifs_get_smb_ses (xid = 73) rc = -22
[177640.339409] CIFS: fs/cifs/dfs_cache.c: cache_refresh_path: search path: \192.168.1.131\backup
[177640.339411] CIFS: fs/cifs/dfs_cache.c: get_dfs_referral: get an DFS referral for \192.168.1.131\backup
[177640.339417] CIFS: fs/cifs/connect.c: VFS: leaving mount_put_conns (xid = 72) rc = 0
[177640.339418] CIFS: VFS: cifs_mount failed w/return code = -22
[177647.747321] device enp4s0 left promiscuous mode
[177647.747339] audit: type=1700 audit(1657508224.877:2035): dev=enp4s0 prom=0 old_prom=256 auid=1000 uid=0 gid=0 ses=4

Re: mount.cifs broken after update, advice?

[Steve French]

This looks like the Samba server bug pointed out in an earlier email
thread by Metze (fixed by
https://git.samba.org/?p=samba.git;a=commitdiff;h=147dd9d58a429695a3b6c6e45c8b0eaafc67908a)

I had trouble reproducing it on my systems but it looks like (based on
Julian Sikorski's testing) when we fixed the netname context to not be
null in some multichannel cases, the reordering of the contexts
(putting netname context after the posix negotiate context) triggered
this bug in some versions of Samba (which was fixed earlier by the
Samba server commit above).

On Sun, Jul 10, 2022 at 10:35 PM Brian Caine <brian.d.caine@gmail.com> wrote:
>
> Hey all,
>
> So I recently updated my kernel and my previously-working CIFS
> mountpoints are broken. The server hasn't changed.
>
> I can successfully access it via smbclient. Only mount.cifs is broken.
>
> On the server:
>
> % /usr/local/sbin/smbd --version
> Version 4.12.15
>
> On the client:
>
> $ mount.cifs --version
> mount.cifs version: 6.15
>
> $ smbclient --version
> Version 4.16.2
>
> $ uname -r
> 5.18.9-arch1-1
>
> (I know it's not a vanilla kernel, so I wanted to ask for advice here
> before making a bug report.)
>
> As mentioned, smbclient still works:
>
> $ smbclient -U brian //192.168.1.131/backup -c ls
> Password for [WORKGROUP\brian]:
>   .                                   D        0  Sat Apr 24 16:01:23 2021
>   ..                                  D        0  Tue Dec  1 20:18:28 2020
>   brian                               D        0  Sat Apr 24 16:09:46 2021
>
> 15119769681 blocks of size 1024. 12418540722 blocks available
>
> This doesn't though:
>
> # mount.cifs --verbose --verbose -o username=brian
> //192.168.1.131/backup /tmp/foo
> Password for brian@//192.168.1.131/backup:
> mount error(22): Invalid argument
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and
> kernel log messages (dmesg)
>
> I attached my kernel output. Is there anything there that jumps out at
> anyone? Any easy fixes or should I look into opening a bug report?
> Anything else I can provide, just ask.
>
> Thanks,
> Brian



-- 
Thanks,

Steve

Re: mount.cifs broken after update, advice?

[Steve French]

I was able to reproduce it to older Samba server (4.12.5) and could
workaround the Samba server bug by using mount option "compress" on
the client (which won't do anything different since it is not
supported but  interestingly it avoids the problem by adding another
context at the end).

On Sun, Jul 10, 2022 at 11:08 PM Steve French <smfrench@gmail.com> wrote:
>
> This looks like the Samba server bug pointed out in an earlier email
> thread by Metze (fixed by
> https://git.samba.org/?p=samba.git;a=commitdiff;h=147dd9d58a429695a3b6c6e45c8b0eaafc67908a)
>
> I had trouble reproducing it on my systems but it looks like (based on
> Julian Sikorski's testing) when we fixed the netname context to not be
> null in some multichannel cases, the reordering of the contexts
> (putting netname context after the posix negotiate context) triggered
> this bug in some versions of Samba (which was fixed earlier by the
> Samba server commit above).
>
> On Sun, Jul 10, 2022 at 10:35 PM Brian Caine <brian.d.caine@gmail.com> wrote:
> >
> > Hey all,
> >
> > So I recently updated my kernel and my previously-working CIFS
> > mountpoints are broken. The server hasn't changed.
> >
> > I can successfully access it via smbclient. Only mount.cifs is broken.
> >
> > On the server:
> >
> > % /usr/local/sbin/smbd --version
> > Version 4.12.15
> >
> > On the client:
> >
> > $ mount.cifs --version
> > mount.cifs version: 6.15
> >
> > $ smbclient --version
> > Version 4.16.2
> >
> > $ uname -r
> > 5.18.9-arch1-1
> >
> > (I know it's not a vanilla kernel, so I wanted to ask for advice here
> > before making a bug report.)
> >
> > As mentioned, smbclient still works:
> >
> > $ smbclient -U brian //192.168.1.131/backup -c ls
> > Password for [WORKGROUP\brian]:
> >   .                                   D        0  Sat Apr 24 16:01:23 2021
> >   ..                                  D        0  Tue Dec  1 20:18:28 2020
> >   brian                               D        0  Sat Apr 24 16:09:46 2021
> >
> > 15119769681 blocks of size 1024. 12418540722 blocks available
> >
> > This doesn't though:
> >
> > # mount.cifs --verbose --verbose -o username=brian
> > //192.168.1.131/backup /tmp/foo
> > Password for brian@//192.168.1.131/backup:
> > mount error(22): Invalid argument
> > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and
> > kernel log messages (dmesg)
> >
> > I attached my kernel output. Is there anything there that jumps out at
> > anyone? Any easy fixes or should I look into opening a bug report?
> > Anything else I can provide, just ask.
> >
> > Thanks,
> > Brian
>
>
>
> --
> Thanks,
>
> Steve



-- 
Thanks,

Steve