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]
Date:   Wed, 27 Feb 2019 08:49:56 +0800
From:   zerons <>
To:     Daniel Borkmann <>,
Subject: Re: [PATCH] bpf: decrease usercnt if bpf_map_new_fd() fails in

On 2/27/19 00:24, Daniel Borkmann wrote:
> On 02/26/2019 03:58 PM, zerons wrote:
>> On 2/26/19 22:44, Daniel Borkmann wrote:
>>> On 02/26/2019 03:15 PM, zerons wrote:
>>>> [ Upstream commit c91951f15978f1a0c6b65f063d30f7ea7bc6fb42 ]
>>> Thanks for the fix! What do you mean by "upstream commit" above in this context?
>> This patch is based on that commit, I thought I should mention this.
>> Sorry for the confusion.
> Ah, no. Usually that line is placed into stable commits that are
> cherry-picked to point to the original commit sha in the mainline
> tree. In any case, I didn't find c91951f15978, hence my question.

That is v4.20.12.

> Anyway, for normal patch submissions in future, please don't add
> it into the log, we'll remove it this time.

Thanks for reminding me. I won't do that again.

Powered by blists - more mailing lists