[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130814110422.GH26773@secunet.com>
Date: Wed, 14 Aug 2013 13:04:23 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Fan Du <fan.du@...driver.com>
Cc: davem@...emloft.net, herbert@...dor.hengli.com.au,
netdev@...r.kernel.org
Subject: Re: [PATCHv3 net-next ] xfrm: Update xfrm_state lifetime expire
after clock_was_set
On Wed, Aug 14, 2013 at 01:26:02PM +0800, Fan Du wrote:
>
> From bf282199fd172d1bbc6dcd0e38d1b8fc2192e5f5 Mon Sep 17 00:00:00 2001
> From: Fan Du <fan.du@...driver.com>
> Date: Wed, 14 Aug 2013 12:59:11 +0800
> Subject: [PATCHv3 net-next ] xfrm: Update xfrm_state lifetime expire after clock_was_set
>
> After clock_was_set called to set new time or host resume from suspend
> state. Notify IKED with soft timeout for SAs which haven't reach its
> soft timeout limit. For those dying SAs, arrange them to hard expire.
>
> This modification is characterized by SA is sensible to any degree of
> clock changes while as SA lifetime is marked by second.
>
> Another point is clock_was_set is traversing all net name space to
> update SA time while holding rtnl_lock, it may not scale very well.
>
> Signed-off-by: Fan Du <fan.du@...driver.com>
>
> v3:
> - Fix lockdep complaint about circular locking with trying to acquire
> state->clock while holding xfrm_state_lock.
Fan, please resubmit the whole patchset and not single patches from a
patchset. Also, please Cc Thomas Gleixner for review of the hrtimer
changes when you resubmit.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists