linux-kernel - Re: [PATCH] softlockup: show irqtrace

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: <20080625160016.GA24967@elte.hu>
Date:	Wed, 25 Jun 2008 18:00:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Johannes Weiner <hannes@...urebad.de>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] softlockup: show irqtrace

* Vegard Nossum <vegard.nossum@...il.com> wrote:

> Hi,
> 
> Ingo, can you please drop the "softirq softlockup debugging" patch and 
> apply this instead? This much, much prettier, reuses existing 
> debugging infrastructure, and is a lot more generic.

applied to tip/core/softlockup, thanks Vegard.

> (Compile tested on allyesconfig, allnoconfig, allnoconfig + softlockup 
> debugging.)

hm, that must have taken quite some time to do on your desktop, right?

FYI, there's no mandatory need to go through that buerocratic testing 
hassle with patches submitted to -tip - especially with small patches 
that look obvious and have a high chance of being right. We do non-stop 
allyes/allno/allmod+randconfig 64-bit/32-bit build and boot testing for 
every single patch added to the repository.

Building, booting and testing it in the environment where you expect it 
to be used primarily should be more than enough.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/