linux-kernel - Re: [PATCH v3 4/7] seccomp: mark first listener in the tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a54303d478e4492977f8760b0f2d22894bfe604a.camel@mihalicyn.com>
Date: Wed, 28 Jan 2026 20:05:25 +0100
From: Alexander Mikhalitsyn <alexander@...alicyn.com>
To: Aleksa Sarai <cyphar@...har.com>, Alexander Mikhalitsyn
	 <alexander@...alicyn.com>
Cc: kees@...nel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org,  Andy Lutomirski <luto@...capital.net>, Will
 Drewry <wad@...omium.org>, Jonathan Corbet <corbet@....net>, Shuah Khan	
 <shuah@...nel.org>, Tycho Andersen <tycho@...ho.pizza>, Andrei Vagin	
 <avagin@...il.com>, Christian Brauner <brauner@...nel.org>, 
 Stéphane Graber	 <stgraber@...raber.org>
Subject: Re: [PATCH v3 4/7] seccomp: mark first listener in the tree

On Wed, 2026-01-21 at 13:22 +0100, Aleksa Sarai wrote:
> On 2025-12-11, Alexander Mikhalitsyn
> <aleksandr.mikhalitsyn@...onical.com> wrote:
> > Let's note if listener was a first one installed in the seccomp
> > filters tree. We will need this information to retain old
> > quirk behavior (as before seccomp nesting introduced).
> > 
> > Also, rename has_duplicate_listener() to
> > check_duplicate_listener(),
> > cause now this function is not read-only, but also modifies a state
> > of a new_child seccomp_filter.
> > 
> > No functional change intended at this point.
> 
> Ah sorry, I didn't notice the date of the mails -- this was sent
> before
> the LPC discussion! I'll wait for the v4 before reviewing further.

Hi Aleksa,

Yeah, I'm thinking about preparing a separate patches to address
a quirky seccomp behavior we discussed during LPC and then resend this
series.

Kind regards,
Alex