linux-kernel - Re: [PATCH v4 1/4] devres: Make locking straight forward in release

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: <YMjD0kUXZasI+vyY@kroah.com>
Date:   Tue, 15 Jun 2021 17:14:26 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v4 1/4] devres: Make locking straight forward in
 release_nodes()

On Fri, Jun 11, 2021 at 01:12:45PM +0300, Andy Shevchenko wrote:
> On Wed, May 26, 2021 at 02:53:57PM +0300, Andy Shevchenko wrote:
> > On Mon, May 17, 2021 at 03:29:43PM +0300, Andy Shevchenko wrote:
> > > It seems for the sake of saving stack memory of couple of pointers,
> > > the locking in release_nodes() callers becomes interesting.
> > > 
> > > Replace this logic with a straight forward locking and unlocking scheme.
> > 
> > Any comments on the series?
> 
> Greg, Rafael, anything I should do here?

Sorry for the delay.  This looks good to me, and it's a step forward
into adding tracing to the driver core, which I've wanted to add for a
while now.

So I'll take it, thanks!

greg k-h