linux-kernel - RFC: a failing pm_runtime

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-next>] [day] [month] [year] [list]

Message-ID: <20200614090751.GA2878@kunai>
Date:   Sun, 14 Jun 2020 11:07:51 +0200
From:   Wolfram Sang <wsa@...nel.org>
To:     linux-pm@...r.kernel.org, "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-i2c@...r.kernel.org
Subject: RFC: a failing pm_runtime_get increases the refcnt?

Hi Linux-PM,

both in the I2C subsystem and also for Renesas drivers I maintain, I am
starting to get boilerplate patches doing some pm_runtime_put_* variant
because a failing pm_runtime_get is supposed to increase the ref
counters? Really? This feels wrong and unintuitive to me. I expect there
has been a discussion around it but I couldn't find it. I wonder why we
don't fix the code where the incremented refcount is expected for some
reason.

Can I have some pointers please?

Thanks,

   Wolfram

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)