af_key: Add lock to key dump

af_key: Add lock to key dump

[Mark Salyzyn]

Subject: af_key: Add lock to key dump upstream sha 
89e357d83c06b6fac581c3ca7f0ee3ae7e67109e

Please apply to 3.10, 3.18 (?, I see it is not under longterm support), 
4.4 and 4.9 stable trees

Along with the stated reason (prevent a NULL pointer access), this also 
prevents unbounded reference counter activities which can lead to a Use 
After Free situation.

FYI: The back-port to 3.10.y has a minor conflict resolved by dropping 
one of the patch fragments. 4.4 and 4.9 were clear.

Signed-off-by: Mark Salyzyn <salyzyn@android.com>

Re: af_key: Add lock to key dump

[Greg KH]

On Thu, Jul 27, 2017 at 03:51:43PM -0700, Mark Salyzyn wrote:
> Subject: af_key: Add lock to key dump upstream sha
> 89e357d83c06b6fac581c3ca7f0ee3ae7e67109e
> 
> Please apply to 3.10, 3.18 (?, I see it is not under longterm support), 4.4
> and 4.9 stable trees

3.18 is under "special" support (i.e. I'm maintaining it as a favor for
some companies for now...)

> Along with the stated reason (prevent a NULL pointer access), this also
> prevents unbounded reference counter activities which can lead to a Use
> After Free situation.
> 
> FYI: The back-port to 3.10.y has a minor conflict resolved by dropping one
> of the patch fragments. 4.4 and 4.9 were clear.
> 
> Signed-off-by: Mark Salyzyn <salyzyn@android.com>

Thanks, now queued up for 3.18, 4.4, and 4.9.

But really, it should go back farther than 3.10, 3.2 should get it as
well...

thanks,

greg k-h

Re: af_key: Add lock to key dump

[Mark Salyzyn]

On 07/27/2017 06:08 PM, Greg KH wrote:
> Thanks, now queued up for 3.18, 4.4, and 4.9.
>
> But really, it should go back farther than 3.10, 3.2 should get it as
> well...
>
> thanks,
>
> greg k-h

This "special" company was only interested in 3.10, 3.18, 4.4 and 4.9 
;-) sorry for being to focused in the request. _all_ stable releases sgtm!

-- Mark