From: Zhang Yi <yi.zhang@huawei•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Theodore Ts'o <tytso@mit•edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the ext4 tree
Date: Tue, 15 Jul 2025 11:31:50 +0800 [thread overview]
Message-ID: <3738cc55-f3fd-4b6c-b1dd-3f469c00b9f1@huawei.com> (raw)
In-Reply-To: <20250715082230.7f5bcb1e@canb.auug.org.au>
On 2025/7/15 6:22, Stephen Rothwell wrote:
> Hi all,
>
> After merging the ext4 tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
Hi Stephen!
I'm sorry for the regression, but I cannot reproduce this error
on my machine, could you please try this patch?
https://lore.kernel.org/linux-ext4/20250715031203.2966086-1-yi.zhang@huaweicloud.com/
Thanks,
Yi.
>
> In file included from <command-line>:
> fs/ext4/inode.c: In function 'ext4_set_inode_mapping_order':
> include/linux/compiler_types.h:568:45: error: call to '__compiletime_assert_652' declared with attribute error: min(({ __auto_type __UNIQUE_ID_x_647 = (((0 ? 4 : 6) * 2 - 1)); __auto_type __UNIQUE_ID_y_648 = (((16 + __pte_index_size)-16)); do { __attribute__((__noreturn__)) extern void __compiletime_assert_649(void) __attribute__((__error__("min""(""((0 ? 4 : 6) * 2 - 1)"", ""((16 + __pte_index_size)-16)"") signedness error"))); if (!(!(!(((((typeof(__UNIQUE_ID_x_647))(-1)) < ( typeof(__UNIQUE_ID_x_647))1) ? (2 + (__builtin_constant_p((long long)(__UNIQUE_ID_x_647) >= 0) && ((long long)(__UNIQUE_ID_x_647) >= 0))) : (1 + 2 * (sizeof(__UNIQUE_ID_x_647) < 4))) & ((((typeof(__UNIQUE_ID_y_648))(-1)) < ( typeof(__UNIQUE_ID_y_648))1) ? (2 + (__builtin_constant_p((long long)(__UNIQUE_ID_y_648) >= 0) && ((long long)(__UNIQUE_ID_y_648) >= 0))) : (1 + 2 * (sizeof(__UNIQUE_ID_y_648) < 4))))))) __compiletime_assert_649(); } while (0); ((__UNIQUE_ID_x_647) < (__UNIQUE_ID_y_648) ? (__UNIQUE_ID_x_647) : (__UNIQUE_ID_y_648)); }), (11 + (inode)->i_blkbits - 16)) signedness error
> 568 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> | ^
> include/linux/compiler_types.h:549:25: note: in definition of macro '__compiletime_assert'
> 549 | prefix ## suffix(); \
> | ^~~~~~
> include/linux/compiler_types.h:568:9: note: in expansion of macro '_compiletime_assert'
> 568 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> | ^~~~~~~~~~~~~~~~~~~
> include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
> 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
> | ^~~~~~~~~~~~~~~~~~
> include/linux/minmax.h:93:9: note: in expansion of macro 'BUILD_BUG_ON_MSG'
> 93 | BUILD_BUG_ON_MSG(!__types_ok(ux, uy), \
> | ^~~~~~~~~~~~~~~~
> include/linux/minmax.h:98:9: note: in expansion of macro '__careful_cmp_once'
> 98 | __careful_cmp_once(op, x, y, __UNIQUE_ID(x_), __UNIQUE_ID(y_))
> | ^~~~~~~~~~~~~~~~~~
> include/linux/minmax.h:105:25: note: in expansion of macro '__careful_cmp'
> 105 | #define min(x, y) __careful_cmp(min, x, y)
> | ^~~~~~~~~~~~~
> fs/ext4/inode.c:5204:17: note: in expansion of macro 'min'
> 5204 | min(MAX_PAGECACHE_ORDER, (11 + (i)->i_blkbits - PAGE_SHIFT))
> | ^~~
> fs/ext4/inode.c:5211:39: note: in expansion of macro 'EXT4_MAX_PAGECACHE_ORDER'
> 5211 | EXT4_MAX_PAGECACHE_ORDER(inode));
> | ^~~~~~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> e14bef2a00b5 ("ext4: limit the maximum folio order")
>
> I have used the ext4 tree from next-20250714 for today.
>
next prev parent reply other threads:[~2025-07-15 3:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 22:22 linux-next: build failure after merge of the ext4 tree Stephen Rothwell
2025-07-15 3:31 ` Zhang Yi [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-29 11:59 Mark Brown
2026-06-01 12:43 ` Mark Brown
2026-06-01 15:17 ` Guan-Chun Wu
2025-02-13 22:58 Stephen Rothwell
2018-10-08 23:51 Stephen Rothwell
2018-10-09 5:23 ` Theodore Y. Ts'o
2016-02-07 23:50 Stephen Rothwell
2016-01-03 23:34 Stephen Rothwell
2016-01-04 13:49 ` Theodore Ts'o
2015-07-23 0:56 Stephen Rothwell
2015-07-23 16:49 ` Theodore Ts'o
2015-07-23 17:23 ` Theodore Ts'o
2015-07-23 17:41 ` Tejun Heo
2015-05-07 1:14 Stephen Rothwell
2013-07-29 1:08 Stephen Rothwell
2013-07-31 1:27 ` Stephen Rothwell
2013-08-07 5:16 ` Sedat Dilek
2013-08-07 5:38 ` Stephen Rothwell
2013-08-07 5:43 ` Sedat Dilek
2013-08-07 5:59 ` Stephen Rothwell
2013-08-07 15:28 ` Kevin Hilman
2013-08-08 0:22 ` Stephen Rothwell
2013-08-08 0:36 ` Stephen Rothwell
2013-08-08 19:16 ` Yann E. MORIN
2013-08-08 21:54 ` Yann E. MORIN
2013-08-08 23:58 ` Stephen Rothwell
2013-08-09 11:42 ` Sam Ravnborg
2013-08-11 21:39 ` Yann E. MORIN
2013-08-16 13:10 ` Michal Marek
2013-08-16 17:14 ` Sam Ravnborg
2013-08-16 18:02 ` Yann E. MORIN
2013-04-03 23:43 Stephen Rothwell
2013-04-04 13:18 ` Lukáš Czerner
2013-04-04 13:20 ` Theodore Ts'o
2013-04-04 13:27 ` Lukáš Czerner
2012-07-10 1:23 Stephen Rothwell
2012-07-10 1:48 ` Aditya Kali
2012-01-03 0:35 Stephen Rothwell
2012-01-05 21:06 ` Stephen Rothwell
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=3738cc55-f3fd-4b6c-b1dd-3f469c00b9f1@huawei.com \
--to=yi.zhang@huawei$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tytso@mit$(echo .)edu \
/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