From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: hardcoded SIGSEGV in __die() ?
Date: Mon, 23 Mar 2020 14:17:36 +0000 [thread overview]
Message-ID: <73da05c0f54692a36471a2539dbd9b30594b687a.camel@infinera.com> (raw)
In __die(), see below, there is this call to notify_send() with SIGSEGV hardcoded, this seems odd
to me as the variable "err" holds the true signal(in my case SIGBUS)
Should not SIGSEGV be replaced with the true signal no.?
Jocke
static int __die(const char *str, struct pt_regs *regs, long err)
{
printk("Oops: %s, sig: %ld [#%d]\n", str, err, ++die_counter);
if (IS_ENABLED(CONFIG_CPU_LITTLE_ENDIAN))
printk("LE ");
else
printk("BE ");
if (IS_ENABLED(CONFIG_PREEMPT))
pr_cont("PREEMPT ");
if (IS_ENABLED(CONFIG_SMP))
pr_cont("SMP NR_CPUS=%d ", NR_CPUS);
if (debug_pagealloc_enabled())
pr_cont("DEBUG_PAGEALLOC ");
if (IS_ENABLED(CONFIG_NUMA))
pr_cont("NUMA ");
pr_cont("%s\n", ppc_md.name ? ppc_md.name : "");
if (notify_die(DIE_OOPS, str, regs, err, 255, SIGSEGV) == NOTIFY_STOP)
return 1;
print_modules();
show_regs(regs);
return 0;
}
next reply other threads:[~2020-03-23 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:17 Joakim Tjernlund [this message]
2020-03-23 14:43 ` hardcoded SIGSEGV in __die() ? Christophe Leroy
2020-03-23 14:45 ` Christophe Leroy
2020-03-23 15:08 ` Joakim Tjernlund
2020-03-23 15:31 ` Christophe Leroy
2020-03-23 15:44 ` Joakim Tjernlund
2020-03-25 17:02 ` David Laight
2020-03-25 17:09 ` Joakim Tjernlund
2020-03-26 0:28 ` Michael Ellerman
2020-03-27 10:10 ` Joakim Tjernlund
2020-03-30 17:16 ` Joakim Tjernlund
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=73da05c0f54692a36471a2539dbd9b30594b687a.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).