mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Leon Yu <chianglungyu@gmail.com>, linux-kernel@vger.kernel.org
Cc: Leon Yu <chianglungyu@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] perf: fix event leak when perf_event_open() failed to create event_file
Date: Mon, 21 Mar 2016 10:02:42 +0200	[thread overview]
Message-ID: <87twk06yxp.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <1458489135-5016-1-git-send-email-chianglungyu@gmail.com>

Leon Yu <chianglungyu@gmail.com> writes:

> If something went wrong in anon_inode_getfile, event_file will be set to
> non-zero error number and able to bypass the NULL test afterward.
>
> Consolidate the error path by testing event_file with handly
> IS_ERR_OR_NULL() helper since we do want to free event in both cases.
>
> Signed-off-by: Leon Yu <chianglungyu@gmail.com>
> Fixes: 130056275ade ("perf: Do not double free")
> Cc: <stable@vger.kernel.org> # v4.5
> ---
>  kernel/events/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 6146148..5f2e19f 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8617,7 +8617,7 @@ err_alloc:
>  	 * If event_file is set, the fput() above will have called ->release()
>  	 * and that will take care of freeing the event.
>  	 */
> -	if (!event_file)
> +	if (IS_ERR_OR_NULL(event_file))
>  		free_event(event);

By this time, we have already checked for IS_ERR(event_file) once, why
not just fix it up there like so:

---
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Date: Mon, 21 Mar 2016 09:55:09 +0200
Subject: perf: Don't leak event in the syscall error path

In the error path, event_file not being NULL is used to determine
whether the event itself still needs to be free'd, so fix it up to avoid
leaking.

Reported-by: Leon Yu <chianglungyu@gmail.com>
Fixes: 130056275ade ("perf: Do not double free")
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
 kernel/events/core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index ab83640a50..cc34d55f1e 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -9414,6 +9414,7 @@ SYSCALL_DEFINE5(perf_event_open,
 					f_flags);
 	if (IS_ERR(event_file)) {
 		err = PTR_ERR(event_file);
+		event_file = NULL;
 		goto err_context;
 	}
 
-- 
2.7.0

  reply	other threads:[~2016-03-21  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20 15:52 Leon Yu
2016-03-21  8:02 ` Alexander Shishkin [this message]
2016-03-21 15:21   ` Leon Yu
2016-03-31  9:19   ` [tip:perf/core] perf/core: Don't leak event in the syscall error path tip-bot for Alexander Shishkin

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=87twk06yxp.fsf@ashishki-desk.ger.corp.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=chianglungyu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@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

all inboxes | Powered by JetHome®