linux-kernel - Re: [KDUMP] Ignore spurious IPI

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: <imhdm5$9u8$2@dough.gmane.org>
Date:	Fri, 25 Mar 2011 06:45:25 +0000 (UTC)
From:	WANG Cong <xiyou.wangcong@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	kexec@...ts.infradead.org
Subject: Re: [KDUMP] Ignore spurious IPI

On Thu, 24 Mar 2011 08:20:32 -0600, Milton Miller wrote:
> If so, just initialize the data structure earlier -- change
> init_call_single_data from early_initcall to an explict call after the
> per-cpu areas are initialized.
> 

Yeah, this is a good idea, IPI related data structures should be
ready before interrupts are enabled. We should not assume that
there is no IPI pending before init_call_single_data gets initialized,
altough this is true in non-kdump kernel.

Thanks.

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