linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Yufen <wangyufen@huawei.com>
To: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <pavel@ucw.cz>, Wang Yufen <wangyufen@huawei.com>
Subject: [PATCH 00/13] leds: Fix devm vs. non-devm ordering
Date: Wed, 9 Nov 2022 16:48:01 +0800	[thread overview]
Message-ID: <1667983694-15040-1-git-send-email-wangyufen@huawei.com> (raw)

Fault-inject tests reports this issue:

DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 2 PID: 52 at kernel/locking/mutex.c:582 __mutex_lock+0x1366/0x15b0
Call Trace:
 <TASK>
   cr0014114_set_sync+0x2d/0x80 [leds_cr0014114 dbd1de3fefae3e163bcc08f4eeaa6d1b243203a9]
   set_brightness_delayed+0xc2/0x140
   process_one_work+0x651/0xc30
   worker_thread+0x30b/0x820
   kthread+0x1a0/0x1e0
   ret_from_fork+0x1f/0x30
 </TASK>

The issue occurs in the following scenarios:

.probe()
  mutex_init()
  led->brightness_set_blocking = callback  <-- e.g. cr0014114_set_sync()
  devm_led_classdev_register_ext()
  <-- dr->node.release = devm_led_classdev_release()
...

.remove()
  mutex_destroy(lock)         <-- lock destroy

worker_thread()
  set_brightness_work
    set_brightness_delayed()
      __led_set_brightness_blocking()
        led_cdev->brightness_set_blocking()
        <-- callback, e.g. cr0014114_set_sync()
          mutex_lock(lock)              <-- lock is used after destroy

.release()
  devm_led_classdev_release()
    led_classdev_unregister()
      <-- flush set_brightness_work

When non-devm resources are allocated they mustn't be followed by devm
allocations, otherwise it will break the tear down ordering and might
lead to crashes or other bugs during ->remove() stage. Fix this by
wrapping mutex_destroy() call with devm_add_action_or_reset().

Wang Yufen (13):
  leds: cr0014114: Fix devm vs. non-devm ordering
  leds: el15203000: Fix devm vs. non-devm ordering
  leds: lm3532: Fix devm vs. non-devm ordering
  leds: lm3692x: Fix devm vs. non-devm ordering
  leds: lm3697: Fix devm vs. non-devm ordering
  leds: lp50xx: Fix devm vs. non-devm ordering
  leds: lp8860: Fix devm vs. non-devm ordering
  leds: mlxreg: Fix devm vs. non-devm ordering
  leds: mt6323: Fix devm vs. non-devm ordering
  leds: powernv: Fix devm vs. non-devm ordering
  leds: sc27xx: Fix devm vs. non-devm ordering
  leds: spi-byte: Fix devm vs. non-devm ordering
  leds: rt8515: Fix devm vs. non-devm ordering

 drivers/leds/flash/leds-rt8515.c | 11 +++++++++--
 drivers/leds/leds-cr0014114.c    | 11 ++++++++++-
 drivers/leds/leds-el15203000.c   | 18 +++++++++++-------
 drivers/leds/leds-lm3532.c       | 10 ++++++++++
 drivers/leds/leds-lm3692x.c      | 11 ++++++++++-
 drivers/leds/leds-lm3697.c       | 13 ++++++++++---
 drivers/leds/leds-lp50xx.c       | 12 ++++++++++--
 drivers/leds/leds-lp8860.c       | 11 +++++++++--
 drivers/leds/leds-mlxreg.c       | 20 ++++++++++----------
 drivers/leds/leds-mt6323.c       | 11 +++++++++--
 drivers/leds/leds-powernv.c      | 12 +++++++++---
 drivers/leds/leds-sc27xx-bltc.c  | 27 +++++++++++----------------
 drivers/leds/leds-spi-byte.c     | 21 ++++++++++-----------
 13 files changed, 128 insertions(+), 60 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2022-11-09  8:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  8:48 Wang Yufen [this message]
2022-11-09  8:48 ` [PATCH 01/13] leds: cr0014114: Fix devm vs. non-devm ordering Wang Yufen
2022-11-09  8:48 ` [PATCH 02/13] leds: el15203000: " Wang Yufen
2022-11-09  9:39   ` Oleh Kravchenko
2022-11-09 10:25     ` wangyufen
2022-11-09 10:43       ` Oleh Kravchenko
     [not found]         ` <c53e4614-eb06-cda8-f9da-2ca58396df54@huawei.com>
2022-11-11 10:39           ` Oleh Kravchenko
2022-11-15  2:06             ` Wei Yongjun
2022-11-22  1:10               ` Wang Yufen
2022-11-25 22:21                 ` Oleh Kravchenko
2022-11-09  8:48 ` [PATCH 03/13] leds: lm3532: " Wang Yufen
2022-11-09  8:48 ` [PATCH 04/13] leds: lm3692x: " Wang Yufen
2022-11-09  8:48 ` [PATCH 05/13] leds: lm3697: " Wang Yufen
2022-11-09  8:48 ` [PATCH 06/13] leds: lp50xx: " Wang Yufen
2022-11-09  8:48 ` [PATCH 07/13] leds: lp8860: " Wang Yufen
2022-11-09  8:48 ` [PATCH 08/13] leds: mlxreg: " Wang Yufen
2022-11-09  8:48 ` [PATCH 09/13] leds: mt6323: " Wang Yufen
2022-11-09  8:48 ` [PATCH 10/13] leds: powernv: " Wang Yufen
2022-11-09  8:48 ` [PATCH 11/13] leds: sc27xx: " Wang Yufen
2022-11-09  8:48 ` [PATCH 12/13] leds: spi-byte: " Wang Yufen
2022-11-09  8:48 ` [PATCH 13/13] leds: rt8515: " Wang Yufen
2022-12-07 20:20 ` [PATCH 00/13] leds: " Pavel Machek
2022-12-08  2:23   ` wangyufen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1667983694-15040-1-git-send-email-wangyufen@huawei.com \
    --to=wangyufen@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).