linux-kernel - Re: [PATCH] debugfs: allow bad parent pointers to be passed in

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKohpon__6B7GVWky_XP8=-TCyT+-9zO6mLxmxq9By0djAjjKw@mail.gmail.com>
Date:	Mon, 30 Mar 2015 18:37:12 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alex Elder <elder@...aro.org>
Subject: Re: [PATCH] debugfs: allow bad parent pointers to be passed in

On 30 March 2015 at 18:29, Greg KH <gregkh@...uxfoundation.org> wrote:
> If something went wrong with creating a debugfs file/symlink/directory,
> that value could be passed down into debugfs again as a parent dentry.
> To make caller code simpler, just error out if this happens, and don't
> crash the kernel.
>
> Reported-by: Alex Elder <elder@...aro.org>
> Cc: Viresh Kumar <viresh.kumar@...aro.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
> ---
>  fs/debugfs/inode.c |    3 +++
>  1 file changed, 3 insertions(+)
>
> --- a/fs/debugfs/inode.c
> +++ b/fs/debugfs/inode.c
> @@ -254,6 +254,9 @@ static struct dentry *start_creating(con
>
>         pr_debug("debugfs: creating file '%s'\n",name);
>
> +       if (IS_ERR(parent))
> +               return parent;
> +
>         error = simple_pin_fs(&debug_fs_type, &debugfs_mount,
>                               &debugfs_mount_count);
>         if (error)

Reviewed-by: Viresh Kumar <viresh.kumar@...aro.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/