From: Jeff Moyer <jmoyer@redhat.com>
To: Nick Piggin <npiggin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] fs: aio fix rcu lookup
Date: Fri, 14 Jan 2011 09:52:47 -0500 [thread overview]
Message-ID: <x494o9bbkqo.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <AANLkTimMwZnm3UKvmrPscBeZF77vh1sW0ERO1tuv1oNW@mail.gmail.com> (Nick Piggin's message of "Fri, 14 Jan 2011 12:35:32 +1100")
Nick Piggin <npiggin@gmail.com> writes:
> Hi,
>
> While hunting down a bug in NFS's AIO, I believe I found this
> buggy code...
>
> fs: aio fix rcu ioctx lookup
>
> aio-dio-invalidate-failure GPFs in aio_put_req from io_submit.
>
> lookup_ioctx doesn't implement the rcu lookup pattern properly.
> rcu_read_lock does not prevent refcount going to zero, so we
> might take a refcount on a zero count ioctx.
So, does this patch fix the problem? You didn't actually say....
> Signed-off-by: Nick Piggin <npiggin@kernel.dk>
>
> Index: linux-2.6/fs/aio.c
> ===================================================================
> --- linux-2.6.orig/fs/aio.c 2011-01-14 00:29:00.000000000 +1100
> +++ linux-2.6/fs/aio.c 2011-01-14 11:31:47.000000000 +1100
> @@ -239,15 +239,23 @@ static void __put_ioctx(struct kioctx *c
> call_rcu(&ctx->rcu_head, ctx_rcu_free);
> }
>
> -#define get_ioctx(kioctx) do { \
> - BUG_ON(atomic_read(&(kioctx)->users) <= 0); \
> - atomic_inc(&(kioctx)->users); \
> -} while (0)
> -#define put_ioctx(kioctx) do { \
> - BUG_ON(atomic_read(&(kioctx)->users) <= 0); \
> - if (unlikely(atomic_dec_and_test(&(kioctx)->users))) \
> - __put_ioctx(kioctx); \
> -} while (0)
> +static inline void get_ioctx(struct kioctx *kioctx)
> +{
> + BUG_ON(atomic_read(&kioctx->users) <= 0);
> + atomic_inc(&kioctx->users);
> +}
> +
> +static inline int try_get_ioctx(struct kioctx *kioctx)
> +{
> + return atomic_inc_not_zero(&kioctx->users);
> +}
> +
> +static inline void put_ioctx(struct kioctx *kioctx)
> +{
> + BUG_ON(atomic_read(&kioctx->users) <= 0);
> + if (unlikely(atomic_dec_and_test(&kioctx->users)))
> + __put_ioctx(kioctx);
> +}
Why did you switch from macros? Personal preference? Can you at least
mention it in the changelog?
>
> /* ioctx_alloc
> * Allocates and initializes an ioctx. Returns an ERR_PTR if it failed.
> @@ -601,8 +609,7 @@ static struct kioctx *lookup_ioctx(unsig
> rcu_read_lock();
>
> hlist_for_each_entry_rcu(ctx, n, &mm->ioctx_list, list) {
> - if (ctx->user_id == ctx_id && !ctx->dead) {
> - get_ioctx(ctx);
> + if (ctx->user_id == ctx_id && !ctx->dead && try_get_ioctx(ctx)){
> ret = ctx;
> break;
> }
next prev parent reply other threads:[~2011-01-14 14:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 1:35 [patch] fs: aio fix rcu lookup Nick Piggin
2011-01-14 14:52 ` Jeff Moyer [this message]
2011-01-14 15:00 ` Nick Piggin
2011-01-17 19:07 ` Jeff Moyer
2011-01-17 23:24 ` Nick Piggin
2011-01-18 17:21 ` Jeff Moyer
2011-01-18 19:01 ` Jan Kara
2011-01-18 22:17 ` Nick Piggin
2011-01-18 23:00 ` Jeff Moyer
2011-01-18 23:05 ` Nick Piggin
2011-01-18 23:52 ` Jan Kara
2011-01-19 0:20 ` Nick Piggin
2011-01-19 13:21 ` Jan Kara
2011-01-19 16:03 ` Nick Piggin
2011-01-19 16:50 ` Jan Kara
2011-01-19 17:37 ` Nick Piggin
2011-01-20 20:21 ` Jan Kara
2011-01-19 19:13 ` Jeff Moyer
2011-01-19 19:46 ` Jeff Moyer
2011-01-19 20:18 ` Nick Piggin
2011-01-19 20:32 ` Jeff Moyer
2011-01-19 20:45 ` Nick Piggin
2011-01-19 21:03 ` Jeff Moyer
2011-01-19 21:20 ` Nick Piggin
2011-01-20 4:03 ` Paul E. McKenney
2011-01-20 18:31 ` Nick Piggin
2011-01-20 20:02 ` Paul E. McKenney
2011-01-20 20:15 ` Eric Dumazet
2011-01-21 21:22 ` Paul E. McKenney
2011-01-20 20:16 ` Jan Kara
2011-01-20 21:16 ` Jeff Moyer
2011-02-01 16:24 ` Jan Kara
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=x494o9bbkqo.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).