** Description changed:
- In mantic, we migrated livecd-rootfs to use losetup -P instead of
- kpartx, with the expectation that this would give us a reliable, race-
- free way of loop-mounting partitions from a disk image during image
- build.
+ [impact]
+ In mantic, we migrated livecd-rootfs to
Here is a backport of the partial fix to jammy
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-
rootfs/+merge/460729
I'm not sure I am best placed to update this bug description to match
the SRU template though -- I'm not sure which builds are being affected
in practice and so
Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.
--
You received this bug notification because you are a member of Kernel
Packages,
Here's my workaround then https://code.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-rootfs/+merge/459380
--
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/2045586
Title:
Amazing debugging Dann. Until we can get a kernel fix, what's the way
forward here? Run losetup without -P, run udevadm settle, run partprobe
on the device (then maybe run udevadm settle again??)
--
You received this bug notification because you are a member of Kernel
Packages, which is
> Is only asking kernel to scan the device; to then generate "kernel udev"
> events; for then udev to wakeup and process/emit "udev udev" events; and
> create the required device nodes.
>
It's not udev that creates nodes like /dev/loop1p1 though is it? That's
devtmpfs surely.
--
You received
Ah no it's a bit simpler than that https://github.com/util-linux/util-
linux/issues/2528.
--disable-libmount-mountfd-support looking better tbh.
** Bug watch added: github.com/util-linux/util-linux/issues #2528
https://github.com/util-linux/util-linux/issues/2528
--
You received this bug
So the cause of this, I am fairly sure, is the new "libmount-mountfd"
support in util-linux which seems to have the consequence that "mount -o
remount $mountpoint" fails for an overlay that references paths no
longer available in the current mount namespace.
You can see the discussion of a
** Also affects: util-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/2037417
Title:
mantic images after 20230917 are failing
** Tags added: foundaitions-todo
** Tags removed: foundaitions-todo
** Tags added: foundations-todo
--
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/2037417
Title:
mantic images after
** No longer affects: linux (Ubuntu)
** Also affects: snapcraft
Importance: Undecided
Status: New
** Summary changed:
- Subiquity segfault in ARM64 with -64k Kernel
+ classic snaps do not work on ARM64 kernel configured to use 64k pages
--
You received this bug notification because
Digging a bit suggests this is a result of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.18.y=b9cabd2ec2ff6f452bd5744326cc5c5f503448c6?
At any rate, not a glibc issue.
** Package changed: glibc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification
By reading the LVM source I found that unpartitioned CDL formatted DASDs
cannot be included in a LVM volume group. So I guess we should update
the interface to prohibit their use! I would expect that if you add a
single partition to dasdb and put that in the VG instead things will
work.
--
You
The change to omit DT_HASH was only in 2.36 and so was only present in
kinetic/22.10, and then only briefly as we patched it before release. I
doubt it's that.
Have you reported this upstream at https://sourceware.org/bugzilla/ ?
Have you tried building glibc 2.35 from source? (would be
https://github.com/strace/strace/commit/aeb29a3238ef3cc7f191f98743678d3b4ec949b9
and
https://github.com/strace/strace/commit/a30e5defe41b5b806c223865e92b20d8c9b08f4b
look relevant.
In general, does strace get a release for each kernel release? Should it
be updated in parallel?
** Tags added:
I think
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=774058d72942249f71d74e7f2b639f77184160a6
might help here.
--
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/1985956
Title:
So the reason this doesn't work is that the udev data for the container,
/dev/md/imsm0, does not contain the keys we look for to work out which
devices are part of it. We expect to find keys called things like
MD_DEVICE_dev_sda_DEV but they are not there. There is
UDISKS_MD_DEVICE_dev_sda_DEV
I had a poke at this, and although the cet-backport.diff file is present
in the source package, it is not actually applied and hasn't been since
some time in Groovy's development cycle afaict. This makes sense because
also afaict, this all went upstream in glibc 2.32, which was the version
in
I should say here that I don't really know what changes to subiquity are
desirable here. I don't really like the idea of subiquity always using
set-name, that just feels wrong, but I can see the problem here too.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: subiquity
Status: New => In Progress
--
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/1876011
Title:
Kernel Panic when dasd-fba device is selected for install
Err. Just to check, you are booting with the right initramfs? Can you
share your pxe(linux emulation) config?
--
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/1890884
Title:
kernel trace
** Changed in: subiquity
Status: Confirmed => 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/1534162
Title:
symlinks managed by kernel postinst are different from
I don't think this was ever a bug in subiquity.
** Changed in: subiquity
Status: New => Fix Released
** Changed in: subiquity
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm not sure of the status of this bug now. Was it all fixed by release?
** Changed in: subiquity
Status: New => 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/1871611
** No longer affects: linux-azure (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Also affects: cloud-utils (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug
Great, thanks for confirming.
I wonder if we should SRU this. You see it on Eoan I presume? The bug is
theoretically present in Bionic too aiui but if it never crops up I
don't know if it's worth it.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Can someone from CPC confirm that this has fixed the issues in the Azure
tests?
--
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/1834875
Title:
cloud-init growpart race with udev
Talking about this more, the Ubuntu solution for this sort of thing is
to configure sudo appropriately, so we'll close the bug here.
** Changed in: iproute2 (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Well this is a consequence of this upstream change in iproute2:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?h=v4.16.0=ba2fc55b99f8363c80ce36681bc1ec97690b66f5.
Upstream discussion, such as it is, of the patch appears to be here:
** Package changed: libcap2 (Ubuntu) => iproute2 (Ubuntu)
--
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/1856045
Title:
capabilities set with setcap
> Ah, no I think this might be along right lines: udev is calling blkid
> on the _partition_ of course, so it can probe for filesystem etc without
> looking at the partition table. After it's done that, it does look for
> the partition table so it can read the ID_PART_ENTRY_* values from it,
> but
On another tangent, I wonder if the change that brought this to light
was the switch to booting without initrd. The timing is about right, and
fits with the fact that it doesn't occur with the generic kernel (which
cannot boot without initrd in Azure). So if someone has an excess of
time to test ,
Hi, could someone prepare an image with
https://paste.ubuntu.com/p/HYGv6m8gCc/ at /etc/systemd/system/systemd-
udevd.service.d/udevd-debugging.conf, boot it on azure until it fails
and put the journalctl output (probably a few megs) somewhere I can read
it? Output from a successful boot would also
Oh yeah and one other thing I don't understand: why udev is processing
the partition while sgdisk is still running.
--
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/1834875
Title:
Ah, no I think this might be along right lines: udev is calling blkid on
the _partition_ of course, so it can probe for filesystem etc without
looking at the partition table. After it's done that, it does look for
the partition table so it can read the ID_PART_ENTRY_* values from it,
but if it
So I've been handed the job of moving this bug forward this iteration.
Having just re-read all the comments again and read some source code
while listening to loud techno music my observations/questions are
these:
1) this is a doozy
2) I would really like to see complete udevadm monitor and
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
** This bug is no longer a duplicate of bug 1844101
5.3.0-10 crashes immediately in init_tis -> ... -> tpm_init -> ... ->
tpm_tis_core_init.cold -> ... (never boots)
** This bug has been marked a
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
Bug 1845454 was filed later but has more useful comments, so I'm going
to mark this a duplicate of that.
** This bug has been marked a duplicate of bug 1845454
Kernel panic with 19.10 beta image
--
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
** This bug is no longer a duplicate of bug 1844101
5.3.0-10 crashes immediately in init_tis -> ... -> tpm_init -> ... ->
tpm_tis_core_init.cold -> ... (never boots)
** This bug has been marked a
This is the same bug as bug 1844101 I think? If it is, it doesn't
reproduce with secure boot off and we'll need a signed kernel to test.
I'm happy to enrol whatever key in my firmware to test a self-signed
kernel...
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1844101 ***
https://bugs.launchpad.net/bugs/1844101
Yes, I assume it's the same bug. Julian and I were actually sitting next
to each other yesterday trying to diagnose things. As the other bug has
logs, let's mark this a duplicate of the other.
** This bug
Update: disabling TPM is enough to allow boot.
>From dmidecode:
Handle 0x000C, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20L8S7X100
Version: ThinkPad T480s
Serial Number: xxx
UUID: xxx
Wake-up Type: Power Switch
mwhudson@anduril:~$ apport-collect 1843860
dpkg-query: no packages found matching linux
** 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.
Public bug reported:
I have no further information, sadly. The boot stops at the message "EFI
stub: UEFI Secure Boot is enabled". Disabling secure boot or selecting
an older kernel both work fine.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received
I had a look at this and got pretty confused! Feels more like a kernel
problem than a casper one, somehow.
--
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/1840122
Title:
System fails to
I've verified the fix in the way I suspected I'd have to, with one extra
wrinkle.
1) In a trusty VM, I verified that the C test case from the gist failed. (It
did).
2) I launched a xenial lxd container on the VM and built the Go test case with
version 1.6.2-0ubuntu5~16.04.2 of golang-1.6-go.
3)
** Changed in: golang-1.6 (Ubuntu Xenial)
Status: New => In Progress
--
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/1672819
Title:
exec'ing a setuid binary from a threaded
** Description changed:
+ == SRU template for golang-1.6 ==
+
+ [Impact]
+ The kernel bug reported below means that occasionally (maybe 1 in 1000 times)
the snapd -> snap-confine exec that is part of a snap execution fails to take
the setuid bit on the snap-confine binary into account which
; Invalid
** Changed in: golang-1.6 (Ubuntu Xenial)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: golang-1.6 (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
On 8 May 2017 at 10:32, Colin Ian King <1672...@bugs.launchpad.net>
wrote:
> exec'ing from a thread is an interesting problem; the semantics of exec
> should be to terminal all the threads before the exec occurs according
> to http://maxim.int.ru/bookshelf/PthreadsProgram/htm/r_44.html
>
> The
I had a bit of a stare at the kernel source and suspected that the
downgrade of uid is happening here:
https://github.com/torvalds/linux/blob/v4.4/security/commoncap.c#L547-L548
I added a "WARN(1, "downgrading in subprocess %d %d\n", bprm->unsafe,
(int)capable(CAP_SETUID))" which revealed that
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snap-confine (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Xenial)
** Changed in: snap-confine (Ubuntu Xenial)
Status: New => In Progress
** Also affects: snap-confine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snap-confine (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
cpu-checker / kvm-ok is not available on s390x. I'm not sure what it
should do, otherwise I'd attach a patch :-)
** Affects: cpu-checker
Importance: Undecided
Status: New
** Affects: cpu-checker (Ubuntu)
Importance: Undecided
Status: New
** Also
I haven't had this problem in a long time indeed. Don't see the point
in keeping it open.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
55 matches
Mail list logo
