From: Matthias Kaehlcke <mka@chromium.org>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Mark Charlebois <charlebm@gmail.com>,
Behan Webster <behanw@converseincode.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Grant Grundler <grundler@chromium.org>,
Michael Davidson <md@google.com>,
Greg Hackmann <ghackmann@google.com>,
Peter Foley <pefoley2@pefoley.com>,
Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH] fs: compat: Remove warning from COMPATIBLE_IOCTL
Date: Tue, 4 Apr 2017 11:07:20 -0700 [thread overview]
Message-ID: <20170404180720.182336-1-mka@chromium.org> (raw)
From: Mark Charlebois <charlebm@gmail.com>
cmd in COMPATIBLE_IOCTL is always a u32, so cast it so there isn't a
warning about an overflow in XFORM.
From: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Behan Webster <behanw@converseincode.com>
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
---
Resending https://patchwork.kernel.org/patch/4961631/
fs/compat_ioctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 11d087b2b28e..6116d5275a3e 100644
--- a/fs/compat_ioctl.c
+++ b/fs/compat_ioctl.c
@@ -833,7 +833,7 @@ static int compat_ioctl_preallocate(struct file *file,
*/
#define XFORM(i) (((i) ^ ((i) << 27) ^ ((i) << 17)) & 0xffffffff)
-#define COMPATIBLE_IOCTL(cmd) XFORM(cmd),
+#define COMPATIBLE_IOCTL(cmd) XFORM((u32)cmd),
/* ioctl should not be warned about even if it's not implemented.
Valid reasons to use this:
- It is implemented with ->compat_ioctl on some device, but programs
--
2.12.2.715.g7642488e1d-goog
next reply other threads:[~2017-04-04 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 18:07 Matthias Kaehlcke [this message]
2017-04-19 18:14 ` Matthias Kaehlcke
2017-04-19 20:48 ` Arnd Bergmann
2017-04-19 21:37 ` Matthias Kaehlcke
2017-04-20 8:45 ` Arnd Bergmann
2017-04-20 19:56 ` Matthias Kaehlcke
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=20170404180720.182336-1-mka@chromium.org \
--to=mka@chromium.org \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=ghackmann@google.com \
--cc=grundler@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=pefoley2@pefoley.com \
--cc=viro@zeniv.linux.org.uk \
--subject='Re: [PATCH] fs: compat: Remove warning from COMPATIBLE_IOCTL' \
/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
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).