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

Message-ID: <YK421dBVoXLElvKB@smile.fi.intel.com>
Date:   Wed, 26 May 2021 14:53:57 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v4 1/4] devres: Make locking straight forward in
 release_nodes()

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?

-- 
With Best Regards,
Andy Shevchenko