** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2049634
Title:
smb: wsize blocks of bytes followed with
Hi R. Diez,
The 6.5.0-27-generic kernel just got released, so it should make its way
to an archive mirror near you in the next couple of hours, and should
solve your SMB 1 issue. The 6.8 kernel should be good to go when you get
it in the next couple of months.
Let us know if you encounter any
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If
This bug was fixed in the package linux - 6.5.0-27.28
---
linux (6.5.0-27.28) mantic; urgency=medium
* mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)
* Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
-
Performing verification for mantic.
I started two VMs. A jammy VM for the cifs server, and a mantic VM, for
the client.
I set the jammy VM up as per the testcase.
I set the mantic VM up as per the testcase.
The mantic VM uses kernel 6.5.0-25-generic from -updates.
$ uname -rv
6.5.0-25-generic
The fix for noble should be present in 6.8.0-16-generic and later.
Marking as Fix committed for Noble.
--
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/2049634
Title:
smb: wsize blocks of
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
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/2049634
Title:
smb: wsize blocks of bytes followed with
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
Reviews from Senior Kernel Team Members:
ACK 1
https://lists.ubuntu.com/archives/kernel-team/2024-February/149051.html
ACK 2
https://lists.ubuntu.com/archives/kernel-team/2024-February/149061.html
Applied
https://lists.ubuntu.com/archives/kernel-team/2024-February/149119.html
Will let you know
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
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/2049634
Title:
smb: wsize blocks of bytes followed with
Submitted the patch as SRU to mantic. Noble will pick it up when the
kernel team pulls in 6.8-rc5.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149042.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149043.html
--
You received this bug
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/2049634
+
[Impact]
Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
set will see data destruction when copying files from their systems onto
- a cifs smb 1.0 mount.
+ a cifs smb mount.
wsize
Hi R. Diez,
The patch was merged upstream in 6.8-rc5:
commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
Author: Steve French
Date: Tue Feb 6 16:34:22 2024 -0600
Subject: smb: Fix regression in writes when non-standard maximum write size
negotiated
Link:
The patch does seem like a step forwards, but the warning messages are
still easy to miss and misleading. I would rather abort the connection
than risking a non-functional connection (in the case of the round-up I
described with PAGE_SIZE = 64 KiB). I do not think it is a good idea
either to
Hi R. Diez,
Steve posted a new patch [1] that also rounds the wsize down when specified on
the mount command line, just as we wanted:
[1] https://lore.kernel.org/linux-
cifs/CAH2r5mvPz2CUyKDZv_9fYGu=9L=3uime7xajgbbu+if8ch8...@mail.gmail.com/
I tested it, and it works great.
$ sudo mount -t
I had some difficulty with the test kernel, because the installation
command wanted to remove the running kernel, so I got a warning about
it. I think there was some kind of conflict with the normal 6.5.0-15
kernel. In the meantime, the kernel has been upgraded to 6.5.0-17, so I
removed all older
Thanks, I'll test the new kernel over the weekend.
--
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/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros on copy,
Hi R. Diez,
You have probably been following the chatter on the upstream mailing list
discussion. I initially thought the patch didn't fix the issue, as when I mount
with wsize=16850, the issue still occurs [1], but it seems that the intent of
the patch is to only correct when the server
** Summary changed:
- smb1: wsize blocks of bytes followed with binary zeros on copy, destroying
data
+ smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
19 matches
Mail list logo
