linux-kernel - Re: [PATCH 36/37] binder: fix death race conditions

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]

Date:   Fri, 30 Jun 2017 08:05:01 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Todd Kjos <tkjos@...roid.com>
Cc:     arve@...roid.com, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org, maco@...gle.com, tkjos@...gle.com
Subject: Re: [PATCH 36/37] binder: fix death race conditions

On Thu, Jun 29, 2017 at 12:02:10PM -0700, Todd Kjos wrote:
> From: Martijn Coenen <maco@...gle.com>
> 
> A race existed where one thread could register
> a death notification for a node, while another
> thread was cleaning up that node and sending
> out death notifications for its references,
> causing simultaneous access to ref->death
> because different locks were held.
> 
> Signed-off-by: Martijn Coenen <maco@...gle.com>

Note, if you forward on a patch from someone else, like this, you should
also put your signed-off-by: on it, as you hopefully are agreeing that
it is ok to forward on.

thanks,

greg k-h