I have kept one corrupt text file (which I cannot post here), and I ran
this command on it:
grep --perl-regexp --text --byte-offset '\x00{3900}' my-corrupt-
text-file
The file has 2 blocks of binary zeros which should not be there. Their
offsets are random, but both blocks are exactly 3900 bytes long. I had
expected some power of 2 like 1024.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
SMB 1 broken in kernel 6.5.0.14.14~22.04.7
Status in linux-hwe-6.5 package in Ubuntu:
New
Bug description:
Hi all:
I upgraded my Ubuntu yesterday and automatically got the newer Linux
Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was
running kernel version 6.2 .
I still have a legacy system on the network using SMB protocol version
1.0.
With the new kernel version, copying files does not work reliably
anymore. Some random byte blocks in the destination files are
overwritten with binary zeros. It happens quite often.
This is not the first time the Linux guys temporarily break SMB protocol
version 1.0, see for example this bug report of mine:
https://bugs.launchpad.net/ubuntu/+bug/2033732
I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it
lists just 2 versions:
6.5.0.14.14~22.04.7 (jammy-updates)
5.15.0.25.27 (jammy)
Is there a way to go back to the latest 6.2 kernel version?
How do I prevent Ubuntu from upgrading to 6.5 next time around? I have
searched the Internet, but I haven't
found yet a usable answer. I don't want to go back all the way to Kernel 5.15
if I can avoid it.
Thanks in advance,
rdiez
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049634/+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
