public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us•net>
To: Greg KH <gregkh@linuxfoundation•org>
Cc: nvdimm@lists•linux.dev, legousb-devel@lists•sourceforge.net,
	dri-devel@lists•freedesktop.org, linux-sctp@vger•kernel.org,
	linux-stm32@st-md-mailman•stormreply.com,
	linux-samsung-soc@vger•kernel.org, ceph-devel@vger•kernel.org,
	linux-pm@vger•kernel.org, usbb2k-api-dev@nongnu•org,
	linux-omap@vger•kernel.org, megaraidlinux.pdl@broadcom•com,
	linux-usb@vger•kernel.org, linux-wireless@vger•kernel.org,
	linux-perf-users@vger•kernel.org,
	netfilter-devel@vger•kernel.org, linux-crypto@vger•kernel.org,
	linux-fsdevel@vger•kernel.org,
	Andrew Morton <akpm@linux-foundation•org>,
	linux-wpan@vger•kernel.org, linux-fbdev@vger•kernel.org,
	linux-parport@lists•infradead.org, linux-doc@vger•kernel.org,
	samba-technical@lists•samba.org, linux-cxl@vger•kernel.org,
	virtualization@lists•linux-foundation.org, dm-devel@redhat•com,
	target-devel@vger•kernel.org, dev@openvswitch•org,
	linux-cifs@vger•kernel.org, kernel test robot <lkp@intel•com>,
	linux-clk@vger•kernel.org, linux-rockchip@lists•infradead.org,
	iomm u@lists•linux.dev, coreteam@netfilter•org,
	linux-media@vger•kernel.org, linux-watchdog@vger•kernel.org,
	linux-arm-msm@vger•kernel.org, linaro-mm-sig@lists•linaro.org,
	greybus-dev@lists•linaro.org, linux-amlogic@lists•infradead.org,
	linux-arm-kernel@lists•infradead.org,
	linux-block@vger•kernel.org, linux-renesas-soc@vger•kernel.org,
	linux-integrity@vger•kernel.org, linux-efi@vger•kernel.org,
	linux-iio@vger•kernel.org, linux-pci@vger•kernel.org,
	linux-fpga@vger•kernel.org, alsa-devel@alsa-project•org,
	linux-mtd@lists•infradead.org, cgroups@vger•kernel.org,
	linux-phy@lists•infradead.org,
	sound-open-firmware@alsa-project•org, linux-rdma@vger•kernel.org,
	linux-staging@lists•linux.dev, amd-gfx@lists•freedesktop.org,
	isdn4linux@listserv•isdn4linux.de, linux-input@vger•kernel.org,
	linux-ext4@vger•kernel.org, ath11k@lists•infradead.org,
	mjpeg-users@lists•sourceforge.net,
	openipmi-developer@lists•sourceforge.net,
	linux-hwmon@vger•kernel.org, linux-parisc@vger•kernel.org,
	linux-ide@vger•kernel .org, linux-mmc@vger•kernel.org,
	iommu@lists•linux-fo
Subject: Re: [linux-next:master] BUILD REGRESSION 088b9c375534d905a4d337c78db3b3bfbb52c4a0
Date: Thu, 7 Jul 2022 07:02:58 -0700	[thread overview]
Message-ID: <20220707140258.GA3492673@roeck-us.net> (raw)
In-Reply-To: <YsaUgfPbOg7WuBuB@kroah.com>

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" <linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists•ozlabs.org>

On Thu, Jul 07, 2022 at 10:08:33AM +0200, Greg KH wrote:

[ ... ]
> > 
> > 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

  parent reply	other threads:[~2022-07-08  1:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  6:56 [linux-next:master] BUILD REGRESSION 088b9c375534d905a4d337c78db3b3bfbb52c4a0 kernel test robot
2022-07-07  8:08 ` Greg KH
2022-07-07  8:44   ` Chen, Rong A
2022-07-07 14:02   ` Guenter Roeck [this message]
2022-07-08 10:02     ` Dan Carpenter

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=20220707140258.GA3492673@roeck-us.net \
    --to=linux@roeck-us$(echo .)net \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=ceph-devel@vger$(echo .)kernel.org \
    --cc=dev@openvswitch$(echo .)org \
    --cc=dm-devel@redhat$(echo .)com \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=legousb-devel@lists$(echo .)sourceforge.net \
    --cc=linux-cifs@vger$(echo .)kernel.org \
    --cc=linux-clk@vger$(echo .)kernel.org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-cxl@vger$(echo .)kernel.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-fbdev@vger$(echo .)kernel.org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-omap@vger$(echo .)kernel.org \
    --cc=linux-parport@lists$(echo .)infradead.org \
    --cc=linux-perf-users@vger$(echo .)kernel.org \
    --cc=linux-pm@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=linux-samsung-soc@vger$(echo .)kernel.org \
    --cc=linux-sctp@vger$(echo .)kernel.org \
    --cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=linux-wpan@vger$(echo .)kernel.org \
    --cc=lkp@intel$(echo .)com \
    --cc=megaraidlinux.pdl@broadcom$(echo .)com \
    --cc=netfilter-devel@vger$(echo .)kernel.org \
    --cc=nvdimm@lists$(echo .)linux.dev \
    --cc=samba-technical@lists$(echo .)samba.org \
    --cc=target-devel@vger$(echo .)kernel.org \
    --cc=usbb2k-api-dev@nongnu$(echo .)org \
    --cc=virtualization@lists$(echo .)linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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