From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steffen Klassert Subject: Re: [PATCHv2 net-next] xfrm: Make xfrm_state timer monotonic Date: Tue, 13 Aug 2013 09:55:20 +0200 Message-ID: <20130813075519.GN25511@secunet.com> References: <1375772225-19265-1-git-send-email-fan.du@windriver.com> <20130806092220.GH25511@secunet.com> <52087537.6060200@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: davem@davemloft.net, netdev@vger.kernel.org To: Fan Du Return-path: Received: from a.mx.secunet.com ([195.81.216.161]:39999 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755769Ab3HMHzW (ORCPT ); Tue, 13 Aug 2013 03:55:22 -0400 Content-Disposition: inline In-Reply-To: <52087537.6060200@windriver.com> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Aug 12, 2013 at 01:40:07PM +0800, Fan Du wrote: >=20 >=20 > On 2013=E5=B9=B408=E6=9C=8806=E6=97=A5 17:22, Steffen Klassert wrote: > >On Tue, Aug 06, 2013 at 02:57:05PM +0800, Fan Du wrote: > >>xfrm_state timer should be independent of system clock change, > >>so switch to monotonic clock base. > >> > > > >I think a monotonic timer will reintroduce a bug on suspend/resume > >that was fixed by commit 9e0d57fd6 > >(xfrm: SAD entries do not expire correctly after suspend-resume) > > > >Please make sure that this does not happen. >=20 > What about using CLOCK_BOOTTIME? it's monotonic, but includes suspend= time as well. As I said, I'm open to everything that fixes your problem and does not introduce a regression. I'll consider applying after some testing if noone else has objections. Thanks!