From: Chuck Lever <cel@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
Steve French <stfrench@microsoft.com>,
Roland Mainz <roland.mainz@nrubsig.org>
Subject: Re: [cifs:for-next-next 15/16] fs/smb/client/cifsfs.c:1204:22: error: use of undeclared identifier 'FS_XFLAG_CASEFOLD'
Date: Tue, 9 Jun 2026 10:11:07 -0400 [thread overview]
Message-ID: <20260609141108.90414-1-cel@kernel.org> (raw)
In-Reply-To: <202606091825.Fvo4zzYp-lkp@intel.com>
On 6/9/26 6:24 AM, kernel test robot wrote:
> >> fs/smb/client/cifsfs.c:1204:22: error: use of undeclared identifier 'FS_XFLAG_CASEFOLD'
FS_XFLAG_CASEFOLD and FS_XFLAG_CASENONPRESERVING are defined by
"fs: Add case sensitivity flags to file_kattr", the foundational
patch of the case-sensitivity series. That patch adds the two
macros to include/uapi/linux/fs.h and folds them into
FS_XFLAG_RDONLY_MASK in include/linux/fileattr.h.
The cifs consumer ("cifs: Implement fileattr_get for case
sensitivity") landed in for-next-next without that prerequisite,
so the identifiers are undeclared. The failure reproduces under
both clang and gcc because the macros are simply absent, not
because of any arch- or compiler-specific construct.
Steve, the cifs patch should not be applied ahead of its
dependency. Either base for-next-next on the branch carrying
"fs: Add case sensitivity flags to file_kattr", or drop the cifs
patch until that patch lands. The full series is intended to be
merged together for this reason.
No fix is needed in the cifs patch itself.
next prev parent reply other threads:[~2026-06-09 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:24 [cifs:for-next-next 15/16] fs/smb/client/cifsfs.c:1204:22: error: use of undeclared identifier 'FS_XFLAG_CASEFOLD' kernel test robot
2026-06-09 14:11 ` Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-05 7:15 kernel test robot
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=20260609141108.90414-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roland.mainz@nrubsig.org \
--cc=samba-technical@lists.samba.org \
--cc=stfrench@microsoft.com \
/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.