From: kernel test robot <lkp@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: oe-kbuild-all@lists.linux.dev, linux-ext4@vger.kernel.org
Subject: [tytso-ext4:dev 15/15] include/linux/fs.h:1268:12: error: 'struct super_block' has no member named 's_encoding_flags'
Date: Thu, 13 Feb 2025 16:19:53 +0800 [thread overview]
Message-ID: <202502131639.HjJlsWin-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
head: ab00acfcfc62ade16f642841d8807816b27b8944
commit: ab00acfcfc62ade16f642841d8807816b27b8944 [15/15] ext4: introduce linear search for dentries
config: x86_64-buildonly-randconfig-002-20250213 (https://download.01.org/0day-ci/archive/20250213/202502131639.HjJlsWin-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250213/202502131639.HjJlsWin-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502131639.HjJlsWin-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/ext4/namei.c:28:
fs/ext4/namei.c: In function '__ext4_find_entry':
>> include/linux/fs.h:1268:12: error: 'struct super_block' has no member named 's_encoding_flags'
1268 | (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) &&
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +1268 include/linux/fs.h
1263
1264 #define sb_has_strict_encoding(sb) \
1265 (sb->s_encoding_flags & SB_ENC_STRICT_MODE_FL)
1266
1267 #define sb_no_casefold_compat_fallback(sb) \
> 1268 (sb->s_encoding_flags & SB_ENC_NO_COMPAT_FALLBACK_FL)
1269
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-13 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502131639.HjJlsWin-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.