From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Simon Kirby <sim@hostway.ca>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Lech Perczak <l.perczak@camlintechnologies.com>,
Theodore Ts'o <tytso@mit.edu>,
John Ogness <john.ogness@linutronix.de>,
Jann Horn <jannh@google.com>
Subject: Re: [PATCHv2] printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
Date: Fri, 10 Apr 2020 12:07:04 +0900 [thread overview]
Message-ID: <20200410030704.GA20227@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200409192543.GA30816@hostway.ca>
On (20/04/09 12:25), Simon Kirby wrote:
> This causes "dmesg -w" or "cat /dev/kmsg" to not print new messages after
> dumping the current ring. I hit this on v5.5.9, v5.5.15, v5.6.3, and
> Linus HEAD. This prints no "hi":
>
> (sleep 1;echo hi > /dev/kmsg)& dmesg -w
>
> ...curiously, "strace dmesg -w" shows the data received once ^C is hit.
>
> Jann pointed me to this patch. Applying it or reverting 1b710b1b10eff9d4
> does fix it for me. However, Linus HEAD is still broken and, AFAICS,
> remains unreverted and unfixed in stable/linux-5.4.y through linux-5.6.y.
> It was introduced in 5.6 but backported to those, not just the LTS above.
I'm trying to land this patch. Give me a moment, I'll come back to
you shortly.
-ss
next prev parent reply other threads:[~2020-04-10 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 11:30 [PATCHv2] printk: queue wake_up_klogd irq_work only if per-CPU areas are ready Sergey Senozhatsky
2020-03-04 15:21 ` Petr Mladek
2020-03-05 1:30 ` Sergey Senozhatsky
2020-03-05 18:53 ` Greg Kroah-Hartman
2020-04-09 19:25 ` Simon Kirby
2020-04-10 3:07 ` Sergey Senozhatsky [this message]
2020-04-10 23:21 ` Sergey Senozhatsky
2020-04-01 19:34 ` Jann Horn
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=20200410030704.GA20227@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=john.ogness@linutronix.de \
--cc=l.perczak@camlintechnologies.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sim@hostway.ca \
--cc=tytso@mit.edu \
/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).