Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4150721ybg; Tue, 29 Oct 2019 02:57:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqxUByaQVGV8g4Hs1zo9dkKX2G3BsV53HjO5L+5A78+g9tKdb/Z8j4fovNHQieejkk7Dcx0c X-Received: by 2002:aa7:d714:: with SMTP id t20mr25092894edq.129.1572343038417; Tue, 29 Oct 2019 02:57:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572343038; cv=none; d=google.com; s=arc-20160816; b=iuuCFvFoKncdLpaJQfcLetC66UAc/EiLmbzpuZx7j1RlvGE9psFQtUPzp10WaI4pf9 OBECNAACXForrXKJa0LS/hKVeaWqMlrhhZIYDVbyqEB5J02fvAtH2NqwmlKcqQFuf/YS NLc/2XpVEyLrfsZRtaeMFzoxey//EFEvExc5YwaqRADfc9KiTmjqKn7Ex2GCzwtWnVyW TomBTmpFknFvu/x4RRenaU3wliXsuxiEil8vPDqiRfIwzcOj5Hcld8qmBJzfTlUIvsI5 a8cDuNWEuRLE8vVQtWnS5Rzi7JTQWJsvJoK/8Db1oMWn0qR1volnhYJkztTWeHPbcfvX Q1vA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject:dkim-signature; bh=m2LAJqvz5BHhT0hEXJpcsiP/gHskrUk9SC7/ECwsvhE=; b=eGv/0BEn2uIEh8svESJZnUPJ9cdaw44jERZmICam5Ovd5oChOOlwaYqr2wFJZuj1jl SOTBFOF7gmIO3qvXLVHDaJwsC/jfLQ86yAfDjpiuaAIs6JBsBZrc4+lDb4NSbmP3tUtf ACsTRmf3iB74Ns/DxiVmSR9o7CpdaRmTsnGQbtQe19o9MM+C9LRSRfQjY81kFrdaqjoM cnJjtzFoBsefYRRZ6Is98UuI7cU1xu/ljNdtPCbl2VIrYCq0uGhkkOcX6OJl8uNZ+E01 4g0tZ1NIKfoHzZe2rpXEytAJZuspe3qIoW554b9346fhSqOfOpZ68hfQG3XpewpT3Qln fTtQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@jv-coder.de header.s=dkim header.b=J1VKZqoB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id nt21si6398189ejb.119.2019.10.29.02.56.54; Tue, 29 Oct 2019 02:57:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@jv-coder.de header.s=dkim header.b=J1VKZqoB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726495AbfJ2HdF (ORCPT + 99 others); Tue, 29 Oct 2019 03:33:05 -0400 Received: from mail.jv-coder.de ([5.9.79.73]:57316 "EHLO mail.jv-coder.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725839AbfJ2HdE (ORCPT ); Tue, 29 Oct 2019 03:33:04 -0400 Received: from [10.61.40.7] (unknown [37.156.92.209]) by mail.jv-coder.de (Postfix) with ESMTPSA id 8456D9F655; Tue, 29 Oct 2019 07:33:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jv-coder.de; s=dkim; t=1572334381; bh=m2LAJqvz5BHhT0hEXJpcsiP/gHskrUk9SC7/ECwsvhE=; h=Subject:To:From:Message-ID:Date:MIME-Version; b=J1VKZqoBtr+17CR4/Lkmq8HUDVR+ov75UtOmaUZxGm/50kl12zerVuWFr2Mq43l+3 OZsmsXOTDyGHeMo+JekEgdvbN4zFwUDnI8s3T8yK9MGHzFXj+WlHhd1bjq+mCP0mtG p6eSgAmJAhG2hvSrvkjNuHlKu2taFx4kcNYHZ3zE= Subject: Re: [PATCH v2 1/1] xfrm : lock input tasklet skb queue To: Sebastian Andrzej Siewior Cc: Steffen Klassert , Tom Rix , Steven Rostedt , Thomas Gleixner , herbert@gondor.apana.org.au, davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20191024103134.GD13225@gauss3.secunet.de> <20191025094758.pchz4wupvo3qs6hy@linutronix.de> <202da67b-95c7-3355-1abc-f67a40a554e9@jv-coder.de> <20191025102203.zmkqvvg5tofaqfw6@linutronix.de> <5b45c8f6-1aa2-2e1e-9019-a140988bba80@jv-coder.de> <20191028151447.xwtyh6hfwfvzwmmu@linutronix.de> From: Joerg Vehlow Message-ID: <5575bb95-b89a-727d-0587-9c462f1fddef@jv-coder.de> Date: Tue, 29 Oct 2019 08:33:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <20191028151447.xwtyh6hfwfvzwmmu@linutronix.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,HELO_MISC_IP,RDNS_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.jv-coder.de Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On 2019-10-28 11:44:57 [+0100], Joerg Vehlow wrote: >> I was unable to reproduce it with 5.2.21-rt13. Do you know if something >> changed in network scheduling code or could it be just less likely? > the softirq/BH handling has been rewritten in the v5.0-RT cycle, > v5.0.19-rt11 to be exact. So if that the cause for it (which I hope) > then you should be able to trigger the problem before that release and > not later. > I testes again with 5.0.19-rt10 and 5.0.19-rt11  and I am pretty sure the bug wasfixed by the changes in rt11. I was able to reproduce it with rt10 within secondsand unable to reproduce it at all in several minutes on rt11. Will 4.19 rt patches receive anymore updates? Is it possible to backport the changes to softirq/BH habdling from 5.0.16-rt11 to 4.19?