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, Colin Ian King <colin.king@canonical.com>
Subject: [GIT PULL] seccomp fix for v4.14-rc5
Date: Tue, 10 Oct 2017 11:50:24 -0700	[thread overview]
Message-ID: <20171010185024.GA144580@beast> (raw)

Hi,

Please pull this minor seccomp fix for v4.14-rc5. I debated sending this
at all for v4.14, but since it fixes a minor issue in the prior fix, which
also went to -stable, it seemed better to just get all of it cleaned up
right now.

Thanks!

-Kees

The following changes since commit 66a733ea6b611aecf0119514d2dddab5f9d6c01e:

  seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter() (2017-09-27 22:51:12 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v4.14-rc5

for you to fetch changes up to 084f5601c357e4ee59cf0712200d3f5c4710ba40:

  seccomp: make function __get_seccomp_filter static (2017-10-10 11:45:29 -0700)

----------------------------------------------------------------
- fix missed "static" to avoid Sparse warning (Colin King).

----------------------------------------------------------------
Colin Ian King (1):
      seccomp: make function __get_seccomp_filter static

 kernel/seccomp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-10-10 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171010185024.GA144580@beast \
    --to=keescook@chromium.org \
    --cc=colin.king@canonical.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.