[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100107162928.1d6eba76.akpm@linux-foundation.org>
Date: Thu, 7 Jan 2010 16:29:28 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Daisuke HATAYAMA <d.hatayama@...fujitsu.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
mhiramat@...hat.com, xiyou.wangcong@...il.com, andi@...stfloor.org,
jdike@...toit.com, tony.luck@...el.com
Subject: Re: [RESEND][mmotm][PATCH v2, 0/5] elf coredump: Add extended
numbering support
On Mon, 04 Jan 2010 10:06:07 +0900 (JST)
Daisuke HATAYAMA <d.hatayama@...fujitsu.com> wrote:
> The current ELF dumper can produce broken corefiles if program headers
> exceed 65535. In particular, the program in 64-bit environment often
> demands more than 65535 mmaps. If you google max_map_count, then you
> can find many users facing this problem.
>
> Solaris has already dealt with this issue, and other OSes have also
> adopted the same method as in Solaris. Currently, Sun's document and
> AMD 64 ABI include the description for the extension, where they call
> the extension Extended Numbering. See Reference for further information.
>
> I believe that linux kernel should adopt the same way as they did, so
> I've written this patch.
>
> I am also preparing for patches of GDB and binutils.
That's a beautifully presented patchset. Thanks for doing all that
work - it helps.
UML maintenance appears to have ceased in recent times, so if we wish
to have these changes runtime tested (we should) then I think it would
be best if you could find someone to do that please.
And no akpm code-review would be complete without: dump_seek() is
waaaay to large to be inlined. Is there some common .c file to where
we could move it?
--
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/
Powered by blists - more mailing lists