From: kernel test robot <lkp@intel.com>
To: Jori Koolstra <jkoolstra@xs4all.nl>,
Christian Brauner <brauner@kernel.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Taotao Chen <chentaotao@didiglobal.com>,
Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
NeilBrown <neil@brown.name>
Cc: oe-kbuild-all@lists.linux.dev, jkoolstra@xs4all.nl,
linux-kernel@vger.kernel.org,
syzbot+a65e824272c5f741247d@syzkaller.appspotmail.com
Subject: Re: [PATCH] Fix a drop_nlink warning in minix_rename
Date: Mon, 3 Nov 2025 12:42:37 +0800 [thread overview]
Message-ID: <202511031229.rqpKLU46-lkp@intel.com> (raw)
In-Reply-To: <20251102182532.2442670-1-jkoolstra@xs4all.nl>
Hi Jori,
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on linus/master v6.18-rc4 next-20251031]
[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/Jori-Koolstra/Fix-a-drop_nlink-warning-in-minix_rename/20251103-022646
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20251102182532.2442670-1-jkoolstra%40xs4all.nl
patch subject: [PATCH] Fix a drop_nlink warning in minix_rename
config: arc-randconfig-r073-20251103 (https://download.01.org/0day-ci/archive/20251103/202511031229.rqpKLU46-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251103/202511031229.rqpKLU46-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/202511031229.rqpKLU46-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/minix/namei.c: In function 'minix_unlink':
>> fs/minix/namei.c:151:11: error: 'EFSCORRUPTED' undeclared (first use in this function); did you mean 'FS_NRSUPER'?
return -EFSCORRUPTED;
^~~~~~~~~~~~
FS_NRSUPER
fs/minix/namei.c:151:11: note: each undeclared identifier is reported only once for each function it appears in
fs/minix/namei.c: In function 'minix_rename':
fs/minix/namei.c:217:10: error: 'EFSCORRUPTED' undeclared (first use in this function); did you mean 'FS_NRSUPER'?
err = -EFSCORRUPTED;
^~~~~~~~~~~~
FS_NRSUPER
vim +151 fs/minix/namei.c
140
141 static int minix_unlink(struct inode * dir, struct dentry *dentry)
142 {
143 struct inode * inode = d_inode(dentry);
144 struct folio *folio;
145 struct minix_dir_entry * de;
146 int err;
147
148 if (inode->i_nlink < 1) {
149 printk(KERN_CRIT "minix-fs error: inode (ino: %ld) "
150 "has corrupted nlink", inode->i_ino);
> 151 return -EFSCORRUPTED;
152 }
153
154 de = minix_find_entry(dentry, &folio);
155 if (!de)
156 return -ENOENT;
157 err = minix_delete_entry(de, folio);
158 folio_release_kmap(folio, de);
159
160 if (err)
161 return err;
162 inode_set_ctime_to_ts(inode, inode_get_ctime(dir));
163 inode_dec_link_count(inode);
164 return 0;
165 }
166
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-03 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 18:25 Jori Koolstra
2025-11-03 4:42 ` kernel test robot [this message]
2025-11-03 7:58 ` kernel test robot
2025-11-04 8:03 ` Jan Kara
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=202511031229.rqpKLU46-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=chentaotao@didiglobal.com \
--cc=jack@suse.cz \
--cc=jkoolstra@xs4all.nl \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+a65e824272c5f741247d@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®