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:	Sun, 4 Jan 2015 15:42:31 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: linux-next: bad commit in the luto-misc tree

On Sun, Jan 4, 2015 at 3:35 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 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.

Sorry.  I totally failed here.  I swear I rebased onto the latest RCU
tree, double-checked it, and pushed that exact revision to luto/next.
Somehow I pushed a much older development commit.  I have no idea how
I did that.  I didn't even know I still had that commit around at all.

Fixed now, I think.  Next time I will push to luto/next and
double-check that I pushed the commit I thought I pushed.

Sorry for causing trouble.

--Andy



>
> 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



-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ