linux-kernel - Re: [PATCH] conditionalize call from panic() to smp_send

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

Message-Id: <496F0CEB.76E4.0078.0@novell.com>
Date:	Thu, 15 Jan 2009 09:16:11 +0000
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] conditionalize call from panic() to
	 smp_send_stop()

>>> Andi Kleen <andi@...stfloor.org> 15.01.09 04:34 >>>
>"Jan Beulich" <jbeulich@...ell.com> writes:
>
>> ... avoiding nested warnings and/or oopses as much as possible (namely
>> durin early boot).
>
>Better would be to fix smp_send_stop than to work around it for this
>very limited case. I've been running into this with machine checks
>too. The new fancy smp_call_function() that is there now just doesn't
>work in any unusual situation like early boot or fatal exceptions,

Indeed - I wasn't used to smp_call_function...() to be generic functions
that can be fixed for all architectures at once. I simply wanted to avoid
needing individual changes in all architectures...

Jan



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