From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236
Date: Mon, 30 Nov 2015 11:20:44 -0500 [thread overview]
Message-ID: <565C775C.9050004@oracle.com> (raw)
Hi all,
I've hit the following while fuzzing with trinity on the latest -next kernel:
[ 587.536319] WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 sigsuspend+0x194/0x1b0()
[ 587.540863] Modules linked in:
[ 587.541742] CPU: 12 PID: 16862 Comm: trinity-c421 Not tainted 4.4.0-rc2-next-20151127-sasha-00011-g1ca161c-dirty #2660
[ 587.543554] 0000000000000000 000000002c914859 ffff8806e3347e38 ffffffff9ea923db
[ 587.545672] 0000000000000000 ffff8800c8032000 ffffffffa64a5120 ffff8806e3347e78
[ 587.547042] ffffffff9d2e00d9 ffffffff9d307334 ffffffffa64a5120 00000000000000ec
[ 587.549585] Call Trace:
[ 587.550261] [<ffffffff9ea923db>] dump_stack+0x72/0xb7
[ 587.551125] [<ffffffff9d2e00d9>] warn_slowpath_common+0x109/0x130
[ 587.553088] [<ffffffff9d2e0329>] warn_slowpath_null+0x29/0x30
[ 587.554164] [<ffffffff9d307334>] sigsuspend+0x194/0x1b0
[ 587.555116] [<ffffffff9d30b47b>] SyS_rt_sigsuspend+0xbb/0x110
[ 587.561511] [<ffffffffa61fbbd5>] entry_SYSCALL_64_fastpath+0x35/0x99
[ 587.563289] ---[ end trace 76d0b7c8c18c2a7d ]---
Thanks,
Sasha
next reply other threads:[~2015-11-30 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 16:20 Sasha Levin [this message]
2015-11-30 16:44 ` WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Al Viro
2015-11-30 16:52 ` Peter Zijlstra
2015-11-30 18:48 ` Oleg Nesterov
2016-01-09 7:08 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565C775C.9050004@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox