From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jdike@addtoit.com, tony.luck@intel.com, mhiramat@redhat.com
Subject: Re: [RFC, PATCH 1/4] cleanup elf_core_dump(): remove ELF_CORE_EXTRA_* macro
Date: Tue, 15 Dec 2009 15:58:58 +0800 [thread overview]
Message-ID: <2375c9f90912142358j24cc1bf8p2f696f56537befc6@mail.gmail.com> (raw)
In-Reply-To: <20091215.114118.226800461.d.hatayama@jp.fujitsu.com>
On Tue, Dec 15, 2009 at 10:41 AM, Daisuke HATAYAMA
<d.hatayama@jp.fujitsu.com> wrote:
> elf_core_dump() uses #ifdef and the corresponding macro for hiding
> _multiline_ logics in functions. This patch removes #ifdef and
> replaces ELF_CORE_EXTRA_* by corresponding functions. For
> architectures not implemeonting ELF_CORE_EXTRA_*, we use weak
> functions in order to reduce a range of modification.
>
> This cleanup is for my next patches, but I think this cleanup itself
> is worth doing regardless of my firnal purpose.
>
> Signed-off-by: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Good patch! I like it!
Just one problem below.
> --- /dev/null
> +++ b/arch/um/sys-i386/elfcore.c
> @@ -0,0 +1,78 @@
> +#include <linux/elf.h>
> +#include <linux/fs.h>
> +#include <linux/mm.h>
> +
> +#include <asm/elf.h>
> +
> +static int dump_write(struct file *file, const void *addr, int nr)
> +{
> + return file->f_op->write(file, addr, nr, &file->f_pos) == nr;
> +}
We already have the same dump_write() in fs/binfmt_elf.c, can't we
reuse it? e.g. moving it to a header and make it staic inline.
Thanks!
next prev parent reply other threads:[~2009-12-15 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 2:41 Daisuke HATAYAMA
2009-12-15 7:58 ` Américo Wang [this message]
2009-12-16 2:23 ` Daisuke HATAYAMA
2009-12-15 14:05 ` Andi Kleen
2009-12-15 15:14 ` Masami Hiramatsu
2009-12-16 4:07 ` Daisuke HATAYAMA
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=2375c9f90912142358j24cc1bf8p2f696f56537befc6@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®