All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: Benjamin <bcrl@kvack.org>,
	linux-aio@kvack.org, fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Kent <kmo@daterainc.com>,
	Kristian Nielsen <knielsen@knielsen-hq.org>
Subject: Re: [PATCH] aio: clean up aio ring in the fail path
Date: Wed, 4 Dec 2013 09:54:16 -0500	[thread overview]
Message-ID: <20131204145416.GA22438@redhat.com> (raw)
In-Reply-To: <529F019A.2040401@cn.fujitsu.com>

On Wed, Dec 04, 2013 at 06:19:06PM +0800, Gu Zheng wrote:
 > Clean up the aio ring file in the fail path of aio_setup_ring
 > and ioctx_alloc. And maybe it can fix the GPF issue reported by
 > Dave Jones:
 > https://lkml.org/lkml/2013/11/25/898
 > 
 > 
 > Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>
 > ---
 >  fs/aio.c |    8 ++++++--
 >  1 files changed, 6 insertions(+), 2 deletions(-)
 > 
 > diff --git a/fs/aio.c b/fs/aio.c
 > index 08159ed..6efb7f6 100644
 > --- a/fs/aio.c
 > +++ b/fs/aio.c
 > @@ -367,8 +367,10 @@ static int aio_setup_ring(struct kioctx *ctx)
 >  	if (nr_pages > AIO_RING_PAGES) {
 >  		ctx->ring_pages = kcalloc(nr_pages, sizeof(struct page *),
 >  					  GFP_KERNEL);
 > -		if (!ctx->ring_pages)
 > +		if (!ctx->ring_pages) {
 > +			put_aio_ring_file(ctx);
 >  			return -ENOMEM;
 > +		}
 >  	}
 >  

  CC      fs/aio.o
fs/aio.c: In function ‘aio_setup_ring’:
fs/aio.c:363:4: error: implicit declaration of function ‘put_aio_ring_file’ [-Werror=implicit-function-declaration]
    put_aio_ring_file(ctx);


Is this dependant on another patch ?

	Dave

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: Benjamin <bcrl@kvack.org>,
	linux-aio@kvack.org, fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Kent <kmo@daterainc.com>,
	Kristian Nielsen <knielsen@knielsen-hq.org>
Subject: Re: [PATCH] aio: clean up aio ring in the fail path
Date: Wed, 4 Dec 2013 09:54:16 -0500	[thread overview]
Message-ID: <20131204145416.GA22438@redhat.com> (raw)
In-Reply-To: <529F019A.2040401@cn.fujitsu.com>

On Wed, Dec 04, 2013 at 06:19:06PM +0800, Gu Zheng wrote:
 > Clean up the aio ring file in the fail path of aio_setup_ring
 > and ioctx_alloc. And maybe it can fix the GPF issue reported by
 > Dave Jones:
 > https://lkml.org/lkml/2013/11/25/898
 > 
 > 
 > Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>
 > ---
 >  fs/aio.c |    8 ++++++--
 >  1 files changed, 6 insertions(+), 2 deletions(-)
 > 
 > diff --git a/fs/aio.c b/fs/aio.c
 > index 08159ed..6efb7f6 100644
 > --- a/fs/aio.c
 > +++ b/fs/aio.c
 > @@ -367,8 +367,10 @@ static int aio_setup_ring(struct kioctx *ctx)
 >  	if (nr_pages > AIO_RING_PAGES) {
 >  		ctx->ring_pages = kcalloc(nr_pages, sizeof(struct page *),
 >  					  GFP_KERNEL);
 > -		if (!ctx->ring_pages)
 > +		if (!ctx->ring_pages) {
 > +			put_aio_ring_file(ctx);
 >  			return -ENOMEM;
 > +		}
 >  	}
 >  

  CC      fs/aio.o
fs/aio.c: In function ‘aio_setup_ring’:
fs/aio.c:363:4: error: implicit declaration of function ‘put_aio_ring_file’ [-Werror=implicit-function-declaration]
    put_aio_ring_file(ctx);


Is this dependant on another patch ?

	Dave


  reply	other threads:[~2013-12-04 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 10:19 [PATCH] aio: clean up aio ring in the fail path Gu Zheng
2013-12-04 14:54 ` Dave Jones [this message]
2013-12-04 14:54   ` Dave Jones
2013-12-05  1:14   ` Gu Zheng
2013-12-05  1:14     ` Gu Zheng
2013-12-05  1:22     ` Gu Zheng
2013-12-05  1:22       ` Gu Zheng
2013-12-06 15:26 ` Benjamin LaHaise
2013-12-06 15:26   ` Benjamin LaHaise
2013-12-06 15:34   ` Dave Jones
2013-12-06 15:34     ` Dave Jones
2013-12-06 15:36     ` Benjamin LaHaise
2013-12-06 15:36       ` Benjamin LaHaise

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=20131204145416.GA22438@redhat.com \
    --to=davej@redhat.com \
    --cc=bcrl@kvack.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=kmo@daterainc.com \
    --cc=knielsen@knielsen-hq.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.