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  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]
Date:   Fri, 11 Jun 2021 13:12:45 +0300
From:   Andy Shevchenko <>
To:     Heikki Krogerus <>,
        Bartosz Golaszewski <>,
        Greg Kroah-Hartman <>,
Cc:     "Rafael J. Wysocki" <>
Subject: Re: [PATCH v4 1/4] devres: Make locking straight forward in

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?

With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists