Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 14 May 2021 06:55:37 +0200
From:   "Ahmed S. Darwish" <a.darwish@linutronix.de>
To:     Davidlohr Bueso <dave@stgolabs.net>
Cc:     Peter Zijlstra <peterz@infradead.org>, bigeasy@linutronix.de,
        tglx@linutronix.de, shung-hsi.yu@suse.com,
        linux-kernel@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH v2] seqlock,lockdep: Only check for preemption_disabled
 in non-rt
Message-ID: <YJ4CydK5NiSkpkSO@lx-t490>
References: <20210507233951.78950-1-dave@stgolabs.net>
 <20210507234713.86097-1-dave@stgolabs.net>
 <YJuVhR9C6pUmZBOs@hirez.programming.kicks-ass.net>
 <20210513195357.xq57b2t26hhhmdn4@offworld>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210513195357.xq57b2t26hhhmdn4@offworld>
Precedence: bulk

On Thu, May 13, 2021, Davidlohr Bueso wrote:
>
> And therefore converting it to an associated spinlock would avoid the
> preemption check, which is exactly what Ahmed has already done:
>
> bc8e0adff34 (net: xfrm: Use sequence counter with associated spinlock)
> e88add19f68 (net: xfrm: Localize sequence counter per network namespace)
>
> Sorry for the noise.
>

Exactly, so it seems everything is good on your side :)

(The pending patch queue I mentioned is much larger and gets rid of the
 main packet scheduling sequence counter Qdisc::running, but I'm
 brushing it up, then sending it for an internal review round, first.
 There are already some workarounds in the RT tree for that one until
 the correct fix is merged mainline.)

Kind regards,

--
Ahmed S. Darwish
Linutronix GmbH