mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Anna Schumaker <anna.schumaker@oracle.com>,
	Benjamin Coddington <bcodding@redhat.com>
Subject: fs/nfs/./nfstrace.h:1483:1: sparse: sparse: dereference of noderef expression
Date: Tue, 17 Feb 2026 09:04:10 +0800	[thread overview]
Message-ID: <202602170807.6sL9tkvg-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   9702969978695d9a699a1f34771580cdbb153b33
commit: b6ef079fd984930dcc42f4b247777f296528507e nfs: more in-depth tracing of writepage events
date:   5 months ago
config: i386-randconfig-061-20260215 (https://download.01.org/0day-ci/archive/20260217/202602170807.6sL9tkvg-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260217/202602170807.6sL9tkvg-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/202602170807.6sL9tkvg-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   fs/nfs/nfstrace.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, fs/nfs/nfstrace.h):
>> fs/nfs/./nfstrace.h:1483:1: sparse: sparse: dereference of noderef expression
   fs/nfs/nfstrace.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, fs/nfs/nfstrace.h):
>> fs/nfs/./nfstrace.h:1483:1: sparse: sparse: dereference of noderef expression
   fs/nfs/nfstrace.c: note: in included file (through include/trace/perf.h, include/trace/define_trace.h, fs/nfs/nfstrace.h):
>> fs/nfs/./nfstrace.h:1483:1: sparse: sparse: dereference of noderef expression

vim +1483 fs/nfs/./nfstrace.h

  1482	
> 1483	DECLARE_EVENT_CLASS(nfs_page_class,
  1484			TP_PROTO(
  1485				const struct nfs_page *req
  1486			),
  1487	
  1488			TP_ARGS(req),
  1489	
  1490			TP_STRUCT__entry(
  1491				__field(dev_t, dev)
  1492				__field(u32, fhandle)
  1493				__field(u64, fileid)
  1494				__field(const struct nfs_page *__private, req)
  1495				__field(loff_t, offset)
  1496				__field(unsigned int, count)
  1497				__field(unsigned long, flags)
  1498			),
  1499	
  1500			TP_fast_assign(
  1501				const struct inode *inode = folio_inode(req->wb_folio);
  1502				const struct nfs_inode *nfsi = NFS_I(inode);
  1503	
  1504				__entry->dev = inode->i_sb->s_dev;
  1505				__entry->fileid = nfsi->fileid;
  1506				__entry->fhandle = nfs_fhandle_hash(&nfsi->fh);
  1507				__entry->req = req;
  1508				__entry->offset = req_offset(req);
  1509				__entry->count = req->wb_bytes;
  1510				__entry->flags = req->wb_flags;
  1511			),
  1512	
  1513			TP_printk(
  1514				"fileid=%02x:%02x:%llu fhandle=0x%08x req=%p offset=%lld count=%u flags=%s",
  1515				MAJOR(__entry->dev), MINOR(__entry->dev),
  1516				(unsigned long long)__entry->fileid, __entry->fhandle,
  1517				__entry->req, __entry->offset, __entry->count,
  1518				nfs_show_wb_flags(__entry->flags)
  1519			)
  1520	);
  1521	

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

             reply	other threads:[~2026-02-17  1:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  1:04 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-10 22:19 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=202602170807.6sL9tkvg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anna.schumaker@oracle.com \
    --cc=bcodding@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome