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:1539:1: sparse: sparse: incorrect type in assignment (different base types)
Date: Wed, 10 Dec 2025 22:24:27 +0800 [thread overview]
Message-ID: <202512102249.0H1AhKrr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c9b47175e9131118e6f221cc8fb81397d62e7c91
commit: b0b7cdc99431655aec3f3afcf05e3eeca0f8dd79 nfs: new tracepoint in match_stateid operation
date: 5 months ago
config: x86_64-randconfig-r134-20251210 (https://download.01.org/0day-ci/archive/20251210/202512102249.0H1AhKrr-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251210/202512102249.0H1AhKrr-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/202512102249.0H1AhKrr-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.h:1539:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected int s1_seq @@ got restricted __be32 const [usertype] seqid @@
fs/nfs/./nfs4trace.h:1539:1: sparse: expected int s1_seq
fs/nfs/./nfs4trace.h:1539:1: sparse: got restricted __be32 const [usertype] seqid
fs/nfs/./nfs4trace.h:1539:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected int s2_seq @@ got restricted __be32 const [usertype] seqid @@
fs/nfs/./nfs4trace.h:1539:1: sparse: expected int s2_seq
fs/nfs/./nfs4trace.h:1539:1: sparse: got restricted __be32 const [usertype] seqid
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
>> fs/nfs/./nfs4trace.h:1539:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected int s1_seq @@ got restricted __be32 const [usertype] seqid @@
fs/nfs/./nfs4trace.h:1539:1: sparse: expected int s1_seq
fs/nfs/./nfs4trace.h:1539:1: sparse: got restricted __be32 const [usertype] seqid
fs/nfs/./nfs4trace.h:1539:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected int s2_seq @@ got restricted __be32 const [usertype] seqid @@
fs/nfs/./nfs4trace.h:1539:1: sparse: expected int s2_seq
fs/nfs/./nfs4trace.h:1539:1: sparse: got restricted __be32 const [usertype] seqid
vim +1539 fs/nfs/./nfs4trace.h
1526
1527 #define show_stateid_type(type) \
1528 __print_symbolic(type, \
1529 { NFS4_INVALID_STATEID_TYPE, "INVALID" }, \
1530 { NFS4_SPECIAL_STATEID_TYPE, "SPECIAL" }, \
1531 { NFS4_OPEN_STATEID_TYPE, "OPEN" }, \
1532 { NFS4_LOCK_STATEID_TYPE, "LOCK" }, \
1533 { NFS4_DELEGATION_STATEID_TYPE, "DELEGATION" }, \
1534 { NFS4_LAYOUT_STATEID_TYPE, "LAYOUT" }, \
1535 { NFS4_PNFS_DS_STATEID_TYPE, "PNFS_DS" }, \
1536 { NFS4_REVOKED_STATEID_TYPE, "REVOKED" }, \
1537 { NFS4_FREED_STATEID_TYPE, "FREED" })
1538
> 1539 DECLARE_EVENT_CLASS(nfs4_match_stateid_event,
1540 TP_PROTO(
1541 const nfs4_stateid *s1,
1542 const nfs4_stateid *s2
1543 ),
1544
1545 TP_ARGS(s1, s2),
1546
1547 TP_STRUCT__entry(
1548 __field(int, s1_seq)
1549 __field(int, s2_seq)
1550 __field(u32, s1_hash)
1551 __field(u32, s2_hash)
1552 __field(int, s1_type)
1553 __field(int, s2_type)
1554 ),
1555
1556 TP_fast_assign(
1557 __entry->s1_seq = s1->seqid;
1558 __entry->s1_hash = nfs_stateid_hash(s1);
1559 __entry->s1_type = s1->type;
1560 __entry->s2_seq = s2->seqid;
1561 __entry->s2_hash = nfs_stateid_hash(s2);
1562 __entry->s2_type = s2->type;
1563 ),
1564
1565 TP_printk(
1566 "s1=%s:%x:%u s2=%s:%x:%u",
1567 show_stateid_type(__entry->s1_type),
1568 __entry->s1_hash, __entry->s1_seq,
1569 show_stateid_type(__entry->s2_type),
1570 __entry->s2_hash, __entry->s2_seq
1571 )
1572 );
1573
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-10 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 14:24 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-11 14:03 fs/nfs/./nfs4trace.h:1539:1: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2026-01-13 5:59 kernel test robot
2026-01-13 12:39 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=202512102249.0H1AhKrr-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