[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0705180825280.3231@yvahk01.tjqt.qr>
Date: Fri, 18 May 2007 08:28:13 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Rik van Riel <riel@...hat.com>
cc: righiandr@...rs.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
ak@...e.de
Subject: Re: signals logged / [RFC] log out-of-virtual-memory events
On May 17 2007 14:22, Rik van Riel wrote:
> Andrea Righi wrote:
>> I'm looking for a way to keep track of the processes that fail to allocate
>> new
>> virtual memory. What do you think about the following approach (untested)?
>
> Looks like an easy way for users to spam syslogd over and
> over and over again.
>
> At the very least, shouldn't this be dependant on print_fatal_signals?
Speaking of signals, everytime I get a segfault (or force one with a test
program) on x86_64, the kernel prints to dmesg:
fail[22278]: segfault at 0000000000000000 rip 00000000004004b8 rsp
00007ffff7ecda50 error 6
I do not see such on i386, so why for x86_64?
Jan
--
-
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