linux-kernel - Re: [PATCH 0/4] coredump: core dump masking support v2

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:	Fri, 26 Jan 2007 09:29:07 -0600
From:	Robin Holt <holt@....com>
To:	"Kawai, Hidehiro" <hidehiro.kawai.ez@...achi.com>
Cc:	akpm@...l.org, pavel@...e.cz, linux-kernel@...r.kernel.org,
	dhowells@...hat.com, alan@...rguk.ukuu.org.uk
Subject: Re: [PATCH 0/4] coredump: core dump masking support v2

On Fri, Jan 26, 2007 at 11:05:07PM +0900, Kawai, Hidehiro wrote:
> You can specify memory segment types you don't want to dump via
> /proc/<pid>/core_flags file, which is provided per process.
> This file represents a set of flags, but currently, only bit 0 is
> available. If bit 0 is set, the kernel core dump routine doesn't
> dump anonymous shared memory segments, which includes IPC shared
> memory and some of mmap(2)'ed memory.

Can you make this a little more transparent?  Having a magic bitmask does
not seem like the best way to do stuff.  Could you maybe make a core_flags
directory with a seperate file for each flag.  It could still map to a
single field in the mm, but be broken out for the proc filesystem.

I can certainly see the value of this for our customers.  We have some
customers that run jobs in the 1-2TB range.  Most of those customers
have always had coredumps disabled and just rely upon being able to
rerun the application and have MPI drop them into a debugger.

Thanks,
Robin
-
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/