LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: David Laight <David.Laight@ACULAB.COM>,
	'Philippe Bergheaud' <felix@linux.vnet.ibm.com>,
	"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "mikey\@neuling.org" <mikey@neuling.org>,
	"mrochs\@linux.vnet.ibm.com" <mrochs@linux.vnet.ibm.com>,
	"fbarrat\@linux.vnet.ibm.com" <fbarrat@linux.vnet.ibm.com>,
	"manoj\@linux.vnet.ibm.com" <manoj@linux.vnet.ibm.com>,
	"ukrishn\@linux.vnet.ibm.com" <ukrishn@linux.vnet.ibm.com>,
	"imunsie\@au1.ibm.com" <imunsie@au1.ibm.com>
Subject: RE: [PATCH] cxl: Use fixed width predefined types in data structure.
Date: Fri, 05 Aug 2016 17:09:17 +1000	[thread overview]
Message-ID: <87k2fviteq.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D5F509628@AcuExch.aculab.com>

David Laight <David.Laight@ACULAB.COM> writes:

> From: Philippe Bergheaud
>> Sent: 04 August 2016 14:56
>> This patch fixes a regression introduced by commit b810253.
>> It substitutes the type __u8 to u8 in the uapi header cxl.h,
>> because the latter is not always defined in userland build
>> environments, in particular when cross-compiling libcxl on
>> x86_64 linux machines (RHEL6.7 and Ubuntu 16.04).
>> 
>> It also makes the definition of cxl_event_afu_driver_reserved
>> more consistent with the other definitions in the header file.
> ...
>> diff --git a/include/uapi/misc/cxl.h b/include/uapi/misc/cxl.h
>> index cbae529..180d526 100644
>> --- a/include/uapi/misc/cxl.h
>> +++ b/include/uapi/misc/cxl.h
>> @@ -136,8 +136,8 @@ struct cxl_event_afu_driver_reserved {
>>  	 *
>>  	 * Of course the contents will be ABI, but that's up the AFU driver.
>>  	 */
>> -	size_t data_size;
>> -	u8 data[];
>> +	__u32 data_size;
>> +	__u8 data[];
>>  };
>
> You've just changed 'data_size' from 64bit to 32bit (on 64bit systems).
> This isn't mentioned in the commit message and changes the API.

Yeah that's pretty fishy.

In practice I suspect there aren't thousands of users of that API, the
commit is only a month old, so we can probably still change it. But
please call it out in the change log.

cheers

      reply	other threads:[~2016-08-05  7:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 13:56 [PATCH] cxl: Use fixed width predefined types in data structure Philippe Bergheaud
2016-08-04 14:26 ` David Laight
2016-08-05  7:09   ` Michael Ellerman [this message]

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=87k2fviteq.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=David.Laight@ACULAB.COM \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=felix@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=manoj@linux.vnet.ibm.com \
    --cc=mikey@neuling.org \
    --cc=mrochs@linux.vnet.ibm.com \
    --cc=ukrishn@linux.vnet.ibm.com \
    /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