All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Hrycay <jhrycay@gmail.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: Amit Sahrawat <a.sahrawat@samsung.com>,
	Namjae Jeon <namjae.jeon@samsung.com>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	jason.hrycay@motorola.com, linux-fsdevel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 3/4] f2fs: return proper error from start_gc_thread
Date: Thu, 23 May 2013 09:32:30 -0500	[thread overview]
Message-ID: <519E287E.4010307@gmail.com> (raw)
In-Reply-To: <1369317502-14380-1-git-send-email-linkinjeon@gmail.com>

On 5/23/2013 8:58 AM, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@samsung.com>
> 
> when there is an error from kthread_run, then return proper error
> rather than returning -ENOMEM.
> 
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Amit Sahrawat <a.sahrawat@samsung.com>
> ---
>  fs/f2fs/gc.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 25b083c..03d5ba1 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -105,7 +105,7 @@ int start_gc_thread(struct f2fs_sb_info *sbi)
>  	if (IS_ERR(gc_th->f2fs_gc_task)) {
>  		kfree(gc_th);

gc_th is free'd here, save off PTR_ERR result to avoid use-after-free?

>  		sbi->gc_thread = NULL;
> -		return -ENOMEM;
> +		return PTR_ERR(gc_th->f2fs_gc_task);
>  	}
>  	return 0;
>  }
> 

--
Jason Hrycay

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may

WARNING: multiple messages have this Message-ID (diff)
From: Jason Hrycay <jhrycay@gmail.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: jaegeuk.kim@samsung.com, Amit Sahrawat <a.sahrawat@samsung.com>,
	Namjae Jeon <namjae.jeon@samsung.com>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, jason.hrycay@motorola.com
Subject: Re: [f2fs-dev] [PATCH 3/4] f2fs: return proper error from start_gc_thread
Date: Thu, 23 May 2013 09:32:30 -0500	[thread overview]
Message-ID: <519E287E.4010307@gmail.com> (raw)
In-Reply-To: <1369317502-14380-1-git-send-email-linkinjeon@gmail.com>

On 5/23/2013 8:58 AM, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@samsung.com>
> 
> when there is an error from kthread_run, then return proper error
> rather than returning -ENOMEM.
> 
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Amit Sahrawat <a.sahrawat@samsung.com>
> ---
>  fs/f2fs/gc.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 25b083c..03d5ba1 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -105,7 +105,7 @@ int start_gc_thread(struct f2fs_sb_info *sbi)
>  	if (IS_ERR(gc_th->f2fs_gc_task)) {
>  		kfree(gc_th);

gc_th is free'd here, save off PTR_ERR result to avoid use-after-free?

>  		sbi->gc_thread = NULL;
> -		return -ENOMEM;
> +		return PTR_ERR(gc_th->f2fs_gc_task);
>  	}
>  	return 0;
>  }
> 

--
Jason Hrycay

  reply	other threads:[~2013-05-23 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 13:58 [f2fs-dev] [PATCH 3/4] f2fs: return proper error from start_gc_thread Namjae Jeon
2013-05-23 13:58 ` Namjae Jeon
2013-05-23 14:32 ` Jason Hrycay [this message]
2013-05-23 14:32   ` [f2fs-dev] " Jason Hrycay
2013-05-23 22:37   ` Namjae Jeon
2013-05-23 22:37     ` Namjae Jeon

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=519E287E.4010307@gmail.com \
    --to=jhrycay@gmail.com \
    --cc=a.sahrawat@samsung.com \
    --cc=jason.hrycay@motorola.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.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 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.