linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Steger <daniel.steger@xilinx.com>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: sysfs: do not remove files if group is null
Date: Sat, 21 Aug 2021 13:52:44 +0200	[thread overview]
Message-ID: <YSDpDLYuiFDyshwj@kroah.com> (raw)
In-Reply-To: <20210819191019.3380999-1-daniel.steger@xilinx.com>

On Thu, Aug 19, 2021 at 12:10:20PM -0700, Daniel Steger wrote:
> The current implementation allows the remove_files() API to be
> called without checking if the grp->name is null. Ensure that
> the group name is valid prior to removing files.
> 
> This patch fixes a race condition where device_del() will cleanup
> sysfs entries prior to device managed sysfs entries. This results
> in a NULL group->name and a system error during device cleanup.
> 
> To reproduce the issue, simply create a new child device in a
> platform driver of your choice. Add a sysfs file group using
> devm API.

What driver is doing this today?

> On driver exist ensure to unregister your child device.

What child device?  Why is a platform driver creating a child device at
all?

> Do not call devm_device_remove_group() and leave it up to the
> implementation to automatically clean up the files. Here is where
> you will see a kernel error complaining that the files have already
> been removed.
> 
> Signed-off-by: Daniel Steger <daniel.steger@xilinx.com>
> ---
>  fs/sysfs/group.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/sysfs/group.c b/fs/sysfs/group.c
> index 64e6a6698935..023b40840f36 100644
> --- a/fs/sysfs/group.c
> +++ b/fs/sysfs/group.c
> @@ -286,9 +286,10 @@ void sysfs_remove_group(struct kobject *kobj,
>  		kernfs_get(kn);
>  	}
>  
> -	remove_files(kn, grp);
> -	if (grp->name)
> +	if (grp->name) {
> +		remove_files(kn, grp);

What about groups without names?  Will then now not be removed properly?
Why does the name matter here?

thanks,

greg k-h

  reply	other threads:[~2021-08-21 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 19:10 [PATCH] fs: sysfs: do not remove files if group is null Daniel Steger
2021-08-21 11:52 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-18  1:07 Daniel Steger
2021-08-18  5:35 ` Greg KH
     [not found] <20210809204228.2987376-1-daniel.steger@xilinx.com>
2021-08-17 16:13 ` Daniel Steger
2021-08-17 16:18   ` gregkh
2021-08-17 16:19     ` gregkh

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=YSDpDLYuiFDyshwj@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.steger@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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;
as well as URLs for NNTP newsgroup(s).