linux-kernel - Re: [PATCH] drivers core: lookup sysfs power group before removal

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 for Android: free password hash cracker in your pocket

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

Message-ID: <e13104c9e55b0bd8eee0a333b3ed7975@foxhound.fi>
Date:   Tue, 07 Nov 2023 10:56:20 +0200
From:   José Pekkarinen <jose.pekkarinen@...hound.fi>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     rafael@...nel.org, len.brown@...el.com, pavel@....cz,
        skhan@...uxfoundation.org, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        linux-kernel-mentees@...ts.linuxfoundation.org,
        syzbot+95f2e2439b97575ec3c0@...kaller.appspotmail.com
Subject: Re: [PATCH] drivers core: lookup sysfs power group before removal

On 2023-11-03 20:36, Greg KH wrote:
> On Fri, Nov 03, 2023 at 07:49:39PM +0200, José Pekkarinen wrote:
>> On 2023-11-01 19:54, Greg KH wrote:
>> > On Wed, Nov 01, 2023 at 07:36:27PM +0200, José Pekkarinen wrote:
>> > > Hinted by syzboot, there is a few cases where the sysfs power group
>> > > may
>> > > not be there, like the failure while adding it, or adding its runtime
>> > > group, or when the sysfs firmware loader fallback fail to populate. In
>> > > the last case, the device_del function will be called leading to
>> > > attempt
>> > > to remove the sysfs group. This patch will lookup for it in advance to
>> > > grant that it is effectively there before cleaning it up.
>> > >
>> > > Reported-by: syzbot+95f2e2439b97575ec3c0@...kaller.appspotmail.com
>> > >
>> > > Signed-off-by: José Pekkarinen <jose.pekkarinen@...hound.fi>
>> > > ---
>> > >  drivers/base/power/sysfs.c | 4 +++-
>> > >  1 file changed, 3 insertions(+), 1 deletion(-)
>> > >
>> > > diff --git a/drivers/base/power/sysfs.c b/drivers/base/power/sysfs.c
>> > > index a1474fb67db9..6601729c4698 100644
>> > > --- a/drivers/base/power/sysfs.c
>> > > +++ b/drivers/base/power/sysfs.c
>> > > @@ -834,5 +834,7 @@ void dpm_sysfs_remove(struct device *dev)
>> > >  	dev_pm_qos_constraints_destroy(dev);
>> > >  	rpm_sysfs_remove(dev);
>> > >  	sysfs_unmerge_group(&dev->kobj, &pm_wakeup_attr_group);
>> > > -	sysfs_remove_group(&dev->kobj, &pm_attr_group);
>> > > +
>> > > +	if (kernfs_find_and_get((&dev->kobj)->sd, pm_attr_group.name))
>> > > +		sysfs_remove_group(&dev->kobj, &pm_attr_group);
>> >
>> > What's to keep it from going away right after finding it?
>> >
>> > In other words, what is wrong with removing a group that is not there?
>> > What error happens?  It should be fine, or are you seeing real code
>> > failures somewhere?
>> 
>>     No, this is just hitting a warning that sysbot complains about by
>> setting panic on warning, no big deal, though it can be a wrong 
>> behaviour
>> in ueagle-atm driver, since it defines to disconnect the device if the
>> firmware is not there, no matter the sysfs fallback.
> 
> Then fix the driver please.

     I'm afraid I was wrong in the assumption that the probe return value
of the driver would influence the testing result, so this no longer 
seems
fixable from driver side. It may be fixed here in the base, in the sysfs
or not to fix it at all since this seem to be a very difficult to reach
situation. I'm fine with any approach, and I can do the work, I'd just
like to read what are your preferences on the topic.

     Thanks!

     José.