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,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Benjamin Coddington <bcodding@redhat.com>
Subject: fs/nfs/./nfs4trace.h:1002:1: sparse: sparse: incorrect type in assignment (different base types)
Date: Tue, 13 Jan 2026 16:43:42 +0800 [thread overview]
Message-ID: <202601131618.0aUHfobK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b71e635feefc852405b14620a7fc58c4c80c0f73
commit: 5dd03d14b3a9595ea320a55c499ebf85b422392f nfs: new tracepoint in nfs_delegation_need_return
date: 6 months ago
config: i386-randconfig-061-20260113 (https://download.01.org/0day-ci/archive/20260113/202601131618.0aUHfobK-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/20260113/202601131618.0aUHfobK-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/202601131618.0aUHfobK-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/nfs/nfs4trace.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, fs/nfs/nfs4trace.h):
>> fs/nfs/./nfs4trace.h:1002:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int fmode @@ got restricted fmode_t const [usertype] type @@
fs/nfs/./nfs4trace.h:1002:1: sparse: expected unsigned int fmode
fs/nfs/./nfs4trace.h:1002:1: sparse: got restricted fmode_t const [usertype] type
fs/nfs/nfs4trace.c: note: in included file (through include/trace/perf.h, include/trace/define_trace.h, fs/nfs/nfs4trace.h):
>> fs/nfs/./nfs4trace.h:1002:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int fmode @@ got restricted fmode_t const [usertype] type @@
fs/nfs/./nfs4trace.h:1002:1: sparse: expected unsigned int fmode
fs/nfs/./nfs4trace.h:1002:1: sparse: got restricted fmode_t const [usertype] type
vim +1002 fs/nfs/./nfs4trace.h
989
990 #define show_delegation_flags(flags) \
991 __print_flags(flags, "|", \
992 { BIT(NFS_DELEGATION_NEED_RECLAIM), "NEED_RECLAIM" }, \
993 { BIT(NFS_DELEGATION_RETURN), "RETURN" }, \
994 { BIT(NFS_DELEGATION_RETURN_IF_CLOSED), "RETURN_IF_CLOSED" }, \
995 { BIT(NFS_DELEGATION_REFERENCED), "REFERENCED" }, \
996 { BIT(NFS_DELEGATION_RETURNING), "RETURNING" }, \
997 { BIT(NFS_DELEGATION_REVOKED), "REVOKED" }, \
998 { BIT(NFS_DELEGATION_TEST_EXPIRED), "TEST_EXPIRED" }, \
999 { BIT(NFS_DELEGATION_INODE_FREEING), "INODE_FREEING" }, \
1000 { BIT(NFS_DELEGATION_RETURN_DELAYED), "RETURN_DELAYED" })
1001
> 1002 DECLARE_EVENT_CLASS(nfs4_delegation_event,
1003 TP_PROTO(
1004 const struct nfs_delegation *delegation
1005 ),
1006
1007 TP_ARGS(delegation),
1008
1009 TP_STRUCT__entry(
1010 __field(u32, fhandle)
1011 __field(unsigned int, fmode)
1012 __field(unsigned long, flags)
1013 ),
1014
1015 TP_fast_assign(
1016 __entry->fhandle = nfs_fhandle_hash(NFS_FH(delegation->inode));
1017 __entry->fmode = delegation->type;
1018 __entry->flags = delegation->flags;
1019 ),
1020
1021 TP_printk(
1022 "fhandle=0x%08x fmode=%s flags=%s",
1023 __entry->fhandle, show_fs_fmode_flags(__entry->fmode),
1024 show_delegation_flags(__entry->flags)
1025 )
1026 );
1027 #define DEFINE_NFS4_DELEGATION_EVENT(name) \
1028 DEFINE_EVENT(nfs4_delegation_event, name, \
1029 TP_PROTO( \
1030 const struct nfs_delegation *delegation \
1031 ), \
1032 TP_ARGS(delegation))
1033 DEFINE_NFS4_DELEGATION_EVENT(nfs_delegation_need_return);
1034
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-13 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 8:43 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-10 22:20 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=202601131618.0aUHfobK-lkp@intel.com \
--to=lkp@intel.com \
--cc=bcodding@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trond.myklebust@hammerspace.com \
/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
all inboxes | Powered by JetHome®