From: Kent Overstreet <koverstreet@google.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] aio: correct calculation of available events
Date: Wed, 13 Feb 2013 17:33:11 -0800 [thread overview]
Message-ID: <20130214013311.GM12631@moria.home.lan> (raw)
In-Reply-To: <20130213174551.GA19958@kvack.org>
On Wed, Feb 13, 2013 at 12:45:52PM -0500, Benjamin LaHaise wrote:
> When the number of available events in the ring buffer is calculated,
> the avail calculation is incorrect when head == tail. This is harmless
> in aio_read_events_ring(), but in free_ioctx() leads to the subsequent
> WARN_ON(atomic_read(&ctx->reqs_available) > ctx->nr). Correct this.
>
> Signed-off-by: Benjamin LaHaise <bcrl@kvack.org>
> ---
> fs/aio.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/aio.c b/fs/aio.c
> index 24ba228..dc52b0c 100644
> --- a/fs/aio.c
> +++ b/fs/aio.c
> @@ -337,7 +337,8 @@ static void free_ioctx(struct kioctx *ctx)
> while (atomic_read(&ctx->reqs_available) < ctx->nr) {
> wait_event(ctx->wait, head != ctx->shadow_tail);
>
> - avail = (head < ctx->shadow_tail ? ctx->shadow_tail : ctx->nr) - head;
> + avail = (head <= ctx->shadow_tail ?
> + ctx->shadow_tail : ctx->nr) - head;
>
> atomic_add(avail, &ctx->reqs_available);
> head += avail;
> @@ -884,7 +885,7 @@ static long aio_read_events_ring(struct kioctx *ctx,
> goto out;
>
> while (ret < nr) {
> - long avail = (head < ctx->shadow_tail
> + long avail = (head <= ctx->shadow_tail
> ? ctx->shadow_tail : ctx->nr) - head;
> struct io_event *ev;
> struct page *page;
> --
> 1.7.4.1
>
>
> --
> "Thought is the essence of where you are now."
Whoops!
Reviewed-by: Kent Overstreet <koverstreet@google.com>
--
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>
prev parent reply other threads:[~2013-02-14 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 17:45 [PATCH 1/2] aio: correct calculation of available events Benjamin LaHaise
2013-02-14 1:33 ` Kent Overstreet [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=20130214013311.GM12631@moria.home.lan \
--to=koverstreet@google.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--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).