Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80464 > unrolled thread

Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci intrigeri <intrigeri@debian.org> - 2023-09-17 08:40 +0200
    Processed: Re: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-09-17 08:40 +0200
    Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci Salvatore Bonaccorso <carnil@debian.org> - 2023-09-19 07:20 +0200
      Processed: Re: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-09-19 07:20 +0200
      Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci Mathias Gibbens <gibmat@debian.org> - 2023-09-24 16:10 +0200

#80464 — Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

Control: reassign -1 src:linux
Control: retitle -1 AppArmor breaks locking non-fs Unix sockets
Control: affects -1 src:apparmor src:lxc src:systemd src:pdns src:policykit-1
Control: found -1 6.1.38-1
Control: found -1 6.1.38-2
Control: notfound -1 6.3.1-1~exp1

Hi Debian Kernel Team,

In the last month or so, a number of people from various Debian teams
and other distributions have been tracking down a regression that
affects systems upgraded to Bookworm: services that use certain
systemd facilities such as PrivateNetwork=yes fail to start in LXC/LXD
containers. Among other things, this breaks the autopkgtests of many
packages, such as systemd, on ci.debian.net (#1050256). This was
tracked down to a kernel regression, for which a fix landed in Linux
6.2:

  1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets

Work is ongoing to backport the fix to linux-stable/linux-6.1.y.
I'm Cc'ing John and Mathias who have been working on this.

FYI, ideally this would be fixed in the upcoming Bookworm
point-release (12.2, early October).

Current workarounds:

 - ci.debian.net was upgraded to the bookworm-backports kernel
 - various packages maintainers have added workarounds such as disabling
   PrivateNetwork=yes for autopkgtests

Cheers,
-- 
intrigeri

[toc] | [next] | [standalone]

#80465 — Processed: Re: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

Processing control commands:

> reassign -1 src:linux
Bug #1050256 [apparmor,lxc] apparmor makes systemd autopkgtests fail on bookworm
Bug reassigned from package 'apparmor,lxc' to 'src:linux'.
Ignoring request to alter found versions of bug #1050256 to the same values previously set
Ignoring request to alter fixed versions of bug #1050256 to the same values previously set
> retitle -1 AppArmor breaks locking non-fs Unix sockets
Bug #1050256 [src:linux] apparmor makes systemd autopkgtests fail on bookworm
Changed Bug title to 'AppArmor breaks locking non-fs Unix sockets' from 'apparmor makes systemd autopkgtests fail on bookworm'.
> affects -1 src:apparmor src:lxc src:systemd src:pdns src:policykit-1
Bug #1050256 [src:linux] AppArmor breaks locking non-fs Unix sockets
Added indication that 1050256 affects src:apparmor, src:lxc, src:pdns, and src:policykit-1
> found -1 6.1.38-1
Bug #1050256 [src:linux] AppArmor breaks locking non-fs Unix sockets
Marked as found in versions linux/6.1.38-1.
> found -1 6.1.38-2
Bug #1050256 [src:linux] AppArmor breaks locking non-fs Unix sockets
Marked as found in versions linux/6.1.38-2.
> notfound -1 6.3.1-1~exp1
Bug #1050256 [src:linux] AppArmor breaks locking non-fs Unix sockets
Ignoring request to alter found versions of bug #1050256 to the same values previously set

-- 
1050256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050256
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#80475

Control: tags -1 + confirmed moreinfo

Hi,

On Sun, Sep 17, 2023 at 12:01:37PM +0530, intrigeri wrote:
> Control: reassign -1 src:linux
> Control: retitle -1 AppArmor breaks locking non-fs Unix sockets
> Control: affects -1 src:apparmor src:lxc src:systemd src:pdns src:policykit-1
> Control: found -1 6.1.38-1
> Control: found -1 6.1.38-2
> Control: notfound -1 6.3.1-1~exp1
> 
> Hi Debian Kernel Team,
> 
> In the last month or so, a number of people from various Debian teams
> and other distributions have been tracking down a regression that
> affects systems upgraded to Bookworm: services that use certain
> systemd facilities such as PrivateNetwork=yes fail to start in LXC/LXD
> containers. Among other things, this breaks the autopkgtests of many
> packages, such as systemd, on ci.debian.net (#1050256). This was
> tracked down to a kernel regression, for which a fix landed in Linux
> 6.2:
> 
>   1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
> 
> Work is ongoing to backport the fix to linux-stable/linux-6.1.y.
> I'm Cc'ing John and Mathias who have been working on this.
> 
> FYI, ideally this would be fixed in the upcoming Bookworm
> point-release (12.2, early October).

Thanks for the details. Has this already been sent it to the stable
maintainers? I do not see it yet on the stable list.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#80478 — Processed: Re: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

Processing control commands:

> tags -1 + confirmed moreinfo
Bug #1050256 {Done: Salvatore Bonaccorso <carnil@debian.org>} [src:linux] AppArmor breaks locking non-fs Unix sockets
Added tag(s) confirmed and moreinfo.

-- 
1050256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050256
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#80506

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2023-09-19 at 07:17 +0200, Salvatore Bonaccorso wrote:
> On Sun, Sep 17, 2023 at 12:01:37PM +0530, intrigeri wrote:
> > In the last month or so, a number of people from various Debian teams
> > and other distributions have been tracking down a regression that
> > affects systems upgraded to Bookworm: services that use certain
> > systemd facilities such as PrivateNetwork=yes fail to start in LXC/LXD
> > containers. Among other things, this breaks the autopkgtests of many
> > packages, such as systemd, on ci.debian.net (#1050256). This was
> > tracked down to a kernel regression, for which a fix landed in Linux
> > 6.2:
> > 
> >   1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
> > 
> > Work is ongoing to backport the fix to linux-stable/linux-6.1.y.
> > I'm Cc'ing John and Mathias who have been working on this.
> > 
> > FYI, ideally this would be fixed in the upcoming Bookworm
> > point-release (12.2, early October).
> 
> Thanks for the details. Has this already been sent it to the stable
> maintainers? I do not see it yet on the stable list.

  I believe that John has been working on the fix for the 6.1 branch,
although I don't know what the status is. I don't have the necessary
familiarity with apparmor internals to attempt to backport the fix
myself, but I'll be very happy to test once it's available.

Mathias

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web