Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2668417ybc; Mon, 18 Nov 2019 02:49:20 -0800 (PST) X-Google-Smtp-Source: APXvYqylwWACJudClZfttCoJUleZQl0fmlOip5VM9+vprMG2S7D7uyA8jtx0P95wQLLYFjcld1v+ X-Received: by 2002:adf:b686:: with SMTP id j6mr18374531wre.186.1574074160814; Mon, 18 Nov 2019 02:49:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574074160; cv=none; d=google.com; s=arc-20160816; b=b9ZvBG5PnBPHBHCPAMVte88ITa8zBX99i7VU4qeAEoX0NrsnjswMdhkxX+bNIYwngb 3n/rLoFbytkueQlX8JEfgR8oiGvEIlx77cQmKevgO8wgAx/GbaC6ua3ge1FQIXJUs0Pt tJvH5bgCJdju3q+xCUgi1LbynnXP1Ws8w7QtJCy+zG7RZ4uDhwYUg/qV0v0e25xcGt1z +Oc/XrMSIDCRQWje/kDeNodrT2TbVo5V+DQ2AqmeHuIB7f0ykwTqCkuPCb4TeV5axLH1 Tw9KCniFlm9TbFrZCph4bfstcM4szsyhGm48bVdPoDNRDrySgEA/QGnCFyocJBJ3TqFo DIJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=WW6usBju/tze5rQ1bogzPisZOJKrAWhJdzh/zEyISVE=; b=GPemrAOZT+4GPs+nl1WYXRVh9qIGIP1BgT7DIE1S4fQ6AdNUjloCiw6+oKlZ2OE43B e7JUJZjIcAIWVB+Q4pEJUrDYEzdu7fnCIxLHlwFm1bzpH5ZeOCRxgIgcSXwAbXj0chAN OTUWprTeSVl191wNmxlwKwVgSkW1urttH5dlCrWqU9b2pQuyfGWVGhRy4Mp/FcwK9D5b /AiJ3kwnDInUcLPJoMkopW13cjb0wLSMCmV6cWRGPoe+LT/PE0C6SV8MaE5z99pGmK7E NiKJTaLDjqXTAlqdfrEWBtWl9mZwKIsm2Jo1CWKRRVNjXuckmKx3nrL3U6Sz0zQwULxo UahA== ARC-Authentication-Results: i=1; mx.google.com; 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 v16si13455203edc.142.2019.11.18.02.48.57; Mon, 18 Nov 2019 02:49:20 -0800 (PST) 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; 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 S1726635AbfKRKqy convert rfc822-to-8bit (ORCPT + 99 others); Mon, 18 Nov 2019 05:46:54 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:49610 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726460AbfKRKqy (ORCPT ); Mon, 18 Nov 2019 05:46:54 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1iWeYG-0007zG-PF; Mon, 18 Nov 2019 11:46:36 +0100 Date: Mon, 18 Nov 2019 11:46:36 +0100 From: Sebastian Andrzej Siewior To: Joerg Vehlow 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 Subject: Re: [PATCH v2 1/1] xfrm : lock input tasklet skb queue Message-ID: <20191118104636.yrt5dz2zxvpjtgkk@linutronix.de> 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> <5575bb95-b89a-727d-0587-9c462f1fddef@jv-coder.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <5575bb95-b89a-727d-0587-9c462f1fddef@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-29 08:33:01 [+0100], Joerg Vehlow wrote: > 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? Oh, sorry, I almost forgot about it. Please repost the patch, state "RT" next to "PATCH" in the subject line. Please state which kernels are affected (v4.19 and earlier due to BH rework) and how this can be tested. The patch/fix should be included in the affected kernels. The softirq changes are very intrusive and can not be backported for the RT-stable kernels. Sebastian