From: Arjan van de Ven <arjan@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
mingo@elte.hu, akpm@linux-foundation.org
Subject: [PATCH 8/9] Add explicit bound checks in mm/migrate.c
Date: Sat, 26 Sep 2009 20:54:06 +0200 [thread overview]
Message-ID: <20090926205406.30d55b08@infradead.org> (raw)
In-Reply-To: <20090926204951.424e567e@infradead.org>
From: Arjan van de Ven <arjan@linux.intel.com>
Subject: [PATCH 8/9] Add explicit bound checks in mm/migrate.c
CC: akpm@linux-foundation.org
The memory migration code has some curious copy_from_user bounds,
that are likely ok, but are not immediately obvious to me or to GCC.
This patch adds a simple explicit bound check; this allows GCC
and me to be more assured that the copy_from_user will never overwrite
its destination buffer.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
diff --git a/mm/migrate.c b/mm/migrate.c
index 1a4bf48..5b9ebc5 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -1044,11 +1044,15 @@ static int do_pages_stat(struct mm_struct *mm, unsigned long nr_pages,
int err;
for (i = 0; i < nr_pages; i += chunk_nr) {
+ unsigned int copy;
if (chunk_nr + i > nr_pages)
chunk_nr = nr_pages - i;
- err = copy_from_user(chunk_pages, &pages[i],
- chunk_nr * sizeof(*chunk_pages));
+ copy = chunk_nr * sizeof(*chunk_pages);
+ if (copy > DO_PAGES_STAT_CHUNK_NR)
+ return -EFAULT;
+
+ err = copy_from_user(chunk_pages, &pages[i], copy);
if (err) {
err = -EFAULT;
goto out;
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-26 18:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 18:49 [PATCH 0/9] Series to make copy_from_user to a stack slot provable right Arjan van de Ven
2009-09-26 18:50 ` [PATCH 1/9] Fix bound checks for copy_from_user in the acpi /proc code Arjan van de Ven
2009-09-26 18:50 ` [PATCH 2/9] Simplify bound checks in nvram for copy_from_user Arjan van de Ven
2009-09-26 18:51 ` [PATCH 3/9] Add bound checks in wext " Arjan van de Ven
2009-09-26 18:51 ` [PATCH 4/9] Simplify bound checks in the MTRR code Arjan van de Ven
2009-10-02 18:36 ` [tip:x86/urgent] x86: " tip-bot for Arjan van de Ven
2009-09-26 18:52 ` [PATCH 5/9] Add bound checks in acpi/video for copy_from_user Arjan van de Ven
2009-09-26 18:52 ` [PATCH 6/9] Simplify bound checks in cifs " Arjan van de Ven
2009-09-26 18:53 ` [PATCH 7/9] Simplify bound checks in capabilities " Arjan van de Ven
2009-09-29 5:55 ` Dave Airlie
2009-09-29 9:24 ` Arjan van de Ven
2009-10-01 22:34 ` James Morris
2009-09-26 18:54 ` Arjan van de Ven [this message]
2009-09-30 22:20 ` [PATCH 8/9] Add explicit bound checks in mm/migrate.c Andrew Morton
2009-10-01 5:54 ` KOSAKI Motohiro
[not found] ` <tip-b925585039cf39275c2e0e57512e5df27fa73aad@git.kernel.org>
2009-12-13 23:38 ` [tip:x86/urgent] mm: Adjust do_pages_stat() so gcc can see copy_from_user() is safe KOSAKI Motohiro
2009-09-26 18:54 ` [PATCH 9/9] Add explicit bound checks in net/socket.c Arjan van de Ven
2009-09-26 19:01 ` Cyrill Gorcunov
2009-09-26 19:05 ` Arjan van de Ven
2009-09-26 19:23 ` Arjan van de Ven
2009-09-26 19:35 ` Cyrill Gorcunov
2009-09-28 19:57 ` David Miller
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=20090926205406.30d55b08@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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