[systemd-bugs] [Bug 76886] Journald can cause an endless loop

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=76886

Kay Sievers <kay at vrfy.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #1 from Kay Sievers <kay at vrfy.org> ---
(In reply to comment #0)
> 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)

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140402/c007f240/attachment.html>