From: David Laight <David.Laight@ACULAB.COM>
To: 'Joakim Tjernlund' <Joakim.Tjernlund@infinera.com>,
"christophe.leroy@c-s.fr" <christophe.leroy@c-s.fr>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: RE: hardcoded SIGSEGV in __die() ?
Date: Wed, 25 Mar 2020 17:02:40 +0000 [thread overview]
Message-ID: <1bec238369f24e978e0da14f79b9c55f@AcuMS.aculab.com> (raw)
In-Reply-To: <6b3484a7bf0f760570fbe7c8b22c36a244c19ff6.camel@infinera.com>
From: Joakim Tjernlund
> Sent: 23 March 2020 15:45
...
> > > I tried to follow that chain thinking it would end up sending a signal to user space but I cannot
> see
> > > that happens. Seems to be related to debugging.
> > >
> > > In short, I cannot see any signal being delivered to user space. If so that would explain why
> > > our user space process never dies.
> > > Is there a signal hidden in machine_check handler for SIGBUS I cannot see?
> > >
> >
> > Isn't it done in do_exit(), called from oops_end() ?
>
> hmm, so it seems. The odd thing though is that do_exit takes an exit code, not signal number.
> Also, feels a bit odd to force an exit(that we haven't seen happening) rather than just a signal.
Isn't there something 'magic' that converts EFAULT into SIGSEGV?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-03-25 17:11 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
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 [this message]
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=1bec238369f24e978e0da14f79b9c55f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=christophe.leroy@c-s.fr \
--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).