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
Date: Fri, 14 May 2021 06:55:37 +0200 [thread overview]
Message-ID: <YJ4CydK5NiSkpkSO@lx-t490> (raw)
In-Reply-To: <20210513195357.xq57b2t26hhhmdn4@offworld>
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
next prev parent reply other threads:[~2021-05-14 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 23:39 [PATCH] seqlock,lockdep: Only check for preemption_disabled in non-rt Davidlohr Bueso
2021-05-07 23:47 ` [PATCH v2] " Davidlohr Bueso
2021-05-12 8:44 ` Peter Zijlstra
2021-05-13 19:53 ` Davidlohr Bueso
2021-05-14 4:55 ` Ahmed S. Darwish [this message]
2021-05-12 9:47 ` [PATCH] " Ahmed S. Darwish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJ4CydK5NiSkpkSO@lx-t490 \
--to=a.darwish@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=shung-hsi.yu@suse.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).