From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE00EC3A5A0 for ; Mon, 19 Aug 2019 17:38:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ABBD122CE9 for ; Mon, 19 Aug 2019 17:38:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728045AbfHSRiM (ORCPT ); Mon, 19 Aug 2019 13:38:12 -0400 Received: from Chamillionaire.breakpoint.cc ([193.142.43.52]:57846 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726959AbfHSRiM (ORCPT ); Mon, 19 Aug 2019 13:38:12 -0400 Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92) (envelope-from ) id 1hzlbe-0006dN-0z; Mon, 19 Aug 2019 19:38:10 +0200 Date: Mon, 19 Aug 2019 19:38:10 +0200 From: Florian Westphal To: Vakul Garg Cc: "netdev@vger.kernel.org" Subject: Re: Help needed - Kernel lockup while running ipsec Message-ID: <20190819173810.GK2588@breakpoint.cc> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Vakul Garg wrote: > Hi > > With kernel 4.14.122, I am getting a kernel softlockup while running single static ipsec tunnel. > The problem reproduces mostly after running 8-10 hours of ipsec encap test (on my dual core arm board). > > I found that in function xfrm_policy_lookup_bytype(), the policy in variable 'ret' shows refcnt=0 under problem situation. > This creates an infinite loop in xfrm_policy_lookup_bytype() and hence the lockup. > > Can some body please provide me pointers about 'refcnt'? > Is it legitimate for 'refcnt' to become '0'? Under what condition can it become '0'? Yes, when policy is destroyed and the last user calls xfrm_pol_put() which will invoke call_rcu to free the structure.