[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181111210105.7f376c35@vmware.local.home>
Date: Sun, 11 Nov 2018 21:01:05 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Oleksandr Natalenko <oleksandr@...alenko.name>
Cc: "David S. Miller" <davem@...emloft.net>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>,
Eric Dumazet <edumazet@...gle.com>,
Dave Jones <davej@...emonkey.org.uk>, netdev@...r.kernel.org,
linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: WARN_ON() in netconsole with PREEMPT_RT
On Sun, 11 Nov 2018 21:16:00 +0100
Oleksandr Natalenko <oleksandr@...alenko.name> wrote:
> > This is a v4.19.1-rt3-based kernel.
> >
> > The WARN_ON() is:
> >
> > 362 void netpoll_send_udp(struct netpoll *np, const char *msg, int len)
> > 363 {
> > …
> > 372 WARN_ON_ONCE(!irqs_disabled());
> > …
> >
> > If that matters, I have "threadirqs" passed to the kernel.
> >
> > Netconsole seems to work even after this warning. Is this OK/expected?
> >
> > Thanks.
>
> 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?
printk() itself has a lot of issues with PREEMPT_RT that we are working
on dealing with. Right now netconsole is actually at the end of that
todo list.
-- Steve
Powered by blists - more mailing lists