All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [djwong-xfs:llm-fixes-23 65/95] fs/xfs/scrub/inode_repair.c:1773:undefined reference to `xfs_qm_dqget_inode'
Date: Mon, 05 Oct 2026 20:46:42 +0200	[thread overview]
Message-ID: <202610052000.DNFCy2r1-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git llm-fixes-23
head:   cfeb0e609481f4df242684d426d8972e120e1826
commit: d1a9d46e808953ae087cdd9dd7ff545f491064c5 [65/95] xfs: reattach dquots after changing inode ids
config: x86_64-randconfig-r2100-20261005 (https://download.01.org/0day-ci/archive/20261005/202610052000.DNFCy2r1-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261005/202610052000.DNFCy2r1-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/202610052000.DNFCy2r1-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: vmlinux.o: in function `xrep_inode_switch_dquot':
>> fs/xfs/scrub/inode_repair.c:1773:(.text+0x1a2b796): undefined reference to `xfs_qm_dqget_inode'
>> ld: fs/xfs/scrub/inode_repair.c:1773:(.text+0x1a2b83d): undefined reference to `xfs_qm_dqget_inode'
   ld: fs/xfs/scrub/inode_repair.c:1773:(.text+0x1a2b918): undefined reference to `xfs_qm_dqget_inode'


vim +1773 fs/xfs/scrub/inode_repair.c

  1752	
  1753	static void
  1754	xrep_inode_switch_dquot(
  1755		struct xfs_scrub	*sc,
  1756		xfs_dqtype_t		type,
  1757		struct xfs_dquot	**dqp)
  1758	{
  1759		/*
  1760		 * We changed one of the file IDs, so we must detach the dquots to
  1761		 * prevent further changes from being accounted to them, and try to
  1762		 * attach the dquot for the new id to absorb any other block usage
  1763		 * changes.  Schedule a quotacheck so the accounting discrepancies will
  1764		 * get fixed eventually.
  1765		 */
  1766		xrep_force_quotacheck(sc, type);
  1767	
  1768		if (*dqp != NULL) {
  1769			xfs_qm_dqrele(*dqp);
  1770			*dqp = NULL;
  1771		}
  1772	
> 1773		xfs_qm_dqget_inode(sc->ip, type, false, dqp);
  1774	}
  1775	

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

                 reply	other threads:[~2026-10-05 18:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202610052000.DNFCy2r1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=djwong@kernel.org \
    --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.