From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jon Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH printk v2 1/2] printk/nbcon: Flush nbcon_irq_work in nbcon_free()
Date: Mon, 31 Aug 2026 17:15:35 +0206 [thread overview]
Message-ID: <87se3upbrk.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <apWXS74ckfSIrH5m@pathway.suse.cz>
On 2026-08-31, Petr Mladek <pmladek@suse.com> wrote:
>> diff --git a/kernel/printk/nbcon.c b/kernel/printk/nbcon.c
>> index a5921a84a80ed..218b1922a58de 100644
>> --- a/kernel/printk/nbcon.c
>> +++ b/kernel/printk/nbcon.c
>> @@ -1849,6 +1849,8 @@ void nbcon_free(struct console *con)
>> printk_kthreads_running = false;
>> }
>>
>> + irq_work_sync(&con->irq_work);
>
> The irq_work work tries to wake up the printk kthread which
> has been destroyed above.
Note that the irq_work only wakes up con->rcuwait waiters. Since the
kthread has already ended, it certainly is not waiting and there is no
wakeup.
The irq_work_sync() call is literally just to clear out the irq_work
queue, not to actually wake anything.
John
next prev parent reply other threads:[~2026-08-31 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 14:02 [PATCH printk v2 0/2] nbcon irq_work fixes John Ogness
2026-08-28 14:02 ` [PATCH printk v2 1/2] printk/nbcon: Flush nbcon_irq_work in nbcon_free() John Ogness
2026-08-31 15:01 ` Petr Mladek
2026-08-31 15:09 ` John Ogness [this message]
2026-09-01 7:40 ` Petr Mladek
2026-08-28 14:02 ` [PATCH printk v2 2/2] printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY John Ogness
2026-08-28 15:36 ` [PATCH printk v2 0/2] nbcon irq_work fixes Jon Hunter
2026-08-28 23:39 ` Bradley Morgan
2026-08-31 6:36 ` Sebastian Andrzej Siewior
2026-08-31 7:31 ` Bradley Morgan
2026-08-31 8:22 ` Sebastian Andrzej Siewior
2026-08-31 8:42 ` Bradley Morgan
2026-08-31 8:50 ` Petr Mladek
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=87se3upbrk.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=thierry.reding@kernel.org \
/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®