Comment 10 for bug 2049634

Revision history for this message
R. Diez (rdiezmail-ubuntu) wrote : Re: smb1: wsize blocks of bytes followed with binary zeros on copy, destroying data

About the comment "users with a custom wsize", note that I didn't set a custom wsize.

This is the script I am using to mount the SMB 1.0 shares:

https://github.com/rdiez/Tools/blob/master/MountWindowsShares/mount-windows-shares-sudo.sh

There is no wsize parameter there. I did write above that the wsize value I am seeing seems to be the default, and I don't recall having adjusted any such SMB / CIFS parameter anywhere on my systems.

About the comment "Most users will want to use the 6.2 HWE kernel until this is fixed", this is rather hard to do at the moment. If you install HWE (by means of linux-generic-hwe-22.04, which may be there by default), the system will not offer you a way to stay with 6.2. Under package linux-generic-hwe-22.04 you will find only one 5.15 and one 6.5 version now, so there is no easy way to go back to and stay with 6.2.

I asked about this in the "original description" of this bug report, which is now hidden under a link at the top of this report. As I got no answer, I investigated further, and this is how I blocked the 6.5 kernels on a critical PC I have:

echo -e "Package: linux-image*-6.5.*\nPin: release *\nPin-Priority: -1" | sudo tee /etc/apt/preferences.d/99-${USER}-prevent-upgrade-to-kernel-6.5.pref

This blocking is probably problematic. First of all, if a new kernel version like 6.6 is released, the block will no longer work. There is also no guarantee that the system will not download further 5.15 kernels and evict the 6.2 kernel for lack of space in the /boot partition, as there is now nothing that requires the 6.2 version (linux-generic-hwe-22.04 got automatically uninstalled upon applying the block above).

Furthermore, I also understand that 6.2 is (or will soon be) no longer supported. This is probably a shortcoming of choosing non "long term support" kernels for such HWE upgrades.