This bug was fixed in the package linux - 5.15.0-105.115
---------------
linux (5.15.0-105.115) jammy; urgency=medium
* jammy/linux: 5.15.0-105.115 -proposed tracker (LP: #2061372)
* Jammy update: v5.15.149 upstream stable release (LP: #2059014) // CIFS
stopped working/is unstable with kernel update to 5.15.0-102.112
(LP: #2060780)
- smb3: Replace smb2pdu 1-element arrays with flex-arrays
linux (5.15.0-103.113) jammy; urgency=medium
* jammy/linux: 5.15.0-103.113 -proposed tracker (LP: #2059683)
* Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
* Remove getabis scripts (LP: #2059143)
- [Packaging] Remove getabis
* CVE-2023-24023
- Bluetooth: Add more enc key size check
* CVE-2023-52600
- jfs: fix uaf in jfs_evict_inode
* Jammy update: v5.15.149 upstream stable release (LP: #2059014) //
CVE-2023-52603
- UBSAN: array-index-out-of-bounds in dtSplitRoot
* CVE-2024-26581
- netfilter: nft_set_rbtree: skip end interval element from gc
-- Roxana Nicolescu <[email protected]> Mon, 15 Apr 2024
10:38:15 +0200
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-24023
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52600
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52603
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26581
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
Hi,
updated some Ubuntu 22.04 systems to lastest available state this
morning, which caused CIFS mounts (from various fileservers) to stop
working. Kernel was updated to version 5.15.0-102-generic.
I can mount the shares without problems (mount -t cifs), but then, df for
example tells me: df: /mnt: Resource temporarily unavailable.
I'm able to list and browse all the files, but accessing them (even readonly)
is very unstable. Sometimes it works and sometimes it just gives me i/o errors.
Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the
problem and everything works again as expected.
Seems like some bug has been implemented in 5.15.0-102-generic...
To reproduce the problem, I started a while loop on one server to
write to some file on a specific mounted CIFS share and read it from
another one
root@<hostname1>:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt;
sleep 1 ; done
-bash: /mnt/hallo.txt: Input/output error
-bash: /mnt/hallo.txt: Input/output error
^C
root@<hostname2>:~$ tail -f /mnt/hallo.txt
Tue Apr 9 04:10:52 PM CEST 2024 hallo
Tue Apr 9 04:10:53 PM CEST 2024 hallo
Tue Apr 9 04:10:54 PM CEST 2024 hallo
Tue Apr 9 04:10:55 PM CEST 2024 hallo
Tue Apr 9 04:10:56 PM CEST 2024 hallo
Tue Apr 9 04:10:57 PM CEST 2024 hallo
Tue Apr 9 04:10:58 PM CEST 2024 hallo
Tue Apr 9 04:10:59 PM CEST 2024 hallo
Tue Apr 9 04:11:00 PM CEST 2024 hallo
Tue Apr 9 04:11:01 PM CEST 2024 hallo
tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling:
Resource temporarily unavailable
Tue Apr 9 04:11:04 PM CEST 2024 hallo
Tue Apr 9 04:11:05 PM CEST 2024 hallo
Tue Apr 9 04:11:06 PM CEST 2024 hallo
Tue Apr 9 04:11:07 PM CEST 2024 hallo
Tue Apr 9 04:11:08 PM CEST 2024 hallo
Tue Apr 9 04:11:09 PM CEST 2024 hallo
Tue Apr 9 04:11:10 PM CEST 2024 hallo
While doing this, both servers tell me, the resource is unavailable
root@<hostname1>:~# df -h /mnt
df: /mnt: Resource temporarily unavailable
root@<hostname2>:~$ df -h /mnt
df: /mnt: Resource temporarily unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
