linux-kernel - Re: [GIT PULL] SELinux list corruption fix for 3.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Oct 2014 07:29:59 +0200
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Morris <jmorris@...ei.org>
Cc:	LSM List <linux-security-module@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Paul Moore <paul@...l-moore.com>
Subject: Re: [GIT PULL] SELinux list corruption fix for 3.18

On Wed, Oct 15, 2014 at 7:27 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> No, the log is correct (the log always is, the back-merges can cause
> the trivial *diff* to be broken).

To add some details: the commits in there are

  f6ed66087648 Merge branch 'stable-3.18' of
git://git.infradead.org/users/pcmoore/selinux into f
  7c66bdc72bc3 selinux: fix inode security list corruption
  e7387395a07d selinux: normalize audit log formatting
  8497b78ecc9d selinux: cleanup error reporting in selinux_nlmsg_perm()
  6eb1ddc6bd3f selinux: make the netif cache namespace aware
  5e29532fed21 selinux: register nf hooks with single nf_register_hooks call
  82341ad9b962 selinux: fix a problem with IPv6 traffic denials in
selinux_ip_postroute()
  04e8d6ab1fa6 selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.

and all but the list corruption fix seem to just be duplicate commits
of things I have already gotten elsewhere. Somebody cherry-picking
commits and duplicating them?

So there are more things rotten in this tree than a back-merge.

            Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/