Re: hardcoded SIGSEGV in __die() ?

2020-03-30 Thread Joakim Tjernlund
On Thu, 2020-03-26 at 11:28 +1100, Michael Ellerman 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. > > > Joakim Tjernlund writes: > > On Mon, 2020-03-23 at 15:45

Re: hardcoded SIGSEGV in __die() ?

2020-03-27 Thread Joakim Tjernlund
On Thu, 2020-03-26 at 11:28 +1100, Michael Ellerman 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. > > > Joakim Tjernlund writes: > > On Mon, 2020-03-23 at 15:45

Re: hardcoded SIGSEGV in __die() ?

2020-03-25 Thread Michael Ellerman
Joakim Tjernlund writes: > On Mon, 2020-03-23 at 15:45 +0100, Christophe Leroy wrote: >> 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

Re: hardcoded SIGSEGV in __die() ?

2020-03-25 Thread Joakim Tjernlund
On Wed, 2020-03-25 at 17:02 +, 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 > > Sent: 23 March 2020 15:45 > ... > >

RE: hardcoded SIGSEGV in __die() ?

2020-03-25 Thread David Laight
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

Re: hardcoded SIGSEGV in __die() ?

2020-03-23 Thread Joakim Tjernlund
On Mon, 2020-03-23 at 16:31 +0100, Christophe Leroy wrote: > > Le 23/03/2020 à 16:08, Joakim Tjernlund a écrit : > > On Mon, 2020-03-23 at 15:45 +0100, Christophe Leroy wrote: > > > CAUTION: This email originated from outside of the organization. Do not > > > click links or open attachments

Re: hardcoded SIGSEGV in __die() ?

2020-03-23 Thread Christophe Leroy
Le 23/03/2020 à 16:08, Joakim Tjernlund a écrit : On Mon, 2020-03-23 at 15:45 +0100, Christophe Leroy 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. Le 23/03/2020

Re: hardcoded SIGSEGV in __die() ?

2020-03-23 Thread Joakim Tjernlund
On Mon, 2020-03-23 at 15:45 +0100, Christophe Leroy 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. > > > Le 23/03/2020 à 15:43, Christophe Leroy a écrit : > > >

Re: hardcoded SIGSEGV in __die() ?

2020-03-23 Thread Christophe Leroy
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

Re: hardcoded SIGSEGV in __die() ?

2020-03-23 Thread Christophe Leroy
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