From: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
To: LEROY Christophe <christophe.leroy@c-s.fr>
Cc: linuxppc-dev@lists.ozlabs.org, "Tobin C . Harding" <me@tobin.cc>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Simon Guo <wei.guo.simon@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Nicholas Piggin <npiggin@gmail.com>,
Michael Neuling <mikey@neuling.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Cyril Bur <cyrilbur@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Balbir Singh <bsingharora@gmail.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
"Alastair D'Silva" <alastair@d-silva.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] powerpc/traps: Print signal name for unhandled signals
Date: Wed, 25 Jul 2018 17:06:31 -0300 [thread overview]
Message-ID: <20180725200631.GC23643@kermit-br-ibm-com> (raw)
In-Reply-To: <20180725174927.Horde.Sfg4oyTmcaLgHIJr3Gf-oQ1@messagerie.si.c-s.fr>
Hi, Christophe.
On Wed, Jul 25, 2018 at 05:49:27PM +0200, LEROY Christophe wrote:
> Murilo Opsfelder Araujo <muriloo@linux.ibm.com> a écrit :
>
> > This adds a human-readable name in the unhandled signal message.
> >
> > Before this patch, a page fault looked like:
> >
> > Jul 11 16:04:11 localhost kernel: pandafault[6303]: unhandled signal
> > 11 at 00000000100007d0 nip 000000001000061c lr 00007fff93c55100 code 2
> > in pandafault[10000000+10000]
> >
> > After this patch, a page fault looks like:
> >
> > Jul 11 18:14:48 localhost kernel: pandafault[6352]: segfault (11) at
> > 000000013a2a09f8 nip 000000013a2a086c lr 00007fffb63e5100 code 2 in
> > pandafault[13a2a0000+10000]
> >
> > Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
> > ---
> > arch/powerpc/kernel/traps.c | 43 +++++++++++++++++++++++++++++++++----
> > 1 file changed, 39 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
> > index e6c43ef9fb50..e55ee639d010 100644
> > --- a/arch/powerpc/kernel/traps.c
> > +++ b/arch/powerpc/kernel/traps.c
> > @@ -96,6 +96,41 @@ EXPORT_SYMBOL(__debugger_fault_handler);
> > #define TM_DEBUG(x...) do { } while(0)
> > #endif
> >
> > +static const char *signames[SIGRTMIN + 1] = {
> > + "UNKNOWN",
> > + "SIGHUP", // 1
> > + "SIGINT", // 2
> > + "SIGQUIT", // 3
> > + "SIGILL", // 4
> > + "unhandled trap", // 5 = SIGTRAP
> > + "SIGABRT", // 6 = SIGIOT
> > + "bus error", // 7 = SIGBUS
> > + "floating point exception", // 8 = SIGFPE
> > + "illegal instruction", // 9 = SIGILL
> > + "SIGUSR1", // 10
> > + "segfault", // 11 = SIGSEGV
> > + "SIGUSR2", // 12
> > + "SIGPIPE", // 13
> > + "SIGALRM", // 14
> > + "SIGTERM", // 15
> > + "SIGSTKFLT", // 16
> > + "SIGCHLD", // 17
> > + "SIGCONT", // 18
> > + "SIGSTOP", // 19
> > + "SIGTSTP", // 20
> > + "SIGTTIN", // 21
> > + "SIGTTOU", // 22
> > + "SIGURG", // 23
> > + "SIGXCPU", // 24
> > + "SIGXFSZ", // 25
> > + "SIGVTALRM", // 26
> > + "SIGPROF", // 27
> > + "SIGWINCH", // 28
> > + "SIGIO", // 29 = SIGPOLL = SIGLOST
> > + "SIGPWR", // 30
> > + "SIGSYS", // 31 = SIGUNUSED
> > +};
> > +
> > /*
> > * Trap & Exception support
> > */
> > @@ -314,10 +349,10 @@ static void show_signal_msg(int signr, struct
> > pt_regs *regs, int code,
> > if (!unhandled_signal(current, signr))
> > return;
> >
> > - pr_info("%s[%d]: unhandled signal %d at "REG_FMT \
> > - " nip "REG_FMT" lr "REG_FMT" code %x",
> > - current->comm, current->pid, signr, addr,
> > - regs->nip, regs->link, code);
> > + pr_info("%s[%d]: %s (%d) at "REG_FMT" nip "REG_FMT \
> > + " lr "REG_FMT" code %x",
> > + current->comm, current->pid, signames[signr],
> > + signr, addr, regs->nip, regs->link, code);
>
> Are we sure that signr is always within the limits of the table ?
Looking at the code, we only pass the following signals:
SIGBUS
SIGFPE
SIGILL
SIGSEGV
SIGTRAP
All of them are within the limits of the table. We've added other
signals for completeness.
Cheers
Murilo
next prev parent reply other threads:[~2018-07-25 20:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 19:27 [PATCH 0/7] powerpc: Modernize unhandled signals message Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 1/7] powerpc/traps: Print unhandled signals in a separate function Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 2/7] powerpc/traps: Return early in show_signal_msg() Murilo Opsfelder Araujo
2018-07-25 15:42 ` LEROY Christophe
2018-07-25 20:31 ` Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 3/7] powerpc/reg: Add REG_FMT definition Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 4/7] powerpc/traps: Use REG_FMT in show_signal_msg() Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 5/7] powerpc/traps: Print VMA for unhandled signals Murilo Opsfelder Araujo
2018-07-24 19:27 ` [PATCH 6/7] powerpc/traps: Print signal name " Murilo Opsfelder Araujo
2018-07-25 15:19 ` Gustavo Romero
2018-07-25 19:41 ` Murilo Opsfelder Araujo
2018-07-25 15:49 ` LEROY Christophe
2018-07-25 20:06 ` Murilo Opsfelder Araujo [this message]
2018-07-24 19:27 ` [PATCH 7/7] powerpc/traps: Show instructions on exceptions Murilo Opsfelder Araujo
2018-07-25 16:01 ` LEROY Christophe
2018-07-25 20:51 ` Murilo Opsfelder Araujo
2018-07-25 7:00 ` [PATCH 0/7] powerpc: Modernize unhandled signals message Michael Neuling
2018-07-25 19:36 ` Murilo Opsfelder Araujo
2018-07-26 2:11 ` Michael Neuling
2018-07-26 2:20 ` Michael Ellerman
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=20180725200631.GC23643@kermit-br-ibm-com \
--to=muriloo@linux.ibm.com \
--cc=alastair@d-silva.org \
--cc=andrew.donnellan@au1.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=cyrilbur@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=me@tobin.cc \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=wei.guo.simon@gmail.com \
/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).