All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jann Horn <jannh@google.com>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] seccomp fix for v5.18-rc6
Date: Tue, 3 May 2022 14:34:07 -0700	[thread overview]
Message-ID: <202205031433.6CB037ED@keescook> (raw)

Hi Linus,

Please pull this small seccomp selftest fix for v5.18-rc6. The selftest
environment assumptions that seccomp depended on changed slightly in
v5.17 and Jann found a simple fix.

Thanks!

-Kees

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.18-rc6

for you to fetch changes up to 2bfed7d2ffa5d86c462d3e2067f2832eaf8c04c7:

  selftests/seccomp: Don't call read() on TTY from background pgrp (2022-04-29 11:28:41 -0700)

----------------------------------------------------------------
seccomp fix for v5.18-rc6

- Avoid using stdin for read syscall testing (Jann Horn)

----------------------------------------------------------------
Jann Horn (1):
      selftests/seccomp: Don't call read() on TTY from background pgrp

 tools/testing/selftests/seccomp/seccomp_bpf.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2022-05-03 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 21:34 Kees Cook [this message]
2022-05-03 23:08 ` [GIT PULL] seccomp fix for v5.18-rc6 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202205031433.6CB037ED@keescook \
    --to=keescook@chromium.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.