linux-kernel - Re: [PATCH 1/2] seccomp: Use FIFO semantics to order notifications

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 for Android: free password hash cracker in your pocket

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

Message-Id: <165125819819.3692727.9306925856353932810.b4-ty@chromium.org>
Date:   Fri, 29 Apr 2022 11:50:00 -0700
From:   Kees Cook <keescook@...omium.org>
To:     linux-kernel@...r.kernel.org, sargun@...gun.me, luto@...nel.org,
        tycho@...ho.pizza
Cc:     Kees Cook <keescook@...omium.org>,
        Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH 1/2] seccomp: Use FIFO semantics to order notifications

On Wed, 27 Apr 2022 18:54:46 -0700, Sargun Dhillon wrote:
> Previously, the seccomp notifier used LIFO semantics, where each
> notification would be added on top of the stack, and notifications
> were popped off the top of the stack. This could result one process
> that generates a large number of notifications preventing other
> notifications from being handled. This patch moves from LIFO (stack)
> semantics to FIFO (queue semantics).
> 
> [...]

Applied (which comment typo fix) to for-next/seccomp, thanks!

[1/2] seccomp: Use FIFO semantics to order notifications
      https://git.kernel.org/kees/c/4cbf6f621150
[2/2] selftests/seccomp: Ensure that notifications come in FIFO order
      https://git.kernel.org/kees/c/662340ef9218

-- 
Kees Cook