From: Jens Axboe <jens.axboe@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, abhishekrai@google.com,
Linus Torvalds <torvalds@linux-foundation.org>,
davem@davemloft.net
Subject: Re: [PATCH] Fix blktrace setup 32-bit ioctl on 64-bit kernels
Date: Tue, 2 Oct 2007 11:28:56 +0200 [thread overview]
Message-ID: <20071002092856.GG5236@kernel.dk> (raw)
In-Reply-To: <20071002083758.GD5236@kernel.dk>
Hi Arnd,
Updated patch below. I kept the code in compat_ioctl.c, to me it seems
like the cleanest approach. I need the BLKTRACESETUP32 define both in
compat_ioctl.c and blktrace.c if I move it, and I need to hard-core the
struct size or define it in both places. And guard the code in
blktrace.c with an ifdef for CONFIG_COMPAT. Not pretty, imho.
I haven't tested this one yet, but at least it compiles and the sizing
seems right. The u16 padding was an artifact of the
__attribute__((packed)) so that could be removed.
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 5a5b711..54162e5 100644
--- a/fs/compat_ioctl.c
+++ b/fs/compat_ioctl.c
@@ -2052,6 +2052,44 @@ static int raw_ioctl(unsigned fd, unsigned cmd, unsigned long arg)
}
return ret;
}
+
+struct blk_user_trace_setup32 {
+ char name[32];
+ u16 act_mask;
+ u32 buf_size;
+ u32 buf_nr;
+ compat_u64 start_lba;
+ compat_u64 end_lba;
+ u32 pid;
+};
+
+#define BLKTRACESETUP32 _IOWR(0x12,115,struct blk_user_trace_setup32)
+
+static int blktrace32_setup(int fd, unsigned cmd, unsigned long arg)
+{
+ struct blk_user_trace_setup __user *buts = compat_alloc_user_space(sizeof(*buts));
+ struct blk_user_trace_setup32 __user *buts32 = compat_ptr(arg);
+ int err;
+
+ if (copy_in_user(&buts->name, &buts32->name, 32) ||
+ get_user(buts->act_mask, &buts32->act_mask) ||
+ get_user(buts->buf_size, &buts32->buf_size) ||
+ get_user(buts->buf_nr, &buts32->buf_nr) ||
+ get_user(buts->start_lba, &buts32->start_lba) ||
+ get_user(buts->end_lba, &buts32->end_lba) ||
+ get_user(buts->pid, &buts32->pid))
+ return -EFAULT;
+
+ err = sys_ioctl(fd, cmd, (unsigned long) buts);
+ if (err)
+ return err;
+
+ if (copy_to_user(&buts32->name, &buts->name, 32))
+ return -EFAULT;
+
+ return err;
+}
+
#endif /* CONFIG_BLOCK */
struct serial_struct32 {
@@ -2555,7 +2593,7 @@ COMPATIBLE_IOCTL(BLKSECTSET)
COMPATIBLE_IOCTL(BLKSSZGET)
COMPATIBLE_IOCTL(BLKTRACESTART)
COMPATIBLE_IOCTL(BLKTRACESTOP)
-COMPATIBLE_IOCTL(BLKTRACESETUP)
+HANDLE_IOCTL(BLKTRACESETUP32, blktrace32_setup)
COMPATIBLE_IOCTL(BLKTRACETEARDOWN)
ULONG_IOCTL(BLKRASET)
ULONG_IOCTL(BLKFRASET)
--
Jens Axboe
next prev parent reply other threads:[~2007-10-02 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 7:39 [PATCH] Fix blktrace setup 32-bit ioctl on 64-bit kernels Jens Axboe
2007-10-02 7:52 ` David Miller
2007-10-02 8:15 ` Arnd Bergmann
2007-10-02 8:37 ` Jens Axboe
2007-10-02 9:28 ` Jens Axboe [this message]
2007-10-03 9:34 ` Arnd Bergmann
2007-10-03 15:55 ` Arnd Bergmann
2007-10-03 22:48 ` Arnd Bergmann
2007-10-04 18:16 ` Jens Axboe
2007-10-04 18:44 ` Arnd Bergmann
2007-10-05 10:41 ` Jens Axboe
2007-10-05 12:30 ` [PATCH] block: move ioctl conversion to compat_blkdev_ioctl Arnd Bergmann
2007-10-05 12:41 ` Jens Axboe
2007-10-05 12:41 ` Arnd Bergmann
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=20071002092856.GG5236@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=abhishekrai@google.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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