Updated regression potential with theoretical issues, and other info
with status in main for protection-domain-mapper and qrtr.
** Description changed:
[ Impact ]
- * ubuntu-seeds were changed since last meta update
- * to ensure correct upgrades; regenerate ubuntu-meta with contents / cha
(unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2039328
Title:
Update ubuntu-meta with promotions done between last ub
** Changed in: ubuntu-pro/18.04
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2038453
Title:
[SRU] apt snapshot integration backport
Status in
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Bionic)
Status: New => Won't Fix
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Status: Ne
All autopkgtests have now passed (lunar/jammy).
https://ubuntu-archive-team.ubuntu.com/proposed-migration/lunar/update_excuses.html#util-linux
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#util-linux
--
You received this bug notification because you are a me
The autopkgtests failures in lunar seem to be a kernel issue during the
initialization of the virtio rng driver, when the mutex for
(generic/core) hw rng is acquired (apparently something else is holding
it indefinitely, thus the blocked task warnings show up, and it seems
the VM doesn't proceed to
The autopkgtests failures in jammy seem to be of various sorts, but are
not expected to be related to this code change at all. I've skimmed
through them, and some seemed worth of retries (timeouts, network
issues, etc).
--
You received this bug notification because you are a member of Ubuntu
Touc
Thanks for reporting this bug!
Could not reproduce with Kinetic (22.10) or Lunar (23.04).
Kinetic will EOL soon. Can you reproduce this with Lunar?
Thanks!
$ lsb_release -cs
No LSB modules are available.
lunar
$ uuidgen -t
039c7806-20ae-11ee-ba46-54e1ad759c00
...
$ lsb_release -cs
kinetic
The problem does not seem to be in util-linux, as it works correctly
with a loop device.
Can you confirm whether you have /dev/disk/by-label/ symlinks for the
new filesystem?
$ lsb_release -cs
jammy
$ truncate -s 15T disk.img
$ DEV=$(sudo losetup --find --show disk.img)
$ sudo mkfs.btrfs -O zon
Steve / #17,
Sorry, this was discussed internally at the time, but for some reason
the answers didn't make it here back then.
If we get another bug (e.g., another simple change from existing util-
linux bugs, that still makes sense to be SRUed) that can be combined
with this SRU, would that be go
Uploaded to Lunar and Jammy, but not Kinetic (Won't Fix).
$ ubuntu-distro-info --series=kinetic --days=eol
45
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019
util-linux 2.38.1-5ubuntu1 finally migrated from mantic-proposed to mantic
(its autopkgtests were very slow/cycling last week, apparently).
I'll check for potential sponsors to the debdiff in comment #10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
For Mantic, this indeed requires a patch, not a merge/sync, as Debian
doesn't have the commit yet either.
$ git remote get-url origin
git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
$ git describe --contains 6857cccbb4157d5da34ca98f77a0ac9d68e1e740
v2.39-rc1~126^2~4
$ git show v2.39
Debdiff on top of mantic-proposed (2.38.1-5ubuntu1), which should
migrate soon (all good on update-excuses [1] / pending autopkgtests).
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#util-linux
** Patch added: "lp2019856-mantic-util-linux.debdiff"
https:/
Test packages in ppa:mfo/lp2019856, verified with GDB
(to fake CPU IDs) on Google Cloud ARM-based instances.
No differences in `lscpu` output for non-affected CPU.
Expected output for both affected CPUs (0xd15, 0xd4f).
Tested on LXD containers for Mantic, Lunar, and Jammy
(not on Kinetic as it wi
Hey Heather, thanks for the updated debdiffs!
I've looked at them, and did minor fixes to DEP3
(moved them out of the original commit message,
after `---`, and added Origin: fields), and just
a cosmetic adjustment to the changelog.
It turns out this patch isn't present in Mantic.
I already handl
** Description changed:
[Impact]
- When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
report a model name:
+
+ When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
+ report a model name:
Vendor ID: ARM
Model: 0
[Fix]
- Adding the additional a
u Mantic)
Status: New => In Progress
** Changed in: util-linux (Ubuntu Mantic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Tags removed: verification-needed-jammy verification-needed-lunar
--
You received this bug notification because you are a member of Ubunt
Heather mentioned some changes she has for the debdiffs, I also noted
some changes to DEP3 headers, and debdiffs v2 are in progress. Thanks,
Heather!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https:
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
Title:
Add missing ARM-cores to support Grace-based systems
Status in util-linux p
The fix/commit is applied in v5.12, thus available on Jammy
(v5.15-based).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
v5.12-rc1-dontuse~7^2~13
Marking bug as Invalid for MAAS as per previous comment, incomplete
status since, and input from Björn and Jerzy.
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dh
** Tags added: se-00140843
--
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/1677668
Title:
no GARPs during ephemeral boot
Status in MAAS:
Incomplete
Status in cloud-init
Hey Simon. Understood, thanks for the clarification!
--
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/2009699
Title:
sytemd-udev package upgrade breaks if udev is masked
St
Hi Simon,
Thanks for the detailed report!
For testing purposes, this can be reproduced this with standard LXD
images by masking the systemd-udev.service unit, as you described.
Could you please confirm if from the Anbox perspective, for a
workaround, is it OK to temporatily unmask/start the unit
Verification done on focal
(full steps on comment #13)
$ lxc shell focal-dhcpd
# add-apt-repository -y 'deb http://archive.ubuntu.com/ubuntu focal-
proposed main'
root@focal-dhcpd:~# apt policy isc-dhcp-client
isc-dhcp-client:
Installed: 4.4.1-2.1ubuntu5.20.04.4
Candidate: 4.4.1-2.1ubuntu5.2
Verification done on jammy
(full steps on comment #12)
$ lxc shell jammy-dhcpd
# add-apt-repository -yp proposed
# apt policy isc-dhcp-client
isc-dhcp-client:
Installed: 4.4.1-2.3ubuntu2.3
Candidate: 4.4.1-2.3ubuntu2.4
Version table:
4.4.1-2.3ubuntu2.4 500
500 http://archive.u
The -proposed packages have also been verified by the Microsoft Azure team.
14k+ VM deployments with the fix didn't observe the issue over the weekend.
Marking jammy/focal as verified based on that plus 2 synthetic tests
above.
** Tags removed: verification-needed verification-needed-focal
verif
verification done on focal
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -y 'deb http://archive.ubuntu.com/
verification done on jammy
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -yp proposed
# apt policy isc-dh
** Tags added: se-sru-sponsor-mfo
--
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
r
Uploaded to Jammy/Focal.
--
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/1937110
Title:
dhcp option 121 & 249
Status in subiquity:
New
Status in isc-dhcp package in Ubu
Reproducer with DHCP server/client on LXD. [Focal]
Bridge
---
sudo ip link add focalbr type bridge
sudo ip link set focalbr up
LXD container for DHCP server with classless static routes option
---
lxc init ubuntu:focal focal-dhcpd
lxc config device add focal-dhc
ess
** Changed in: isc-dhcp (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: isc-dhcp (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: isc-dhcp (Ubuntu
>From the 'Where problems could occur' section.
Considerations on regressions and approaches.
[Where problems could occur]
isc-dhcp is a core package, and any change comes with the risk that
users would not be able to receive dhcp leases with dhclient, leaving
their systems with no IP address and
From the 'Other Info' section.
Detailed analysis of the issue and more.
[Other Info]
Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/
Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/
When you tcpdump dhclient, we see all DHCPDISCOVER packets being replied
to with DHCPOFFER packets, b
Pressing Page Down 17 times to go over the bug description sounds like a
new record! ;-)
Just in case future reviewers don't find that as exciting while going
through reviews, I'll move some text into comments and reference them
from the description.
** Bug watch added: gitlab.isc.org/isc-project
Jammy/22.04:
- test packages in ppa:mfo/lp1926139
- reproduction steps delta (based on comment #9)
...
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
...
LXD VM:
lxc launch ubuntu:jammy
** Patch added: "lp1926139_focal_isc-dhcp_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5643626/+files/lp1926139_focal_isc-dhcp_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Test packages:
https://launchpad.net/~mfo/+archive/ubuntu/lp1926139
isc-dhcp 4.4.1-2.1ubuntu5.20.04.4+lp1926139.2
Default behavior: issue fixed.
---
(gdb) break omapip/dispatch.c:333
(gdb) commands
shell sleep 0.2
continue
end
(gdb) run -d -v vet
Hey Matthew, Chris,
Apparently there's a simpler, less intrusive, and more specific way to
do this.
Apologies that I missed this earlier, but I found more about the
possibilities in bind9-libs functions while checking the previous fix
approach for regressions.
Could you please provide your thoug
For documentation purposes.
The autopkgtests failures for systemd were unrelated to this
(not regressions).
I checked their logs and reran with the migration-reference/0
trigger so not to use kbd from -proposed; that failed as well.
The pending SRU and update-excuses pages no longer show kbd
blo
** Patch added: "lp1926139_focal_isc-dhcp.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5642442/+files/lp1926139_focal_isc-dhcp.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi Matthew,
Thanks for the excellent analysis and considerate fix proposal, as
always!
I looked at this for the last couple of days, for potential sponsorship.
I have attentively gone through the SRU template and Other Info section,
and considered the proposal to switch bind9-libs into --disable
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
LXD VM:
$ lxc launch ubuntu:focal lp1926139-focal --vm
$ lxc shell lp1926139-focal
Network Setup:
# ip link add br0 t
** Tags removed: 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
receiv
Hi. No, I haven't tested on that; but if this helps, the issue is
independent of platform/hypervisor as it's in ufw/firewall, thus the fix
should help anyway.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
http
Thanks, Heather!
Uploaded to Kinetic and Jammy (minor adjustments; build tested on supported
archs w/ -proposed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1996619
Title:
n: systemd (Ubuntu Bionic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1996958
Title:
[Azure] 18.04
** Patch added: "lp1996958-bionic-systemd.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/systemd/+bug/1996958/+attachment/5635743/+files/lp1996958-bionic-systemd.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Changed in: lvm2 (Ubuntu Focal)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.
Heather and I internally discussed some feedback/review for the revised
debdiffs.
** Tags removed: sts-sponsor
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpa
Scenario 2) LUN numbers 0, 1, and 5 (non-0/1 test).
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sda
Scenario 1) LUN numbers 0 and 1 only.
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sdc
[0:0:0:1]
Test packages on ppa:mfo/lp1996958 [1].
Initial tests show positive results (next comments).
Waiting on feedback from the original reporter.
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1996958
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
I have verified the scenario that Seyeong mentioned
where the patch apparently dit not make a difference
(SCSI disks with LUN numbers greater than 1, eg, 5).
My observation is it indeed works/makes a difference.
He went out on vacation (so I'm reassigning the bug), and
cannot confirm this, but pe
n-unique PATH_ID for SCSI disks
** Changed in: systemd (Ubuntu Bionic)
Assignee: Seyeong Kim (seyeongkim) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep ID_
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep ID_
Ah, you might want to do systemd first, if a reboot isn't desirable.
If a reboot is fine, then maybe also just check again after reboot,
in case it's a transient system condition unrelated to the upgrades.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
> ... from systemd 237-3ubuntu10.53 to 237-3ubuntu10.56
> and are experiencing some performance issues.
> A kernel upgrade also happened (4.15.0.192.177 -> 4.15.0.193.178)
> but I thought I'd check here first.
> Sorry if I'm raising this in the wrong place!
Thanks for the bug report!
No worrie
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie" sta
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this
Nicolas and I talked about a brief review of the debdiff,
and he kindly agreed to provide an update/v2 to address:
- changelog version and description line
- patches dep3 headers and lpnumber- prefix
... while patches are reviewed for feedback (not yet done).
Thanks, Nicolas!
--
You received th
Update: this has been fixed in Focal (same fix commit):
openssl (1.1.1f-1ubuntu2.11) focal; urgency=medium
* Fixup pointer authentication for armv8 systems that support it when
using the poly1305 MAC, preventing segmentation faults. (LP: #1960863)
- d/p/lp-1960863-crypto-poly1305-asm-fi
Setting verification-done-bionic per comments 39/40.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kl
Verification done on focal-proposed; all good.
Host:
---
$ sudo dd if=/dev/sda of=/dev/null
dd: failed to open '/dev/sda': No medium found
$ lxc launch ubuntu:focal lp1834250
$ lxc config device add lp1834250 host-sda unix-block source=/dev/sda
path=/dev/sda
** Patch added: "lp1834250_lvm2_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+attachment/5593897/+files/lp1834250_lvm2_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubu
Uploaded to Focal, and tagged block-proposed-focal.
Attaching slightly modified debdiff (local build version),
for users who want to build lvm2 before a SRU is released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in
** Description changed:
[Impact]
* `update-grub` (actually `vgs`) complains about
'No medium found' on systems with card readers
that have no card in.
* This may confuse users who aren't sure whether
it means problems occurred with the bootloader,
and concern thei
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^ /sys/block/sda/{removable,device/{vend
hanged in: lvm2 (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: lvm2 (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Hey Fabio,
That happens when the package lands in -proposed.
It looks like the SRU vanguards this Wed/Thu are Robie/Lukasz,
which is good as they are familiar with the discussion/changes,
so I'll ask if they have SRU review cycles to for this upload.
Thanks for following up!
** Changed in: kli
Thanks for the bug report!
Changing title to indicate actual impact, and reassining to systemd as
the 'nofail' mount option (which you tried) apparently didn't work.
Per systemd.mount(5) man page:
nofail
[..] This means that the boot will continue without waiting
for
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on network root filesystem
Status in ufw:
Fix Committed
Statu
Thanks, Fabio!
With the regression fixed and Oracle test case working as expected,
I've updated the versioning and patch series, and uploaded for SRU.
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
*** This bug is a duplicate of bug 1802021 ***
https://bugs.launchpad.net/bugs/1802021
For documentation purposes, this issue is likely a duplicate of bug
1802021, fixed in kernel 4.15.0-47.50.
** This bug has been marked a duplicate of bug 1802021
[Hyper-V] srcu: Lock srcu_data structure
We'll have to respin/re-upload with a different version, due to the
recent security update [1].
Let's do that after the testing on Oracle, if at all possible, as that
may be asked by the SRU team for accepting it, and some members may be
busy with the jammy release, so let's save one request. :)
Hey, Fabio!
That looks good; thanks!
I have built/uploaded to ppa:mfo/lp1947099v2 and for SRU,
as the tests on Oracle have `-t` in, thus no code change
from previous tests, effectively.
Per our chat, for completeness/correctness you'll test on
oracle again, and then we can move the SRU upload fo
Fabio is out today, but he mentioned yesterday that the test patch
worked fine locally, and he'd get access to an oracle test system again,
for more tests.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https
Hi Fabio,
> [1] But now when I try to obtain an IP using dhcp without specifying any
> timeout,
> it dumps lots of "Lowered timeout to match user request" messages.
> Is that expected?
>
> https://pastebin.ubuntu.com/p/5Tpc5Rwdkq/
No, this is a regression without `-t`, and has to be fixed befor
Hey Fabio,
Thanks for the lab setup for testing this!
> Anyway, if someone can build a klibc-utils package for me with the proposed
> patch,
> I can test the ipconfig behavior in this Lab.
Sure, there you go!
sudo add-apt-repository ppa:mfo/lp1947099
sudo apt install klibc-utils
> For testing
Seth, ack; thanks!
Matthew, I uploaded the changes to Focal; thanks for the SRU!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1960863
Title:
armv8 paca: poly1305 users
Hi @ubuntu-security,
I believe we should ask for your ack, as this is openssl.
If that's right, could you please review it and comment?
The changes look ok technically and w.r.t. test results
(details in sru template and comment above.)
Thanks!
--
You received this bug notification because you
The changes look good to me.
It built correctly (ie, build-time tests) on all archs on PPAs w/ -updates and
-proposed.
It passed autopkgtests on focal/arm64 against the PPA build too.
Thus, no test regressions in our arm64 cpus, and the synthetic test
passes on newer arm64 cpu (tested by user).
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1960863
Title:
armv8 paca: poly1305 users see segfaults when pointer authentication
in use
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958053
Title:
If dmesg has bug, then make popup
That isn't the case, apparently.
The file is only readable by user/group, but not others, in Impish, at
least.
Upgrade:
$ lsb_release -cs
impish
$ ls -l /var/log/dmesg
-rw-r- 1 root adm 95595 Oct 28 11:46 /var/log/dmesg
Install:
$ lsb_release -cs
impish
$ ls -l /var/log/dmesg
-rw-r-
This has been intentionally changed a while ago, please see [1]. Thanks!
[1] https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Tested with Bionic, Focal, Hirsute, and Impish
with the test steps provided, on Oracle Cloud.
All good.
With the packages in -proposed, the system can reboot correctly.
---
bionic
Version: 0.36-0ubuntu0.18.04.2
focal
Version: 0.36-6ubuntu1
hirsute
Version: 0.36-7.1ubuntu1
impish
Version: 0.36
Tested with Bionic, Focal, and Hirsute, with the test steps provided.
All good.
Bionic:
---
Before:
# dpkg -s ufw | grep Version:
Version: 0.36-0ubuntu0.18.04.1
# iptables -L ufw-user-input -n
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT tc
Uploaded to H/F/B.
(debdiffs in bug 1946804)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1933117
Title:
ufw delete can confuse protocol-specific rule with otherwise matchin
Uploaded to I/H/F/B.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on network root filesystem
Status in ufw:
Fix Committed
Status in ufw pac
** Patch added: "ufw-impish.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536527/+files/ufw-impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/
** Patch added: "ufw-bionic.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536530/+files/ufw-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/
** Patch added: "ufw-focal.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536529/+files/ufw-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/19
Verified test packages (ppa:mfo/lp1946804) for
the Hirsute, Focal, and Bionic releases.
...
Without the patch:
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT tcp -- 0.0.0.0/00.0.0.0/0tcp dpt:22
ACCEPT tcp -- 2.2
** Patch added: "ufw-hirsute.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536528/+files/ufw-hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bug
Verified test packages (ppa:mfo/lp1946804) for
the Impish, Hirsute, Focal, and Bionic releases
on Oracle Cloud's 'BM.Standard1.36' systems.
(Impish/Hirsute: Focal and do-release-upgrade.)
...
Without the patch, the system boot stalls.
With the patch, the system boot continues.
(Note: netfilter-
** Description changed:
[Impact]
A system with rootfs on iSCSI stops booting when ufw.service starts.
The kernel logs iSCSI command/reset timeout until I/O fails and the
root filesystem/journal break.
The issue is that ufw_start() sets the default policy _first_, then
adds rules
101 - 200 of 457 matches
Mail list logo
