Attached is a V3 debdiff for Focal that fixes this issue
** Patch removed: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
** Patch removed: "debdiff for tracker-miners on
Attached is a V3 debdiff for Jammy that fixes this issue
** Patch added: "Debdiff for tracker-miners on Jammy V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679385/+files/lp1779890_jammy_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Focal that fixes this issue
** Patch removed: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
** Patch removed: "debdiff for tracker-miners on
Hi Paul,
Yes, if we look at https://kernel.ubuntu.com/sru/dashboards/web/kernel-
stable-board.html under 2023.05.15 SRU cycle, under Jammy it has linux-
hwe-5.19 5.19.0-44.45~22.04.1 sitting in -proposed, so yes, this fix
will be made available to kinetic and jammy-hwe.
Saying that, the
Hi Paul,
Thanks for verifying that linux-nvidia kernel, but for the future, you
don't need to worry about verifying each and every kernel series. These
days, the kernel team maintains over 100 kernel variants, and it is
simply impossible to check them all.
We just check the primary ones, e.g.
urces ready to go and will
> upload them tomorrow. Thanks again for the help!
>
> Cheers,
> Heitor
>
> On Tue, May 30, 2023 at 2:16 AM Matthew Ruffell
> wrote:
>>
>> Hi everyone,
>>
>> Can you please review and sponsor adsys in LP #2020834?
>>
&
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2020834
Title:
Properly convert DNS names with '-' characters to valid dbus object
paths
Status in adsys
Hi everyone,
Can you please review and sponsor adsys in LP #2020834?
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020834
The package unfortunately uses d/source/format of "3.0 (native)" over
"3.0 (quilt)", so the debdiffs are created in native form not using
quilt.
If this is
Hi everyone,
Can you please review and sponsor needrestart for LP2020826?
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2020826
Its pretty self explanatory. Test packages work great.
Thanks!
Matthew
ps, I will start my sru-developer application soon...
--
Mailing list:
Attached is a debdiff for Jammy. Note the package uses a
debian/source/format of "3.0 (native)", and I did not use quilt to
prepare the patch.
** Patch added: "Debdiff for adsys on Jammy"
Attached is a debdiff for Focal. Note the package uses a
debian/source/format of "3.0 (native)", and I did not use quilt to
prepare the patch.
** Patch added: "Debdiff for adsys on Focal"
Attached is a debdiff for Kinetic. Note the package uses a
debian/source/format of "3.0 (native)", and I did not use quilt to
prepare the patch.
** Patch added: "Debdiff for adsys on Kinetic"
ffects: adsys (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: adsys (Ubuntu Jammy)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: adsys (Ubuntu Kinetic)
Importa
Its not necessary Loic, linux-hwe is a derivative of the kinetic kernel,
and it will be automatically built and pushed to -proposed in due
course, likely over the next few days.
It will be a part of the 5.19.0-44 HWE kernel. I'll keep an eye on it, I
don't think the HWE kernel is moving to the
** No longer affects: linux-hwe-5.19 (Ubuntu)
** No longer affects: linux-hwe-5.19 (Ubuntu Jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2007001
Title:
vmwgfx fails to
Wonderful! Thank you very much Paul for testing!
This will slowly work its way through the Kernel SRU process. We should
see a release to -updates the week of 5th June, as per
https://kernel.ubuntu.com/, give or take a few days if any CVEs turn up.
--
You received this bug notification because
** Patch removed: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
** Patch removed: "Debdiff for tracker-miners fix on Kinetic"
** Patch removed: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
** Patch removed: "Debdiff for tracker-miners fix on Kinetic"
Hi everyone,
Could you please review and sponsor tracker-miners in the below
Launchpad bug for Denison and I? We have been working on this for a
while, and we finally have the right service ordering in place.
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890
Thanks,
Matthew
Hi everyone,
I have submitted the revert to the Kernel Team for SRU:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2023-April/138908.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2023-April/138909.html
The next step is for the kernel team to review the patch, and for
** Summary changed:
- Blank console display with aarch64 kernel 5.19.0-31
+ vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
** Description changed:
- Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion
- 13.0.1 on Apple Silicon_ from 5.19.0-29 to
Hi everyone,
I have built a test kernel based on the current 5.19.0-38-generic kernel for
both Kinetic and Jammy HWE. It has the below patch reverted:
commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
Author: Thomas Zimmermann
Date: Mon Jul 18 09:23:18 2022 +0200
Subject: video/aperture:
Attached is a v2 debdiff for Focal, after Denison correctly pointed out
that I was missing a patch.
** Description changed:
[ Impact ]
The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active
Attached is a v2 debdiff for Focal, after Denison correctly pointed out
that I was missing a patch.
** Description changed:
[ Impact ]
The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active
hanged in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.
*** This bug is a duplicate of bug 2007001 ***
https://bugs.launchpad.net/bugs/2007001
Hi Zack,
Thanks for the report and the link. I'll get a test kernel building with
a revert and we can get some community users to try it out.
I'll post it in bug 2007001 instead, the existing bug, and
Attached is a v2 debdiff for kinetic. Again, minor changes, corrected
version, dep3 tags.
** Patch added: "debdiff for tracker-miners on kinetic"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663489/+files/lp1779890_kinetic_v2.debdiff
--
You received
Attached is a v2 debdiff for kinetic. Again, minor changes, corrected
version, dep3 tags.
** Patch added: "debdiff for tracker-miners on kinetic"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663489/+files/lp1779890_kinetic_v2.debdiff
--
You received
Attached is a v2 debdiff for Jammy. Very minor changes, corrected
version, tidied up dep3 tags.
** Patch added: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
--
You received
Attached is a v2 debdiff for Jammy. Very minor changes, corrected
version, tidied up dep3 tags.
** Patch added: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
--
You received
Attached is a debdiff for Focal.
** Patch added: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
Attached is a debdiff for Focal.
** Patch added: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Description changed:
[ Impact ]
- The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active Directory
servers.
+
+ The KRB5CCNAME environment variable points to the Kerberos ticket of the
+ current
** Description changed:
[ Impact ]
- The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active Directory
servers.
+
+ The KRB5CCNAME environment variable points to the Kerberos ticket of the
+ current
cal)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubun
cal)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad
** Changed in: tracker-miners (Ubuntu Jammy)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Kinetic)
** Changed in: tracker-miners (Ubuntu Jammy)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Kinetic)
Hi Christian, Alfredo,
5.4.0-146-generic was released yesterday with a fix for the NFS
regression, and it should have less bandwidth consumption than
5.4.0-144-generic.
There is still some reports that it still has higher NFS requests than
before the regression was introduced, so please chime in
Hi William.
The libunwind SRU for Bionic and Focal have now been released to
-updates. Their versions are 1.2.1-8ubuntu0.1 for Bionic, and
1.2.1-9ubuntu0.1 for Focal.
I just want to apologise for the significant delay in getting libunwind
released. It really was a exceptional amount of time, and
Performing verification for Jammy.
I started a fresh Jammy VM, and installed 5.15.0-67-generic from
-updates.
I appended apparmor=0 to GRUB_CMDLINE_LINUX_DEFAULT, updated grub, and
rebooted.
>From there, I installed auditd, and stress-ng. I edited
/etc/audit/rules.d/audit.rules to include:
-a
Performing verification for Focal.
The customer in question installed 5.4.0-145-generic to their busy
production Kubernetes cluster, and have had no issues in the week and a
half the kernel has been running for. Before, they would suffer
deadlocks three or four times a day, so the kernel in
Performing verification for Bionic
I started a fresh VM with 4.15.0-206-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.
I ran btrfs/154 with the following results:
# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 bionic-xfs
Performing verification for Focal
I started a fresh VM with 5.4.0-144-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.
I ran btrfs/154 with the following results:
# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 focal-xfs
Hi Alfredo,
Do you happen to use NFSv3 in your environment? There was a regression
in 5.4.0-144-generic that cased a massive spike in ACCESS requests being
made, which could explain low performance.
bug 2009325
Thanks,
Matthew
--
You received this bug notification because you are a member of
** Tags added: seg
--
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/2009325
Title:
NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Status in linux package in Ubuntu:
Hi JianlinLV,
I tried the latest 5.15.0-60-generic kernel from -updates, and I
couldn't reproduce the issue anymore.
Can you try 5.15.0-60-generic and let me know?
I bisected it down to 5.15.0-52-generic being broken, and it being fixed
in 5.15.0-53-generic.
Still trying to find the commit
Hi William,
I sincerely apologise for the delay.
Currently libunwind is stuck in -proposed due to benign autopkgtest
regressions in the kernel packages.
If you go to the below page:
https://people.canonical.com/~ubuntu-archive/pending-sru.html
And search for "libunwind" you will see entries
ovs-vsctl[51186]: ovs|1|vsctl|INFO|Called as ovs-vsctl --timeout=120
--oneline --format=json --db=tcp:127.0.0.1:6640 -- --if-exists del-port br-int
tap8c883ee5-5f
kernel: device tap8c883ee5-5f left promiscuous mode
lldpd[2309]: removal request for address of fe80::fc16:3eff:fe07:2be2%27, but
Hi David,
Thanks for the link, I think that is the most plausible explanation I have
seen so far.
The only problem is, if we look at the patch:
diff --git a/drivers/net/tun.c b/drivers/net/tun.c
index 7a3ab3427369..24001112c323 100644
--- a/drivers/net/tun.c
+++ b/drivers/net/tun.c
@@ -686,7
ntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: focal sts
** Description changed:
- BugLink: https://bugs.launchpad.net/bugs/
+ BugLink: https://bugs.launchpad.net/bugs/2007219
[Impact]
A deadlock exists in the XFS filesys
ecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
**
New => In Progress
** Changed in: isc-dhcp (Ubuntu Jammy)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu Focal)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu Focal)
Assignee: (un
New => In Progress
** Changed in: isc-dhcp (Ubuntu Jammy)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu Focal)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu Focal)
Assi
Hi everyone,
Can I get a courageous person to help sponsor bind9-libs for Focal and
Jammy in LP1926139:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139
Microsoft Azure have been putting a bit of pressure on me about this
case, in SF337873. Not in the case itself, but this went
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
Screenshot of wireshark.
** Attachment added: "Screenshot of wireshark"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641811/+files/Screenshot_2023-01-17-16-14-21_1920x1200%250A1920x1080%250A1920x1080.png
** Description changed:
[Impact]
Occasionally,
packet capture from a reproduction run
** Description changed:
- Platform: Qemu/libvirt on AMD64
- Ubuntu version: 20.04
- isc-dhcp-client version: 4.4.1-2.1ubuntu5
- Problem: When dhclient is used during boot every few reboots the DHCP OFFER
packets aren't pushed from the kernel to dhclient.
** Summary changed:
- dhclient doesn't receive dhcp offer from kernel
+ dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
untu Jammy)
Importance: Undecided => High
** Changed in: bind9-libs (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: bind9-libs (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification becaus
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "Debdiff for bind9-libs for Focal"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641515/+files/lp1926139_focal.debdiff
--
You received this bug notification because you are a member of
Performing verification for Bionic.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-8 from -release.
$ wget
Performing verification for Focal.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-9build1 from -release.
$ wget
t;
> Sure, I'll take care of it!
> A quick review of the debdiffs looks good, I'll give it a more detailed
> lookover tomorrow and upload ASAP (no promises about hitting -proposed this
> year, but let's try! hehehe).
>
> Cheers,
> Heitor
>
> On Tue, Dec 13, 2022 at 6:01 AM
Hi everyone,
Sorry to be a real bother, I need to apply for core-dev, and stop
talking about it and do it, I promise to start my application tomorrow
even.
But in the meantime, can you please review and consider sponsoring
php7.4 in the below launchpad bug.
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1999104
Title:
arm64: broken c++ exception handler support leads to std::terminate()
being
Hi everyone,
Can you please review and sponsor the below bug? AWS is quite
interested in getting this fixed for Reddit:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104
I know it probably won't be released this year, but maybe we can get
it into -proposed.
Thanks!
Matthew
--
** Summary changed:
- libunwind causes crashes on arm64
+ arm64: broken c++ exception handler support leads to std::terminate() being
called and program abort
** Description changed:
- There is a bug in libunwind in both 18.04 and 20.04 on arm64 where when
- linked with libunwind instead of
e: Undecided => Medium
** Changed in: libunwind (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: libunwind (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Patch added: "Debdiff for libunwind on Bionic"
ht
Attached is a debdiff which fixes this problem on Focal.
** Patch added: "Debdiff for libunwind on Focal"
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635451/+files/lp1999104_focal.debdiff
--
You received this bug notification because you are a member of
M Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe to move to LSMBLOB_NOT_NEEDED.
From Matthew Ruffell
https:
Gardner:
Subject:
Please Re-review LSM Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe to
** Tags added: sts
--
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/1962485
Title:
Kernel Crash [general protection fault: [#1] SMP NOPTI]
Status in linux package in Ubuntu:
** Tags added: focal jammy kinetic
--
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/1983656
Title:
iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
Status in linux
ogress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) =&g
gh and Tim Gardner:
Subject:
Please Re-review LSM Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe t
k from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
+
+ The discussion uses largely information found in this SRU template, plus
+ some additional information from mailing list threads highlighting why
+ it is safe to move to LSMBLOB_NOT_NEEDED.
+
+ From Matthew Ruffell
+ https://pastebin.canonical.com/
Attached is an improvement on the previous patch revision. Output is now
forwarded to logger, we use shell expansion to enumerate network
devices, we omit loopback, and we added a udevadm settle to wait for any
thunderstorms to resolve before we continue installing the new udev
package.
** Patch
Attached is the second patch required to fully fix this bug. It adds a
check on preinstall to see if ID_NET_DRIVER is present on the network
interface, and if it is missing, call udevadm trigger -c add on the
interface to add it.
** Patch added: "Debdiff for systemd on Bionic part two"
This is a pretty bizarre crash to tell you the truth. It occurred during
execution of a userspace program, doing a syscall to kernel space.
There's a bunch of userspace addresses in the registers, stack and the
faulting address, and the call trace has consecutive syscalls, and we
fault in some
The failure mode still exists if "udevadm trigger" has been issued
before the package upgrade to systemd 237-3ubuntu10.55.
That is, if unattended-upgrades or the user had installed open-vm-tools,
and has not rebooted yet, they will lose network connection on upgrade
to 237-3ubuntu10.55.
We need
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988119
Title:
systemd-udevd: Run
Hello everyone,
I know there are quite a few people watching this bug, so I will provide
a status update.
The test package has been looking good throughout our internal testing,
and we have proceeded to build the next systemd update, version
237-3ubuntu10.55, and it is currently in the
Attached is a debdiff for systemd on Bionic which fixes this bug.
** Description changed:
- Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
- https://ubuntu.com/security/notices/USN-5583-1
+ [Impact]
- could not resolve dns anymore.
- no dns servers, normally set through
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: bionic sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/b
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided
re kernel instead.
If a regression were to occur, users could configure 2 LSMs instead of
all 3, or not enable Landlock.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Jammy)
Importance: Med
Performing verification for Jammy.
I started one of each of the below instance types, trying to cover one
of all Xen based instance types:
c3.large, c4.large, i3.large, m3.medium, m4.large, r3.large, r4.large,
t2.medium.
Each instance had between 20 to 30gb of encrypted storage, and
hibernation
ssignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: jammy kinetic seg
--
You received this bug notification because you are a member of Kernel
Packages, which i
Hi Chris,
I stood up a Jammy VM, and tried with and without apparmor=0 on the
kernel command line, for a few hours at a time.
The /proc/slabinfo for kmalloc-2k and /proc/meminfo for unreclaimable
slabs were stable and did not grow, so it must be related to your
workload.
What sort of workloads
Performing verification for Focal.
I started a fresh Focal VM, and installed qemu-utils. I then ran
reproducer.sh from the testcase section.
The kernel is 5.4.0-124-generic from -updates.
Within 30 seconds of starting the reproducer, the testcase script hung,
and the following was in dmesg:
** Description changed:
[Impact]
Hibernation currently fails for all AWS Xen instance types
(c3/c4/i3/m3/m4/r3/r4/t2) with all Jammy 5.15 and Kinetic 5.19 linux-aws
kernels.
When attempting to hibernate, the system gets stuck in
sync_inodes_one_sb() when processing the rootfs,
u Kinetic)
Importance: Undecided => Critical
** Changed in: linux-aws (Ubuntu Jammy)
Assignee: (unassigned) => gerald.yang (gerald-yang-tw)
** Changed in: linux-aws (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- Hibernation testing
Performing verification for Focal
I install snmptrapd 5.8+dfsg-2ubuntu2.4 from updates, and edited
/etc/snmp/snmptrapd.conf to have the following contents:
disableAuthorization yes
traphandle default /usr/bin/logger
sqlMaxQueue 1
sqlSaveInterval 9
I disabled all snmptrapd services:
$ sudo
The new upload in the -unapproved upload queue has been bumped by a
security update, and so, attaching a new debdiff rebased to the current
package in -updates and -security.
Mauricio, could you please sponsor the new debdiff?
I took the feedback on Description field formatting into account,
Hi Dariusz, Heitor, Maurico,
Could I please get this debdiff reviewed and sponsored? AT have been
asking for it.
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933
Thanks,
Matthew
On Tue, Jul 5, 2022 at 10:44 AM Matthew Ruffell
wrote:
>
> Hi everyone,
>
> Can you p
Performing verification for Jammy.
I created a new Jammy VM, and installed qemu-utils.
The kernel is 5.15.0-41-generic from -updates.
I ran my reproducer.sh script from the testcase, and within a minute,
the nbd request got stuck, and we started seeing hung task timeout oops
messages in dmesg:
Fix released for linux-azure:
linux-azure (5.4.0-1086.91)
linux-azure (5.15.0.1014.17)
Marking back to Fix Committed for Jammy and In progress for Focal to
track progress in -generic variants.
** Changed in: linux (Ubuntu Jammy)
Status: Fix Released => Fix Committed
** Changed in: linux
Hi Everyone,
Could you please review and sponsor:
https://bugs.launchpad.net/ubuntu/+source/hwloc/+bug/1968742
It has a very straightforward test case, and the patch is also very
straightforward.
Kinetic already has the patch and Focal, Impish are not affected,
Again, I really need to apply
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1978423
[Impact]
When attempting to mount a cifs share, and it fails while the kernel is
attempting to get the root inode, typically in cifs_get_root(), a double
free can occur leading to a general protection fault which panics the
201 - 300 of 2037 matches
Mail list logo
