From: kernel test robot <lkp@intel.com>
To: Kyle Zeng <kylebot@openai.com>, jfs-discussion@lists.sourceforge.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Dave Kleikamp <shaggy@kernel.org>,
outbounddisclosures@openai.com, Kyle Zeng <kylebot@openai.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] jfs: validate active AG before updating db_active
Date: Fri, 12 Jun 2026 18:51:04 +0800 [thread overview]
Message-ID: <202606121834.MtsXleJq-lkp@intel.com> (raw)
In-Reply-To: <20260611212956.10206-1-kylebot@openai.com>
Hi Kyle,
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on linus/master kleikamp-shaggy/jfs-next v7.1-rc7 next-20260611]
[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/Kyle-Zeng/jfs-validate-active-AG-before-updating-db_active/20260612-054255
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20260611212956.10206-1-kylebot%40openai.com
patch subject: [PATCH] jfs: validate active AG before updating db_active
config: s390-defconfig (https://download.01.org/0day-ci/archive/20260612/202606121834.MtsXleJq-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260612/202606121834.MtsXleJq-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/202606121834.MtsXleJq-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/jfs/file.c:52:3: error: call to undeclared function 'jfs_error'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
52 | jfs_error(inode->i_sb,
| ^
fs/jfs/file.c:52:3: note: did you mean 'xas_error'?
include/linux/xarray.h:1435:19: note: 'xas_error' declared here
1435 | static inline int xas_error(const struct xa_state *xas)
| ^
1 error generated.
vim +/jfs_error +52 fs/jfs/file.c
43
44 static int jfs_get_active_ag(struct inode *inode, int *agp)
45 {
46 struct jfs_inode_info *ji = JFS_IP(inode);
47 struct jfs_sb_info *sbi = JFS_SBI(inode->i_sb);
48 struct bmap *bmap = sbi->bmap;
49 u64 ag = BLKTOAG(addressPXD(&ji->ixpxd), sbi);
50
51 if (ag >= bmap->db_numag) {
> 52 jfs_error(inode->i_sb,
53 "inode %lu has invalid active ag %llu\n",
54 inode->i_ino, (unsigned long long)ag);
55 return -EIO;
56 }
57
58 *agp = ag;
59 return 0;
60 }
61
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-06-12 10:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260611212956.10206-1-kylebot@openai.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=202606121834.MtsXleJq-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=outbounddisclosures@openai.com \
--cc=shaggy@kernel.org \
--cc=stable@vger.kernel.org \
/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