<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> <span class="fn">Kay Sievers</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Journald can cause an endless loop"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76886">bug 76886</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTOURBUG
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Journald can cause an endless loop"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76886#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Journald can cause an endless loop"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76886">bug 76886</a>
from <span class="vcard"><a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> <span class="fn">Kay Sievers</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=76886#c0">comment #0</a>)
<span class="quote">> dev_dbg creates an syslog entry - which triggers journald to read uevent
> file for this device, which than again dev_dbg() is called causing journald
> to read uevent file - so there is an endless loop (technically, kernel will
> kill journald after some time)</span >
This sounds like a bug in the kernel.
Most important, the conceptually broken idea of the power_supply class
to transport *measurement data*, *user access* or other unrelated things
over uevents should really be fixed, it cannot fly.
Uevents were never made for such a use case, uevents are very expensive
events for global device state changes regarding the device and its
*integration* into system management; there must never be any uevents
generated for normal expected device operations like device access or
charge level changes.
Please try to get the specific kernel driver fixed, or even the
power_supply class itself fixed. What userspace is doing here sounds totally
fine and nothing should need to work around such kernel brokeness. This
kernel behaviour makes no sense for userspace.</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>