From: Tetsuo Handa <firstname.lastname@example.org>
To: Petr Mladek <email@example.com>
Cc: Sergey Senozhatsky <firstname.lastname@example.org>,
Sergey Senozhatsky <email@example.com>,
Steven Rostedt <firstname.lastname@example.org>,
John Ogness <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
Linus Torvalds <email@example.com>,
firstname.lastname@example.org, Michal Hocko <email@example.com>
Subject: Re: [RFC PATCH] printk: Introduce "store now but print later" prefix.
Date: Thu, 7 Mar 2019 03:24:25 +0900 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2019/03/06 19:04, Petr Mladek wrote:
>> I'm suggesting to use a non-async printk() for $trailer_text_line line. I think
>> that changing all printk() called from out_of_memory() to async is doable, if
>> the caller of out_of_memory() wakes up a dedicated kthread described below.
> This is error prone. The trailing printk is not guaranteed:
> + It might get lost by code refactoring.
Caller uses this async printk() with their own risk. This concern is same with
"buffering into on-stack 'char buf' using snprintf() and forgetting to flush
it using printk()".
> + People would miss that it is needed when async printk is used
> in a shared function, e.g. dump_stack().
I'm planning to allow async printk() for shared functions like dump_stack()
because there will be some $trailer_text_line line after such shared functions.
(By the way, for that reason, I expect that we won't do a tree-wide KERN_DEFAULT
removal so that callers can pass KERN_DEFAULT_ASYNC as an function argument to
such shared functions.)
> + People will not know that it is needed because they
> are not familiar with the API. The would just use it
> as part of a cargo cult programming or so.
Same with "buffering into on-stack buffer and forgetting to flush it" above.
I'm planning to allow any shared functions which can be called from e.g.
warn_alloc(), out_of_memory(), SysRq-t by allowing such shared functions
to accept loglevel argument.
> For this reason, this API is a "no no no" from my side.
There are two types of printk() data. One is "small/short messages but
partial/incomplete line (even if a few bytes) might be helpful" and
the other is "large/long messages but partial/incomplete line is hardly
helpful". The former uses "sync printk()s" and the latter uses "async
printk()s followed by a sync printk()". And this API is powerful for the
latter type which are called by for_each_*() pattern (e.g. dump_tasks()).
> I am open to bring back discussions about a forced offload when
> a single task is blocked in console_unlock() for too long.
This is a matter of adding hints for judging which thread
(console_owner or console_waiter) should continue printing.
> It might be configurable depending on the usecase. For example,
> real time kernel would be more aggressive with offloading.
> It might need to be completely disabled to debug certain
> type of problems, e.g. sudden death.
> But I would really like to avoid even more printk variants.
> They have many problems:
> + Only a handful of people would know how to use them right.
The caller of async printk() knows when/how to use async printk().
> + They are hard to maintain. Any incompatible printk() in the call
> chain might break the intention.
There is no incompatible printk(). Only when to wake up a thread which
writes to consoles differs.
> + They are problematic in a shared code. Incompatible printk()
> variants might be required/preferred according to the use case.
Again, there is no incompatible printk().
> + They might improve situation in one workload and make it
> worse in another one.
Avoiding e.g. RCU stall / OOM stall by deferring write to consoles is
an improvement. Reducing the side effect of accumulated pending logs
is matters of "how we can try to offload to an idle thread (or utilize
idle CPUs) for writing to consoles" and "how we can try to ratelimit
To me, none of these concerns is a valid reason to keep "store now but
print later" prefix away.
>>> For example, I would stop printing allocation failures until
>>> the currently running OOM killer succeeds in freeing some memory.
>> We could serialize out_of_memory() and warn_alloc(), but since warn_alloc()
>> can be called from atomic context (e.g. GFP_ATOMIC from interrupt handler)
>> while out_of_memory() is always called from schedulable context (e.g.
>> GFP_KERNEL), we can't use oom_lock mutex.
> I did not mean serializing. I meant to avoid printing the warnings
> at all until OOM killer finishes its job.
But your ratelimit_reset() below requires serializing.
>> Also, both nopage_rs in warn_alloc() and oom_rs in oom_kill_process() are not
>> working well. This is because ___ratelimit() function assumes that operations
>> to be ratelimited complete fast enough to be able to repeat many times within
>> a second. If one operation to be ratelimited takes many seconds (or even
>> minutes), ___ratelimit() becomes always true and can not ratelimit at all.
> The current ratelimiting is time driven. We might need an event
> driven variant. It might even be done with the current
> implementation if we add something like:
> void ratelimit_reset(struct ratelimit_state *rs)
> unsigned long flags;
> raw_spin_irqsave(&rs->lock, flags);
> rs->begin = jiffies;
> rs->printed = 0;
> raw_spin_unlock_irqrestore(&rs->lock, flags);
> We could call this when some event "solved" the problem.
This requires serialization among threads using "rs". I already
proposed ratelimit_reset() for memcg's OOM problem at
but it was not accepted.
> It means that it makes sense to enable the related
> ratelimited messages again because they would describe
> another problem.
___ratelimit() could also check number of not-yet-flushed
printk() records (e.g. log_next_seq - console_seq <= $some_threshold).
next prev parent reply other threads:[~2019-03-06 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 4:42 [RFC PATCH] printk: Introduce "store now but print later" prefix Tetsuo Handa
2019-03-04 3:22 ` Sergey Senozhatsky
2019-03-04 11:40 ` Tetsuo Handa
2019-03-04 12:09 ` Sergey Senozhatsky
2019-03-04 14:23 ` Petr Mladek
2019-03-04 14:37 ` Sergey Senozhatsky
2019-03-05 1:23 ` Tetsuo Handa
2019-03-05 7:52 ` Sergey Senozhatsky
2019-03-05 12:57 ` Michal Hocko
2019-03-06 10:04 ` Petr Mladek
2019-03-06 14:27 ` Sergey Senozhatsky
2019-03-06 18:24 ` Tetsuo Handa [this message]
2019-03-15 10:49 ` Tetsuo Handa
2019-03-20 15:04 ` Petr Mladek
2019-03-20 15:25 ` ratelimit API: was: " Petr Mladek
2019-03-21 8:13 ` Tetsuo Handa
2019-03-21 8:49 ` Michal Hocko
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.