linux-kernel - Re: per-cpu related?

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: <19f34abd0807130346p58872bado5d7217fe85e74c1f@mail.gmail.com>
Date:	Sun, 13 Jul 2008 12:46:51 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Yinghai Lu" <yhlu.kernel@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"Mike Travis" <travis@....com>
Subject: Re: per-cpu related?

On Sun, Jul 13, 2008 at 11:26 AM, Ingo Molnar <mingo@...e.hu> wrote:
> [    9.270000] BUG: unable to handle kernel paging request at ffff88080101c1f8
> [    9.270000] IP: [<ffffffff80230576>] dequeue_task+0x73/0xf0

[...]

> [    9.270000] RIP: 0010:[<ffffffff80230576>]  [<ffffffff80230576>] dequeue_task+0x73/0xf0
> [    9.270000] RSP: 0018:ffff88003f9b7420  EFLAGS: 00010046
> [    9.270000] RAX: ffff88000101c200 RBX: ffff88003f9b4000 RCX: ffffffff80db5d40
> [    9.270000] RDX: 00000000ffffffff RSI: ffff88003f9b6000 RDI: ffff880001026d40

I don't think this is per-cpu related.

It seems that task_thread_info(p)->cpu returns -1. This is the number
that is loaded into %rdx:

mov    0x1c(%rsi),%edx
mov    (%rax,%rdx,8),%rax <-- faulting instruction

You also had this:

[    9.270000] Thread overran stack, or stack corrupted

so it seems likely that your thread_info was corrupted as well.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/