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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 15 Jul 2015 20:08:19 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Levente Kurusa <lkurusa@...hat.com>
Cc:	ARM PORT <linux-arm-kernel@...ts.infradead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm: fault.c: fix unhandled page fault message

On Wed, Jul 15, 2015 at 05:30:50PM +0200, Levente Kurusa wrote:
> Even if the signal was handled using signal(2) the message
> would be printed. Fix that by checking whether the signal
> is handled.

Why?

Even if the application handles the signal, the point of this debugging is
to have the kernel report the reason for the fault.

Just because the application has installed a SIGSEGV handler to print some
nice "oops" message, and to cleanly shut down (eg, like Xorg) doesn't mean
we should hide this debugging.  In fact, as such handlers generally get in
the way of getting a decent dump from the application, having the kernel
report this information is even more valuable in this situation.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
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