linux-kernel - Re: [PATCH v4 0/3] Handle seccomp notification preemption

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] [day] [month] [year] [list]

Message-Id: <165161294755.3926933.6572056353019699340.b4-ty@chromium.org>
Date:   Tue,  3 May 2022 14:22:30 -0700
From:   Kees Cook <keescook@...omium.org>
To:     linux-kernel@...r.kernel.org, sargun@...gun.me,
        containers@...ts.linux.dev
Cc:     Kees Cook <keescook@...omium.org>, wad@...omium.org,
        rodrigo@...volk.io, gscrivan@...hat.com, luto@...capital.net,
        alban@...volk.io, tycho@...ho.pizza,
        Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH v4 0/3] Handle seccomp notification preemption

On Tue, 3 May 2022 01:09:55 -0700, Sargun Dhillon wrote:
> This patchset addresses a race condition we've dealt with recently with
> seccomp. Specifically programs interrupting syscalls while they're in
> progress. This was exacerbated by Golang's[1] recent adoption of
> "Non-cooperative goroutine preemption", in which they try to interrupt any
> syscall that's been running for more than 10ms. During certain syscalls,
> it's non-trivial to write them in a reetrant manner in userspace (mount).
> 
> [...]

Applied to for-next/seccomp, thanks!

[1/3] seccomp: Add wait_killable semantic to seccomp user notifier
      https://git.kernel.org/kees/c/c2aa2dfef243
[2/3] selftests/seccomp: Refactor get_proc_stat to split out file reading code
      https://git.kernel.org/kees/c/922a1b520c5f
[3/3] selftests/seccomp: Add test for wait killable notifier
      https://git.kernel.org/kees/c/3b96a9c522b2

-- 
Kees Cook