linux-kernel - Re: [PATCH v1] base: soc: Handle custom soc information sysfs entries

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] [day] [month] [year] [list]

Message-ID: <20191004070516.GA6371@kroah.com>
Date:   Fri, 4 Oct 2019 09:05:16 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Murali Nalajala <mnalajal@...eaurora.org>, rafael@...nel.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] base: soc: Handle custom soc information sysfs entries

On Thu, Oct 03, 2019 at 11:17:45PM -0700, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2019-10-03 22:50:57)
> > On Thu 03 Oct 22:38 PDT 2019, Stephen Boyd wrote:
> > 
> > > Quoting Murali Nalajala (2019-10-03 16:51:50)
> > > > @@ -151,14 +156,16 @@ struct soc_device *soc_device_register(struct soc_device_attribute *soc_dev_attr
> > > >  
> > > >         ret = device_register(&soc_dev->dev);
> > > >         if (ret)
> > > > -               goto out3;
> > > > +               goto out4;
> > > >  
> > > >         return soc_dev;
> > > >  
> > > > -out3:
> > > > +out4:
> > > >         ida_simple_remove(&soc_ida, soc_dev->soc_dev_num);
> > > >         put_device(&soc_dev->dev);
> > > >         soc_dev = NULL;
> > > > +out3:
> > > > +       kfree(soc_attr_groups);
> > > 
> > > This code is tricky. put_device(&soc_dev->dev) will call soc_release()
> > > so we set soc_dev to NULL before calling kfree() on the error path. This
> > > way we don't doubly free a pointer that the release function will take
> > > care of. I wonder if the release function could free the ida as well,
> > > and then we could just make the device_register() failure path call
> > > put_device() and return ERR_PTR(ret) directly. Then the error path is
> > > simpler because we can avoid changing two pointers to NULL to avoid the
> > > double free twice. Or just inline the ida remove and put_device() call
> > > in the if and then goto out1 to consolidate the error pointer
> > > conversion.
> > > 
> > 
> > But if we instead allocates the ida before the soc_dev, wouldn't the
> > error path be something like?:
> > 
> > foo:
> >         put_device(&soc_dev->dev);
> > bar:
> >         ida_simple_remove(&soc_ida, soc_num);
> >         return err;
> > 
> > 
> > I think we still need two exit paths from soc_device_register()
> > regardless of moving the ida_simple_remove() into the release, but we
> > could drop it from the unregister(). So not sure if this is cleaner...
> > 
> 
> It doesn't seem "safe" to let the number be reused before the device is
> destroyed by put_device(). It would be clearer to do all the cleanup
> from the release function so that the soc_device_unregister() path isn't
> racy with another device being registered and reusing the same ID.
> 
> Of course this probably doesn't matter because the race I'm talking
> about is extremely unlikely given there's only ever one soc device.
> Reordering the put and remove would be fine too.

As the number is "owned" by the device, yes, it should just be removed
in the release function that frees the device memory, making this all
much simpler overall.

thanks,

greg k-h