From: Martin KaFai Lau <martin.lau@linux.dev>
To: Tirthendu Sarkar <tirthendu.sarkar@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 21ef7b1e17d039053edaeaf41142423810572741
Date: Wed, 9 Aug 2023 16:31:10 -0700 [thread overview]
Message-ID: <230ada70-82e4-5350-e3f1-48555670d775@linux.dev> (raw)
In-Reply-To: <202308100207.to2feahW-lkp@intel.com>
On 8/9/23 11:29 AM, kernel test robot wrote:
> Unverified Error/Warning (likely false positive, please contact us if interested):
>
> drivers/block/ublk_drv.c:445 ublk_setup_iod_zoned() warn: signedness bug returning '(-95)'
> drivers/gpu/drm/tests/drm_exec_test.c:166 test_prepare_array() error: uninitialized symbol 'ret'.
> drivers/input/touchscreen/iqs7211.c:1761 iqs7211_parse_cycles() error: buffer overflow 'cycle_alloc[0]' 2 <= 41
> drivers/regulator/max77857-regulator.c:430:28: sparse: sparse: symbol 'max77857_id' was not declared. Should it be static?
> drivers/soundwire/qcom.c:905:22-23: WARNING opportunity for min()
> drivers/video/fbdev/core/fb_chrdev.c:239 do_fscreeninfo_to_user() warn: ignoring unreachable code.
> kernel/workqueue.c:324:40: sparse: sparse: duplicate [noderef]
> kernel/workqueue.c:324:40: sparse: sparse: multiple address spaces given: __percpu & __rcu
> mm/khugepaged.c:2138 collapse_file() warn: variable dereferenced before check 'cc' (see line 1787)
> net/xdp/xsk.c:696 xsk_build_skb() error: 'skb' dereferencing possible ERR_PTR()
Maciej and Tirthendu, the report on xsk looks legit and may be related to commit
cf24f5a5feea ("xsk: add support for AF_XDP multi-buffer on Tx path"). Please
help to take a look. Thanks.
prev parent reply other threads:[~2023-08-09 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:29 [linux-next:master] BUILD REGRESSION 21ef7b1e17d039053edaeaf41142423810572741 kernel test robot
2023-08-09 18:29 ` kernel test robot
2023-08-09 23:31 ` Martin KaFai Lau [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=230ada70-82e4-5350-e3f1-48555670d775@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tirthendu.sarkar@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.