Thread (11 messages) 11 messages, 4 authors, 2020-03-30

Re: hardcoded SIGSEGV in __die() ?

From: Joakim Tjernlund <hidden>
Date: 2020-03-25 17:13:02

On Wed, 2020-03-25 at 17:02 +0000, David Laight wrote:
CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.


From: Joakim Tjernlund
quoted
Sent: 23 March 2020 15:45
...
quoted
quoted
quoted
I tried to follow that chain thinking it would end up sending a
signal to user space but I cannot
see
quoted
quoted
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?
I have tried to find out and I cannot see a signal beeing sent.
Also, SEGV is wrong, this is a SIGBUS fault.
        David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes,
MK1 1PT, UK
Registration No: 1397386 (Wales)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help