From: agordeev@linux.ibm.com
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Alexander Gordeev <agordeev@linux.ibm.com>
Subject: [PATCH 0/2] mm/mmap: check mapping limits more strictly
Date: Mon, 23 Mar 2020 14:29:27 +0100 [thread overview]
Message-ID: <cover.1584958099.git.agordeev@linux.ibm.com> (raw)
From: Alexander Gordeev <agordeev@linux.ibm.com>
This series is against v5.6-rc7
Alexander Gordeev (2):
mm/mmap.c: add more sanity checks to get_unmapped_area()
mm/mmap.c: do not allow mappings outside of allowed limits
mm/mmap.c | 29 +++++++++++++++++------------
1 file changed, 17 insertions(+), 12 deletions(-)
--
2.23.0
next reply other threads:[~2020-03-23 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:29 agordeev [this message]
2020-03-23 13:29 ` [PATCH 1/2] mm/mmap.c: add more sanity checks to get_unmapped_area() agordeev
2020-03-23 13:29 ` [PATCH 2/2] mm/mmap.c: do not allow mappings outside of allowed limits agordeev
2020-04-21 2:59 ` Andrew Morton
2020-04-21 5:29 ` Alexander Gordeev
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=cover.1584958099.git.agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).