linux-kernel - Re: [RFC][PATCH] printk: increase devkmsg write() ratelimit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 18 Dec 2018 22:09:46 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        Petr Mladek <pmladek@...e.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Borislav Petkov <bp@...en8.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [RFC][PATCH] printk: increase devkmsg write() ratelimit

On (12/18/18 12:29), Peter Zijlstra wrote:
> > We certainly can. As far as I understand, they log shutdown events
> > (including errors and warnings): what they kill, what they stop,
> > what they umount, etc. The more partitions, services are running
> > (I guess), the more things they need to umount, kill, stop; hence,
> > the more messages. I kinda can imagine what they will answer ;)
> > 
> > The below (and a bunch of other) messages are getting ratelimited.
> > I'm not sure what will happen should any of those steps fail and
> > print warning-s. My guess would be that we probably can ratelimit
> > those warnings:
> 
> Why are they writing it to /dev/kmsg though? Shouldn't they be writing
> this to syslog directly?

Can't really answer for systemd developers. To make those messages
appear on the serial/net console?

	-ss