public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, Josh Triplett <josh@joshtriplett.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: do not include rtmutex_common.h unconditionally
Date: Wed, 18 Oct 2017 13:42:59 -0700	[thread overview]
Message-ID: <20171018204259.GR3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171018161621.3o7fljv4wl3geutv@linutronix.de>

On Wed, Oct 18, 2017 at 06:16:21PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-10-18 08:39:46 [-0700], Paul E. McKenney wrote:
> > Thank you very much, hand-applied as a preparatory patch for
> > "Suppress lockdep false-positive ->boost_mtx complaints", please see
> > below.
> okay.
> 
> > What I don't understand is why 0day test robot didn't complain about
> > my copy of the exact same patch.  Or maybe it did and I fat-fingered it?
> > Except that I have gotten "BUILD SUCCESS" reports for commits including
> > that one.
> 
> I don't know. It is a "defconfig" for m32r. Unless it skipped that one,
> dunno.

No idea here, either.

> > commit a06f537e75ea0a9e81245ede1b97bb3a5762b81b
> > Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > Date:   Wed Oct 18 08:33:44 2017 -0700
> > 
> >     rcu: do not include rtmutex_common.h unconditionally
> >     
> >     This commit adjusts include files and provides definitions in preparation
> >     for suppressing lockdep false-positive ->boost_mtx complaints.  Without
> >     this preparation, architectures not supporting rt_mutex will get build
> >     failures.
> >     
> >     Reported-by: kbuild test robot <fengguang.wu@intel.com>
> >     Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> >     Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > 
> > diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> > index fed95fa941e6..969eae45f05d 100644
> > --- a/kernel/rcu/tree_plugin.h
> > +++ b/kernel/rcu/tree_plugin.h
> > @@ -54,6 +54,7 @@ DEFINE_PER_CPU(char, rcu_cpu_has_work);
> >   * This probably needs to be excluded from -rt builds.
> >   */
> >  #define rt_mutex_owner(a) ({ WARN_ON_ONCE(1); NULL; })
> > +#define rt_mutex_futex_unlock(x) WARN_ON_ONCE(1)
> >  
> >  #endif /* #else #ifdef CONFIG_RCU_BOOST */
> >  
> > @@ -911,8 +912,6 @@ void exit_rcu(void)
> >  
> >  #ifdef CONFIG_RCU_BOOST
> >  
> > -#include "../locking/rtmutex_common.h"
> > -
> >  static void rcu_wake_cond(struct task_struct *t, int status)
> >  {
> >  	/*
> 
> So this probably works. This is
>   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?h=rcu%2Fdev&id=a06f537e75ea0a9e81245ede1b97bb3a5762b81b&context=40&ignorews=0&dt=0
> 
> and the rtmutex_common is still in the ifdef which confused me at first.
> But then you wrote "preparatory" and I saw the following patch
>   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?h=rcu/next&id=33d7471ce21202ce954993552c2e0298d9e0f031
> 
> where you move that include rtmutex_common.h. You shouldn't do that
> because "rt_mutex_futex_unlock()" has been added added here for the
> !BOOST + TREE case. So I thing this should break your build if you
> disable CONFIG_FUTEX (which in turn unselects CONFIg_RT_MUTEX).

Builds for me on x86 and 0day test robot hasn't complained, but might
as well get it right.  The new commits are:

a06f537e75ea ("rcu: do not include rtmutex_common.h unconditionally")
4a0fb5d70bb2 ("rcu: Suppress lockdep false-positive ->boost_mtx complaints")

							Thanx, Paul

  reply	other threads:[~2017-10-18 20:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201710180754.irSSdw3W%fengguang.wu@intel.com>
     [not found] ` <20171018041447.GF3521@linux.vnet.ibm.com>
     [not found]   ` <20171018073209.7l4p3lloqiw4bm6y@linutronix.de>
2017-10-18  8:34     ` [PATCH] rcu: do not include rtmutex_common.h unconditionally Sebastian Andrzej Siewior
2017-10-18 15:39       ` Paul E. McKenney
2017-10-18 16:16         ` Sebastian Andrzej Siewior
2017-10-18 20:42           ` Paul E. McKenney [this message]
2017-10-19 18:15             ` Sebastian Andrzej Siewior
2017-10-19 19:50               ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171018204259.GR3521@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=fengguang.wu@intel.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox