From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [-next] fs/eventpoll.c:545 suspicious rcu_dereference_check() usage
Date: Sun, 24 Mar 2013 11:40:36 +0300 [thread overview]
Message-ID: <20130324084036.GB2297@swordfish> (raw)
In-Reply-To: <20130323173422.GA13205@dcvr.yhbt.net>
On (03/23/13 17:34), Eric Wong wrote:
> Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> > [ 3.163894] ===============================
> > [ 3.163895] [ INFO: suspicious RCU usage. ]
> > [ 3.163897] 3.9.0-rc3-next-20130322-dbg-dirty #1 Not tainted
> > [ 3.163898] -------------------------------
> > [ 3.163900] fs/eventpoll.c:545 suspicious rcu_dereference_check() usage!
>
> Sorry about this, I've fixed this and it is in the latest -mm
>
> http://mid.gmane.org/20130321192748.6D86F31C23C@corp2gmr1-1.hot.corp.google.com
>
thanks a lot.
-ss
prev parent reply other threads:[~2013-03-24 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:42 [-next] fs/eventpoll.c:545 suspicious rcu_dereference_check() usage Sergey Senozhatsky
2013-03-23 17:34 ` Eric Wong
2013-03-24 8:40 ` Sergey Senozhatsky [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=20130324084036.GB2297@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).