linux-kernel - [PATCH 0/2] driver core: Improve warning backtrace in device probing

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: <20191120143619.1027-1-geert+renesas@glider.be>
Date:   Wed, 20 Nov 2019 15:36:17 +0100
From:   Geert Uytterhoeven <geert+renesas@...der.be>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Geert Uytterhoeven <geert+renesas@...der.be>
Subject: [PATCH 0/2] driver core: Improve warning backtrace in device probing

	Hi Greg, Rafael,

Once in a while, the WARN_ON() in really_probe() is triggered due to a
bug in a driver or subsystem.  While the backtrace provides some clues,
it does not reveal the offending device.

Hence this patch series adds a new dev_WARN_ON() helper, and uses that.

Thanks!

Geert Uytterhoeven (2):
  driver core: Add dev_WARN_ON() helper
  driver core: Print device in really_probe() warning backtrace

 drivers/base/dd.c      | 2 +-
 include/linux/device.h | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

-- 
2.17.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds