Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220429023113.74993-1-sargun@sargun.me>
In-Reply-To: <20220429023113.74993-1-sargun@sargun.me>
From:   Rodrigo Campos <rodrigo@kinvolk.io>
Date:   Fri, 29 Apr 2022 11:24:54 +0200
Message-ID: <CACaBj2Z7BpLMYYEbqB8=gyQqbJdevLrRMbDcDzRAtP=Tn+4Ftg@mail.gmail.com>
Subject: Re: [PATCH v3 0/2] Handle seccomp notification preemption
To:     Sargun Dhillon <sargun@sargun.me>
Cc:     Kees Cook <keescook@chromium.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux Containers <containers@lists.linux-foundation.org>,
        Christian Brauner <christian.brauner@ubuntu.com>,
        Giuseppe Scrivano <gscrivan@redhat.com>,
        Will Drewry <wad@chromium.org>,
        Andy Lutomirski <luto@amacapital.net>,
        Alban Crequy <alban@kinvolk.io>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Apr 29, 2022 at 4:32 AM Sargun Dhillon <sargun@sargun.me> wrote:
>
> This patchset addresses a race condition we've dealt with recently with
> seccomp. Specifically programs interrupting syscalls while they're in

I think you sent it to the wrong containers ml. It should be
containers@lists.linux.dev, right?

If the next time you can cc me to rodrigo@sdfg.com.ar instead, it will be great.


Best,
Rodrigo