[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXMbGS6xFyW80Cv1xOSF=e76G16vVrboQUkgC7Q_mgZtw@mail.gmail.com>
Date: Thu, 24 Apr 2014 09:18:25 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
Cc: Ley Foon Tan <lftan@...era.com>,
Linux-Arch <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
LeyFoon Tan <lftan.linux@...il.com>, cltang@...esourcery.com,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 08/28] nios2: MMU Fault handling
On Tue, Apr 22, 2014 at 4:30 PM, Ezequiel Garcia
<ezequiel.garcia@...e-electrons.com> wrote:
> On Apr 18, Ley Foon Tan wrote:
>> +
>> +bad_area_nosemaphore:
>> + /* User mode accesses just cause a SIGSEGV */
>> + if (user_mode(regs)) {
>
> I found that it's useful to add some printing here, just as ARM
> does. I carry this patch on my kernel:
>
> + printk(KERN_INFO "%s: unhandled page fault (%d) at 0x%08lx, cause %ld\n",
> + current->comm, SIGSEGV, address, cause);
> + show_regs(regs);
>
> Do you think we could do something like it? Maybe with a compile time option?
Can this easily be triggered from userspace? If yes, please use
pr_info_ratelimited().
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists