From: Fan Du <fan.du@windriver.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>, <fdu@windriver.com>
Subject: Re: [XFRM][RFC v1] Fix unexpected SA hard expiration after setting new date
Date: Mon, 18 Jun 2012 16:53:05 +0800 [thread overview]
Message-ID: <4FDEEC71.50302@windriver.com> (raw)
In-Reply-To: <20120618084021.GA24902@gondor.apana.org.au>
On 2012年06月18日 16:40, Herbert Xu wrote:
> On Mon, Jun 18, 2012 at 04:24:15PM +0800, fan.du wrote:
>>
>> So, could you please give your comments on this?
>
> Well, this used to work back when we were using relative time
> instead of absolute time. Then someone came along and changed
> it for suspend/resume.
>
> I didn't like this new behaviour but Dave convinced me that
> it is a good thing :)
>
One of our custom complained the networking down when changing date,
even it's only less than 10 seconds, but they complain anyway:)
So it probably hurts much in practice for tel comm company.
> I guess I can live with your workaround if Dave is happy with
> it. But IMHO we should just go back to relative time and fix
> the suspend/resume user-space scripts instead.
Ok, let's see what Dave will say about this.
And thanks for your comments.
>
> Cheers,
--
Love each day!
--fan
next prev parent reply other threads:[~2012-06-18 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 8:24 [XFRM][RFC v1] Fix unexpected SA hard expiration after setting new date fan.du
2012-06-18 8:24 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date fan.du
2012-06-18 11:05 ` Steffen Klassert
2012-06-19 1:34 ` Fan Du
2012-06-18 8:40 ` [XFRM][RFC v1] Fix unexpected SA hard expiration after setting new date Herbert Xu
2012-06-18 8:53 ` Fan Du [this message]
2012-06-19 7:34 ` David Miller
2012-06-19 7:43 ` Herbert Xu
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=4FDEEC71.50302@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=fdu@windriver.com \
--cc=herbert@gondor.hengli.com.au \
--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 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).