netdev - Re: pull request (net): ipsec 2022-03-16

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: <20220319074911.GB4161825@gauss3.secunet.de>
Date:   Sat, 19 Mar 2022 08:49:11 +0100
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Jakub Kicinski <kuba@...nel.org>
CC:     David Miller <davem@...emloft.net>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        <netdev@...r.kernel.org>
Subject: Re: pull request (net): ipsec 2022-03-16

On Wed, Mar 16, 2022 at 11:44:38AM -0700, Jakub Kicinski wrote:
> On Wed, 16 Mar 2022 13:11:40 +0100 Steffen Klassert wrote:
> > Two last fixes for this release cycle:
> > 
> > 1) Fix a kernel-info-leak in pfkey.
> >    From Haimin Zhang.
> > 
> > 2) Fix an incorrect check of the return value of ipv6_skip_exthdr.
> >    From Sabrina Dubroca.
> 
> Excellent, thank you!
> 
> > Please pull or let me know if there are problems.
> 
> One minor improvement to appease patchwork would be to add / keep the
> [PATCH 0/n] prefix on the PR / cover letter when posting the patches
> under it.

I did that in the ipsec-next pull request, let me know if this is
OK as I did it.

> It seems that patchwork is hopeless in delineating the
> patches and the PR if that's not there. For whatever reason it grouped
> the PR and patch 2 as a series and patch 1 was left separate :S

I guess this is why I get always two mails from patchwork-bot for
each pull request. I already wondered why that happens :)