Processing control commands:
> severity -1 important
Bug #1050256 [apparmor,lxc] apparmor makes systemd autopkgtests fail on bookworm
Severity set to 'important' from 'serious'
--
1050256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050256
Debian Bug Tracking System
Contact
Control: severity -1 important
Am 09.09.23 um 14:20 schrieb intrigeri:
Hi again,
Thank you all for working both on workarounds for Debian CI and on
a proper upstream Linux kernel fix. Impressive cross-team work! :)
+1
At this stage it seems clear that the bug and the corresponding ideal
Hi again,
Thank you all for working both on workarounds for Debian CI and on
a proper upstream Linux kernel fix. Impressive cross-team work! :)
At this stage it seems clear that the bug and the corresponding ideal
fix are in the AppArmor part of src:linux, and the bug affects at
least
Hi,
On 03-09-2023 10:50, Paul Gevers wrote:
I have manually upgraded the s390x host and
rebooted, so that can serve as a test arch.
All ci.d.n workers (except riscv64) now run the kernel from
bookworm-backports. systemd passes it's autopkgtest again in unstable,
testing and stable.
Paul
On 9/4/23 12:32, Michael Biebl wrote:
Am 04.09.23 um 20:23 schrieb Mathias Gibbens:
On Mon, 2023-09-04 at 01:00 -0700, John Johansen wrote:
I took a quick look through v6.1..v6.3.1
there is a patch that I think is the likely fix, it first landed in v6.2
1cf26c3d2c4c apparmor: fix apparmor
Am 04.09.23 um 20:23 schrieb Mathias Gibbens:
On Mon, 2023-09-04 at 01:00 -0700, John Johansen wrote:
I took a quick look through v6.1..v6.3.1
there is a patch that I think is the likely fix, it first landed in v6.2
1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
On Mon, 2023-09-04 at 01:00 -0700, John Johansen wrote:
> I took a quick look through v6.1..v6.3.1
>
> there is a patch that I think is the likely fix, it first landed in v6.2
>
> 1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
Thanks for the pointer John -- I think
Hello,
Am Samstag, 2. September 2023, 01:13:11 CEST schrieb Mathias Gibbens:
> A minimal reproducer is to install bookworm and create a container
> with a systemd service using a hardening option like
> PrivateNetwork=yes. With the latest bookworm kernel (6.1.38-4), the
> service will fail.
I took a quick look through v6.1..v6.3.1
there is a patch that I think is the likely fix, it first landed in v6.2
1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
it matches up the reported audit logs. Unfortunately it does not have a Fixes
tag but as best I can figure
Am 03.09.23 um 10:50 schrieb Paul Gevers:
Hi,
On 03-09-2023 02:56, Michael Biebl wrote:
ng?
Do the debci maintainers / lxc maintainers / release team have any
preference regarding a/, b/ and c/ ?
One part of me likes the ci.d.n infrastructure to run stable as an
example of "eat your own
Hi,
On 03-09-2023 02:56, Michael Biebl wrote:
My main concern is to "stop the bleeding" quickly, so to speak,
especially/mainly for debci.
I agree with you, but also consider that with this issue being there
since ~ April 2023 we don't need to rush.
I guess we have three options here:
a/
Processing control commands:
> severity -1 serious
Bug #1050256 [apparmor,lxc] apparmor makes systemd autopkgtests fail on bookworm
Severity set to 'serious' from 'important'
--
1050256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050256
Debian Bug Tracking System
Contact
12 matches
Mail list logo
