From: Masami Hiramatsu <mhiramat@redhat.com>
To: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1
Date: Sun, 20 Dec 2009 21:14:12 -0500 [thread overview]
Message-ID: <4B2ED9F4.5050109@redhat.com> (raw)
In-Reply-To: <20091221.110431.189715673.d.hatayama@jp.fujitsu.com>
Daisuke HATAYAMA wrote:
> The commit f6151dfea21496d43dbaba32cfcd9c9f404769bc causes build
> break, so this patch fixes it together with the correction for printk
> format.
>
> Thanks.
>
> Signed-off-by: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Thanks for fixing that! looks good to me.
Reviewed-by: Masami Hiramatsu <mhiramat@redhat.com>
> ---
> fs/binfmt_elf_fdpic.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c
> index c25256a..b0f2732 100644
> --- a/fs/binfmt_elf_fdpic.c
> +++ b/fs/binfmt_elf_fdpic.c
> @@ -1798,11 +1798,11 @@ static int elf_fdpic_core_dump(struct coredump_params *cprm)
> ELF_CORE_WRITE_EXTRA_DATA;
> #endif
>
> - if (file->f_pos != offset) {
> + if (cprm->file->f_pos != offset) {
> /* Sanity check */
> printk(KERN_WARNING
> - "elf_core_dump: file->f_pos (%lld) != offset (%lld)\n",
> - file->f_pos, offset);
> + "elf_fdpic_core_dump: cprm->file->f_pos (%lld) != offset (%lld)\n",
> + cprm->file->f_pos, offset);
> }
>
> end_coredump:
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-12-21 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 2:04 [PATCH] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1 Daisuke HATAYAMA
2009-12-21 2:14 ` Masami Hiramatsu [this message]
2009-12-21 3:07 ` Paul Mundt
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=4B2ED9F4.5050109@redhat.com \
--to=mhiramat@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--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