Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Kees Cook <keescook@chromium.org>
To:     linux-kernel@vger.kernel.org, sargun@sargun.me, luto@kernel.org,
        tycho@tycho.pizza
Cc:     Kees Cook <keescook@chromium.org>,
        Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 1/2] seccomp: Use FIFO semantics to order notifications
Date:   Fri, 29 Apr 2022 11:50:00 -0700
Message-Id: <165125819819.3692727.9306925856353932810.b4-ty@chromium.org>
In-Reply-To: <20220428015447.13661-1-sargun@sargun.me>
References: <20220428015447.13661-1-sargun@sargun.me>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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