All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] seccomp updates for next
Date: Mon, 26 Jun 2017 10:02:05 -0700	[thread overview]
Message-ID: <20170626170205.GA108402@beast> (raw)

Hi James,

Please pull these seccomp changes for next. These are all tiny changes,
but I got delayed sending them to you. I'd like have these land for v4.13;
I should have sent them for v4.12. :P

Thanks!

-Kees

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:

  Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next

for you to fetch changes up to 0b5fa2290637a3235898d18dc0e7a136783f1bd2:

  seccomp: Switch from atomic_t to recount_t (2017-06-26 09:24:00 -0700)

----------------------------------------------------------------
- cleans up some coding style issues
- adjusts selftests to work correctly under Bionic
- switch from atomic_t to refcount_t for usage tracking

----------------------------------------------------------------
Kees Cook (3):
      seccomp: Clean up core dump logic
      seccomp: Adjust selftests to avoid double-join
      seccomp: Switch from atomic_t to recount_t

 kernel/seccomp.c                              | 16 ++++-----
 tools/testing/selftests/seccomp/seccomp_bpf.c | 51 ++++++++++++++++++---------
 2 files changed, 42 insertions(+), 25 deletions(-)

-- 
Kees Cook
Pixel Security

WARNING: multiple messages have this Message-ID (diff)
From: keescook@chromium.org (Kees Cook)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] seccomp updates for next
Date: Mon, 26 Jun 2017 10:02:05 -0700	[thread overview]
Message-ID: <20170626170205.GA108402@beast> (raw)

Hi James,

Please pull these seccomp changes for next. These are all tiny changes,
but I got delayed sending them to you. I'd like have these land for v4.13;
I should have sent them for v4.12. :P

Thanks!

-Kees

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:

  Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next

for you to fetch changes up to 0b5fa2290637a3235898d18dc0e7a136783f1bd2:

  seccomp: Switch from atomic_t to recount_t (2017-06-26 09:24:00 -0700)

----------------------------------------------------------------
- cleans up some coding style issues
- adjusts selftests to work correctly under Bionic
- switch from atomic_t to refcount_t for usage tracking

----------------------------------------------------------------
Kees Cook (3):
      seccomp: Clean up core dump logic
      seccomp: Adjust selftests to avoid double-join
      seccomp: Switch from atomic_t to recount_t

 kernel/seccomp.c                              | 16 ++++-----
 tools/testing/selftests/seccomp/seccomp_bpf.c | 51 ++++++++++++++++++---------
 2 files changed, 42 insertions(+), 25 deletions(-)

-- 
Kees Cook
Pixel Security
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-06-26 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 17:02 Kees Cook [this message]
2017-06-26 17:02 ` [GIT PULL] seccomp updates for next Kees Cook
2017-06-27  3:27 ` James Morris
2017-06-27  3:27   ` James Morris
2017-08-15 22:03 Kees Cook
2017-08-15 22:03 ` Kees Cook
2017-08-16  2:33 ` James Morris
2017-08-16  2:33   ` James Morris
2017-11-29  0:38 Kees Cook
2017-11-29  0:38 ` Kees Cook
2017-11-29  1:55 ` James Morris
2017-11-29  1:55   ` James Morris
2018-12-12 23:16 Kees Cook
2018-12-13  0:08 ` James Morris

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=20170626170205.GA108402@beast \
    --to=keescook@chromium.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.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.