public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: "Kawai, Hidehiro" <hidehiro.kawai.ez@hitachi.com>,
	linux-kernel@vger.kernel.org, gregkh@suse.de,
	james.bottomley@steeleye.com, Satoshi OSHIMA <soshima@redhat.com>,
	"Hideo AOKI@redhat" <haoki@redhat.com>,
	sugita <yumiko.sugita.yf@hitachi.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] binfmt_elf: core dump masking support
Date: Wed, 20 Dec 2006 15:40:56 +0000	[thread overview]
Message-ID: <20061220154056.GA4261@ucw.cz> (raw)
In-Reply-To: <20061213132358.ddcaaaf4.akpm@osdl.org>

Hi!

> > When a new process is created, the process inherits the coremask
> > setting from its parent. It is useful to set the coremask before
> > the program runs. For example:
> > 
> >   $ echo 1 > /proc/self/coremask
> >   $ ./some_program
> 
> The requirement makes sense, I guess.
> 
> Regarding the implementation: if we add
> 
> 	unsigned char coredump_omit_anon_memory:1;
> 
> into the mm_struct right next to `dumpable' then we avoid increasing the
> size of the mm_struct, and the code gets neater.
> 
> 
> Modification of this field is racy, and we don't have a suitable lock in
> mm_struct to fix that.  I don't think we care about that a lot, but it'd be
> best to find some way of fixing it.
> 
> 
> Really we should convert binfmt_aout.c and any other coredumpers too.
> 
> 
> Does this feature have any security implications?  For example, there might
> be system administration programs which force a coredump on a "bad"
> process, and leave the core somewhere for the administrator to look at. 
> With this change, we permit hiding of that corefile's anon memory from the
> administrator.  OK, lame example, but perhaps there are better ones.

User can already ulimit -c 0 on himself, perhaps we want to use same
interface here? ulimit -cmask=(bitmask)?
							Pavel
-- 
Thanks for all the (sleeping) penguins.

  parent reply	other threads:[~2006-12-20 15:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13  7:14 [PATCH] binfmt_elf: core dump masking support Kawai, Hidehiro
2006-12-13 21:23 ` Andrew Morton
2006-12-18  8:08   ` Kawai, Hidehiro
2006-12-20 15:40   ` Pavel Machek [this message]
2007-01-09  1:07     ` Kawai, Hidehiro
2007-01-09 14:39       ` Pavel Machek
2007-01-12  8:49         ` Kawai, Hidehiro
2007-01-14 20:01           ` Pavel Machek
2007-01-19  0:40             ` Kawai, Hidehiro
2007-01-19  0:45               ` Pavel Machek
2007-01-22  2:29                 ` Kawai, Hidehiro
2007-01-22 10:06                   ` Pavel Machek
2007-01-23  4:42                     ` Kawai, Hidehiro
2007-01-23  9:08                       ` Pavel Machek
2007-01-23 12:17                         ` Kawai, Hidehiro

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=20061220154056.GA4261@ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=haoki@redhat.com \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=soshima@redhat.com \
    --cc=yumiko.sugita.yf@hitachi.com \
    /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