lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 25 Apr 2014 00:02:13 +0800
From:	Ley Foon Tan <lftan@...era.com>
To:	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
Cc:	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>,
	cltang@...esourcery.com
Subject: Re: [PATCH 08/28] nios2: MMU Fault handling

On Thu, Apr 24, 2014 at 11:22 PM, Ezequiel Garcia
<ezequiel.garcia@...e-electrons.com> wrote:
>> > 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?
>> Yes, this is useful debug message. I can add this.
>> Prefer not to add new compile time option, I think this shouldn't
>> happen frequently.
>
> No, it shouldn't happen frequently. You can take a look at what ARM does.
> They use a DEBUG_USER compile-time option, much more complex than my silly
> proposal.
For now, we can print it always if this shouldn't happen frequently.
Compile time option can be added later if we have more other debug
stuff to print later.

Thanks.

Regard,
Ley Foon
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ