Re: [PATCH 7/7] documentation for /proc/pid/coredump_filter

From: Randy Dunlap
Date: Sun May 27 2007 - 21:13:18 EST


On Fri, 25 May 2007 22:12:55 +0900 Kawai, Hidehiro wrote:

> This patch adds the documentation for /proc/<pid>/coredump_filter.
>
> Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@xxxxxxxxxxx>
> ---
> Documentation/filesystems/proc.txt | 38 +++++++++++++++++++++++++++
> 1 files changed, 38 insertions(+)
>
> Index: linux-2.6.22-rc2-mm1/Documentation/filesystems/proc.txt
> ===================================================================
> --- linux-2.6.22-rc2-mm1.orig/Documentation/filesystems/proc.txt
> +++ linux-2.6.22-rc2-mm1/Documentation/filesystems/proc.txt
> @@ -42,6 +42,7 @@ Table of Contents
> 2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score
> 2.13 /proc/<pid>/oom_score - Display current oom-killer score
> 2.14 /proc/<pid>/io - Display the IO accounting fields
> + 2.15 /proc/<pid>/coredump_filter - Core dump filtering settings

Looks good. Just one typo below.

------------------------------------------------------------------------------
> Preface
> @@ -2135,4 +2136,41 @@ those 64-bit counters, process A could s
> More information about this can be found within the taskstats documentation in
> Documentation/accounting.
>
> +2.15 /proc/<pid>/coredump_filter - Core dump filtering settings
> +---------------------------------------------------------------
> +When a process is dumped, all anonymous memory is written to a core file as
> +long as the size of the core file isn't limited. But sometimes we don't want
> +to dump some memory segments, for example, huge shared memory. Conversely,
> +sometimes we wnat to save file-backed memory segments into a core file, not

want

> +only the individual files.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/