[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
@tjaalton what will happen to impish 5.13 and focal hwe-5.13? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
5.14.0-1023.25 seems to work fine.
I used the steps similar to
https://lore.kernel.org/io-uring/CABVffEM79CZ+4SW0+yP0+NioMX=shhoobcefbhqs6g6hex2...@mail.gmail.com/
cmake -DPLUGIN_{MROONGA,ROCKSDB,CONNECT,SPIDER,SPHINX,S3,COLUMNSTORE}=NO
-DWITH_URING=ON ../mariadb-server
make -j8
mysql-test/mtr --mysqld=--innodb_use_native_aio=1 --nowarnings --parallel=4
--force encryption.innochecksum{,} --mysqld=--innodb_io_capacity=5
--mysqld=--innodb_io_capacity_max=9
And it failed twice with 5.14.0-1022.24, while it finished twice on
5.14.0-1023.25
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/195
Title:
io_uring regression - lost write request
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.13 source package in Focal:
Confirmed
Status in linux-oem-5.13 source package in Focal:
Won't Fix
Status in linux-oem-5.14 source package in Focal:
Confirmed
Status in linux source package in Impish:
Confirmed
Status in linux-hwe-5.13 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
There's a regression with io_uring reported against 5.11-5.14 kernels,
see:
https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_-
ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b
From reading the thread and looking at the history in
linux-stable/linux-5.15.y,
I assume that Linux 5.15.3 is the first fully fixed version.
And 5.10 was not affected.
Sadly all other versions are EOL for kernel.org.
But ubuntu provides 5.11, 5.13 and 5.14 based kernels,
which most likely have the bug.
I'm reporting it against linux-hwe-5.13 as that's what I test on most systems,
but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
Thanks Timo for taking a look! ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07
Why is this commit not included here?
commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe
CommitDate: Wed Sep 1 12:35:30 2021 -0600
io-wq: split bounded and unbounded work into separate lists
We've got a few issues that all boil down to the fact that we have one
list of pending work items, yet two different types of workers to
serve them. This causes some oddities around workers switching type and
even hashed work vs regular work on the same bounded list.
Just separate them out cleanly, similarly to how we already do
accounting of what is running. That provides a clean separation and
removes some corner cases that can cause stalls when handling IO
that is punted to io-wq.
Fixes: ecc53c48c13d ("io-wq: check max_worker limits if a worker
transitions bound state")
Signed-off-by: Jens Axboe
Other io_uring related patches where backported here even without being
in linux-stable/linux-5.14.y. So why is this missing?
See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1956720
Title:
Focal update: upstream stable patchset 2022-01-07
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Incomplete
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2022-01-07
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955070] Re: Impish update: upstream stable patchset 2021-12-16
Why is this commit not included here?
commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe
CommitDate: Wed Sep 1 12:35:30 2021 -0600
io-wq: split bounded and unbounded work into separate lists
We've got a few issues that all boil down to the fact that we have one
list of pending work items, yet two different types of workers to
serve them. This causes some oddities around workers switching type and
even hashed work vs regular work on the same bounded list.
Just separate them out cleanly, similarly to how we already do
accounting of what is running. That provides a clean separation and
removes some corner cases that can cause stalls when handling IO
that is punted to io-wq.
Fixes: ecc53c48c13d ("io-wq: check max_worker limits if a worker
transitions bound state")
Signed-off-by: Jens Axboe
I guess because it was added before v5.15 final, but it's critical to have,
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195
** Changed in: linux (Ubuntu Impish)
Status: Fix Committed => Incomplete
--
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/1955070
Title:
Impish update: upstream stable patchset 2021-12-16
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Impish:
Incomplete
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-12-16
Ported from the following upstream stable releases:
v5.10.81, v5.14.21, v5.15.4
from git://git.kernel.org/
Note: upstream stable v5.14 has now reached EOL, as of
v5.14.21.
fortify: Explicitly disable Clang support
block: Add a helper to validate the block size
loop: Use blk_validate_block_size() to validate block size
bootconfig: init: Fix memblock leak in xbc_make_cmdline()
net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings
parisc/entry: fix trace test in syscall exit path
PCI/MSI: Destroy sysfs before freeing entries
PCI/MSI: Deal with devices lying about their MSI mask capability
PCI: Add MSI masking quirk for Nvidia ION AHCI
erofs: remove the occupied parameter from z_erofs_pagevec_enqueue()
erofs: fix unsafe pagevec reuse of hooked pclusters
perf/core: Avoid put_page() when GUP fails
thermal: Fix NULL pointer dereferences in of_thermal_ functions
selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage
KVM: Fix steal time asm constraints
Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device.
Bluetooth: btusb: Add support for TP-Link UB500 Adapter
string: uninline memcpy_and_pad
btrfs: introduce btrfs_is_data_reloc_root
btrfs: zoned: add a dedicated data relocation block group
btrfs: zoned: only allow one process to add pages to a relocation inode
btrfs: zoned: use regular writes for relocation
btrfs: check for relocation inodes on zoned btrfs in should_nocow
btrfs: zoned: allow preallocation for relocation inodes
UBUNTU: upstream stable to v5.10.81, v5.14.21, v5.15.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955070/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
apport-collect is not useful, someone needs to read the initial comment and backport the existing fixes from 5.15.y ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Confirmed Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] [NEW] io_uring regression - lost write request
Public bug reported: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b >From reading the thread and looking at the history in >linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Package changed: samba (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848013] Re: [needs-packaging] liburing package needed for >= 5.1 kernels
I changed the layout to match the libaio packages and my changes were just merged to the upstream branch at http://git.kernel.dk/cgit/liburing/ And liburing-0.4 should be tagged shortly. -- 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/1848013 Title: [needs-packaging] liburing package needed for >= 5.1 kernels Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1848013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848013] Re: liburing package missing for >= 5.1 kernels
I'm not sure if this belongs to the "linux" or "libaio" package maintainers. ** Also affects: libaio (Ubuntu) Importance: Undecided Status: New -- 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/1848013 Title: liburing package missing for >= 5.1 kernels Status in libaio package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/1848013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848008] Re: eoan needs iproute2 v5.3.0
It's mainly about new features, so this isn't urgent. In general I think there should be some kind of process that makes sure certain packages are kept in sync with the kernel version. It's not as strict as with the linux-tools packages, but some kind of coordination with the kernel team would be good to have matching iproute2 package, maybe also -hwe and -hwe-edge versions of it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1848008 Title: eoan needs iproute2 v5.3.0 Status in iproute2 package in Ubuntu: New Bug description: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1848008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848013] Re: liburing package missing for >= 5.1 kernels
There's no real but just a missing userspace library for a kernel feature ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1848013 Title: liburing package missing for >= 5.1 kernels Status in linux package in Ubuntu: Confirmed Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848013] [NEW] liburing package missing for >= 5.1 kernels
Public bug reported: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1848013 Title: liburing package missing for >= 5.1 kernels Status in linux package in Ubuntu: Incomplete Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848008] [NEW] eoan needs iproute2 v5.3.0
Public bug reported: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1848008 Title: eoan needs iproute2 v5.3.0 Status in iproute2 package in Ubuntu: New Bug description: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1848008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543980] Re: Kernel 3.13.0-77 crashes (can be triggered by Samba)
Are the 3.13.0-84.128 packages available somewhere for testing? -- 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/1543980 Title: Kernel 3.13.0-77 crashes (can be triggered by Samba) Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Bug description: Ubuntu 14.04.3 LTS After updating to kernel 3.13.0-77 system crashes. First, network dies, then the whole system. There are several kernel crashes in the logs. --- snip --- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Wed Feb 10 09:20:35 2016 Failure: oops OopsText: BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908] --- snap --- Followed by kernel stack traces. After some investigation, it turned out that the crash can be triggered by Samba. It's easily reproducible by running the following commands in the Samba master branch: ./configure.developer TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 TESTS="samba3.raw.composite" Downgrading to kernel 3.13.0-76 solves this problem. Please let me know if we can provide more information or help testing. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543980] Re: Kernel 3.13.0-77 crashes (can be triggered by Samba)
Thanks Philipp! I just hope to trigger some reaction from the ubuntu maintainers in order get a usable kernel more than two week after breaking it. -- 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/1543980 Title: Kernel 3.13.0-77 crashes (can be triggered by Samba) Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: Ubuntu 14.04.3 LTS After updating to kernel 3.13.0-77 system crashes. First, network dies, then the whole system. There are several kernel crashes in the logs. --- snip --- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Wed Feb 10 09:20:35 2016 Failure: oops OopsText: BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908] --- snap --- Followed by kernel stack traces. After some investigation, it turned out that the crash can be triggered by Samba. It's easily reproducible by running the following commands in the Samba master branch: ./configure.developer TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 TESTS="samba3.raw.composite" Downgrading to kernel 3.13.0-76 solves this problem. Please let me know if we can provide more information or help testing. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543980] Re: Kernel 3.13.0-77 crashes (can be triggered by Samba)
Ping! -- 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/1543980 Title: Kernel 3.13.0-77 crashes (can be triggered by Samba) Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: Ubuntu 14.04.3 LTS After updating to kernel 3.13.0-77 system crashes. First, network dies, then the whole system. There are several kernel crashes in the logs. --- snip --- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Wed Feb 10 09:20:35 2016 Failure: oops OopsText: BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908] --- snap --- Followed by kernel stack traces. After some investigation, it turned out that the crash can be triggered by Samba. It's easily reproducible by running the following commands in the Samba master branch: ./configure.developer TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 TESTS="samba3.raw.composite" Downgrading to kernel 3.13.0-76 solves this problem. Please let me know if we can provide more information or help testing. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543980] Re: Kernel 3.13.0-77 crashes (can be triggered by Samba)
https://forge.univention.org/bugzilla/show_bug.cgi?id=40558#c11 Indicates that commit 51cd3ed4c41b3895869925b99dd95a704bd2c91a unix: avoid use-after-free in ep_remove_wait_queue should be reverted in order to avoid this regression. Can we please get some progress on this? -- 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/1543980 Title: Kernel 3.13.0-77 crashes (can be triggered by Samba) Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: Ubuntu 14.04.3 LTS After updating to kernel 3.13.0-77 system crashes. First, network dies, then the whole system. There are several kernel crashes in the logs. --- snip --- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Wed Feb 10 09:20:35 2016 Failure: oops OopsText: BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908] --- snap --- Followed by kernel stack traces. After some investigation, it turned out that the crash can be triggered by Samba. It's easily reproducible by running the following commands in the Samba master branch: ./configure.developer TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 TESTS="samba3.raw.composite" Downgrading to kernel 3.13.0-76 solves this problem. Please let me know if we can provide more information or help testing. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
