From: David Miller <davem@davemloft.net>
To: ubraun@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
jwi@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, raspl@linux.vnet.ibm.com
Subject: Re: [PATCH net-next 2/5] net/smc: fix structure size
Date: Thu, 22 Feb 2018 14:10:34 -0500 (EST) [thread overview]
Message-ID: <20180222.141034.147310516964522686.davem@davemloft.net> (raw)
In-Reply-To: <20180221113235.46702-3-ubraun@linux.vnet.ibm.com>
From: Ursula Braun <ubraun@linux.vnet.ibm.com>
Date: Wed, 21 Feb 2018 12:32:32 +0100
> diff --git a/net/smc/smc_cdc.h b/net/smc/smc_cdc.h
> index ab240b37ad11..d2012fd22100 100644
> --- a/net/smc/smc_cdc.h
> +++ b/net/smc/smc_cdc.h
> @@ -48,7 +48,7 @@ struct smc_cdc_msg {
> struct smc_cdc_producer_flags prod_flags;
> struct smc_cdc_conn_state_flags conn_state_flags;
> u8 reserved[18];
> -} __aligned(8);
> +} __packed; /* format defined in RFC7609 */
Hold on, __packed should only be used as the absolute last possible
option to fix structure layout problems.
Also, a sub-structure of smc_cdc_msg, union smc_cdc_cursor, is still
marked with __aligned(8). That makes no sense at all.
Please fix this without using __packed, as __packed has a severe
detrimental effect on code generation for accessing such structure
on several cpu architectures.
Also, if this these are legitimate bug fixes you should target those
at 'net' not 'net-next'.
Thank you.
next prev parent reply other threads:[~2018-02-22 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 11:32 [PATCH net-next 0/5] net/smc: fixes 2018-02-21 Ursula Braun
2018-02-21 11:32 ` [PATCH net-next 1/5] net/smc: cleanup smc_llc.h and smc_clc.h headers Ursula Braun
2018-02-21 11:32 ` [PATCH net-next 2/5] net/smc: fix structure size Ursula Braun
2018-02-22 19:10 ` David Miller [this message]
2018-02-21 11:32 ` [PATCH net-next 3/5] net/smc: move netinfo function to file smc_clc.c Ursula Braun
2018-02-21 11:32 ` [PATCH net-next 4/5] net/smc: remove unused fields from smc structures Ursula Braun
2018-02-21 11:32 ` [PATCH net-next 5/5] net/smc: use server link_id in confirm link reply Ursula Braun
2018-02-21 14:06 ` [PATCH net-next 0/5] net/smc: fixes 2018-02-21 Stefan Raspl
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=20180222.141034.147310516964522686.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=jwi@linux.vnet.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=ubraun@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;
as well as URLs for NNTP newsgroup(s).