All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
To: lkp@lists.01.org
Subject: Re: [locktorture] 5f6a140f30: kernel BUG at drivers/base/driver.c:153!
Date: Thu, 10 Sep 2015 10:18:02 -0700	[thread overview]
Message-ID: <20150910171802.GF4029@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150910135942.GA21983@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Thu, Sep 10, 2015 at 03:59:42PM +0200, Oleg Nesterov wrote:
> On 09/09, Paul E. McKenney wrote:
> >
> > This is obsolete, but its replacement is the same patch.
> 
> fbe3b97183f84155d81e506b1aa7d2ce986f7a36 in linux-rcu.git#experimental
> I guess?
> 
> > Oleg, Davidlohr, am I missing something on how percpu_rwsem or
> > locktorture work?
> 
> No, I think the patch is fine. Thanks for doing this! I was going to
> send something like this change too. And in fact I am still thinking
> about another test which plays with rcu_sync only, but probably we
> need some cleanups first (and we need them anyway). I'll try to do
> this a bit later.

I would welcome an rcu_sync-specific torture patch!

> > +void torture_percpu_rwsem_init(void)
> > +{
> > +	BUG_ON(percpu_init_rwsem(&pcpu_rwsem));
> > +}
> > +
> 
> Aha, we don't really need this... I mean we can use the static initialiser
> which can also be used by uprobes and cgroups. I'll try to send the patch
> tomorrow.

Very good, please do!

							Thanx, Paul


      reply	other threads:[~2015-09-10 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 18:03 [locktorture] 5f6a140f30: kernel BUG at drivers/base/driver.c:153! kernel test robot
2015-09-09 18:56 ` Paul E. McKenney
2015-09-10  1:04   ` Fengguang Wu
2015-09-10 13:59   ` Oleg Nesterov
2015-09-10 17:18     ` Paul E. McKenney [this message]

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=20150910171802.GF4029@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=lkp@lists.01.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.