Re: [linux-next:master] BUILD REGRESSION 088b9c375534d905a4d337c78db3b3bfbb52c4a0
From: Guenter Roeck <linux@roeck-us.net>
Date: 2022-07-07 14:03:18
Also in:
alsa-devel, amd-gfx, ath11k, ceph-devel, damon, dm-devel, dri-devel, intel-wired-lan, keyrings, kvm, linux-amlogic, linux-arm-msm, linux-bcache, linux-block, linux-bluetooth, linux-btrfs, linux-cifs, linux-clk, linux-crypto, linux-cxl, linux-devicetree, linux-doc, linux-efi, linux-ext4, linux-fbdev, linux-fpga, linux-fsdevel, linux-hwmon, linux-ide, linux-iio, linux-input, linux-integrity, linux-iommu, linux-leds, linux-media, linux-mediatek, linux-mm, linux-mmc, linux-omap, linux-pci, linux-perf-users, linux-phy, linux-pm, linux-raid, linux-rdma, linux-renesas-soc, linux-samsung-soc, linux-scsi, linux-sctp, linux-serial, linux-staging, linux-tegra, linux-unionfs, linux-usb, linux-watchdog, linux-wireless, netdev, netfilter-devel, nvdimm, target-devel, virtualization
undation.org, keyrings@vger.kernel.org, netdev@vger.kernel.org, kvm@vger.kernel.org, damon@lists.linux.dev, linux-mm@kvack.org, accessrunner-general@lists.sourceforge.net, linux1394-devel@lists.sourceforge.net, linux-leds@vger.kernel.org, rds-devel@oss.oracle.com, linux-x25@vger.kernel.org, dccp@vger.kernel.org, intel-wired-lan@lists.osuosl.org, linux-serial@vger.kernel.org, devicetree@vger.kernel.org, linux-nfc@lists.01.org, osmocom-net-gprs@lists.osmocom.org, apparmor@lists.ubuntu.com, linux-raid@vger.kernel.org, linux-bcache@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-tegra@vger.kernel.org, linux-scsi@vger.kernel.org, patches@opensource.cirrus.com, linux-unionfs@vger.kernel.org, linux-bluetooth@vger.kernel.org, ntb@lists.linux.dev, tipc-discussion@lists.sourceforge.net, linuxppc-dev@lists.ozlabs.org, linux-btrfs@vger.kernel.org
Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org
Sender: "Linuxppc-dev" [off-list ref]
On Thu, Jul 07, 2022 at 10:08:33AM +0200, Greg KH wrote:
[ ... ]
quoted
Unverified Error/Warning (likely false positive, please contact us if interested):
arch/x86/events/core.c:2114 init_hw_perf_events() warn: missing error code 'err'
drivers/android/binder.c:1481:19-23: ERROR: from is NULL but dereferenced.
drivers/android/binder.c:2920:29-33: ERROR: target_thread is NULL but dereferenced.
drivers/android/binder.c:353:25-35: ERROR: node -> proc is NULL but dereferenced.
drivers/android/binder.c:4888:16-20: ERROR: t is NULL but dereferenced.
drivers/base/regmap/regmap.c:1996:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/char/random.c:869:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/firmware/arm_scmi/clock.c:394:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/firmware/arm_scmi/powercap.c:376:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/vega10_powertune.c:1214:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/gpu/drm/amd/display/dc/os_types.h: drm/drm_print.h is included more than once.
drivers/gpu/drm/bridge/ite-it66121.c:1398:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
drivers/greybus/operation.c:617:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
<snip>
When the compiler crashes, why are you blaming all of these different
mailing lists? Perhaps you need to fix your compiler :)
To be fair, it says above "likely false positive, please contact us
if interested". Also, the 32-bit build errors _are_ real, and the NULL
dereferences in the binder driver are at the very least suspicious.
Guenter