From: Benjamin LaHaise Subject: Re: [PATCH] aio: rcu_read_lock protection for new rcu_dereference calls Date: Mon, 9 Sep 2013 12:31:30 -0400 Message-ID: <20130909163130.GB11250@kvack.org> References: <1378649444-28054-1-git-send-email-artem.savkov@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: viro@zeniv.linux.org.uk, linux-aio@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Artem Savkov Return-path: Content-Disposition: inline In-Reply-To: <1378649444-28054-1-git-send-email-artem.savkov@gmail.com> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org 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." -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org