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, sfrench@samba.org
Subject: [PATCH 6/9] Simplify bound checks in cifs for copy_from_user
Date: Sat, 26 Sep 2009 20:52:55 +0200 [thread overview]
Message-ID: <20090926205255.1d9de6c7@infradead.org> (raw)
In-Reply-To: <20090926204951.424e567e@infradead.org>
From: Arjan van de Ven <arjan@linux.intel.com>
Subject: [PATCH 6/9] Simplify bound checks in cifs for copy_from_user
CC: Steve French <sfrench@samba.org>
The CIFS code unfortunately hits a missed optimization in gcc
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41477)
where gcc can't prove to itself that count will not be larger than 11.
This patch simplifies the expression so that GCC does realize this,
giving slightly better code soon when copy_from_user() grows some checks.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
diff --git a/fs/cifs/cifs_debug.c b/fs/cifs/cifs_debug.c
index 42cec2a..94b86da 100644
--- a/fs/cifs/cifs_debug.c
+++ b/fs/cifs/cifs_debug.c
@@ -732,11 +732,13 @@ static ssize_t cifs_security_flags_proc_write(struct file *file,
char flags_string[12];
char c;
- if ((count < 1) || (count > 11))
- return -EINVAL;
-
memset(flags_string, 0, 12);
+ if (count < 1)
+ return -EINVAL;
+ if (count > 11)
+ return -EINVAL;
+
if (copy_from_user(flags_string, buffer, count))
return -EFAULT;
--
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 ` Arjan van de Ven [this message]
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 ` [PATCH 8/9] Add explicit bound checks in mm/migrate.c Arjan van de Ven
2009-09-30 22:20 ` 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=20090926205255.1d9de6c7@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfrench@samba.org \
--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