From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Eric Dumazet <edumazet@google.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: bpf <bpf@vger.kernel.org>, netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net-next 1/4] net: dev: Remove the preempt_disable() in netif_rx_internal().
Date: Thu, 03 Feb 2022 13:00:06 +0100 [thread overview]
Message-ID: <87v8xwb1o9.fsf@toke.dk> (raw)
In-Reply-To: <CANn89iJm9krQ-kjVBxFzxh0nG46O5RWDg=QyXhiq1nA3Erf9KQ@mail.gmail.com>
Eric Dumazet <edumazet@google.com> writes:
> On Wed, Feb 2, 2022 at 4:28 AM Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
>>
>> The preempt_disable() and rcu_disable() section was introduced in commit
>> bbbe211c295ff ("net: rcu lock and preempt disable missing around generic xdp")
>>
>> The backtrace shows that bottom halves were disabled and so the usage of
>> smp_processor_id() would not trigger a warning.
>> The "suspicious RCU usage" warning was triggered because
>> rcu_dereference() was not used in rcu_read_lock() section (only
>> rcu_read_lock_bh()). A rcu_read_lock() is sufficient.
>>
>> Remove the preempt_disable() statement which is not needed.
>
> I am confused by this changelog/analysis of yours.
>
> According to git blame, you are reverting this patch.
>
> commit cece1945bffcf1a823cdfa36669beae118419351
> Author: Changli Gao <xiaosuo@gmail.com>
> Date: Sat Aug 7 20:35:43 2010 -0700
>
> net: disable preemption before call smp_processor_id()
>
> Although netif_rx() isn't expected to be called in process context with
> preemption enabled, it'd better handle this case. And this is why get_cpu()
> is used in the non-RPS #ifdef branch. If tree RCU is selected,
> rcu_read_lock() won't disable preemption, so preempt_disable() should be
> called explictly.
>
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
> But I am not sure we can.
>
> Here is the code in larger context:
>
> #ifdef CONFIG_RPS
> if (static_branch_unlikely(&rps_needed)) {
> struct rps_dev_flow voidflow, *rflow = &voidflow;
> int cpu;
>
> preempt_disable();
> rcu_read_lock();
>
> cpu = get_rps_cpu(skb->dev, skb, &rflow);
> if (cpu < 0)
> cpu = smp_processor_id();
>
> ret = enqueue_to_backlog(skb, cpu, &rflow->last_qtail);
>
> rcu_read_unlock();
> preempt_enable();
> } else
> #endif
>
> This code needs the preempt_disable().
This is mostly so that the CPU ID stays the same throughout that section
of code, though, right? So wouldn't it work to replace the
preempt_disable() with a migrate_disable()? That should keep _RT happy,
no?
-Toke
next prev parent reply other threads:[~2022-02-03 12:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 12:28 [PATCH net-next 0/4] net: dev: PREEMPT_RT fixups Sebastian Andrzej Siewior
2022-02-02 12:28 ` [PATCH net-next 1/4] net: dev: Remove the preempt_disable() in netif_rx_internal() Sebastian Andrzej Siewior
2022-02-02 17:10 ` Eric Dumazet
2022-02-03 12:00 ` Toke Høiland-Jørgensen [this message]
2022-02-03 12:17 ` Sebastian Andrzej Siewior
2022-02-03 12:41 ` Toke Høiland-Jørgensen
2022-02-03 15:50 ` Sebastian Andrzej Siewior
2022-02-04 15:20 ` [PATCH net-next v2 1/4] net: dev: Remove preempt_disable() and get_cpu() " Sebastian Andrzej Siewior
2022-02-04 16:31 ` Jakub Kicinski
2022-02-04 16:42 ` Sebastian Andrzej Siewior
2022-02-04 16:32 ` Eric Dumazet
2022-02-03 12:16 ` [PATCH net-next 1/4] net: dev: Remove the preempt_disable() " Sebastian Andrzej Siewior
2022-02-02 12:28 ` [PATCH net-next 2/4] net: dev: Remove get_cpu() " Sebastian Andrzej Siewior
2022-02-02 17:14 ` Eric Dumazet
2022-02-03 12:14 ` Toke Høiland-Jørgensen
2022-02-02 12:28 ` [PATCH net-next 3/4] net: dev: Makes sure netif_rx() can be invoked in any context Sebastian Andrzej Siewior
2022-02-02 16:50 ` Jakub Kicinski
2022-02-03 12:20 ` Sebastian Andrzej Siewior
2022-02-03 19:38 ` Jakub Kicinski
2022-02-02 17:43 ` Eric Dumazet
2022-02-03 12:19 ` Toke Høiland-Jørgensen
2022-02-03 15:10 ` Sebastian Andrzej Siewior
2022-02-03 15:25 ` Eric Dumazet
2022-02-03 15:40 ` Sebastian Andrzej Siewior
2022-02-03 16:18 ` Eric Dumazet
2022-02-03 16:44 ` Sebastian Andrzej Siewior
2022-02-03 17:45 ` Sebastian Andrzej Siewior
2022-02-04 13:00 ` [PATCH net-next v2 " Sebastian Andrzej Siewior
2022-02-04 18:46 ` Eric Dumazet
2022-02-02 12:28 ` [PATCH net-next 4/4] net: dev: Make rps_lock() disable interrupts Sebastian Andrzej Siewior
2022-02-02 16:47 ` Jakub Kicinski
2022-02-03 16:41 ` [PATCH net-next v2 " Sebastian Andrzej Siewior
2022-02-03 19:39 ` Jakub Kicinski
2022-02-02 16:14 ` [PATCH net-next 0/4] net: dev: PREEMPT_RT fixups Jakub Kicinski
2022-02-03 11:59 ` Toke Høiland-Jørgensen
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=87v8xwb1o9.fsf@toke.dk \
--to=toke@toke.dk \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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).