From: Philip Li <philip.li@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Avri Altman <avri.altman@wdc.com>
Subject: Re: [linux-next:master 5069/12910] include/linux/build_bug.h:78:41: error: static assertion failed: "sizeof(struct utp_upiu_header) == 12"
Date: Sat, 26 Aug 2023 08:18:24 +0800 [thread overview]
Message-ID: <ZOlE0C8lm3EVS+8m@rli9-mobl> (raw)
In-Reply-To: <b9c87261-9358-a76d-62d2-743d8162010b@acm.org>
On Fri, Aug 25, 2023 at 10:00:47AM -0700, Bart Van Assche wrote:
> On 8/25/23 02:07, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 6269320850097903b30be8f07a5c61d9f7592393
> > commit: 617bfaa8dd50d6a3ffc8694b4696bf2aa196bd44 [5069/12910] scsi: ufs: Simplify response header parsing
> > config: arm-randconfig-r001-20230825 (https://download.01.org/0day-ci/archive/20230825/202308251634.tuRn4OVv-lkp@intel.com/config)
> > compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
> > reproduce: (https://download.01.org/0day-ci/archive/20230825/202308251634.tuRn4OVv-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202308251634.tuRn4OVv-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from include/linux/container_of.h:5,
> > from include/linux/list.h:5,
> > from include/linux/async.h:12,
> > from drivers/ufs/core/ufshcd.c:12:
> > > > include/linux/build_bug.h:78:41: error: static assertion failed: "sizeof(struct utp_upiu_header) == 12"
> > 78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
> > | ^~~~~~~~~~~~~~
> > include/linux/build_bug.h:77:34: note: in expansion of macro '__static_assert'
> > 77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
> > | ^~~~~~~~~~~~~~~
> > include/ufs/ufs.h:22:1: note: in expansion of macro 'static_assert'
> > 22 | static_assert(sizeof(struct utp_upiu_header) == 12);
> > | ^~~~~~~~~~~~~
>
> Can anyone tell me where to find the gcc binaries used by the kernel test
Hi Bart, the gcc binary we use is put at [1]
You may also give a try for the reproduce step [2] which might help to
ease the reproduce. If it has issue to access the url or other issue
during reproduce, you can try to
export URL=https://cdn.kernel.org/pub/tools/crosstool/files/bin/x86_64
Then rerun the make.cross command of reproduce step. Kindly let us know if there's
any issue.
[1] https://download.01.org/0day-ci/cross-package/gcc-13.2.0-nolibc/x86_64-gcc-13.2.0-nolibc_arm-linux-gnueabi.tar.xz
[2] https://download.01.org/0day-ci/archive/20230825/202308251634.tuRn4OVv-lkp@intel.com/reproduce
> robot? I cannot reproduce the above build error with
> arm-linux-gnueabi-gcc 13.2.0 from godbolt.org.
>
> This is the code that I provided as input to godbolt.org:
>
> #include <stdint.h>
>
> #define __LITTLE_ENDIAN 1
>
> typedef uint32_t __be32;
> typedef uint16_t __be16;
> typedef uint8_t __u8;
>
> struct utp_upiu_header {
> union {
> struct {
> __be32 dword_0;
> __be32 dword_1;
> __be32 dword_2;
> };
> struct {
> __u8 transaction_code;
> __u8 flags;
> __u8 lun;
> __u8 task_tag;
> #if defined(__BIG_ENDIAN)
> __u8 iid: 4;
> __u8 command_set_type: 4;
> #elif defined(__LITTLE_ENDIAN)
> __u8 command_set_type: 4;
> __u8 iid: 4;
> #else
> #error
> #endif
> union {
> __u8 tm_function;
> __u8 query_function;
> };
> __u8 response;
> __u8 status;
> __u8 ehs_length;
> __u8 device_information;
> __be16 data_segment_length;
> };
> };
> };
>
> static_assert(sizeof(struct utp_upiu_header) == 12, "");
>
> Thanks,
>
> Bart.
>
prev parent reply other threads:[~2023-08-26 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 9:07 kernel test robot
2023-08-25 17:00 ` Bart Van Assche
2023-08-26 0:18 ` Philip Li [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=ZOlE0C8lm3EVS+8m@rli9-mobl \
--to=philip.li@intel.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@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