linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: hardcoded SIGSEGV in __die() ?
Date: Mon, 23 Mar 2020 15:45:14 +0100	[thread overview]
Message-ID: <c14de482-6784-f1ac-f675-d771e55ac688@c-s.fr> (raw)
In-Reply-To: <b20d978b-268b-773a-a43e-7ff4c741f2df@c-s.fr>



Le 23/03/2020 à 15:43, Christophe Leroy a écrit :
> 
> 
> Le 23/03/2020 à 15:17, Joakim Tjernlund a écrit :
>> 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.?
> 
> As far as I can see, comes from 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=66fcb1059 
> 

And 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae87221d3ce49d9de1e43756da834fd0bf05a2ad 
shows it is (was?) similar on x86.

Christophe

  reply	other threads:[~2020-03-23 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 14:17 hardcoded SIGSEGV in __die() ? Joakim Tjernlund
2020-03-23 14:43 ` Christophe Leroy
2020-03-23 14:45   ` Christophe Leroy [this message]
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=c14de482-6784-f1ac-f675-d771e55ac688@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=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).