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] [day] [month] [year] [list]
Date:   Thu, 18 Apr 2019 13:03:05 -0700
From:   Andrey Smirnov <andrew.smirnov@...il.com>
To:     Sebastian Reichel <sre@...nel.org>
Cc:     Chris Healy <cphealy@...il.com>, linux-pm@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

On Wed, Apr 17, 2019 at 7:35 PM Sebastian Reichel <sre@...nel.org> wrote:
>
> Hi,
>
> On Fri, Apr 05, 2019 at 12:30:20AM -0700, Andrey Smirnov wrote:
> > Fix a similar endless event loop as was done in commit 8dcf32175b4e
> > ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"):
> >
> >   The culprit is the dev_dbg printk in the i2c uevent handler. If
> >   this is activated (for instance by CONFIG_I2C_DEBUG_CORE) it results
> >   in an endless loop with systemd-journald.
> >
> >   This happens if user-space scans the system log and reads the uevent
> >   file to get information about a newly created device, which seems
> >   fair use to me. Unfortunately reading the "uevent" file uses the
> >   same function that runs for creating the uevent for a new device,
> >   generating the next syslog entry
> >
> > Both CONFIG_I2C_DEBUG_CORE and CONFIG_POWER_SUPPLY_DEBUG were reported
> > in https://bugs.freedesktop.org/show_bug.cgi?id=76886 but only former
> > seems to have been fixed. Change debug prints to use pr_debug insted
> > to resolve the issue.
> >
> > Signed-off-by: Andrey Smirnov <andrew.smirnov@...il.com>
> > Cc: Chris Healy <cphealy@...il.com>
> > Cc: Sebastian Reichel <sre@...nel.org>
> > Cc: linux-pm@...r.kernel.org
> > Cc: linux-kernel@...r.kernel.org
> > ---
>
> I think we should just drop these debug messages, just like I2C did.
> They don't offer any useful information considering the info is already
> exposed to userspace via the uevent.

OK, sounds good, will do in v2.

Thanks,
Andrey Smirnov

Powered by blists - more mailing lists