Hi everyone,
Thanks for helping to test the test kernel, and I am glad that it fixes
the issue.
I have written a SRU template and have set it as the description of the
bug.
I have submitted the revert to the Kernel team mailing list for SRU:
Cover Letter:
Hi everyone,
Thanks for helping to test the test kernel, and I am glad that it fixes
the issue.
I have written a SRU template and have set it as the description of the
bug.
I have submitted the revert to the Kernel team mailing list for SRU:
Cover Letter:
** Summary changed:
- Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu"
(aarch64).
+ cifs: Copying file to same directory results in page fault
** Description changed:
- Remote filesystems
** Summary changed:
- Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu"
(aarch64).
+ cifs: Copying file to same directory results in page fault
** Description changed:
- Remote filesystems
Hi Axel,
Sorry about you getting spammed about all these verifications. The robot
that posts these messages looks for the Launchpad bug number in the
package changelogs, and just makes a post for every package it sees it
in.
You might not know, but Ubuntu has slightly over 100 kernels these
Hi Axel,
Sorry about you getting spammed about all these verifications. The robot
that posts these messages looks for the Launchpad bug number in the
package changelogs, and just makes a post for every package it sees it
in.
You might not know, but Ubuntu has slightly over 100 kernels these
) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060919
Title:
Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-27-generic #28-Ubunt
) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2060919
Title:
Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-2
** 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
h:
commit 9dc02a5b7540d18a69bcbaf8f4fa428e32075b4b (HEAD -> lp2060919-test)
Author: Matthew Ruffell
Date: Fri Apr 19 17:25:48 2024 +1200
Revert "cifs: fix flushing folio regression for 6.1 backport"
This reverts commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1.
dif
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros
h:
commit 9dc02a5b7540d18a69bcbaf8f4fa428e32075b4b (HEAD -> lp2060919-test)
Author: Matthew Ruffell
Date: Fri Apr 19 17:25:48 2024 +1200
Revert "cifs: fix flushing folio regression for 6.1 backport"
This reverts commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1.
dif
Hello,
I can't actually reproduce the issue, I seem to be missing something.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
server min protocol = NT1
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
Hello,
I can't actually reproduce the issue, I seem to be missing something.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
server min protocol = NT1
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
Hi everyone,
5.15.0-105-generic has been released to -updates now. It fixes the cifs
issue.
https://launchpad.net/ubuntu/+source/linux/5.15.0-105.115
Please let us know if you find any more issues.
Thanks,
Matthew
--
You received this bug notification because you are a member of Kernel
Hi everyone,
5.15.0-105-generic has been released to -updates now. It fixes the cifs
issue.
https://launchpad.net/ubuntu/+source/linux/5.15.0-105.115
Please let us know if you find any more issues.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Performing verification for Focal.
I started two VMs, one Jammy, which is the nfs server, and one Focal,
which is the client. I used the instructions in the testcase sections of
this bug, and also bug 2049262.
The Focal VM has nfs-common 1:1.3.4-2.5ubuntu3.6 from -updates.
Let's try the
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received this bug notification because you are a member of Ubuntu
Performing verification for Jammy.
I started two Jammy VMs. One is a server and the other a client.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read
Performing verification for Jammy.
I started two Jammy VMs. One is a server and the other a client.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read
Hi everyone, the fix will also be available for Focal, as part of it
getting the Jammy HWE kernel. It will be released at the same time as
Jammy's kernel is released.
We got the notification above that the kernel should be in -proposed,
but I have been refreshing -proposed all day and the kernel
Hi everyone, the fix will also be available for Focal, as part of it
getting the Jammy HWE kernel. It will be released at the same time as
Jammy's kernel is released.
We got the notification above that the kernel should be in -proposed,
but I have been refreshing -proposed all day and the kernel
I think we should be pointing it back to paste.ubuntu.com, because our
existing users expect it will go to a distro owned pastebin, and we
should remain consistent.
I am also all for keeping user data on IS controlled assets, we don't
exactly know who controls dpaste, and if they parse dmesg or
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of
5.15.0-103-generic with the fix.
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115
It should be available in -proposed soon, the Kernel Team are still
rebuilding all the
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of
5.15.0-103-generic with the fix.
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115
It should be available in -proposed soon, the Kernel Team are still
rebuilding all the
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Come over to bug 2060780 and talk about it with us there.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Come over to bug 2060780 and talk about it with us there.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received
Hi everyone,
5.15.0-104-generic just hit jammy-proposed a couple minutes ago. It
isn't available for focal users yet.
Can someone please test 5.15.0-104-generic on jammy and let me know if
it fixes the issue? Thanks.
Instructions to Install (On a mantic system):
1) cat << EOF | sudo tee
Hi everyone,
5.15.0-104-generic just hit jammy-proposed a couple minutes ago. It
isn't available for focal users yet.
Can someone please test 5.15.0-104-generic on jammy and let me know if
it fixes the issue? Thanks.
Instructions to Install (On a mantic system):
1) cat << EOF | sudo tee
Thanks for pointing out the missing patch Heitor. I was indeed missing
it.
Please review and sponsor the V2 debdiff.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059197
Title:
Sanity testing the test package:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test
nfs-common 1:1.3.4-2.5ubuntu3.6+lp2059197v20240411b1
Testcase for this bug, i.e. the regression.
$ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt
mount.nfs4: timeout set for Thu Apr 11
Hi everyone,
Reading:
https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/
It seems the issue was introduced in
commit 33eae65c6f49770fec7a662935d4eb4a6406d24b
Author: Paulo Alcantara
Date: Wed Dec 13 12:25:57 2023 -0300
Subject: smb: client: fix OOB in
Hi everyone,
Reading:
https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/
It seems the issue was introduced in
commit 33eae65c6f49770fec7a662935d4eb4a6406d24b
Author: Paulo Alcantara
Date: Wed Dec 13 12:25:57 2023 -0300
Subject: smb: client: fix OOB in
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Tags added: seg
--
You received this bug notification because you
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Tags added: seg
--
You received this bug notification because you
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Hi everyone, I will provide updates on the other bug 2060780.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You
Attached is a new debdiff which includes the missing patch. I did
another look upstream, but I think we are okay now.
** Patch added: "Debdiff for nfs-utils on Focal V2"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5763564/+files/lp2059197_focal_V2.debdiff
**
** Patch removed: "Debdiff for nfs-utils on Focal"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5761398/+files/lp2059197_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
Hi Jeff,
Again, I apologise for introducing this regression, but we are on our
way to getting this fixed.
The fixes are:
commit 1e3ca7fe199531a372bb8e1c1033d8973097be50
Author: NeilBrown
Date: Wed Jul 26 13:47:42 2017 -0400
Subject: mount: move handling of "-t nfs4" into nfs_nfs_version()
Attached is a debdiff for Focal which fixes this issue.
** Summary changed:
- Issue with nfs4.0 mounts after upgrade to 3.6
+ Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
** Summary changed:
- Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used
Fix Released
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => In Progress
** Changed in: nfs-utils (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nfs-utils (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notif
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug not
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug not
Thank you for the help sorting autopkgtests Mauricio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost
Thank you for the help sorting autopkgtests Mauricio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option is present
or
Performing verification for Jammy
I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs-
client.
The client is using coreutils 8.32-4.1ubuntu1.1 from -updates.
$ apt-cache policy coreutils | grep Installed
Installed: 8.32-4.1ubuntu1.1
I set up the nfs server and autofs
Performing verification for Jammy
I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs-
client.
The client is using coreutils 8.32-4.1ubuntu1.1 from -updates.
$ apt-cache policy coreutils | grep Installed
Installed: 8.32-4.1ubuntu1.1
I set up the nfs server and autofs
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attempting to display
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix
Performing verification for Jammy.
I started a fresh VM, with 5.15.0-101-generic from updates. I ran the
following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt
mkpart primary
Performing verification for Jammy.
I started a fresh VM, with 5.15.0-101-generic from updates. I ran the
following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt
mkpart primary
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes
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
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros on
** 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
Hi Rainer.
I think we will leave it as is. Keep using v4.0 for now, and you should
be fine.
I'll close the bug.
Andreas, I will remove regression-update if that is okay with you.
Thanks,
Matthew
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => Invalid
** Changed in: nfs-utils
Hi Rainer,
Thanks for trying that out, and it is great to hear that v4.0 works for
you, and you added it to your /etc/fstab as a good workaround for the
meantime.
Are you interested in debugging why your system hangs when trying v4.2
and v4.1? or do you want to leave it there? 4.0 will keep
I think the fix was included in 5.15.149 upstream;
https://lwn.net/Articles/963359/
Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
The kernel team have just pulled in 5.15.148, and haven't started on
149. They will likely get to it in the next week or so.
Thanks,
Matthew
I think the fix was included in 5.15.149 upstream;
https://lwn.net/Articles/963359/
Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
The kernel team have just pulled in 5.15.148, and haven't started on
149. They will likely get to it in the next week or so.
Thanks,
Matthew
Hi Rainer,
Thanks for the screenshots.
The updated package changes how the '-o vers=4' parameter works. The old
/ wrong behaviour would always use nfs v4.0 no matter what. All other
nfs-common versions apart from the version in focal would try v4.2, then
if that didn't work, then v4.1, and then
Hi Rainer,
I developed the nfs-utils update of 1:1.3.4-2.5ubuntu3.6, and I am very
interested to hear more about the possible regression.
The intention was to fix version negotiation when using the '-t nfs4' or
'-o vers=4' parameters in your mount command. You can find more about it
here:
Yes, 6.5.0-25-generic is available for both jammy and mantic systems. It
was released earlier this week.
Is anyone able to try it out and let me know if it fixes the issue?
Thanks.
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug
Yes, 6.5.0-25-generic is available for both jammy and mantic systems. It
was released earlier this week.
Is anyone able to try it out and let me know if it fixes the issue?
Thanks.
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Hi cipricus,
This is a security feature working as intended. Ubuntu recently decided
to disable unprivileged access to user namespaces. You can find more
information it about it here:
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Hi cipricus,
This is a security feature working as intended. Ubuntu recently decided
to disable unprivileged access to user namespaces. You can find more
information it about it here:
Hi Sly,
We do actually test as many dkms builds as we can. Well, mainly all the
kernel modules present in the Ubuntu archive, like evdi-dkms.
The trouble starts when you get dkms sources from other places that we
don't know about, like the DisplayLink installer that I linked above.
You, me, and
Hi Sly,
We do actually test as many dkms builds as we can. Well, mainly all the
kernel modules present in the Ubuntu archive, like evdi-dkms.
The trouble starts when you get dkms sources from other places that we
don't know about, like the DisplayLink installer that I linked above.
You, me, and
Hi Sly,
Your evdi kernel module for DisplayLink docks failed to compile. It
likely couldn't generate your initramfs, leaving your 6.5.0-21-generic
not able to boot.
Your logs say its trying to build version 1.11.0:
ERROR (dkms apport): binary package for evdi: 1.11.0 not found
Error! Bad return
Hi Sly,
Your evdi kernel module for DisplayLink docks failed to compile. It
likely couldn't generate your initramfs, leaving your 6.5.0-21-generic
not able to boot.
Your logs say its trying to build version 1.11.0:
ERROR (dkms apport): binary package for evdi: 1.11.0 not found
Error! Bad return
Hi everyone,
@angros47, yes, this issue looks to be what you are experiencing here.
https://bugs.archlinux.org/task/80064 mentions that the issue was
introduced in:
commit aa3998dbeb3abce63653b7f6d4542e7dcd022590
Author: Damien Le Moal
Date: Sat Aug 26 09:43:39 2023 +0900
Subject: ata:
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
Performing verification for Focal.
I set up a Jammy VM to be the nfs server, using the instructions in the
SRU template.
$ sudo cat /proc/fs/nfsd/versions
-2 -3 +4 -4.0 +4.1 +4.2
4.0 is not allowed, but 4.1 and 4.2 are.
I then started a fresh Focal VM, and installed nfs-common
Hi everyone,
@angros47, yes, this issue looks to be what you are experiencing here.
https://bugs.archlinux.org/task/80064 mentions that the issue was
introduced in:
commit aa3998dbeb3abce63653b7f6d4542e7dcd022590
Author: Damien Le Moal
Date: Sat Aug 26 09:43:39 2023 +0900
Subject: ata:
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
I have been running the test packages on AWS with the reproducer running
for 20 days now, and they are still running great. The change to direct
IO really does fix this issue, and my testing has removed any and all
concerns of causing a regression.
Previously focal wouldn't last more than 20
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:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148896.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148897.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
could cause it
to page fault and subsequently crash, resulting in downtime.
The only workaround will be to disable all profiling tools until a fix
is available.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Mantic)
Importance: Medium
I tried on a random lab machine with 2x HP MM0500GBKAK disks.
With 6.5.0-18-generic:
Before:
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
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
Hi everyone,
Would it be possible if you could try 6.8-rc4 mainline to see if the
issue is fixed there?
https://kernel.ubuntu.com/mainline/v6.8-rc4/
$ wget
https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-headers-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb
$ wget
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
--
You
*** This bug is a duplicate of bug 2053041 ***
https://bugs.launchpad.net/bugs/2053041
Hi Alex, please come over to bug 2053041 and we can try figure this out.
Thanks!
** This bug has been marked a duplicate of bug 2053041
Issue when shutting down computer: internal hard drive is not shut
** Description changed:
- Release: 22.04.3 LTS
- coreutils 8.32-4.1ubuntu1
+ [Impact]
- ls triggers unwanted mounts of autofs filesystems
+ Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
+ --ghost in the auto.master file, or browse_mode=yes in autofs.conf will
+ lead to the
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
1 - 100 of 2021 matches
Mail list logo
