From: kernel test robot <lkp@intel.com>
To: Horst Birthelmer <horst@birthelmer.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Horst Birthelmer <hbirthelmer@ddn.com>
Subject: Re: [PATCH] dcache: add fs.dentry-limit sysctl with negative-first reaper
Date: Fri, 15 May 2026 23:09:54 +0800 [thread overview]
Message-ID: <202605152333.0pOd2zJR-lkp@intel.com> (raw)
In-Reply-To: <20260514-limit-dentries-cache-v1-1-431b9eb0c530@ddn.com>
Hi Horst,
kernel test robot noticed the following build errors:
[auto build test ERROR on 5d6919055dec134de3c40167a490f33c74c12581]
url: https://github.com/intel-lab-lkp/linux/commits/Horst-Birthelmer/dcache-add-fs-dentry-limit-sysctl-with-negative-first-reaper/20260515-154600
base: 5d6919055dec134de3c40167a490f33c74c12581
patch link: https://lore.kernel.org/r/20260514-limit-dentries-cache-v1-1-431b9eb0c530%40ddn.com
patch subject: [PATCH] dcache: add fs.dentry-limit sysctl with negative-first reaper
config: openrisc-randconfig-r073-20260515 (https://download.01.org/0day-ci/archive/20260515/202605152333.0pOd2zJR-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 10.5.0
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605152333.0pOd2zJR-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/202605152333.0pOd2zJR-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/dcache.c: In function 'dentry_limit_worker_fn':
>> fs/dcache.c:1474:7: error: implicit declaration of function 'get_nr_dentry'; did you mean 'retain_dentry'? [-Werror=implicit-function-declaration]
1474 | nr = get_nr_dentry();
| ^~~~~~~~~~~~~
| retain_dentry
cc1: some warnings being treated as errors
vim +1474 fs/dcache.c
1463
1464 static void dentry_limit_worker_fn(struct work_struct *work)
1465 {
1466 struct dentry_limit_ctx ctx;
1467 unsigned long limit = READ_ONCE(sysctl_dentry_limit);
1468 unsigned int ms;
1469 long nr;
1470
1471 if (!limit)
1472 return;
1473
> 1474 nr = get_nr_dentry();
1475 if (nr <= (long)limit)
1476 return;
1477
1478 ctx.over = nr - (long)limit;
1479
1480 /* Phase 1: drain negative dentries across every superblock. */
1481 ctx.isolate = dentry_lru_isolate_negative;
1482 iterate_supers(dentry_limit_prune_sb, &ctx);
1483
1484 /* Phase 2: still over? Apply the ordinary LRU policy. */
1485 if (ctx.over > 0) {
1486 ctx.isolate = dentry_lru_isolate;
1487 iterate_supers(dentry_limit_prune_sb, &ctx);
1488 }
1489
1490 /*
1491 * Re-arm while still above the limit. Re-read the sysctls in
1492 * case the admin raised the cap or disabled the feature during
1493 * the walk.
1494 */
1495 limit = READ_ONCE(sysctl_dentry_limit);
1496 if (!limit || get_nr_dentry() <= (long)limit)
1497 return;
1498
1499 ms = READ_ONCE(sysctl_dentry_limit_interval_ms);
1500 queue_delayed_work(system_unbound_wq, &dentry_limit_work,
1501 msecs_to_jiffies(ms));
1502 }
1503
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-15 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 15:13 [PATCH] dcache: add fs.dentry-limit sysctl with negative-first reaper Horst Birthelmer
2026-05-15 15:09 ` kernel test robot [this message]
2026-05-16 6:55 ` Horst Birthelmer
2026-05-16 10:33 ` Stafford Horne
2026-05-16 14:15 ` Horst Birthelmer
2026-05-15 15:09 ` 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=202605152333.0pOd2zJR-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=hbirthelmer@ddn.com \
--cc=horst@birthelmer.com \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.