On Wed, Mar 19, 2025 at 03:25:50PM -0700, Hardik Garg wrote: > v6.1.132-rc1 build fails on Azure x86 and arm64 VM: Odd, there is no real 6.1.132-rc1 announcement yet, so there's no rush at the moment :) > fs/xfs/libxfs/xfs_alloc.c: In function '__xfs_free_extent_later': > fs/xfs/libxfs/xfs_alloc.c:2551:51: error: 'mp' undeclared (first use in this function); did you mean 'tp'? > 2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len))) > | ^~ > ./include/linux/compiler.h:78:45: note: in definition of macro 'unlikely' > 78 | # define unlikely(x) __builtin_expect(!!(x), 0) > | ^ > fs/xfs/libxfs/xfs_alloc.c:2551:13: note: in expansion of macro 'XFS_IS_CORRUPT' > 2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len))) > | ^~~~~~~~~~~~~~ > fs/xfs/libxfs/xfs_alloc.c:2551:51: note: each undeclared identifier is reported only once for each function it appears in > 2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len))) > | ^~ > ./include/linux/compiler.h:78:45: note: in definition of macro 'unlikely' > 78 | # define unlikely(x) __builtin_expect(!!(x), 0) > | ^ > fs/xfs/libxfs/xfs_alloc.c:2551:13: note: in expansion of macro 'XFS_IS_CORRUPT' > 2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len))) > | ^~~~~~~~~~~~~~ > In file included from ./fs/xfs/xfs.h:22, > from fs/xfs/libxfs/xfs_alloc.c:6: > ./fs/xfs/xfs_linux.h:225:63: warning: left-hand operand of comma expression has no effect [-Wunused-value] > 225 | __this_address), \ > | ^ > fs/xfs/libxfs/xfs_alloc.c:2551:13: note: in expansion of macro 'XFS_IS_CORRUPT' > 2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len))) > | ^~~~~~~~~~~~~~ > CC [M] net/ipv4/netfilter/arpt_mangle.o > CC net/unix/scm.o > make[3]: *** [scripts/Makefile.build:250: fs/xfs/libxfs/xfs_alloc.o] Error 1 > make[2]: *** [scripts/Makefile.build:503: fs/xfs] Error 2 Something is odd with the xfs patches I took? Any hints on what to do is appreciated. thanks, greg k-h
