From: Stephen Rothwell <sfr@canb•auug.org.au>
To: 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: linux-next: build failure after merge of the ext4 tree
Date: Fri, 14 Feb 2025 09:58:23 +1100 [thread overview]
Message-ID: <20250214095823.2fdf796f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Hi all,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from fs/ext4/namei.c:28:
fs/ext4/namei.c: In function '__ext4_find_entry':
include/linux/fs.h:1258:12: error: 'struct super_block' has no member named 's_encoding_flags'
1258 | (sb->s_encoding_flags & SB_ENC_NO_COMPAT_FALLBACK_FL)
| ^~
fs/ext4/namei.c:1602:27: note: in expansion of macro 'sb_no_casefold_compat_fallback'
1602 | else if (!sb_no_casefold_compat_fallback(dir->i_sb) &&
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
ab00acfcfc62 ("ext4: introduce linear search for dentries")
# CONFIG_UNICODE is not set
I have used the ext4 tree from next-20250213 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-02-13 22:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 22:58 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-29 11:59 linux-next: build failure after merge of the ext4 tree Mark Brown
2026-06-01 12:43 ` Mark Brown
2026-06-01 15:17 ` Guan-Chun Wu
2025-07-14 22:22 Stephen Rothwell
2025-07-15 3:31 ` Zhang Yi
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=20250214095823.2fdf796f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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