From: Chen Gang <gang.chen.5i5j@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: devel@driverdev.osuosl.org, andreas.dilger@intel.com,
Antonio Quartulli <antonio@meshcoding.com>,
Greg KH <gregkh@linuxfoundation.org>,
bergwolf@gmail.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
oleg.drokin@intel.com, jacques-charles.lafoucriere@cea.fr,
jinshan.xiong@intel.com, netdev <netdev@vger.kernel.org>,
linux-metag@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] drivers: staging: lustre: lustre: include: add "__attribute__((packed))" for the related union
Date: Sat, 25 Jan 2014 19:55:46 +0800 [thread overview]
Message-ID: <52E3A642.7010307@gmail.com> (raw)
In-Reply-To: <52DE4DA3.7090301@imgtec.com>
On 01/21/2014 06:36 PM, James Hogan wrote:
> Hi Dan,
>
> On 20/01/14 21:13, Dan Carpenter wrote:
>> I made a quick and dirty sparse patch to check for this. I don't think
>> I will bother trying to send it to sparse upstream, but you can if you
>> want to.
>>
>> It found 289 unions which might need a __packed added. The lustre
>> unions were not in my allmodconfig so they're not listed.
>
> Thanks a lot for this, it seems to be useful. I'm adapting it to reduce
> false negatives (e.g. omitting the check if the struct/union is already
> packed), and I imagine it could be made to only warn about padded
> unpacked structs/unions which are used as nested members of packed
> structs/unions. It wouldn't catch everything but would probably catch a
> lot of cases that are most likely to be genuine since they would have
> been packed at the outer level for a reason.
>
>> Perhaps there could be a command line option or a pragma so that unions
>> will work in the kernel. We don't care about linking to outside
>> libraries.
>
> We still interact with userland via structs and unions, so it would
> probably have to exclude anything in uapi/.
>
Thank all of you firstly.
But excuse me, I am still not quit clear that: "what need we do enough
to solve this feature issue?"
So I guess our current result is:
- It is not a good idea to only let kernel to fit with compiler.
- It is not a good idea to only let compiler to fit with kernel.
- Need let compiler and kernel to fit with each other:
- compiler will print related warning, but not break compiling.
so metag compiler need be improvement (check and warn for it).
- if check alignment explicitly in kernel source code, it need be
fixed within kernel: "apply related patches (pack each struct or
union), but the related patch comments need be improved".
Is what I guess correct?
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next parent reply other threads:[~2014-01-25 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52DA4E6A.1000308@gmail.com>
[not found] ` <20140118100547.GS7444@mwanda>
[not found] ` <52DA56C2.5010802@gmail.com>
[not found] ` <20140118142404.GT7444@mwanda>
[not found] ` <52DBA3D4.3090308@gmail.com>
[not found] ` <52DD0EFF.2010305@imgtec.com>
[not found] ` <20140120123045.GV7444@mwanda>
[not found] ` <52DD18A5.1090308@imgtec.com>
[not found] ` <20140120125603.GD4815@mwanda>
[not found] ` <20140120211356.GG4815@mwanda>
[not found] ` <52DE4DA3.7090301@imgtec.com>
2014-01-25 11:55 ` Chen Gang [this message]
2014-02-01 13:57 ` [PATCH] drivers: staging: lustre: lustre: include: add "__attribute__((packed))" for the related union Chen Gang
2014-02-03 8:58 ` Dan Carpenter
2014-02-03 10:03 ` Chen Gang
[not found] ` <52EF6965.6040406-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
[not found] ` <52EF6DCC.6040807-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2014-02-03 10:35 ` David Laight
2014-02-03 11:02 ` James Hogan
2014-02-03 11:54 ` David Laight
[not found] ` <063D6719AE5E284EB5DD2968C1650D6D0F6B772B-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-02-03 10:25 ` Chen Gang
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=52E3A642.7010307@gmail.com \
--to=gang.chen.5i5j@gmail.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;
as well as URLs for NNTP newsgroup(s).