mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "'Dan Carpenter'" <dan.carpenter@oracle.com>,
	James Hogan <james.hogan@imgtec.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"andreas.dilger@intel.com" <andreas.dilger@intel.com>,
	Antonio Quartulli <antonio@meshcoding.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	"bergwolf@gmail.com" <bergwolf@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	"oleg.drokin@intel.com" <oleg.drokin@intel.com>,
	"jacques-charles.lafoucriere@cea.fr" 
	<jacques-charles.lafoucriere@cea.fr>,
	"jinshan.xiong@intel.com" <jinshan.xiong@intel.com>,
	netdev <netdev@vger.kernel.org>,
	"linux-metag@vger.kernel.org" <linux-metag@vger.kernel.org>
Subject: Re: [PATCH] drivers: staging: lustre: lustre: include: add "__attribute__((packed))" for the related union
Date: Mon, 03 Feb 2014 18:25:41 +0800	[thread overview]
Message-ID: <52EF6EA5.1050701@gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D0F6B772B@AcuExch.aculab.com>

On 02/03/2014 06:05 PM, David Laight wrote:
> From: Dan Carpenter
>> On Sat, Feb 01, 2014 at 09:57:39PM +0800, Chen Gang wrote:
>>> It seems, our kernel still stick to treate 'pack' region have effect
>>> with both 'align' and 'sizeof'.
>>
>> It's not about packed regions.  It's about unions.  It's saying the
>> sizeof() a union is a multiple of 4 unless it's packed.
>>
>> union foo {
>> 	short x;
>> 	short y;
>> };
>>
>> The author intended the sizeof(union foo) to be 2 but on metag arch then
>> it is 4.
> 
> The same is probably be true of: struct foo { _u16 bar; };
> 

I guess so.


> Architectures that define such alignment rules are a right PITA.

Sorry, I do not know about PITA (after google or wiki, I can not get
more related information).

Could you provide more information about PITA, thanks?


> You either need to get the size to 2 without using 'packed', or
> just not define such structures.

Excuse me, I don't quite understand your meaning. I guess your meaning
is:

  "normally, we should not use a struct/union like that, no matter what it is (2 or 4)".

Is it correct.


> It is worth seeing if adding aligned(2) will change the size - I'm
> not sure.
> 

Yes, it will/should make sure that it must be 2.


Thanks.
-- 
Chen Gang

Open, share and attitude like air, water and life which God blessed

      parent reply	other threads:[~2014-02-03 10:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18  9:50 Chen Gang
2014-01-18 10:05 ` Dan Carpenter
2014-01-18 10:26   ` Chen Gang
2014-01-18 14:24     ` Dan Carpenter
2014-01-19 10:07       ` Chen Gang
2014-01-20 11:56         ` James Hogan
2014-01-20 12:30           ` Dan Carpenter
2014-01-20 12:37             ` James Hogan
2014-01-20 12:56               ` Dan Carpenter
2014-01-20 13:01                 ` Dan Carpenter
2014-01-20 13:38                   ` James Hogan
2014-01-20 21:13                 ` Dan Carpenter
2014-01-21 10:36                   ` James Hogan
2014-01-25 11:55                     ` Chen Gang
2014-02-01 13:57                       ` Chen Gang
2014-02-03  8:58                         ` Dan Carpenter
2014-02-03 10:03                           ` Chen Gang
2014-02-03 11:35                             ` Chen Gang
2014-02-03 10:05                           ` David Laight
2014-02-03 10:22                             ` James Hogan
2014-02-03 10:30                               ` Chen Gang
2014-02-03 10:35                               ` David Laight
2014-02-03 11:02                                 ` James Hogan
2014-02-03 11:54                                   ` David Laight
2014-02-03 10:25                             ` Chen Gang [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=52EF6EA5.1050701@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=andreas.dilger@intel.com \
    --cc=antonio@meshcoding.com \
    --cc=bergwolf@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacques-charles.lafoucriere@cea.fr \
    --cc=james.hogan@imgtec.com \
    --cc=jinshan.xiong@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleg.drokin@intel.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

Powered by JetHome