netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antony Antony <antony.antony@secunet.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Antony Antony <antony.antony@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	<netdev@vger.kernel.org>, Tobias Brunner <tobias@strongswan.org>
Subject: Re: [PATCH ipsec-next] xfrm: update x->lastused for every packet
Date: Tue, 16 Aug 2022 23:44:45 +0200	[thread overview]
Message-ID: <YvwPzdnyOCWR4UIx@moon.secunet.de> (raw)
In-Reply-To: <20220816092736.GE2950045@gauss3.secunet.de>

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@secunet.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.

Would you prefer a rebased patch?

regards,
-antony


  reply	other threads:[~2022-08-16 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  9:17 [PATCH ipsec-next] xfrm: update x->lastused for every packet Antony Antony
2022-08-16  9:27 ` Steffen Klassert
2022-08-16 21:44   ` Antony Antony [this message]
2022-08-17 10:16     ` Steffen Klassert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YvwPzdnyOCWR4UIx@moon.secunet.de \
    --to=antony.antony@secunet.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=tobias@strongswan.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).