From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: akpm@linux-foundation.org
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, ebiederm@xmission.com,
holzheu@linux.vnet.ibm.com, adobriyan@gmail.com,
vgoyal@redhat.com
Subject: [PATCH 0/3] procfs, vmcore: fix regression of mmap on /proc/vmcore since v3.12-rc1
Date: Mon, 14 Oct 2013 18:36:06 +0900 [thread overview]
Message-ID: <20131014093606.9801.11175.stgit@localhost6.localdomain6> (raw)
This patch set fixes regression of mmap on /proc/vmcore since
v3.12-rc1. The primary one is the 2nd patch. The 1st patch is another
bug I found during investiation and it affects mmap on /proc/vmcore
even if only 2nd patch is applied, so fix it together in this patch
set. The last patch is just for cleaning up of target function in both
1st and 2nd patches.
---
HATAYAMA Daisuke (3):
procfs: fix unintended truncation of returned mapped address
procfs: Call default get_unmapped_area on MMU-present architectures
procfs: clean up proc_reg_get_unmapped_area for 80-column limit
fs/proc/inode.c | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
--
Thanks.
HATAYAMA, Daisuke
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2013-10-14 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 9:36 HATAYAMA Daisuke [this message]
2013-10-14 9:36 ` [PATCH 1/3] procfs: fix unintended truncation of returned mapped address HATAYAMA Daisuke
2013-10-14 9:36 ` [PATCH 2/3] procfs: Call default get_unmapped_area on MMU-present architectures HATAYAMA Daisuke
2013-10-14 9:36 ` [PATCH 3/3] procfs: clean up proc_reg_get_unmapped_area for 80-column limit HATAYAMA Daisuke
2013-10-15 11:30 ` [PATCH 0/3] procfs, vmcore: fix regression of mmap on /proc/vmcore since v3.12-rc1 Michael Holzheu
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=20131014093606.9801.11175.stgit@localhost6.localdomain6 \
--to=d.hatayama@jp.fujitsu.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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