linux-kernel - kdump: kdump can't boot in this case

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: <52561232.2060505@huawei.com>
Date:	Thu, 10 Oct 2013 10:34:26 +0800
From:	Xishi Qiu <qiuxishi@...wei.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: kdump: kdump can't boot in this case

I write a module, and find kdump can't boot in this case.
kernel version is 3.12, Intel(R) Xeon(R) CPU	E5620

struct timer_list g_timer;

void tmrhnd_invtssfault(unsigned long data)
{
	long __res;
	printk(KERN_EMERG "invalid TSS fault in interrupt context.\n");
	__asm__ volatile("int $0x0A" : "=a"(__res):);
}

{
	...
	init_timer(&g_timer);
	g_timer.expires = jiffies + 10;
	g_timer.data = 0;
	g_timer.function = tmrhnd_invtssfault;
	add_timer(&g_timer);
	...
}

If access NULL pointer instead of "__asm__ volatile("int $0x0A" : "=a"(__res):);" 
in tmrhnd_invtssfault(), kdump can boot.
And if not use timer, just do "__asm__ volatile("int $0x0A" : "=a"(__res):);" only
once in module, kdump can boot too.

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