Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sun YangKai <sunk67188@gmail.com>, linux-btrfs@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Sun YangKai <sunyangkai@fnnas.com>
Subject: Re: [PATCH] btrfs: check if root is readonly when setting posix acl
Date: Sun, 9 Aug 2026 06:19:33 +0800	[thread overview]
Message-ID: <202608090528.DQ0KtccR-lkp@intel.com> (raw)
In-Reply-To: <20260709071529.4033-1-sunk67188@gmail.com>

Hi Sun,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v7.2-rc6]
[cannot apply to kdave/for-next next-20260807]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Sun-YangKai/btrfs-check-if-root-is-readonly-when-setting-posix-acl/20260807-183739
base:   linus/master
patch link:    https://lore.kernel.org/r/20260709071529.4033-1-sunk67188%40gmail.com
patch subject: [PATCH] btrfs: check if root is readonly when setting posix acl
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260809/202608090528.DQ0KtccR-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260809/202608090528.DQ0KtccR-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/202608090528.DQ0KtccR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/btrfs/acl.c:110:26: error: call to undeclared function 'BTRFS_I'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     110 |         if (btrfs_root_readonly(BTRFS_I(inode)->root))
         |                                 ^
>> fs/btrfs/acl.c:110:42: error: member reference type 'int' is not a pointer
     110 |         if (btrfs_root_readonly(BTRFS_I(inode)->root))
         |                                 ~~~~~~~~~~~~~~  ^
   2 errors generated.


vim +/BTRFS_I +110 fs/btrfs/acl.c

   102	
   103	int btrfs_set_acl(struct mnt_idmap *idmap, struct dentry *dentry,
   104			  struct posix_acl *acl, int type)
   105	{
   106		int ret;
   107		struct inode *inode = d_inode(dentry);
   108		umode_t old_mode = inode->i_mode;
   109	
 > 110		if (btrfs_root_readonly(BTRFS_I(inode)->root))

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2026-08-08 22:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260709071529.4033-1-sunk67188@gmail.com>]

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=202608090528.DQ0KtccR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sunk67188@gmail.com \
    --cc=sunyangkai@fnnas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox