From: Greg KH <gregkh@linuxfoundation.org>
To: Hardik Garg <hargar@linux.microsoft.com>
Cc: frank.scheiner@web.de, dchinner@redhat.com, djwong@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: 6.1.132-rc1 build regression on Azure x86 and arm64 VM
Date: Wed, 19 Mar 2025 16:53:53 -0700 [thread overview]
Message-ID: <2025031946-polygon-barrel-6df0@gregkh> (raw)
In-Reply-To: <1742423150-5185-1-git-send-email-hargar@linux.microsoft.com>
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
prev parent reply other threads:[~2025-03-19 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 13:40 6.1.132-rc1 build regression on ia64 (and possibly other architectures) Frank Scheiner
2025-03-19 22:25 ` 6.1.132-rc1 build regression on Azure x86 and arm64 VM Hardik Garg
2025-03-19 23:50 ` Leah Rumancik
2025-03-21 10:53 ` Frank Scheiner
2025-03-19 23:53 ` Greg KH [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=2025031946-polygon-barrel-6df0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=frank.scheiner@web.de \
--cc=hargar@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox