From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
riel@redhat.com,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
hughd@google.com, linux-kernel@vger.kernel.org,
lisa.mitchell@hp.com, Vivek Goyal <vgoyal@redhat.com>,
linux-mm@kvack.org, HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
kosaki.motohiro@jp.fujitsu.com,
Andrew Morton <akpm@linux-foundation.org>,
walken@google.com, Cliff Wickman <cpw@sgi.com>,
jingbai.ma@hp.com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
Date: Fri, 07 Jun 2013 09:11:10 +0800 [thread overview]
Message-ID: <51B1332E.4030907@cn.fujitsu.com> (raw)
In-Reply-To: <CAJGZr0KV9hmdFWQE5Z9kOieHSPhGKLAhsw1Me2RE2ADsbU=b7w@mail.gmail.com>
On 06/04/2013 11:34 PM, Maxim Uvarov wrote:
>
>
>
> 2013/6/3 Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp <mailto:kumagai-atsushi@mxc.nes.nec.co.jp>>
>
> Hello Maxim,
>
> On Thu, 30 May 2013 14:30:01 +0400
> Maxim Uvarov <muvarov@gmail.com <mailto:muvarov@gmail.com>> wrote:
>
> > 2013/5/30 Zhang Yanfei <zhangyanfei@cn.fujitsu.com <mailto:zhangyanfei@cn.fujitsu.com>>
> >
> > > On 05/30/2013 05:14 PM, Maxim Uvarov wrote:
> > > >
> > > >
> > > >
> > > > 2013/5/27 HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com <mailto:d.hatayama@jp.fujitsu.com> <mailto:
> > > d.hatayama@jp.fujitsu.com <mailto:d.hatayama@jp.fujitsu.com>>>
> > > >
> > > > (2013/05/24 18:02), Maxim Uvarov wrote:
> > > >
> > > >
> > > >
> > > >
> > > > 2013/5/24 Andrew Morton <akpm@linux-foundation.org <mailto:akpm@linux-foundation.org> <mailto:
> > > akpm@linux-foundation.org <mailto:akpm@linux-foundation.org>> <mailto:akpm@linux-foundation. <mailto:akpm@linux-foundation.>__org <mailto:
> > > akpm@linux-foundation.org <mailto:akpm@linux-foundation.org>>>>
> > > >
> > > >
> > > > On Thu, 23 May 2013 14:25:48 +0900 HATAYAMA Daisuke <
> > > d.hatayama@jp.fujitsu.com <mailto:d.hatayama@jp.fujitsu.com> <mailto:d.hatayama@jp.fujitsu.com <mailto:d.hatayama@jp.fujitsu.com>> <mailto:
> > > d.hatayama@jp.fujitsu.__com <mailto:d.hatayama@jp.fujitsu.com <mailto:d.hatayama@jp.fujitsu.com>>>> wrote:
> > > >
> > > > > This patch introduces mmap_vmcore().
> > > > >
> > > > > Don't permit writable nor executable mapping even with
> > > mprotect()
> > > > > because this mmap() is aimed at reading crash dump memory.
> > > > > Non-writable mapping is also requirement of
> > > remap_pfn_range() when
> > > > > mapping linear pages on non-consecutive physical pages;
> > > see
> > > > > is_cow_mapping().
> > > > >
> > > > > Set VM_MIXEDMAP flag to remap memory by remap_pfn_range
> > > and by
> > > > > remap_vmalloc_range_pertial at the same time for a single
> > > > > vma. do_munmap() can correctly clean partially remapped
> > > vma with two
> > > > > functions in abnormal case. See zap_pte_range(),
> > > vm_normal_page() and
> > > > > their comments for details.
> > > > >
> > > > > On x86-32 PAE kernels, mmap() supports at most 16TB
> > > memory only. This
> > > > > limitation comes from the fact that the third argument of
> > > > > remap_pfn_range(), pfn, is of 32-bit length on x86-32:
> > > unsigned long.
> > > >
> > > > More reviewing and testing, please.
> > > >
> > > >
> > > > Do you have git pull for both kernel and userland changes? I
> > > would like to do some more testing on my machines.
> > > >
> > > > Maxim.
> > > >
> > > >
> > > > Thanks! That's very helpful.
> > > >
> > > > --
> > > > Thanks.
> > > > HATAYAMA, Daisuke
> > > >
> > > > Any update for this? Where can I checkout all sources?
> > >
> > > This series is now in Andrew Morton's -mm tree.
> > >
> > > Ok, and what about makedumpfile changes? Is it possible to fetch them from
> > somewhere?
>
> You can fetch them from here, "mmap" branch is the change:
>
> git://git.code.sf.net/p/makedumpfile/code <http://git.code.sf.net/p/makedumpfile/code>
>
> And they will be merged into v1.5.4.
>
>
> thank you, got it. But still do not see kernel patches in akpm tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
>
> Should I look at different branch?
Now it is merged into the next tree you list above. See the commit:
author HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> 2013-06-06 00:40:01 (GMT)
committer Stephen Rothwell <sfr@canb.auug.org.au> 2013-06-06 05:50:03 (GMT)
commit 4be2c06c30e4c3994d86e0be24ff1af12d2c71d5 (patch)
tree d7fb8c64c628600e8ba24481927f087fc11c2986
parent 99f80952861807e521ed30c22925f009f543a5ec (diff)
--
Thanks.
Zhang Yanfei
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-06-07 1:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 5:24 [PATCH v8 0/9] kdump, " HATAYAMA Daisuke
2013-05-23 5:25 ` [PATCH v8 1/9] vmcore: clean up read_vmcore() HATAYAMA Daisuke
2013-05-23 5:25 ` [PATCH v8 2/9] vmcore: allocate buffer for ELF headers on page-size alignment HATAYAMA Daisuke
2013-05-23 14:22 ` Vivek Goyal
2013-05-23 21:46 ` Andrew Morton
2013-05-23 5:25 ` [PATCH v8 3/9] vmcore: treat memory chunks referenced by PT_LOAD program header entries in page-size boundary in vmcore_list HATAYAMA Daisuke
2013-05-23 21:49 ` Andrew Morton
2013-05-24 13:12 ` Vivek Goyal
2013-05-27 0:13 ` HATAYAMA Daisuke
2013-05-23 5:25 ` [PATCH v8 4/9] vmalloc: make find_vm_area check in range HATAYAMA Daisuke
2013-05-23 5:25 ` [PATCH v8 5/9] vmalloc: introduce remap_vmalloc_range_partial HATAYAMA Daisuke
2013-05-23 22:00 ` Andrew Morton
2013-05-23 5:25 ` [PATCH v8 6/9] vmcore: allocate ELF note segment in the 2nd kernel vmalloc memory HATAYAMA Daisuke
2013-05-23 14:28 ` Vivek Goyal
2013-05-23 22:17 ` Andrew Morton
2013-05-23 5:25 ` [PATCH v8 7/9] vmcore: Allow user process to remap ELF note segment buffer HATAYAMA Daisuke
2013-05-23 14:32 ` Vivek Goyal
2013-05-23 5:25 ` [PATCH v8 8/9] vmcore: calculate vmcore file size from buffer size and total size of vmcore objects HATAYAMA Daisuke
2013-05-23 14:34 ` Vivek Goyal
2013-05-23 5:25 ` [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore HATAYAMA Daisuke
2013-05-23 22:24 ` Andrew Morton
2013-05-24 9:02 ` Maxim Uvarov
2013-05-27 1:49 ` HATAYAMA Daisuke
2013-05-30 9:14 ` Maxim Uvarov
2013-05-30 9:26 ` Zhang Yanfei
2013-05-30 10:30 ` Maxim Uvarov
2013-06-03 8:43 ` Atsushi Kumagai
2013-06-04 15:34 ` Maxim Uvarov
2013-06-07 1:11 ` Zhang Yanfei [this message]
2013-06-28 16:40 ` Maxim Uvarov
2013-06-30 23:53 ` HATAYAMA Daisuke
2013-07-01 14:34 ` Maxim Uvarov
2013-07-01 19:53 ` Andrew Morton
2013-07-02 7:00 ` Maxim Uvarov
2013-06-06 21:31 ` Arnd Bergmann
2013-06-07 1:01 ` HATAYAMA Daisuke
2013-06-07 18:34 ` Arnd Bergmann
2013-06-08 10:42 ` HATAYAMA Daisuke
2013-05-23 14:35 ` [PATCH v8 0/9] kdump, " Vivek Goyal
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=51B1332E.4030907@cn.fujitsu.com \
--to=zhangyanfei@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=hughd@google.com \
--cc=jingbai.ma@hp.com \
--cc=kexec@lists.infradead.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lisa.mitchell@hp.com \
--cc=muvarov@gmail.com \
--cc=riel@redhat.com \
--cc=vgoyal@redhat.com \
--cc=walken@google.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