From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Paul Cercueil <paul@crapouillou.net>,
wanghongzhe <wanghongzhe@huawei.com>
Subject: [GIT PULL] seccomp updates for v5.12-rc1
Date: Wed, 17 Feb 2021 12:54:03 -0800 [thread overview]
Message-ID: <202102171252.B769A2FB@keescook> (raw)
Hi Linus,
Please pull these two small seccomp updates for v5.12-rc1. This contains a
fix for a build failure that went unnoticed for many years, and a memory
barrier correction.
Thanks!
-Kees
The following changes since commit e71ba9452f0b5b2e8dc8aa5445198cd9214a6a62:
Linux 5.11-rc2 (2021-01-03 15:55:30 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.12-rc1
for you to fetch changes up to a381b70a1cf88e4a2d54f24d59abdcad0ff2dfe6:
seccomp: Improve performace by optimizing rmb() (2021-02-10 12:40:11 -0800)
----------------------------------------------------------------
seccomp updates for v5.12-rc1
- Fix a non-FILTER build failure for some architectures (Paul Cercueil)
- Improve performance with correct memory barrier (wanghongzhe)
----------------------------------------------------------------
Paul Cercueil (1):
seccomp: Add missing return in non-void function
wanghongzhe (1):
seccomp: Improve performace by optimizing rmb()
kernel/seccomp.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
Kees Cook
next reply other threads:[~2021-02-17 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 20:54 Kees Cook [this message]
2021-02-22 1:21 ` [GIT PULL] seccomp updates for v5.12-rc1 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=202102171252.B769A2FB@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=torvalds@linux-foundation.org \
--cc=wanghongzhe@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox