<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-journald rate limits on kernel messages"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83221">83221</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-journald rate limits on kernel messages
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>wzyboies@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>I can see there are some rate limits in /etc/systemd/journald.conf and the
default values, according to journald.conf(5) is "1000 messages in 30s". This
is nice. However, it seems that these limits do not apply to kernel messages.
My / partition is 10 GiB so journals by defaults take up to 1 GiB space, this
is enough for months of logs on my laptop. However, yesterday I encountered a
bug related to USB kernel module while traferring data from my laptop to my USB
device, this bug made the USB kernel module keep generating kernel messages
(that kind of [---cut here---] stuff) at a rate of thousands of lines per
second. These kernel messages quickly took up 1 GiB space and totally flushed
all the logs of previous months in a few minutes.
Generating more than 1 GiB of kernel messages in a few minutes is apprently
more than the defaults limit of "1000 messages in 30s", but journald did not
stop this kind of "stupid" behaviour.
May I suggest that journald should also apply the rate limit not only on
service messages, but also on kernel messages? This will help a lot when some
kernel module generates tons of messages.
Thanks.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>