Re: Logging a kernel message when blocking on entropy

[David Brownlee <abs%absd.org@localhost>]

On Tue, 22 Sep 2020 at 12:35, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
>
> On Tue, Sep 22, 2020 at 02:31:50PM +0300, Andreas Gustafsson wrote:
> > Manuel Bouyer wrote:
> > > I'm not sure we want a user-triggerable kernel printf enabled by default.
> > > This could be used to DOS the system (especially on serial consoles)
> >
> > You can already trigger kernel printfs as an unprivileged user.
> > The first one that comes to mind is "sorry, pid %d was killed:
> > orphaned traced process", but I'm sure there are many others.
>
> I think we should find and remove theses (or make them conditional)
> instead of adding unconditional new ones

Maybe a standard way of rate limiting such messages, including
indicating how many were skipped due to rate limiting when the next
one gets printed?

David