All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-next-5 23/29] fs/netfs/write_collect.c:178:25: error: implicit declaration of function 'mempool_free'
Date: Fri, 02 Oct 2026 11:35:51 +0800	[thread overview]
Message-ID: <202610021144.U4c09yz8-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-next-5
head:   5c15345b43019adfd7a82be7f4f190a37dd19310
commit: 8b4e1988ee6980c07bfa9304296feaaee4d7f50c [23/29] netfs: Simplify writeback cleanup
config: microblaze-defconfig (https://download.01.org/0day-ci/archive/20261002/202610021144.U4c09yz8-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261002/202610021144.U4c09yz8-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/202610021144.U4c09yz8-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/netfs/write_collect.c: In function 'netfs_writeback_unlock_folios':
>> fs/netfs/write_collect.c:178:25: error: implicit declaration of function 'mempool_free' [-Wimplicit-function-declaration]
     178 |                         mempool_free(wback, &netfs_bvecq_pool);
         |                         ^~~~~~~~~~~~


vim +/mempool_free +178 fs/netfs/write_collect.c

   137	
   138	/*
   139	 * Unlock any folios we've finished with.
   140	 */
   141	static void netfs_writeback_unlock_folios(struct netfs_io_request *wreq,
   142						  unsigned int *notes)
   143	{
   144		struct netfs_writeback *wback, *next;
   145	
   146		if (wreq->origin == NETFS_PGPRIV2_COPY_TO_CACHE) {
   147			if (netfs_pgpriv2_unlock_copied_folios(wreq))
   148				*notes |= MADE_PROGRESS;
   149			return;
   150		}
   151	
   152		wback = wreq->writebacks;
   153	
   154		for (;;) {
   155			uoff_t stop_at;
   156			size_t len;
   157	
   158			/* Jump over discontiguities. */
   159			if (wreq->cleaned_to < wback->start)
   160				wreq->cleaned_to = wback->start;
   161	
   162			if (wreq->collected_to <= wreq->cleaned_to)
   163				break;
   164	
   165			/* Order read of region length before reading folios. */
   166			len = smp_load_acquire(&wback->len);
   167	
   168			if (wreq->cleaned_to >= wback->start + len) {
   169				/* Order read of next before recheck length. */
   170				next = smp_load_acquire(&wback->next);
   171				if (!next)
   172					break; /* We don't remove the tail writeback. */
   173	
   174				/* Order read of region length before reading folios. */
   175				if (len != smp_load_acquire(&wback->len))
   176					continue; /* len/next update race. */
   177	
 > 178				mempool_free(wback, &netfs_bvecq_pool);
   179				wreq->writebacks = next;
   180				wback = next;
   181				continue;
   182			}
   183	
   184			stop_at = min(wreq->collected_to, wback->start + len);
   185	
   186			trace_netfs_collect_folios(wreq, wback->start, len);
   187			if (!netfs_writeback_unlock_range(wreq, stop_at))
   188				break;
   189			*notes |= MADE_PROGRESS;
   190		}
   191	}
   192	

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

             reply	other threads:[~2026-10-02  3:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  3:35 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-02  8:27 [dhowells-fs:netfs-next-5 23/29] fs/netfs/write_collect.c:178:25: error: implicit declaration of function 'mempool_free' 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=202610021144.U4c09yz8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.