| 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
| ||
|
Message-ID: <20150902072918.GA2677@gmail.com> Date: Wed, 2 Sep 2015 09:29:18 +0200 From: Ingo Molnar <mingo@...nel.org> To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> Cc: Davidlohr Bueso <dave@...olabs.net>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, peterz@...radead.org Subject: Re: linux-next: build failure after merge of the rcu tree * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote: > On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > > > exported, so that Stephen gets this failure when building modules. > > > This is 04be76a9b067 (locktorture: Support rtmutex torturing) in -rcu. > > > > > > Thoughts? > > > > Right, the below should take care of it. Although I think it makes sense > > to get this into at least 4.3 even if we won't use it until 4.4. Simply > > because we already export sched_setscheduler(). If you agree I guess we > > could route via -tip. > > Given an ack from Peter or Ingo, I would happy to queue it. But we are > talking 4.4 rather than 4.3, sorry! The export looks good to me: Acked-by: Ingo Molnar <mingo@...nel.org> Thanks, Ingo -- 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