mbox series

[GIT,PULL] Security subsystem: Smack updates for v5.2

Message ID alpine.LRH.2.21.1905100325330.25349@namei.org (mailing list archive)
State New, archived
Headers show
Series [GIT,PULL] Security subsystem: Smack updates for v5.2 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

Message

James Morris May 9, 2019, 5:28 p.m. UTC
From Casey: "There's one bug fix for IPv6 handling and two memory use 
improvements."

Plus a couple of further bugfixes.

The following changes since commit fe9fd2ef383c2f5883fcd3f7adce0de9ce2556ff:

  Revert "security: inode: fix a missing check for securityfs_create_file" (2019-04-10 14:59:20 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

for you to fetch changes up to 8d31a5c35ed179825a2145881ad7cd8f9907d94b:

  Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack (2019-05-06 20:24:51 -0700)

----------------------------------------------------------------
Casey Schaufler (3):
      Smack: Create smack_rule cache to optimize memory usage
      Smack: Fix IPv6 handling of 0 secmark
      Smack: Fix kbuild reported build error

James Morris (3):
      Merge branch 'smack-for-5.2' of https://github.com/cschaufler/next-smack into next-smack
      Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack
      Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack

Tetsuo Handa (1):
      smack: Check address length before reading address family

Vishal Goel (1):
      smack: removal of global rule list

 security/smack/smack.h     |  1 +
 security/smack/smack_lsm.c | 34 +++++++++++++++++++++++-----
 security/smack/smackfs.c   | 55 ++++++++++++++--------------------------------
 3 files changed, 45 insertions(+), 45 deletions(-)

Comments

Linus Torvalds May 9, 2019, 8:02 p.m. UTC | #1
On Thu, May 9, 2019 at 10:28 AM James Morris <jmorris@namei.org> wrote:
>
> From Casey: "There's one bug fix for IPv6 handling and two memory use
> improvements."
>
> Plus a couple of further bugfixes.

I'm going to stop pulling these silly security subsystem "contains
just about as many merges as regular commits" branches starting next
merge window.

Security subsystem guys: just send your pull requests to me directly.
The history is illegible with the completely random pulls in the
middle, and I'm having a hard time editing sane merge messages with
quotes from submaintainers mixed up with other quotes.

This subsystem isn't working. I'm already taking SElinux, audit and
apparmor updates directly from the submaintainers, I'd ratehr just
take the smack updates and the TPM ones that way too. Because this is
just adding confusion as things are now.

I've pulled this, just to not cause extra confusion this merge window,
so this is just a heads-up for the future.

               Linus
pr-tracker-bot@kernel.org May 9, 2019, 8:50 p.m. UTC | #2
The pull request you sent on Fri, 10 May 2019 03:28:49 +1000 (AEST):

> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/800c608c976c3f0a6d02ed7fbc600f1f6962ac73

Thank you!
Tetsuo Handa May 10, 2019, 10:50 a.m. UTC | #3
Hello, Linus.

On 2019/05/10 5:02, Linus Torvalds wrote:
> Security subsystem guys: just send your pull requests to me directly.

git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-tomoyo
contains 4 patches for this merge window

  commit cff0e6c3ec3e6230 ("tomoyo: Add a kernel config option for fuzzing testing.")
  commit ffd7af3def1985e0 ("tomoyo: Check address length before reading address family")
  commit 5385195a7b57cb3d ("tomoyo: Change pathname calculation for read-only filesystems.")
  commit 5c6b31e31adc31bd ("tomoyo: Don't emit WARNING: string while fuzzing testing.")

but I don't maintain a git tree for sending pull requests.
May I send these patches to you using below command line?

  git format-patch -4
  git send-email --to=you --cc=lsm-ml 000[1-4]-tomoyo-*.patch
Linus Torvalds May 10, 2019, 4:54 p.m. UTC | #4
On Fri, May 10, 2019 at 3:50 AM Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> but I don't maintain a git tree for sending pull requests.

Any chance you would do so?

Anyway, I am not suggesting we change anything this merge window,
that's just too painful and would be too chaotic. But I'd love for
this to be sorted out by the next one, perhaps?

                 Linus