From: Alan Stern <stern@rowland.harvard.edu>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LinusTorvalds@rowland.harvard.edu, torvalds@linux-foundation.org,
USB mailing list <linux-usb@vger.kernel.org>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>
Subject: Re: [linux-next:master] BUILD REGRESSION 8a11187eb62b8b910d2c5484e1f5d160e8b11eb4
Date: Thu, 17 Mar 2022 12:17:34 -0400 [thread overview]
Message-ID: <YjNfHsqfjPqBMejZ@rowland.harvard.edu> (raw)
In-Reply-To: <6232d299.9omOW8g6S6l31UFc%lkp@intel.com>
On Thu, Mar 17, 2022 at 02:18:01PM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 8a11187eb62b8b910d2c5484e1f5d160e8b11eb4 Add linux-next specific files for 20220316
> drivers/usb/storage/ene_ub6250.c:2416:27: warning: array subscript 'struct SD_STATUS[0]' is partly outside array bounds of 'u8[1]' {aka 'unsigned char[1]'} [-Warray-bounds]
> drivers/usb/storage/ene_ub6250.c:2417:27: warning: array subscript 'struct MS_STATUS[0]' is partly outside array bounds of 'u8[1]' {aka 'unsigned char[1]'} [-Warray-bounds]
> drivers/usb/storage/ene_ub6250.c:2418:27: warning: array subscript 'struct SM_STATUS[0]' is partly outside array bounds of 'u8[1]' {aka 'unsigned char[1]'} [-Warray-bounds]
These warnings seem pretty bogus. Their meaning isn't entirely clear,
but the statements they complain about copy a 1-byte location to a
structure consisting of eight 1-bit fields (or the equivalent).
Do the structure declarations need to be "packed"?
Alan Stern
next prev parent reply other threads:[~2022-03-17 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 6:18 [linux-next:master] BUILD REGRESSION 8a11187eb62b8b910d2c5484e1f5d160e8b11eb4 kernel test robot
2022-03-17 16:17 ` Alan Stern [this message]
2022-03-17 19:11 ` Linus Torvalds
2022-03-17 19:21 ` Alan Stern
2022-03-17 20:39 ` [PATCH] USB: usb-storage: Fix use of bitfields for hardware data in ene_ub6250.c Alan Stern
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=YjNfHsqfjPqBMejZ@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=LinusTorvalds@rowland.harvard.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=usb-storage@lists.one-eyed-alien.net \
/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