All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Julien Grall <julien.grall@linaro.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH RFC] xen-block: correctly define structures in public headers
Date: Tue, 3 Dec 2013 12:14:06 +0100	[thread overview]
Message-ID: <529DBCFE.9030004@citrix.com> (raw)
In-Reply-To: <1386068729.13256.8.camel@kazak.uk.xensource.com>

On 03/12/13 12:05, Ian Campbell wrote:
> On Tue, 2013-12-03 at 11:57 +0100, Roger Pau Monne wrote:
>> Using __packed__ on the public interface is not correct, this
>> structures should be compiled using the native ABI, and __packed__
>> should only be used in the backend counterpart of those structures
>> (which needs to handle different ABIs).
>>
>> This was even worse in the ARM case, where the Linux kernel was
>> incorrectly using the X86_32 protocol ABI. This patch fixes it, but
>> also breaks compatibility, so an ARM DomU kernel compiled with
>> this patch will fail to communicate with PV disk devices unless the
>> Dom0 also has this patch.
> 
> This is acceptable IMHO, the ARM ABI is clearly defined and previous
> kernels were simply buggy. The fact that front and backend were
> equivalently buggy and so it happened to work is not an excuse.
> 
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>> Reported-by: Julien Grall <julien.grall@linaro.org>
>> Cc: Julien Grall <julien.grall@linaro.org>
>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Cc: David Vrabel <david.vrabel@citrix.com>
>> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> ---
>>  include/xen/interface/io/blkif.h |   28 +++++++---------------------
>>  1 files changed, 7 insertions(+), 21 deletions(-)
>>
>> diff --git a/include/xen/interface/io/blkif.h b/include/xen/interface/io/blkif.h
>> index 65e1209..002ea22 100644
>> --- a/include/xen/interface/io/blkif.h
>> +++ b/include/xen/interface/io/blkif.h
>> @@ -141,14 +141,11 @@ struct blkif_request_segment_aligned {
>>  	/* @last_sect: last sector in frame to transfer (inclusive).     */
>>  	uint8_t     first_sect, last_sect;
>>  	uint16_t    _pad; /* padding to make it 8 bytes, so it's cache-aligned */
>> -} __attribute__((__packed__));
>> +};
>>  
>>  struct blkif_request_rw {
>>  	uint8_t        nr_segments;  /* number of segments                   */
>>  	blkif_vdev_t   handle;       /* only for read/write requests         */
>> -#ifdef CONFIG_X86_64
>> -	uint32_t       _pad1;	     /* offsetof(blkif_request,u.rw.id) == 8 */
>> -#endif
> 
> These padding fields would still serve a purpose even after removing the
> packing, which is to document/clarify where there are holes for various
> architectures. They could either be retained or perhaps replaced by a
> comment?

Those paddings are already present in drivers/block/xen-blkback/common.h
for each of the different ABIs, which I think is enough, but if I had
to, I would rather replace them with comments.


  parent reply	other threads:[~2013-12-03 11:14 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 10:57 [PATCH RFC] xen-block: correctly define structures in public headers Roger Pau Monne
2013-12-03 11:01 ` David Vrabel
2013-12-03 11:01 ` David Vrabel
2013-12-03 11:07   ` Paul Durrant
2013-12-03 11:07   ` [Xen-devel] " Paul Durrant
2013-12-03 11:08   ` Ian Campbell
2013-12-03 11:59     ` David Vrabel
2013-12-03 11:59     ` [Xen-devel] " David Vrabel
2013-12-03 13:41       ` Ian Campbell
2013-12-03 15:11         ` David Vrabel
2013-12-03 15:11         ` [Xen-devel] " David Vrabel
2013-12-03 15:17           ` Ian Campbell
2013-12-03 15:17           ` [Xen-devel] " Ian Campbell
2013-12-03 15:51             ` One Thousand Gnomes
2013-12-03 16:06               ` Ian Campbell
2013-12-03 16:06               ` Ian Campbell
2013-12-03 15:51             ` One Thousand Gnomes
2013-12-03 20:11             ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-12-04  9:28               ` Ian Campbell
2013-12-04  9:43                 ` Roger Pau Monné
2013-12-04  9:43                 ` Roger Pau Monné
2013-12-04 12:10                 ` [Xen-devel] " Ian Campbell
2013-12-04 12:10                 ` Ian Campbell
2013-12-04  9:28               ` Ian Campbell
2013-12-04 11:03               ` [Xen-devel] " Stefano Stabellini
2013-12-04 11:33                 ` Stefano Stabellini
2013-12-04 11:33                 ` [Xen-devel] " Stefano Stabellini
2013-12-04 11:03               ` Stefano Stabellini
2013-12-11 16:18               ` [Xen-devel] " Stefano Stabellini
2013-12-11 16:23                 ` Roger Pau Monné
2013-12-11 16:29                   ` Stefano Stabellini
2013-12-11 16:29                   ` [Xen-devel] " Stefano Stabellini
2013-12-11 16:23                 ` Roger Pau Monné
2013-12-11 16:18               ` Stefano Stabellini
2013-12-03 20:11             ` Konrad Rzeszutek Wilk
2013-12-03 13:41       ` Ian Campbell
2013-12-03 11:08   ` Ian Campbell
2013-12-03 11:09   ` Roger Pau Monné
2013-12-03 11:09   ` Roger Pau Monné
2013-12-03 11:05 ` [Xen-devel] " Ian Campbell
2013-12-03 11:11   ` Jan Beulich
2013-12-03 11:11   ` [Xen-devel] " Jan Beulich
2013-12-03 11:15     ` Ian Campbell
2013-12-03 11:15     ` Ian Campbell
2013-12-03 11:14   ` Roger Pau Monné
2013-12-03 11:14   ` Roger Pau Monné [this message]
2013-12-03 11:05 ` Ian Campbell
2013-12-03 11:14 ` [Xen-devel] " Jan Beulich
2013-12-03 11:18   ` Roger Pau Monné
2013-12-03 11:18   ` [Xen-devel] " Roger Pau Monné
2013-12-03 11:14 ` Jan Beulich

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=529DBCFE.9030004@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.