public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Benjamin LaHaise <bcrl@kvack.org>,
	linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] aio_ring_remap: turn the ctx->dead check into WARN_ON()
Date: Wed, 17 Jun 2015 20:42:45 +0200	[thread overview]
Message-ID: <20150617184245.GA9295@redhat.com> (raw)
In-Reply-To: <x49pp4uns04.fsf@segfault.boston.devel.redhat.com>

On 06/17, Jeff Moyer wrote:
>
> Oleg Nesterov <oleg@redhat.com> writes:
>
> > atomic_read(&ctx->dead) in aio_ring_remap() looks confusing.
> > kill_ioctx() sets ctx->dead and removes ctx from ->ioctx_table
> > "atomically" under mm->ioctx_lock, so aio_ring_remap() can never
> > see a dead ctx.
> >
> > If we really want this check, we should put it under WARN_ON()
> > and it should not depend on aio_ring_file == file.
>
> Just get rid of the check, it doesn't make any sense.

Yes, agreed, will redo/resend tomorrow.

Thanks!

> -Jeff
> 
> >
> > Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> > ---
> >  fs/aio.c |   16 ++++++++--------
> >  1 files changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/fs/aio.c b/fs/aio.c
> > index 480440f..0693333 100644
> > --- a/fs/aio.c
> > +++ b/fs/aio.c
> > @@ -325,14 +325,14 @@ static int aio_ring_remap(struct file *file, struct vm_area_struct *vma)
> >  	rcu_read_lock();
> >  	table = rcu_dereference(mm->ioctx_table);
> >  	for (i = 0; i < table->nr; i++) {
> > -		struct kioctx *ctx;
> > -
> > -		ctx = table->table[i];
> > -		if (ctx && ctx->aio_ring_file == file) {
> > -			if (!atomic_read(&ctx->dead)) {
> > -				ctx->user_id = ctx->mmap_base = vma->vm_start;
> > -				res = 0;
> > -			}
> > +		struct kioctx *ctx = table->table[i];
> > +
> > +		if (!ctx || WARN_ON(atomic_read(&ctx->dead)))
> > +			continue;
> > +
> > +		if (ctx->aio_ring_file == file) {
> > +			ctx->user_id = ctx->mmap_base = vma->vm_start;
> > +			res = 0;
> >  			break;
> >  		}
> >  	}


  reply	other threads:[~2015-06-17 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 23:04 [PATCH 0/3] aio: ctx->dead cleanups Oleg Nesterov
2015-06-16 23:04 ` [PATCH 1/3] aio_ring_remap: turn the ctx->dead check into WARN_ON() Oleg Nesterov
2015-06-17 17:50   ` Jeff Moyer
2015-06-17 18:42     ` Oleg Nesterov [this message]
2015-06-16 23:04 ` [PATCH 2/3] aio: make aio_ring->dead boolean Oleg Nesterov
2015-06-16 23:50   ` [PATCH v2 " Oleg Nesterov
2015-06-17 19:33     ` Jeff Moyer
2015-06-16 23:04 ` [PATCH 3/3] aio_free_ring: don't do page_count(NULL) Oleg Nesterov
2015-06-17 18:26   ` Jeff Moyer
2015-06-17  0:39 ` [PATCH 0/3] aio: ctx->dead cleanups Al Viro
2015-06-17  0:50   ` Al Viro
2015-06-17  1:22     ` Oleg Nesterov
2015-06-18 16:08       ` Oleg Nesterov
2015-06-17  1:05   ` Oleg Nesterov
2015-06-17  1:14     ` Oleg Nesterov
2015-06-17  1:32       ` Oleg Nesterov

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=20150617184245.GA9295@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcrl@kvack.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-aio@kvack.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