All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mathias Krause <minipli@grsecurity.net>
Cc: "Masami Hiramatsu" <mhiramat@kernel.org>,
	"Ajay Kaher" <ajay.kaher@broadcom.com>,
	"Ilkka Naulapää" <digirigawa@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@leemhuis.info,
	"Dan Carpenter" <dan.carpenter@linaro.org>
Subject: Re: tracing: user events UAF crash report
Date: Mon, 22 Jul 2024 20:11:25 -0400	[thread overview]
Message-ID: <20240722201125.3fa6314b@gandalf.local.home> (raw)
In-Reply-To: <20240719204701.1605950-1-minipli@grsecurity.net>

On Fri, 19 Jul 2024 22:47:01 +0200
Mathias Krause <minipli@grsecurity.net> wrote:

> Subject: [PATCH] eventfs: Don't return NULL in eventfs_create_dir()
> 
> Commit 77a06c33a22d ("eventfs: Test for ei->is_freed when accessing
> ei->dentry") added another check, testing if the parent was freed after
> we released the mutex. If so, the function returns NULL. However, all
> callers expect it to either return a valid pointer or an error pointer,
> at least since commit 5264a2f4bb3b ("tracing: Fix a NULL vs IS_ERR() bug
> in event_subsystem_dir()"). Returning NULL will therefore fail the error
> condition check in the caller.
> 
> Fix this by substituting the NULL return value with a fitting error
> pointer.
> 
> Fixes: 77a06c33a22d ("eventfs: Test for ei->is_freed when accessing ei->dentry")
> Cc: Dan Carpenter <dan.carpenter@linaro.org>
> Signed-off-by: Mathias Krause <minipli@grsecurity.net>

This will not get into the workflow without being sent as a normal patch.

Please send it and Cc those listed in MAINTAINERS (see get_maintainers.pl).

-- Steve


> ---
>  fs/tracefs/event_inode.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/tracefs/event_inode.c b/fs/tracefs/event_inode.c
> index 5d88c184f0fc..a9c28a1d5dc8 100644
> --- a/fs/tracefs/event_inode.c
> +++ b/fs/tracefs/event_inode.c
> @@ -736,7 +736,7 @@ struct eventfs_inode *eventfs_create_dir(const char *name, struct eventfs_inode
>  	/* Was the parent freed? */
>  	if (list_empty(&ei->list)) {
>  		cleanup_ei(ei);
> -		ei = NULL;
> +		ei = ERR_PTR(-EBUSY);
>  	}
>  	return ei;

  parent reply	other threads:[~2024-07-23  0:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 20:47 tracing: user events UAF crash report Mathias Krause
2024-07-20  3:33 ` Dan Carpenter
2024-07-22 11:13 ` Ajay Kaher
2024-07-22 12:08   ` Mathias Krause
2024-07-25 13:33     ` Ajay Kaher
2024-07-25 16:15       ` Ajay Kaher
2024-07-25 16:30         ` Ajay Kaher
2024-07-25 17:10           ` Steven Rostedt
2024-07-25 17:16             ` Steven Rostedt
2024-07-25 18:12               ` Mathias Krause
2024-07-25 19:05                 ` Steven Rostedt
2024-07-25 19:42                   ` Mathias Krause
2024-07-25 20:15                     ` Steven Rostedt
2024-07-25 20:41                       ` Mathias Krause
2024-07-25 21:14                         ` Steven Rostedt
2024-07-25 21:32                           ` Mathias Krause
2024-07-25 23:06                             ` Steven Rostedt
2024-07-26  8:25                               ` Mathias Krause
2024-07-25 19:53                   ` Mathias Krause
2024-07-25 16:48         ` Steven Rostedt
2024-07-23  0:11 ` Steven Rostedt [this message]
2024-07-23 12:25   ` [PATCH] eventfs: Don't return NULL in eventfs_create_dir() Mathias Krause
2024-07-23 14:43 ` tracing: user events UAF crash report Steven Rostedt
2024-07-23 20:54   ` Mathias Krause
2024-07-23 21:07   ` [PATCH] eventfs: Use SRCU for freeing eventfs_inodes Mathias Krause
2024-07-23 21:23     ` Steven Rostedt

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=20240722201125.3fa6314b@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=dan.carpenter@linaro.org \
    --cc=digirigawa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=minipli@grsecurity.net \
    --cc=regressions@leemhuis.info \
    --cc=torvalds@linux-foundation.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.