From: Joe Thornber <thornber@redhat.com>
To: Joe Thornber <thornber@redhat.com>
Cc: Andi Kleen <ak@muc.de>, Mickael Marchand <marchand@kde.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-mm1
Date: Fri, 12 Mar 2004 09:49:51 +0000 [thread overview]
Message-ID: <20040312094951.GP18345@reti> (raw)
In-Reply-To: <20040312082214.GO18345@reti>
On Fri, Mar 12, 2004 at 08:22:14AM +0000, Joe Thornber wrote:
> name len == 128, uuid_len == 129, so is the uuid_len being rounded up
> to the nearest 64bit boundary on x86-64 and only 32bit boundary on
> x86-32 ? (Sounds likely)
In which case the following ugly patch should fix things. Mickael,
any chance you could test this please ?
- Joe
Fix ioctl breakage on x86-64.
--- diff/include/linux/dm-ioctl.h 2004-03-11 10:20:28.000000000 +0000
+++ source/include/linux/dm-ioctl.h 2004-03-12 09:44:58.000000000 +0000
@@ -187,23 +187,37 @@ enum {
DM_TABLE_STATUS_CMD,
};
+/*
+ * The dm_ioctl struct passed into the ioctl is just the header
+ * on a larger chunk of memory. On x86-64 the dm-ioctl struct
+ * will be padded to an 8 byte boundary so the size will be
+ * different, which would change the ioctl code - yes I really
+ * messed up. This hack forces x86-64 to have the correct ioctl
+ * code.
+ */
+#ifdef CONFIG_X86_64
+typedef char ioctl_struct[308];
+#else
+typedef struct dm_ioctl ioctl_struct;
+#endif
+
#define DM_IOCTL 0xfd
-#define DM_VERSION _IOWR(DM_IOCTL, DM_VERSION_CMD, struct dm_ioctl)
-#define DM_REMOVE_ALL _IOWR(DM_IOCTL, DM_REMOVE_ALL_CMD, struct dm_ioctl)
-#define DM_LIST_DEVICES _IOWR(DM_IOCTL, DM_LIST_DEVICES_CMD, struct dm_ioctl)
-
-#define DM_DEV_CREATE _IOWR(DM_IOCTL, DM_DEV_CREATE_CMD, struct dm_ioctl)
-#define DM_DEV_REMOVE _IOWR(DM_IOCTL, DM_DEV_REMOVE_CMD, struct dm_ioctl)
-#define DM_DEV_RENAME _IOWR(DM_IOCTL, DM_DEV_RENAME_CMD, struct dm_ioctl)
-#define DM_DEV_SUSPEND _IOWR(DM_IOCTL, DM_DEV_SUSPEND_CMD, struct dm_ioctl)
-#define DM_DEV_STATUS _IOWR(DM_IOCTL, DM_DEV_STATUS_CMD, struct dm_ioctl)
-#define DM_DEV_WAIT _IOWR(DM_IOCTL, DM_DEV_WAIT_CMD, struct dm_ioctl)
-
-#define DM_TABLE_LOAD _IOWR(DM_IOCTL, DM_TABLE_LOAD_CMD, struct dm_ioctl)
-#define DM_TABLE_CLEAR _IOWR(DM_IOCTL, DM_TABLE_CLEAR_CMD, struct dm_ioctl)
-#define DM_TABLE_DEPS _IOWR(DM_IOCTL, DM_TABLE_DEPS_CMD, struct dm_ioctl)
-#define DM_TABLE_STATUS _IOWR(DM_IOCTL, DM_TABLE_STATUS_CMD, struct dm_ioctl)
+#define DM_VERSION _IOWR(DM_IOCTL, DM_VERSION_CMD, ioctl_struct)
+#define DM_REMOVE_ALL _IOWR(DM_IOCTL, DM_REMOVE_ALL_CMD, ioctl_struct)
+#define DM_LIST_DEVICES _IOWR(DM_IOCTL, DM_LIST_DEVICES_CMD, ioctl_struct)
+
+#define DM_DEV_CREATE _IOWR(DM_IOCTL, DM_DEV_CREATE_CMD, ioctl_struct)
+#define DM_DEV_REMOVE _IOWR(DM_IOCTL, DM_DEV_REMOVE_CMD, ioctl_struct)
+#define DM_DEV_RENAME _IOWR(DM_IOCTL, DM_DEV_RENAME_CMD, ioctl_struct)
+#define DM_DEV_SUSPEND _IOWR(DM_IOCTL, DM_DEV_SUSPEND_CMD, ioctl_struct)
+#define DM_DEV_STATUS _IOWR(DM_IOCTL, DM_DEV_STATUS_CMD, ioctl_struct)
+#define DM_DEV_WAIT _IOWR(DM_IOCTL, DM_DEV_WAIT_CMD, ioctl_struct)
+
+#define DM_TABLE_LOAD _IOWR(DM_IOCTL, DM_TABLE_LOAD_CMD, ioctl_struct)
+#define DM_TABLE_CLEAR _IOWR(DM_IOCTL, DM_TABLE_CLEAR_CMD, ioctl_struct)
+#define DM_TABLE_DEPS _IOWR(DM_IOCTL, DM_TABLE_DEPS_CMD, ioctl_struct)
+#define DM_TABLE_STATUS _IOWR(DM_IOCTL, DM_TABLE_STATUS_CMD, ioctl_struct)
#define DM_VERSION_MAJOR 4
#define DM_VERSION_MINOR 0
next prev parent reply other threads:[~2004-03-12 9:50 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ysXv-wm-11@gated-at.bofh.it>
[not found] ` <1yuG3-2XI-15@gated-at.bofh.it>
2004-03-17 23:21 ` 2.6.4-mm1 Andi Kleen
2004-03-11 19:28 ` 2.6.4-mm1 Andrew Morton
2004-03-11 20:21 ` 2.6.4-mm1 Andi Kleen
2004-03-11 20:48 ` 2.6.4-mm1 Andrew Morton
2004-03-11 23:37 ` 2.6.4-mm1 Nick Piggin
[not found] ` <1yxuq-6y6-13@gated-at.bofh.it>
2004-03-17 23:25 ` 2.6.4-mm1 Andi Kleen
2004-03-11 13:45 ` 2.6.4-mm1 Mickael Marchand
2004-03-11 14:48 ` 2.6.4-mm1 Andi Kleen
2004-03-11 15:10 ` 2.6.4-mm1 Mickael Marchand
2004-03-11 15:20 ` 2.6.4-mm1 Andi Kleen
2004-03-11 21:43 ` 2.6.4-mm1 Joe Thornber
2004-03-11 21:57 ` 2.6.4-mm1 Joe Thornber
2004-03-11 21:59 ` 2.6.4-mm1 Joel Becker
2004-03-11 22:02 ` 2.6.4-mm1 Joel Becker
2004-03-11 22:11 ` 2.6.4-mm1 Chris Friesen
2004-03-11 23:37 ` 2.6.4-mm1 Andi Kleen
2004-03-12 8:22 ` 2.6.4-mm1 Joe Thornber
2004-03-12 9:49 ` Joe Thornber [this message]
2004-03-12 12:11 ` 2.6.4-mm1 Mickael Marchand
2004-03-12 12:35 ` 2.6.4-mm1 Joe Thornber
2004-03-12 22:48 ` 2.6.4-mm1 Hugo Mills
2004-03-11 21:38 ` 2.6.4-mm1 Joe Thornber
2004-03-11 23:33 ` 2.6.4-mm1 Andi Kleen
[not found] <1yygN-7Ut-65@gated-at.bofh.it>
[not found] ` <1yyqt-83X-23@gated-at.bofh.it>
[not found] ` <1yyqs-83X-17@gated-at.bofh.it>
[not found] ` <1yyJK-8mD-41@gated-at.bofh.it>
[not found] ` <1yzPs-1bI-21@gated-at.bofh.it>
[not found] ` <1yGe9-7Rk-23@gated-at.bofh.it>
[not found] ` <1yI6f-1Bj-3@gated-at.bofh.it>
[not found] ` <1yQdz-1Uf-7@gated-at.bofh.it>
[not found] ` <1yRCI-3lE-19@gated-at.bofh.it>
2004-03-19 5:58 ` 2.6.4-mm1 Andi Kleen
2004-03-12 13:49 ` 2.6.4-mm1 Joe Thornber
2004-03-12 14:03 ` 2.6.4-mm1 Andi Kleen
[not found] ` <1yTO6-5JU-25@gated-at.bofh.it>
[not found] ` <1yU7Z-624-11@gated-at.bofh.it>
2004-03-19 6:00 ` 2.6.4-mm1 Andi Kleen
2004-03-14 16:13 2.6.4-mm1 Nakajima, Jun
2004-03-14 17:04 ` 2.6.4-mm1 Grzegorz Kulewski
-- strict thread matches above, loose matches on Subject: below --
2004-03-14 8:04 2.6.4-mm1 Nakajima, Jun
2004-03-14 8:31 ` 2.6.4-mm1 Andrew Morton
2004-03-12 23:04 2.6.4-mm1 Subodh Shrivastava
2004-03-12 23:55 ` 2.6.4-mm1 Andrew Morton
2004-03-13 13:12 ` 2.6.4-mm1 SUBODH SHRIVASTAVA
[not found] <A6974D8E5F98D511BB910002A50A6647615F4D9F@hdsmsx402.hd.intel.com>
2004-03-12 15:48 ` 2.6.4-mm1 Len Brown
2004-03-12 3:04 2.6.4-mm1 Nakajima, Jun
2004-03-12 3:14 ` 2.6.4-mm1 Andi Kleen
2004-03-12 4:24 ` 2.6.4-mm1 Nick Piggin
2004-03-12 14:14 ` 2.6.4-mm1 Andi Kleen
2004-03-12 14:38 ` 2.6.4-mm1 Nick Piggin
2004-03-11 18:46 2.6.4-mm1 Nakajima, Jun
2004-03-11 7:31 2.6.4-mm1 Andrew Morton
2004-03-11 8:26 ` 2.6.4-mm1 Jens Axboe
2004-03-11 8:30 ` 2.6.4-mm1 Andrew Morton
2004-03-11 9:34 ` 2.6.4-mm1 Matthias Urlichs
2004-03-11 9:17 ` 2.6.4-mm1 Mickael Marchand
2004-03-11 11:06 ` 2.6.4-mm1 Andrew Morton
2004-03-11 11:22 ` 2.6.4-mm1 Anton Blanchard
2004-03-11 12:23 ` 2.6.4-mm1 Mickael Marchand
2004-03-11 13:40 ` 2.6.4-mm1 jlnance
2004-03-11 19:25 ` 2.6.4-mm1 Mike Fedyk
2004-03-11 22:22 ` 2.6.4-mm1 Andrew Morton
2004-03-11 13:49 ` 2.6.4-mm1 Anton Blanchard
2004-03-11 23:29 ` 2.6.4-mm1 Nick Piggin
2004-03-12 2:03 ` 2.6.4-mm1 Nick Piggin
2004-03-12 2:12 ` 2.6.4-mm1 Anton Blanchard
2004-03-12 5:11 ` 2.6.4-mm1 Anton Blanchard
2004-03-11 13:52 ` 2.6.4-mm1 Anton Blanchard
2004-03-11 15:23 ` 2.6.4-mm1 William Lee Irwin III
2004-03-11 15:54 ` 2.6.4-mm1 William Lee Irwin III
2004-03-11 17:06 ` 2.6.4-mm1 Redeeman
2004-03-11 17:53 ` 2.6.4-mm1 Norberto Bensa
2004-03-11 18:09 ` 2.6.4-mm1 Andrew Morton
2004-03-11 18:14 ` 2.6.4-mm1 Redeeman
2004-03-11 18:46 ` 2.6.4-mm1 Andrew Morton
2004-03-11 20:58 ` 2.6.4-mm1 Redeeman
2004-03-11 21:10 ` 2.6.4-mm1 Redeeman
2004-03-11 18:22 ` 2.6.4-mm1 Norberto Bensa
2004-03-11 20:29 ` 2.6.4-mm1 Felipe Alfaro Solana
2004-03-12 1:03 ` 2.6.4-mm1 Neil Brown
2004-03-12 1:22 ` 2.6.4-mm1 Andrew Morton
2004-03-12 5:48 ` 2.6.4-mm1 Neil Brown
2004-03-12 7:50 ` 2.6.4-mm1 Andrew Morton
2004-03-13 10:25 ` 2.6.4-mm1 Neil Brown
2004-03-12 9:04 ` 2.6.4-mm1 Helge Hafting
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=20040312094951.GP18345@reti \
--to=thornber@redhat.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marchand@kde.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