From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
"Karsten Graul" <kgraul@linux.ibm.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: net/smc/smc_llc.c:26:2: warning: field within 'struct smc_llc_hdr' is less aligned than 'union smc_llc_hdr::(anonymous at net/smc/smc_llc.c:26:2)' and is usually due to 'struct smc_llc_hdr' being packed, which can lead to unaligned accesses
Date: Sat, 17 Sep 2022 10:16:03 +0200 [thread overview]
Message-ID: <536e1ed3-5d6b-401e-b8b4-888b49aba6df@www.fastmail.com> (raw)
In-Reply-To: <202209171512.qcgXdSrG-lkp@intel.com>
On Sat, Sep 17, 2022, at 10:09 AM, kernel test robot wrote:
> Hi Karsten,
>
> FYI, the error/warning still remains.
>
>
>>> net/smc/smc_llc.c:26:2: warning: field within 'struct smc_llc_hdr' is less aligned than 'union smc_llc_hdr::(anonymous at net/smc/smc_llc.c:26:2)' and is usually due to 'struct smc_llc_hdr' being packed, which can lead to unaligned accesses [-Wunaligned-access]
> union {
> ^
> 1 warning generated.
>
>
> vim +26 net/smc/smc_llc.c
>
> 23
> 24 struct smc_llc_hdr {
> 25 struct smc_wr_rx_hdr common;
> > 26 union {
> 27 struct {
> 28 u8 length; /* 44 */
> 29 #if defined(__BIG_ENDIAN_BITFIELD)
> 30 u8 reserved:4,
> 31 add_link_rej_rsn:4;
> 32 #elif defined(__LITTLE_ENDIAN_BITFIELD)
> 33 u8 add_link_rej_rsn:4,
> 34 reserved:4;
> 35 #endif
> 36 };
> 37 u16 length_v2; /* 44 - 8192*/
> 38 };
> 39 u8 flags;
> 40 } __packed; /* format defined in
> 41 * IBM Shared Memory Communications Version 2
I think the __packed annotation should be moved to the
length_v2 field instead of the outer struct to resolve that.
Arnd
next prev parent reply other threads:[~2022-09-17 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 8:09 net/smc/smc_llc.c:26:2: warning: field within 'struct smc_llc_hdr' is less aligned than 'union smc_llc_hdr::(anonymous at net/smc/smc_llc.c:26:2)' and is usually due to 'struct smc_llc_hdr' being packed, which can lead to unaligned accesses kernel test robot
2022-09-17 8:16 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-26 23:38 kernel test robot
2022-11-09 5:15 kernel test robot
2022-06-25 2:43 kernel test robot
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=536e1ed3-5d6b-401e-b8b4-888b49aba6df@www.fastmail.com \
--to=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=kgraul@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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).