* [PATCH] Drivers: hv: util: make struct hv_do_fcopy match Hyper-V host messages
@ 2014-10-24 10:20 Vitaly Kuznetsov
2014-10-24 15:14 ` KY Srinivasan
0 siblings, 1 reply; 2+ messages in thread
From: Vitaly Kuznetsov @ 2014-10-24 10:20 UTC (permalink / raw)
To: linux-api-u79uwXL29TY76Z2rM5mHXA, K. Y. Srinivasan
Cc: Greg Kroah-Hartman, Jason Wang,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
An attempt to fix fcopy on i586 (bc5a5b0 Drivers: hv: util: Properly pack the data
for file copy functionality) led to a regression on x86_64 (and actually didn't fix
i586 breakage). Fcopy messages from Hyper-V host come in the following format:
struct do_fcopy_hdr | 36 bytes
0000 | 4 bytes
offset | 8 bytes
size | 4 bytes
data | 6144 bytes
On x86_64 struct hv_do_fcopy matched this format without ' __attribute__((packed))'
and on i586 adding ' __attribute__((packed))' to it doesn't change anything. Keep
the structure packed and add padding to match re reality. Tested both i586 and x86_64
on Hyper-V Server 2012 R2.
Signed-off-by: Vitaly Kuznetsov <vkuznets-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
---
include/uapi/linux/hyperv.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/hyperv.h b/include/uapi/linux/hyperv.h
index 0a8e6ba..bb1cb73 100644
--- a/include/uapi/linux/hyperv.h
+++ b/include/uapi/linux/hyperv.h
@@ -134,6 +134,7 @@ struct hv_start_fcopy {
struct hv_do_fcopy {
struct hv_fcopy_hdr hdr;
+ __u32 pad;
__u64 offset;
__u32 size;
__u8 data[DATA_FRAGMENT];
--
1.9.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* RE: [PATCH] Drivers: hv: util: make struct hv_do_fcopy match Hyper-V host messages
2014-10-24 10:20 [PATCH] Drivers: hv: util: make struct hv_do_fcopy match Hyper-V host messages Vitaly Kuznetsov
@ 2014-10-24 15:14 ` KY Srinivasan
0 siblings, 0 replies; 2+ messages in thread
From: KY Srinivasan @ 2014-10-24 15:14 UTC (permalink / raw)
To: Vitaly Kuznetsov, linux-api@vger.kernel.org
Cc: Greg Kroah-Hartman, Jason Wang, linux-kernel@vger.kernel.org
> -----Original Message-----
> From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
> Sent: Friday, October 24, 2014 3:20 AM
> To: linux-api@vger.kernel.org; KY Srinivasan
> Cc: Greg Kroah-Hartman; Jason Wang; linux-kernel@vger.kernel.org
> Subject: [PATCH] Drivers: hv: util: make struct hv_do_fcopy match Hyper-V
> host messages
>
> An attempt to fix fcopy on i586 (bc5a5b0 Drivers: hv: util: Properly pack the
> data for file copy functionality) led to a regression on x86_64 (and actually
> didn't fix
> i586 breakage). Fcopy messages from Hyper-V host come in the following
> format:
>
> struct do_fcopy_hdr | 36 bytes
> 0000 | 4 bytes
> offset | 8 bytes
> size | 4 bytes
> data | 6144 bytes
>
> On x86_64 struct hv_do_fcopy matched this format without '
> __attribute__((packed))'
> and on i586 adding ' __attribute__((packed))' to it doesn't change anything.
> Keep the structure packed and add padding to match re reality. Tested both
> i586 and x86_64 on Hyper-V Server 2012 R2.
Thanks Vitaly.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
Cc: <stable@vger.kernel.org>
> ---
> include/uapi/linux/hyperv.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/hyperv.h b/include/uapi/linux/hyperv.h index
> 0a8e6ba..bb1cb73 100644
> --- a/include/uapi/linux/hyperv.h
> +++ b/include/uapi/linux/hyperv.h
> @@ -134,6 +134,7 @@ struct hv_start_fcopy {
>
> struct hv_do_fcopy {
> struct hv_fcopy_hdr hdr;
> + __u32 pad;
> __u64 offset;
> __u32 size;
> __u8 data[DATA_FRAGMENT];
> --
> 1.9.3
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-10-24 15:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-24 10:20 [PATCH] Drivers: hv: util: make struct hv_do_fcopy match Hyper-V host messages Vitaly Kuznetsov
2014-10-24 15:14 ` KY Srinivasan
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).