From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-lts:pr/59 1/1] fs/xfs/xfs_dquot_item.c:153:20: warning: variable 'dqp' set but not used
Date: Thu, 20 Feb 2025 11:20:02 +0800 [thread overview]
Message-ID: <202502201138.UVTIOQid-lkp@intel.com> (raw)
tree: https://github.com/intel/linux-intel-lts.git pr/59
head: 19ae9bc73680fd6c1c95edb5b7e2aaa790e7f011
commit: 773a1c5baad243ad30b41700111f0c499f6a259d [1/1] xfs: Properly retry failed dquot items in case of error during buffer writeback
config: sparc-randconfig-002-20250218 (https://download.01.org/0day-ci/archive/20250220/202502201138.UVTIOQid-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250220/202502201138.UVTIOQid-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/202502201138.UVTIOQid-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
fs/xfs/xfs_dquot_item.c: In function 'xfs_dquot_item_error':
>> fs/xfs/xfs_dquot_item.c:153:20: warning: variable 'dqp' set but not used [-Wunused-but-set-variable]
struct xfs_dquot *dqp;
^~~
--
arch/sparc/kernel/head_32.o: in function `current_pc':
>> (.head.text+0x2040): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/head_32.o: in function `halt_notsup':
(.head.text+0x2100): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/process_32.o:(.fixup+0x4): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/process_32.o:(.fixup+0xc): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x0): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x8): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x10): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x18): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x20): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x28): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x30): additional relocation overflows omitted from the output
vim +/dqp +153 fs/xfs/xfs_dquot_item.c
139
140 /*
141 * Callback used to mark a buffer with XFS_LI_FAILED when items in the buffer
142 * have been failed during writeback
143 *
144 * this informs the AIL that the dquot is already flush locked on the next push,
145 * and acquires a hold on the buffer to ensure that it isn't reclaimed before
146 * dirty data makes it to disk.
147 */
148 STATIC void
149 xfs_dquot_item_error(
150 struct xfs_log_item *lip,
151 struct xfs_buf *bp)
152 {
> 153 struct xfs_dquot *dqp;
154
155 dqp = DQUOT_ITEM(lip)->qli_dquot;
156 ASSERT(!completion_done(&dqp->q_flush));
157 xfs_set_li_failed(lip, bp);
158 }
159
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-20 3:20 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=202502201138.UVTIOQid-lkp@intel.com \
--to=lkp@intel.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.