From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Vivek Goyal <vgoyal@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: INFO: suspicious RCU usage. on 3.3.0-rc7-next-20120316
Date: Thu, 22 Mar 2012 21:23:46 -0700 [thread overview]
Message-ID: <4F6BFAD2.5020103@gmail.com> (raw)
In-Reply-To: <CAKFRV=N5cF7MTuSpOjySmGgJNnW2b1tBZeF5W4XckA7dMSXysg@mail.gmail.com>
On 03/19/2012 11:17 AM, Justin Mattock wrote:
> Alright!! Will pull that branch as soon as i get to a stable connection
> later today.. as for the patch i probably missed something with the fuzz
> it was generating
>
> Justin P. Mattock
>
> On Mar 19, 2012 10:01 AM, "Tejun Heo" <tj@kernel.org
> <mailto:tj@kernel.org>> wrote:
>
> 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
> <http://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git> blkcg-stats
>
> Thanks.
>
> --
> tejun
alright! looks like on the main linux-next this warning is
fixed(assuming your patches have been pushed in).
uname -r 3.3.0-next-20120322-00001-gba6003c
Thanks for the info and help with this!
Justin P. Mattock
prev parent reply other threads:[~2012-03-23 4:23 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
2012-03-20 6:04 ` Justin P. Mattock
[not found] ` <CAKFRV=N5cF7MTuSpOjySmGgJNnW2b1tBZeF5W4XckA7dMSXysg@mail.gmail.com>
2012-03-23 4:23 ` Justin P. Mattock [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=4F6BFAD2.5020103@gmail.com \
--to=justinmattock@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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