From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: Oleksandr Natalenko <oleksandr@natalenko.name>,
"David S. Miller" <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
Eric Dumazet <edumazet@google.com>,
Dave Jones <davej@codemonkey.org.uk>,
netdev@vger.kernel.org, linux-rt-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: WARN_ON() in netconsole with PREEMPT_RT
Date: Fri, 30 Nov 2018 19:04:43 +0100 [thread overview]
Message-ID: <20181130180443.o2kjcpweaglmsmx6@linutronix.de> (raw)
In-Reply-To: <20181111210105.7f376c35@vmware.local.home>
On 2018-11-11 21:01:05 [-0500], Steven Rostedt wrote:
> On Sun, 11 Nov 2018 21:16:00 +0100
> Oleksandr Natalenko <oleksandr@natalenko.name> wrote:
> > Oh, I see that write_msg() calls netpoll_send_udp() under
> > spin_lock_irqsave(), but in PREEMPT_RT this, AFAIK, does not disable
> > interrupts.
> >
> > So, the real question here is whether the interrupts should be indeed
> > disabled. And if so, -rt should replace spin_lock_irqsave() call there
> > with what? local_irq_save()? and get rid of the warning?
> >
>
> Why do we care if interrupts are disabled with PREEMPT_RT here?
We don't actually. It was broken before for some reason and disabled on
RT. Later people asked for NETCONSOLE on RT and it seemed to have worked
so I allowed it again starting with v3.14.3-rt5.
A year later (v4.3-rc1) commit c9fd56b34efd0 ("netpoll: warn on
netpoll_send_udp users who haven't disabled irqs") introduced that
warning.
It seems the only reason why netpoll_send_udp() is invoked with disabled
interrupts is because the caller acquired `target_list_lock' with
disabled interrupts. I remember that earlier there was some
local_irq_save() based locking but all this is gone now.
Nikolay could you please explain why interrupts have to be disabled at
this point? It looks to me that this check could be dropped.
> -- Steve
Sebastian
prev parent reply other threads:[~2018-11-30 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 19:13 Oleksandr Natalenko
2018-11-11 20:16 ` Oleksandr Natalenko
2018-11-12 2:01 ` Steven Rostedt
2018-11-24 19:15 ` Oleksandr Natalenko
2018-11-30 18:04 ` Sebastian Andrzej Siewior [this message]
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=20181130180443.o2kjcpweaglmsmx6@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=oleksandr@natalenko.name \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®