linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Kent Overstreet <koverstreet@google.com>
Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] aio: only suppress events from cancelled kiocbs if free_ioctx() is in progress
Date: Wed, 13 Feb 2013 16:52:14 -0500	[thread overview]
Message-ID: <20130213215214.GA24582@kvack.org> (raw)

The io_cancel() syscall allows for cancellation of iocbs in flight to
generate a completion event.  The current behaviour of batch_complete_aio()
is to suppress all completion events.  Some types of asynchronous operations
cannot be cancelled synchronously, and must generate a completion event at
some point after the io_cancel() syscall.  Instead, only suppress
completion events during kioctx teardown by free_ioctx().

Signed-off-by: Benjamin LaHaise <bcrl@kvack.org>
---
 fs/aio.c |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/fs/aio.c b/fs/aio.c
index 46f9dd0..1bcb818 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -81,6 +81,7 @@ struct kioctx {
 
 	/* sys_io_setup currently limits this to an unsigned int */
 	unsigned		max_reqs;
+	unsigned		dead;
 
 	unsigned long		mmap_base;
 	unsigned long		mmap_size;
@@ -311,6 +312,7 @@ static void free_ioctx(struct kioctx *ctx)
 	struct kiocb *req;
 	unsigned cpu, head, avail;
 
+	ctx->dead = 1;
 	spin_lock_irq(&ctx->ctx_lock);
 
 	while (!list_empty(&ctx->active_reqs)) {
@@ -749,7 +751,9 @@ void batch_complete_aio(struct batch_complete *batch)
 			n = rb_parent(n);
 		}
 
-		if (unlikely(xchg(&req->ki_cancel,
+		/* Suppress cancelled events if free_ioctx() is in progress. */
+		if (unlikely(req->ki_ctx->dead &&
+			     xchg(&req->ki_cancel,
 				  KIOCB_CANCELLED) == KIOCB_CANCELLED)) {
 			/*
 			 * Can't use the percpu reqs_available here - could race
-- 
1.7.4.1


-- 
"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: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

             reply	other threads:[~2013-02-13 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 21:52 Benjamin LaHaise [this message]
2013-02-14  1:40 ` [PATCH] aio: only suppress events from cancelled kiocbs if free_ioctx() is in progress Kent Overstreet

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=20130213215214.GA24582@kvack.org \
    --to=bcrl@kvack.org \
    --cc=akpm@linux-foundation.org \
    --cc=koverstreet@google.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).