Re: [PATCH 2/2] printk: always report lost messages on serial console

From	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH 2/2] printk: always report lost messages on serial console
Date	2017-01-03 16:50 +0100
Message-ID	<sVzvz-8oo-17@gated-at.bofh.it> (permalink)
References	<sRVkZ-7ZZ-1@gated-at.bofh.it> <sRVkZ-7ZZ-9@gated-at.bofh.it> <sVyJh-7Mp-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On (01/03/17 15:55), Petr Mladek wrote:
[..]
> This causes the opposite problem. We might print a message that was supposed
> to be suppressed.

so what? yes, we print a message that otherwise would have been suppressed.
not a big deal. at all. we are under high printk load and the best thing
we can do is to report "we are losing the messages" straight ahead. the
next 'visible' message may be seconds/minutes/forever away. think of a
printk() flood of messages with suppressed loglevel coming from CPUA-CPUX,
big enough to drain all 'visible' loglevel messages from CPUZ. we are
back to problem "a".

thus I want a simple bool flag and a simple rule: we see something - we say it.

[..]
> The best solution seems to be to print the warning with
> the next visible message.

not sure.

	-ss

Thread

[PATCH 0/2] printk: always report dropped messages Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-12-24 15:20 +0100
  [PATCH 1/2] printk: drop call_console_drivers() unused param Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-12-24 15:20 +0100
    Re: [PATCH 1/2] printk: drop call_console_drivers() unused param Petr Mladek <pmladek@suse.com> - 2017-01-03 11:30 +0100
      Re: [PATCH 1/2] printk: drop call_console_drivers() unused param Petr Mladek <pmladek@suse.com> - 2017-01-09 15:00 +0100
  [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-12-24 15:20 +0100
    Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-03 16:00 +0100
      Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-01-03 16:50 +0100
        Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-03 18:20 +0100
          Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-04 03:50 +0100
            Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-04 12:00 +0100
              Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-01-04 14:40 +0100
                Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-04 16:30 +0100
                Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-05 03:40 +0100
                Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-05 12:20 +0100
    Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-09 18:00 +0100
      Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-10 09:50 +0100
        Re: [PATCH 2/2] printk: always report lost messages on serial console Petr Mladek <pmladek@suse.com> - 2017-01-11 18:00 +0100
          Re: [PATCH 2/2] printk: always report lost messages on serial console Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-13 06:20 +0100

csiph-web