From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: pmladek@suse.com, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
a.sahrawat@samsung.com, pankaj.m@samsung.com,
v.narang@samsung.com
Subject: Re: [PATCH 2/2] printk: make sure to print log on console.
Date: Thu, 31 May 2018 19:52:15 +0900 [thread overview]
Message-ID: <20180531105215.GF477@jagdpanzerIV> (raw)
In-Reply-To: <20180531102246epcas5p2f1cbc6ff217172e12e2f78bb88eb4a7e~zs5h59tMh2250222502epcas5p2S@epcas5p2.samsung.com>
On (05/31/18 15:49), Maninder Singh wrote:
>
> This patch make sure printing of log if loglevel at time of storing
> log is greater than current console loglevel.
>
> @why
> In case of async printk, printk thread can miss logs because it checks
> current log level at time of console_unlock.
Upstream printk has no printing kthread. And we also run
printk()->console_unlock() with disabled preemption.
-ss
next prev parent reply other threads:[~2018-05-31 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180531102246epcas5p2f1cbc6ff217172e12e2f78bb88eb4a7e@epcas5p2.samsung.com>
2018-05-31 10:19 ` [PATCH 2/2] printk: make sure to print log on console Maninder Singh
2018-05-31 10:52 ` Sergey Senozhatsky [this message]
2018-05-31 12:21 ` Petr Mladek
2018-06-01 4:40 ` Sergey Senozhatsky
2018-06-01 8:53 ` Petr Mladek
2018-06-01 9:09 ` Petr Mladek
2018-06-01 9:37 ` Sergey Senozhatsky
2018-06-01 9:18 ` Sergey Senozhatsky
[not found] ` <CGME20180531102246epcas5p2f1cbc6ff217172e12e2f78bb88eb4a7e@epcms5p5>
2018-06-01 8:42 ` Vaneet Narang
2018-06-01 9:34 ` Sergey Senozhatsky
2018-05-31 13:27 ` 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=20180531105215.GF477@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=pankaj.m@samsung.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=v.narang@samsung.com \
/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).