Bug#1014453: samba: error 22 when attempting to mount a share from linux-5.18.8 or newer client

Julian Sikorski

unread,

Jul 6, 2022, 7:20:03 AM7/6/22

to

Package: samba
Version: 2:4.13.13+dfsg-1~deb11u3
Severity: important
Tags: patch
X-Debbugs-Cc: bele...@gmail.com

Dear Maintainer,

After updating my client to kernel 5.18.8, I was no longer able to mount samba shares hosted by my debian install. I was getting mount error 22.
Upon discussing the problem on linux-cifs [1], it was discovered that the issue can be fixed by a patch available in samba versions 4.15 and later [2]. I can confirm that adding this patch to the debian 4.13 package fixes the issue too. Please add this patch to the package.

[1] https://lore.kernel.org/linux-cifs/8ccad303-7489-d90a...@gmail.com/T/#t
[2] https://git.samba.org/?p=samba.git;a=commitdiff;h=147dd9d58a429695a3b6c6e45c8b0eaafc67908a

-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf not present

-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 5.4.199-odroidxu4 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages samba depends on:
ii adduser 3.118
ii dpkg 1.20.10
ii init-system-helpers 1.60
ii libbsd0 0.11.3-1
ii libc6 2.31-13+deb11u3
ii libgnutls30 3.7.1-5
ii libldb2 2:2.2.3-2~deb11u1
ii libpam-modules 1.4.0-9+deb11u1
ii libpam-runtime 1.4.0-9+deb11u1
ii libpopt0 1.18-2
ii libpython3.9 3.9.2-1
ii libtalloc2 2.3.1-2+b1
ii libtasn1-6 4.16.0-2
ii libtdb1 1.4.3-1+b1
ii libtevent0 0.10.2-1
ii libwbclient0 2:4.13.13+dfsg-1~deb11u3.1
ii lsb-base 11.1.0
ii procps 2:3.3.17-5
ii python3 3.9.2-3
ii python3-dnspython 2.0.0-1
ii python3-samba 2:4.13.13+dfsg-1~deb11u3.1
ii samba-common 2:4.13.13+dfsg-1~deb11u3.1
ii samba-common-bin 2:4.13.13+dfsg-1~deb11u3.1
ii samba-libs 2:4.13.13+dfsg-1~deb11u3.1
ii tdb-tools 1.4.3-1+b1

Versions of packages samba recommends:
pn attr <none>
ii logrotate 3.18.0-2
pn python3-markdown <none>
pn samba-dsdb-modules <none>
ii samba-vfs-modules 2:4.13.13+dfsg-1~deb11u3.1

Versions of packages samba suggests:
pn bind9 <none>
pn bind9utils <none>
ii chrony 4.0-8+deb11u2
pn ctdb <none>
pn ldb-tools <none>
pn smbldap-tools <none>
pn ufw <none>
pn winbind <none>

-- Configuration Files:
/etc/logrotate.d/samba changed:
/var/log.hdd/samba/log.smbd {
weekly
missingok
rotate 7
postrotate
[ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config
endscript
compress
delaycompress
notifempty
}
/var/log.hdd/samba/log.nmbd {
weekly
missingok
rotate 7
postrotate
[ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config
endscript
compress
delaycompress
notifempty
}
/var/log.hdd/samba/log.samba {
weekly
missingok
rotate 7
postrotate
if [ -d /run/systemd/system ] && command systemctl >/dev/null 2>&1 && systemctl is-active --quiet samba-ad-dc; then
systemctl kill --kill-who all --signal=SIGHUP samba-ad-dc
elif [ -f /run/samba/samba.pid ]; then
# This only sends to main pid, See #803924
kill -HUP `cat /run/samba/samba.pid`
fi
endscript
compress
delaycompress
notifempty
}

-- no debconf information

smb.conf

Michael Tokarev

unread,

Jul 11, 2022, 11:40:04 AM7/11/22

to

06.07.2022 14:12, Julian Sikorski wrote:
> Package: samba
> Version: 2:4.13.13+dfsg-1~deb11u3
> Severity: important
> Tags: patch
> X-Debbugs-Cc: bele...@gmail.com
>
> Dear Maintainer,
>
> After updating my client to kernel 5.18.8, I was no longer able to mount samba shares hosted by my debian install. I was getting mount error 22.
> Upon discussing the problem on linux-cifs [1], it was discovered that the issue can be fixed by a patch available in samba versions 4.15 and later [2]. I can confirm that adding this patch to the debian 4.13 package fixes the issue too. Please add this patch to the package.
>
> [1] https://lore.kernel.org/linux-cifs/8ccad303-7489-d90a...@gmail.com/T/#t
> [2] https://git.samba.org/?p=samba.git;a=commitdiff;h=147dd9d58a429695a3b6c6e45c8b0eaafc67908a

As far as I can see, this fix is included in samba 4.16 which is currently in
testing and in bullseye-backports. Kernel 5.18 is not in bullseye.

I think you can use samba from bpo to fix this one. I don't have plans
to make another 4.13 in bullseye for now. And I don't really know what
do do with this bugreport which can already be closed since it is fixed
in testing...

Thanks,

/mjt

Julian Sikorski

unread,

Jul 11, 2022, 11:50:03 AM7/11/22

to

Am 11.07.22 um 17:31 schrieb Michael Tokarev:

Thanks for responding. As I am not familiar with Debian's update
policies, please excuse if these are obvious questions.
Are there plans to get samba 4.16 into bullseye-updates? Or will the fix
only be included in bookworm? While kernel 5.18 is not in bullseye yet,
we are specifically talking about client-server situation, meaning that
the client is not unlikely to be running to be a different OS than the
server. For me it is armbian on the server and fedora on the client. The
patch exposing the bug only got into 5.18 stable tree, not to the older
ones, so the issue is likely limited in scope at the moment. It might
become more prevalent as more clients upgrade the kernel.

Best regards,
Julian

Julian Sikorski

unread,

Jul 18, 2022, 2:10:03 AM7/18/22

to

Am 11.07.22 um 17:45 schrieb Julian Sikorski:

Looks like this issue is going to be fixed on the client side after all,
probably in 5.18.13:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.18/smb3-workaround-negprot-bug-in-some-samba-servers.patch
Please feel free to close this bug.

Best regards,
Julian