[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45FFC168.9010807@hitachi.com>
Date: Tue, 20 Mar 2007 20:11:36 +0900
From: "Kawai, Hidehiro" <hidehiro.kawai.ez@...achi.com>
To: Pavel Machek <pavel@....cz>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
kernel list <linux-kernel@...r.kernel.org>,
Robin Holt <holt@....com>, David Howells <dhowells@...hat.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
sugita <yumiko.sugita.yf@...achi.com>,
Satoshi OSHIMA <soshima@...hat.com>,
Hideo AOKI <haoki@...hat.com>
Subject: Re: [PATCH 4/4] coredump: documentation for proc entry
Hi Pavel,
I'm sorry for my late reply.
Pavel Machek wrote:
> Hi!
>
>>+If you don't want to dump all shared memory segments attached to pid 1234,
>>+write 0 to the process's proc file.
>>+
>>+ $ echo 1 > /proc/1234/coredump_omit_anonymous_shared
>
> Write 0?
Thank you for pointing out.
It seems I mistook when I changed the documents.
`write 1' is correct.
>>+When a new process is created, the process inherits the flag status from its
>>+parent. It is useful to set the flag before the program runs.
>>+For example:
>>+
>>+ $ echo 1 > /proc/self/coredump_omit_anonymous_shared
>>+ $ ./some_program
>>+
>
> Notice that this docs is wrong. You have to retry until kernel stops
> producing spurious errors.
> Pavel
I'll fix the patchset so that kernel doesn't produce the spurious error.
For answers to your another mail, please wait a few days.
I'm still considering the answer partly.
Thanks,
--
Hidehiro Kawai
Hitachi, Ltd., Systems Development Laboratory
-
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