public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: INFO: suspicious RCU usage. on 3.3.0-rc7-next-20120316
Date: Mon, 19 Mar 2012 10:01:22 -0700	[thread overview]
Message-ID: <20120319170122.GG11069@google.com> (raw)
In-Reply-To: <4F661E89.5050000@gmail.com>

On Sun, Mar 18, 2012 at 10:42:33AM -0700, Justin P. Mattock wrote:
> >Known problem.  The following pending patchset should fix the problem.
> >
> >   http://thread.gmane.org/gmane.linux.kernel/1263989
> >
> >Jens?
> >
> >Thakns.
> >
> 
> cool thanks for the info..
> I went and applied your patches(all 5) and there is fuzz, and some
> errors with linux-next.
> seems the suspicious message is still there, but the system boots up
> just fine with the patches in.
>  maybe manually applying them by hand is what I need to do for -next
> so I dont miss anything important with the patch that takes care of
> the suspicious message.

Hmm... weird.  I just double check and the patch series makes the
warning go away.  Can you please try the following git branch instead?

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git blkcg-stats

Thanks.

-- 
tejun

  reply	other threads:[~2012-03-19 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 15:36 INFO: suspicious RCU usage. on 3.3.0-rc7-next-20120316 Justin P. Mattock
2012-03-18 15:54 ` Tejun Heo
2012-03-18 17:42   ` Justin P. Mattock
2012-03-19 17:01     ` Tejun Heo [this message]
2012-03-20  6:04       ` Justin P. Mattock
     [not found]       ` <CAKFRV=N5cF7MTuSpOjySmGgJNnW2b1tBZeF5W4XckA7dMSXysg@mail.gmail.com>
2012-03-23  4:23         ` Justin P. Mattock

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=20120319170122.GG11069@google.com \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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