Re: [linux-next:master] BUILD REGRESSION 3d229ce89862b8e82d71a9e11d6f840ca272a6d6

[Andrew Morton <akpm@linux-foundation.org>]

On Wed, 21 Oct 2026 06:38:27 +0800 kernel test robot <lkp@intel.com> wrote:

> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 3d229ce89862b8e82d71a9e11d6f840ca272a6d6  Add linux-next specific files for 20261019
> 
> Error/Warning (recently discovered and may have been fixed):
> 
>     https://lore.kernel.org/oe-kbuild-all/202610210232.uzFGXnjw-lkp@intel.com
>     https://lore.kernel.org/oe-kbuild-all/202610210332.DDqYQv5K-lkp@intel.com
> 
>     arch/arm64/kvm/vgic/vgic-irs-v5.c:1016:15: warning: variable 'addr' set but not used [-Wunused-but-set-variable=]
>     kernel/sched/ext/ext.c:5178:17: error: implicit declaration of function 'scx_reenq_wait_dispatching'; did you mean 'scx_wait_dispatching'? [-Wimplicit-function-declaration]

Thanks.

cc sched peeps.

hp2:/usr/src/linux-next> git grep -r scx_reenq_wait_dispatching . 
kernel/sched/ext/ext.c:         scx_reenq_wait_dispatching(p);
hp2:/usr/src/linux-next> 

yeah, that'll do it.  Probably already fixed.

> Unverified Error/Warning (likely false positive, kindly check if interested):
> 
>     fs/ext2/super.c:1040:7: warning: writing variable 's_mount_state' requires holding spinlock '_res->s_lock' exclusively [-Wthread-safety-precise]
>     fs/ext2/super.c:1138:8: warning: writing variable 's_rsv_window_root' requires holding spinlock '_res->s_rsv_window_lock' exclusively [-Wthread-safety-precise]

I doubt if anything else can see these things within ->fill_super(). 
What tool generated these warnings?