All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: fan.du@windriver.com, netdev@vger.kernel.org
Subject: Re: [PATCHv2 net-next] xfrm: Make xfrm_state timer monotonic
Date: Fri, 16 Aug 2013 11:30:18 +0200	[thread overview]
Message-ID: <20130816093018.GM26773@secunet.com> (raw)
In-Reply-To: <20130815.142334.1736006937556027032.davem@davemloft.net>

On Thu, Aug 15, 2013 at 02:23:34PM -0700, David Miller wrote:
> From: Fan Du <fan.du@windriver.com>
> Date: Thu, 15 Aug 2013 15:49:06 +0800
> 
> > xfrm_state timer should be independent of system clock change,
> > so switch to CLOCK_BOOTTIME base which is not only monotonic but
> > also counting suspend time.
> > 
> > Thus issue reported in commit: 9e0d57fd6dad37d72a3ca6db00ca8c76f2215454
> > ("xfrm: SAD entries do not expire correctly after suspend-resume")
> > could ALSO be avoided.
> > 
> > Signed-off-by: Fan Du <fan.du@windriver.com>
> > 
> > v2: Use CLOCK_BOOTTIME to count suspend time, but still monotonic.
> 
> This seems like a good fix:
> 
> Acked-by: David S. Miller <davem@davemloft.net>

Applied to ipsec-next, thanks!

  reply	other threads:[~2013-08-16  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15  7:49 [PATCHv2 net-next] xfrm: Make xfrm_state timer monotonic Fan Du
2013-08-15 21:23 ` David Miller
2013-08-16  9:30   ` Steffen Klassert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-06  6:57 [PATCH " Fan Du
2013-08-06  9:22 ` Steffen Klassert
2013-08-12  5:40   ` [PATCHv2 " Fan Du
2013-08-13  7:55     ` Steffen Klassert
2013-08-13  8:37       ` Fan Du
2013-08-13 10:59         ` Steffen Klassert
2013-08-14 11:34     ` 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=20130816093018.GM26773@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=fan.du@windriver.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.