netdev - Re: [PATCH ipsec-next] xfrm: update x->lastused for every packet

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] [day] [month] [year] [list]

Date:   Wed, 17 Aug 2022 12:16:11 +0200
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Antony Antony <antony.antony@...unet.com>
CC:     Herbert Xu <herbert@...dor.apana.org.au>, <netdev@...r.kernel.org>,
        "Tobias Brunner" <tobias@...ongswan.org>
Subject: Re: [PATCH ipsec-next] xfrm: update x->lastused for every packet

On Tue, Aug 16, 2022 at 11:44:45PM +0200, Antony Antony wrote:
> Hi Steffen,
> 
> On Tue, Aug 16, 2022 at 11:27:36 +0200, Steffen Klassert wrote:
> > On Thu, Aug 04, 2022 at 11:17:31AM +0200, Antony Antony wrote:
> > > x->lastused was only updated for outgoing mobile IPv6 packet.
> > > With this fix update it for every, in and out, packet.
> > > 
> > > This is useful to check if the a SA is still in use, or when was
> > > the last time an SA was used.  lastused time of in SA can used
> > > to check IPsec path is functional.
> > > 
> > > Signed-off-by: Antony Antony <antony.antony@...unet.com>
> > 
> > Your patch does not apply to current ipsec-next, please
> > rebase.
> > 
> > Thanks!
> 
> thanks for trying to apply this patch to ipsec-next.
> 
> I am happy to send a rebased patch, however I suspect ipsec is yet to be
> merged into ipsec-next? Why didn't ipsec merge into to "net" before 6.0-rc1?
> 
> There is a related patch sitting in in ipsec:
> 717ada9f10f2 ("Revert "xfrm: update SA curlft.use_time""),
> 
> Once that is in ipsec-next this patch would apply.

This means your patch never applied to ipsec-next. Please always test
your patches with the tree you want to have it applied on.

> Would you prefer a rebased patch?

Please resend once the related patch it merged to ipsec-next.

Thanks!