From: "JiSheng Zhang" <jszhang3@mail.ustc.edu.cn>
To: stefanr@s5r6.in-berlin.de
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, krh@redhat.com
Subject: Re: PATCH] firewire: add padding to some struct
Date: Fri, 18 Jul 2008 20:07:55 +0800 [thread overview]
Message-ID: <416382875.30185@ustc.edu.cn> (raw)
Hi,
>From: Stefan Richter <stefanr@s5r6.in-berlin.de>
>Reply-To:
>To: JiSheng Zhang <jszhang3@mail.ustc.edu.cn>
>Subject: Re: PATCH] firewire: add padding to some struct
>Date:Fri, 18 Jul 2008 13:38:25 +0200
>
>JiSheng Zhang wrote:
> > If p is a pointer to struct fw_cdev_event_response), p->data will point to
the
> > padding data rather than the right place, it will cause problem under some
> > platforms. For example, in the function handle_device_event of
libraw1394(ported
> > to juju stack):
> > .....
> > case FW_CDEV_EVENT_RESPONSE:
> > rc = u64_to_ptr(u->response.closure);
> > if (rc->data != NULL)
> > memcpy(rc->data, u->response.data, rc->length);//here it will lost the last
four
> > bytes
> > errcode = juju_to_raw1394_errcode(u->response.rcode);
> > .....
> >
> > Although this problem can be solved by add the offset to the pointer, but the
> > member:__u32 data[0] lost its original meaning.
>
> I don't understand what the problem is. As long as both kernel and
> library use "response.data" or "&response + offsetof(typeof(response),
> data)", they will write and read at the correct location.
>
> There would be a problem if one of the two used "&response +
> sizeof(response)" instead. Does this happen anywhere? If so, then
> these places need to be fixed, not the struct definition.
yes, complete_transaction in fw-cdev.c, it queues the response and data.
how about adding __attribute__((packed)) to the two struct definition? It will not
break abi compatibility.
Thanks in advance,
JiSheng
--- old/include/linux/firewire-cdev.h 2008-07-18 16:34:01.181794046 +0800
+++ new/include/linux/firewire-cdev.h 2008-07-18 19:39:16.389293987 +0800
@@ -93,7 +93,7 @@ struct fw_cdev_event_response {
__u32 rcode;
__u32 length;
__u32 data[0];
-};
+} __attribute__((packed));
/**
* struct fw_cdev_event_request - Sent on incoming request to an address region
@@ -144,7 +144,7 @@ struct fw_cdev_event_iso_interrupt {
__u32 cycle;
__u32 header_length;
__u32 header[0];
-};
+} __attribute__((packed));
/**
* union fw_cdev_event - Convenience union of fw_cdev_event_ types
next reply other threads:[~2008-07-18 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 12:07 JiSheng Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 12:31 JiSheng Zhang
2008-07-18 15:27 ` Mikael Pettersson
[not found] ` <416443505.10974@ustc.edu.cn>
[not found] ` <20080719154115.21334197.jszhang3@mail.ustc.edu.cn>
2008-07-19 7:41 ` JiSheng Zhang
2008-07-19 10:32 ` Stefan Richter
[not found] ` <416463624.22263@ustc.edu.cn>
[not found] ` <20080720142027.772e5d03@debian>
2008-07-20 6:20 ` JiSheng Zhang
2008-07-19 10:09 ` Mikael Pettersson
[not found] ` <416625421.30590@ustc.edu.cn>
[not found] ` <20080721153757.460c6a48@debian>
2008-07-21 7:37 ` JiSheng Zhang
2008-07-18 11:16 JiSheng Zhang
2008-07-18 11:38 ` Stefan Richter
2008-07-18 11:58 ` Stefan Richter
2008-07-18 8:58 JiSheng Zhang
2008-07-18 10:49 ` Stefan Richter
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=416382875.30185@ustc.edu.cn \
--to=jszhang3@mail.ustc.edu.cn \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
Powered by JetHome