linux-kernel - Re: i386-show-unhandled-signals-v3

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, 25 Jul 2007 21:15:28 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	masouds@...gle.com (Masoud Asgharifard Sharbiani)
Cc:	Andi Kleen <ak@...e.de>, Kirill Korotaev <dev@...nvz.org>,
	linux-kernel@...r.kernel.org
Subject: Re: i386-show-unhandled-signals-v3

On Wed, 25 Jul 2007 16:40:06 -0700 masouds@...gle.com (Masoud Asgharifard Sharbiani) wrote:

> This patch makes the i386 behave the same way that x86_64 does when a
> segfault happens. A line gets printed to the kernel log so that tools
> that need to check for failures can behave more uniformly between
> different kernels. Like x86_64, it can be disabled by setting
> debug.show_unhandled_signals sysctl variable to 0 (or by doing
> echo 0 > /proc/sys/debug/show_unhandled_signals)

Is that still correct?  Methinks /proc/sys/debug/exception-trace.

<Looks sadly at Documentation/filesystems/proc.txt>

<Argh, your patch was reversed. Applied with patch -R.>

> Also, all of the lines being printed are now using printk_ratelimit()
> to deny the ability of DoS from a local user with a program like the
> following:
> main()
> {
>        while (1)
>                if (!fork()) *(int *)0 = 0;
> }

yup.
-
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/