linux-kernel - linux-next: bad commit in the luto-misc tree

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-next>] [day] [month] [year] [list]

Date:	Mon, 5 Jan 2015 10:35:47 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: linux-next: bad commit in the luto-misc tree

Hi Andy,

I noticed commit 7d032e5b1042 ("[TEST ONLY] Force RCU NMI nesting") has
no Signed-off-by ... I understand that this is for testing, but that
is *not* what linux-next is really for.  Especially given that that
commit is x86 only, it should be used for unit testing. not a wider
audience like this.

I am also not sure about 9f29ed3365cd ("[DO NOT APPLY] rcu: Make
rcu_nmi_enter() handle nesting") ...  (it is, in particular, not
Signed-off-by the committer, you).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped