From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216020] New: drivers/usb/ folder compilation with allyesconfig fails
Date: Tue, 24 May 2022 14:58:45 +0000 [thread overview]
Message-ID: <bug-216020-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216020
Bug ID: 216020
Summary: drivers/usb/ folder compilation with allyesconfig
fails
Product: Drivers
Version: 2.5
Kernel Version: 5.18
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: kushagra765@outlook.com
Regression: No
When compiling the drivers/usb/ folder with GCC version 12.1.0, the compilation
fails with the following errors:
drivers/usb/storage/ene_ub6250.c: In function ‘ms_lib_process_bootblock’:
drivers/usb/storage/ene_ub6250.c:1050:44: error: array subscript ‘struct
ms_bootblock_idi[0]’ is partly outside array bounds of ‘unsigned char[512]’
[-Werror=array-bounds]
1050 | if (le16_to_cpu(idi->wIDIgeneralConfiguration)
!= MS_IDI_GENERAL_CONF)
| ^~
drivers/usb/storage/ene_ub6250.c: In function ‘ms_lib_process_bootblock’:
drivers/usb/storage/ene_ub6250.c:1053:70: error: array subscript ‘struct
ms_bootblock_idi[0]’ is partly outside array bounds of ‘unsigned char[512]’
[-Werror=array-bounds]
1053 | info->MS_Lib.BytesPerSector =
le16_to_cpu(idi->wIDIbytesPerSector);
| ^~
After these errors, when make waits for unfinished jobs, the following errors
come:
In function ‘xhci_mvebu_mbus_config’,
inlined from ‘xhci_mvebu_mbus_init_quirk’ at
drivers/usb/host/xhci-mvebu.c:66:2:
drivers/usb/host/xhci-mvebu.c:37:28: error: array subscript 0 is outside array
bounds of ‘const struct mbus_dram_window[0]’ [-Werror=array-bounds]
37 | writel(((cs->size - 1) & 0xffff0000) | (cs->mbus_attr
<< 8) |
| ~~^~~~~~
drivers/usb/host/xhci-mvebu.c:37:59: error: array subscript 0 is outside array
bounds of ‘const struct mbus_dram_window[0]’ [-Werror=array-bounds]
37 | writel(((cs->size - 1) & 0xffff0000) | (cs->mbus_attr
<< 8) |
| ~~^~~~~~~~~~~
drivers/usb/host/xhci-mvebu.c:41:27: error: array subscript 0 is outside array
bounds of ‘const struct mbus_dram_window[0]’ [-Werror=array-bounds]
41 | writel((cs->base & 0xffff0000), base +
USB3_WIN_BASE(win));
| ~~^~~~~~
cc1: all warnings being treated as errors
These errors also come when compiling gregkh/usb.git (usb-next branch) with the
GCC version and the configuration mentioned above.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-05-24 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 14:58 bugzilla-daemon [this message]
2022-05-24 15:07 ` [Bug 216020] New: drivers/usb/ folder compilation with allyesconfig fails Greg KH
2022-05-24 15:07 ` [Bug 216020] " bugzilla-daemon
2022-05-24 15:16 ` bugzilla-daemon
2022-05-24 18:48 ` bugzilla-daemon
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=bug-216020-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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