From: Benjamin LaHaise <bcrl@kvack.org>
To: Artem Savkov <artem.savkov@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aio: rcu_read_lock protection for new rcu_dereference calls
Date: Mon, 9 Sep 2013 12:31:30 -0400 [thread overview]
Message-ID: <20130909163130.GB11250@kvack.org> (raw)
In-Reply-To: <1378649444-28054-1-git-send-email-artem.savkov@gmail.com>
On Sun, Sep 08, 2013 at 06:10:43PM +0400, Artem Savkov wrote:
> Patch "aio: fix rcu sparse warnings introduced by ioctx table lookup patch"
> (77d30b14d24e557f89c41980011d72428514d729 in linux-next.git) introduced a
> couple of new rcu_dereference calls which are not protected by rcu_read_lock
> and result in following warnings during syscall fuzzing(trinity):
Applied. Thanks Artem.
-ben
--
"Thought is the essence of where you are now."
prev parent reply other threads:[~2013-09-09 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 14:10 Artem Savkov
2013-09-09 2:20 ` Gu Zheng
2013-09-09 16:31 ` Benjamin LaHaise [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=20130909163130.GB11250@kvack.org \
--to=bcrl@kvack.org \
--cc=artem.savkov@gmail.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®