From: Willy Tarreau <w@1wt.eu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: marcelo@kvack.org, jolivares@gigablast.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-2.4] allow core files bigger than 2GB
Date: Sun, 18 Jun 2006 08:48:32 +0200 [thread overview]
Message-ID: <20060618064832.GA31066@1wt.eu> (raw)
In-Reply-To: <1150610993.3117.2.camel@laptopd505.fenrus.org>
On Sun, Jun 18, 2006 at 08:09:53AM +0200, Arjan van de Ven wrote:
> On Sat, 2006-06-17 at 23:45 +0200, Willy Tarreau wrote:
> > Marcelo,
> >
> > I think I have not sent you this one. It looks valid to me.
> > I can queue it in -upstream if you prefer to pull everything
> > at once.
>
>
> Hi,
>
> This is a rather complex issue, to the point that your patch is not
> sufficient actually. While it will create a core file, it's not really a
> good one, and there are some nasty other issues with it (esp on 64 bit
> systems). The enterprise distro kernels have a more complete patch for
> this (I'm pretty sure both RH and SUSE have fundamentally the same patch
> for this), if you really want this functionality I suggest getting the
> patch from either of those distros to get the full thing (there's some
> security angle to this even iirc).
Thanks for notifying us about this Arjan. I've checked in RHEL patches
and found that this is done in 2.4.21-binfmt-elf.patch with a detailed
explanation. The patch is rather large, not to say invasive. I believe
it serves other purposes but it seems to me that it will still be
invasive enough not to be merged into 2.4 mainline right now.
> Greetings,
> Arjan van de Ven
Regards,
Willy
prev parent reply other threads:[~2006-06-18 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 21:45 [PATCH-2.4] allow core files bigger than 2GB Willy Tarreau
2006-06-18 6:09 ` Arjan van de Ven
2006-06-18 6:48 ` Willy Tarreau [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=20060618064832.GA31066@1wt.eu \
--to=w@1wt.eu \
--cc=arjan@infradead.org \
--cc=jolivares@gigablast.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.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