linux-kernel - Re: [PATCH 00/13] leds: Fix devm vs. non-devm ordering

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

Message-ID: <Y5D1d3WhLCpmfo+N@duo.ucw.cz>
Date:   Wed, 7 Dec 2022 21:20:07 +0100
From:   Pavel Machek <pavel@....cz>
To:     Wang Yufen <wangyufen@...wei.com>
Cc:     linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/13] leds: Fix devm vs. non-devm ordering

Hi!

> 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:

Ok, so:

a) this does not happen in wild

b) you have not actually tested any of this

?

It looks reasonable, but the "Fixes:" tags mean -stable will pick this
up almost immediately.

Is anyone else willing to say this looks ok to him?

Any testers?

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

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