From: Eric Dumazet <dada1@cosmosbay.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, Andi Kleen <ak@suse.de>,
Rik van Riel <riel@redhat.com>,
righiandr@users.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: signals logged / [RFC] log out-of-virtual-memory events
Date: Sun, 20 May 2007 05:55:22 +0200 [thread overview]
Message-ID: <464FC6AA.2060805@cosmosbay.com> (raw)
In-Reply-To: <20070520001418.GJ14578@vanheusden.com>
Folkert van Heusden a ecrit :
>>>> I do not see such on i386, so why for x86_64?
>>> So that you know that one of your programs crashed. That's a feature.
>> This feature could be handy for i386 too.
>
> Since 2.6.18.2 I use this patch. With 2.6.21.1 it still applies altough
> with a small offsets. Works like a charm.
>
>
> Signed-off by: Folkert van Heusden <folkert@vanheusden.com>
>
> --- linux-2.6.18.2/kernel/signal.c 2006-11-04 02:33:58.000000000 +0100
> +++ linux-2.6.18.2.new/kernel/signal.c 2006-11-17 15:59:13.000000000 +0100
> @@ -706,6 +706,15 @@
> struct sigqueue * q = NULL;
> int ret = 0;
>
> + if (sig == SIGQUIT || sig == SIGILL || sig == SIGTRAP ||
> + sig == SIGABRT || sig == SIGBUS || sig == SIGFPE ||
> + sig == SIGSEGV || sig == SIGXCPU || sig == SIGXFSZ ||
> + sig == SIGSYS || sig == SIGSTKFLT)
> + {
> + printk(KERN_WARNING "Sig %d send to %d owned by %d.%d (%s)\n",
> + sig, t -> pid, t -> uid, t -> gid, t -> comm);
> + }
> +
Please check line 219 of Documentation/CodingStyle, Section 3.1: Spaces
and no space around the '.' and "->" structure member operators.
Thank you
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-05-20 3:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 16:24 Andrea Righi
2007-05-17 18:22 ` Rik van Riel
2007-05-18 6:28 ` signals logged / " Jan Engelhardt
2007-05-18 11:47 ` Andi Kleen
2007-05-19 7:46 ` Jan Engelhardt
2007-05-19 9:35 ` Andrea Righi
2007-05-19 10:06 ` Jan Engelhardt
2007-05-19 10:16 ` Andrea Righi
2007-05-20 0:14 ` Folkert van Heusden
2007-05-20 3:55 ` Eric Dumazet [this message]
2007-05-20 11:21 ` Folkert van Heusden
2007-05-20 16:08 ` Stephen Hemminger
2007-05-20 16:12 ` Folkert van Heusden
2007-05-20 20:38 ` Jan Engelhardt
2007-05-20 20:55 ` Folkert van Heusden
2007-05-20 21:14 ` Andi Kleen
2007-05-20 21:20 ` Folkert van Heusden
2007-05-20 21:23 ` Folkert van Heusden
2007-05-20 22:24 ` Andi Kleen
2007-05-20 22:22 ` Jeff Dike
2007-05-21 10:45 ` Andrea Righi
2007-05-21 11:04 ` Folkert van Heusden
2007-05-21 12:30 ` Jan Engelhardt
2007-05-21 12:47 ` Folkert van Heusden
2007-05-21 13:58 ` Andrea Righi
2007-05-21 18:59 ` Folkert van Heusden
2007-05-21 22:15 ` Andrea Righi
2007-05-23 18:00 ` Satyam Sharma
2007-05-23 18:45 ` Folkert van Heusden
2007-06-10 19:53 ` Folkert van Heusden
2007-06-10 20:06 ` Jiri Kosina
2007-06-10 20:37 ` Jan Engelhardt
2007-05-18 7:50 ` Andrea Righi
2007-05-18 9:16 ` Robin Holt
2007-05-18 15:55 ` Andrea Righi
2007-05-18 16:05 ` Andrea Righi
2007-05-20 0:15 ` Folkert van Heusden
2007-05-20 22:21 signals logged / " Mikael Pettersson
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=464FC6AA.2060805@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=ak@suse.de \
--cc=folkert@vanheusden.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=righiandr@users.sourceforge.net \
/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