All of lore.kernel.org
 help / color / mirror / Atom feed
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	"David S. Miller" <davem@davemloft.net>,
	Vivek Goyal <vgoyal@redhat.com>, Jan Willeke <willeke@de.ibm.com>
Subject: Re: mmap for /proc/vmcore broken since 3.12-rc1
Date: Thu, 03 Oct 2013 15:12:47 +0900	[thread overview]
Message-ID: <524D0ADF.2010507@jp.fujitsu.com> (raw)
In-Reply-To: <20131002140356.63706540@holzheu>

(2013/10/02 21:03), Michael Holzheu wrote:
> Hello Alexey,
>
> Looks like the following commit broke mmap for /proc/vmcore:
>
> commit c4fe24485729fc2cbff324c111e67a1cc2f9adea
> Author: Alexey Dobriyan <adobriyan@gmail.com>
> Date:   Tue Aug 20 22:17:24 2013 +0300
>
>      sparc: fix PCI device proc file mmap(2)
>
> Because /proc/vmcore (fs/proc/vmcore.c) does not implement the
> get_unmapped_area() fops function mmap now always returns EIO.
>
> Michael
>

I confirmed the bug on v3.12-rc3. According to makedumpfile's log,
mmap failed on /proc/vmcore.

mem_map (271)
   mem_map    : ffffea001da40000
   pfn_start  : 878000
   pfn_end    : 880000
Kernel can't mmap vmcore, using reads.
STEP [Excluding unnecessary pages] : 1.268799 seconds
STEP [Excluding unnecessary pages] : 1.268756 seconds
STEP [Copying data               ] : 44.847924 seconds
Writing erase info...

I'll post a patch later.

-- 
Thanks.
HATAYAMA, Daisuke


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	Alexey Dobriyan <adobriyan@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Vivek Goyal <vgoyal@redhat.com>, Jan Willeke <willeke@de.ibm.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: mmap for /proc/vmcore broken since 3.12-rc1
Date: Thu, 03 Oct 2013 15:12:47 +0900	[thread overview]
Message-ID: <524D0ADF.2010507@jp.fujitsu.com> (raw)
In-Reply-To: <20131002140356.63706540@holzheu>

(2013/10/02 21:03), Michael Holzheu wrote:
> Hello Alexey,
>
> Looks like the following commit broke mmap for /proc/vmcore:
>
> commit c4fe24485729fc2cbff324c111e67a1cc2f9adea
> Author: Alexey Dobriyan <adobriyan@gmail.com>
> Date:   Tue Aug 20 22:17:24 2013 +0300
>
>      sparc: fix PCI device proc file mmap(2)
>
> Because /proc/vmcore (fs/proc/vmcore.c) does not implement the
> get_unmapped_area() fops function mmap now always returns EIO.
>
> Michael
>

I confirmed the bug on v3.12-rc3. According to makedumpfile's log,
mmap failed on /proc/vmcore.

mem_map (271)
   mem_map    : ffffea001da40000
   pfn_start  : 878000
   pfn_end    : 880000
Kernel can't mmap vmcore, using reads.
STEP [Excluding unnecessary pages] : 1.268799 seconds
STEP [Excluding unnecessary pages] : 1.268756 seconds
STEP [Copying data               ] : 44.847924 seconds
Writing erase info...

I'll post a patch later.

-- 
Thanks.
HATAYAMA, Daisuke


  reply	other threads:[~2013-10-03  6:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 12:03 mmap for /proc/vmcore broken since 3.12-rc1 Michael Holzheu
2013-10-02 12:03 ` Michael Holzheu
2013-10-03  6:12 ` HATAYAMA Daisuke [this message]
2013-10-03  6:12   ` HATAYAMA Daisuke
2013-10-07  2:42   ` HATAYAMA Daisuke
2013-10-07  2:42     ` HATAYAMA Daisuke
2013-10-08 12:49     ` Alexey Dobriyan
2013-10-08 12:49       ` Alexey Dobriyan
2013-10-09 10:14       ` HATAYAMA Daisuke
2013-10-09 10:14         ` HATAYAMA Daisuke
2013-10-12 20:32         ` Alexey Dobriyan
2013-10-12 20:32           ` Alexey Dobriyan
2013-10-14  4:52           ` HATAYAMA Daisuke
2013-10-14  4:52             ` HATAYAMA Daisuke

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=524D0ADF.2010507@jp.fujitsu.com \
    --to=d.hatayama@jp.fujitsu.com \
    --cc=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=willeke@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.