From: Guenter Roeck <linux@roeck-us.net>
To: paulmck@linux.vnet.ibm.com
Cc: Boqun Feng <boqun.feng@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: next: suspicious RCU usage message since commit 'rcu: Remove superfluous versions of rcu_read_lock_sched_held()'
Date: Mon, 25 Apr 2016 20:13:09 -0700 [thread overview]
Message-ID: <571EDCC5.1080106@roeck-us.net> (raw)
In-Reply-To: <20160425204921.GN3874@linux.vnet.ibm.com>
On 04/25/2016 01:49 PM, Paul E. McKenney wrote:
> On Mon, Apr 25, 2016 at 01:25:10PM -0700, Guenter Roeck wrote:
>> On Mon, Apr 25, 2016 at 10:12:39AM -0700, Paul E. McKenney wrote:
>>> On Sun, Apr 24, 2016 at 11:26:41PM -0700, Guenter Roeck wrote:
>>>> On 04/24/2016 10:49 PM, Paul E. McKenney wrote:
>>>>> On Sun, Apr 24, 2016 at 10:37:25PM -0700, Guenter Roeck wrote:
>>>>>> On 04/24/2016 10:28 PM, Paul E. McKenney wrote:
>>>>>>> On Sun, Apr 24, 2016 at 04:56:38PM -0700, Guenter Roeck wrote:
>>>
>>> [ . . . ]
>>>
>>>>>>>> After making the same change in _pwrdm_state_switch(), the traceback is gone
>>>>>>> >from my tests (beagle, beagle-xm, and overo-tobi).
>>>>>>>
>>>>>>> Very good!
>>>>>>>
>>>>>>> (And yes, you normally find these one at a time...)
>>>>>>>
>>>>>> Are you going to submit a formal patch ?
>>>>>
>>>>> I can, but please feel free to send mine along with yours, if you wish.
>>>>>
>>>> I think it would be best if you send a single patch which fixes both calls.
>>>
>>> Like this one?
>>>
>>> If so, could you please run it to make sure that it actually fixes the
>>> problem? And if it does, would you be willing to give me a Tested-by?
>>>
>> It does. Tested-by: inline below.
>
> Got it, thank you!
>
> If the ARM guys are willing to take this, it might hit the next merge
> window, or perhaps they will take it as an exception. If I push it
> up my usual route, it will be a bit later.
>
> I just now sent it out, so hopefully they will grab it. ;-)
>
Hi Paul,
Either it fixes a zero-day bug which was exposed by 'rcu: Remove superfluous
versions ...", or it fixes a problem with that commit, so I would hope that
_someone_ will pick it up.
Anyway, thanks a lot for looking into it, and for the patch!
Guenter
next prev parent reply other threads:[~2016-04-26 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 21:14 next: suspicious RCU usage message since commit 'rcu: Remove superfluous versions of rcu_read_lock_sched_held()' Guenter Roeck
2016-04-24 21:31 ` Paul E. McKenney
2016-04-24 23:56 ` Guenter Roeck
2016-04-25 5:28 ` Paul E. McKenney
2016-04-25 5:37 ` Guenter Roeck
2016-04-25 5:49 ` Paul E. McKenney
2016-04-25 6:26 ` Guenter Roeck
2016-04-25 17:12 ` Paul E. McKenney
2016-04-25 20:25 ` Guenter Roeck
2016-04-25 20:49 ` Paul E. McKenney
2016-04-26 3:13 ` Guenter Roeck [this message]
2016-05-14 15:42 ` Guenter Roeck
2016-05-16 17:00 ` 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=571EDCC5.1080106@roeck-us.net \
--to=linux@roeck-us.net \
--cc=boqun.feng@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.