From: Roland McGrath <roland@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 2.6.28-rc2] CORE_DUMP_DEFAULT_ELF_HEADERS depends on ELF_CORE
Date: Tue, 6 Jan 2009 16:44:47 -0800 (PST) [thread overview]
Message-ID: <20090107004447.3FD19FC305@magilla.sf.frob.com> (raw)
In-Reply-To: David Brownell's message of Tuesday, 6 January 2009 12:37:00 -0800 <200901061237.01020.david-b@pacbell.net>
Acked-by: Roland McGrath <roland@redhat.com>
> On Thursday 30 October 2008, David Brownell wrote:
> > From: David Brownell <dbrownell@users.sourceforge.net>
> >
> > Kernels that don't support ELF coredumps at all surely can't
> > be supporting new partial-segment flavored ELF coredumps ...
> > don't make folk answer Kconfig questions about that flavor.
>
> PING?
>
> >
> > Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> > Cc: Roland McGrath <roland@redhat.com>
> > ---
> > fs/Kconfig.binfmt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- a/fs/Kconfig.binfmt
> > +++ b/fs/Kconfig.binfmt
> > @@ -43,7 +43,7 @@ config BINFMT_ELF_FDPIC
> > config CORE_DUMP_DEFAULT_ELF_HEADERS
> > bool "Write ELF core dumps with partial segments"
> > default n
> > - depends on BINFMT_ELF
> > + depends on BINFMT_ELF && ELF_CORE
> > help
> > ELF core dump files describe each memory mapping of the crashed
> > process, and can contain or omit the memory contents of each one.
> >
>
>
prev parent reply other threads:[~2009-01-07 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 22:59 [patch 2.6.28-rc2] CORE_DUMP_DEFAULT_ELF_HEADERS depends on ELF_CORE David Brownell
2009-01-06 20:37 ` David Brownell
2009-01-07 0:44 ` Roland McGrath [this message]
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=20090107004447.3FD19FC305@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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