From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
dhowells@redhat.com,
syzbot+6182afad5045e6703b3d@syzkaller.appspotmail.com,
Marc Dionne <marc.dionne@auristor.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
linux-afs@lists.infradead.org, stable@kernel.org,
linux-kernel@kernel.org
Subject: Re: [PATCH] rxrpc: Fix data-race warning and potential load/store tearing
Date: Wed, 14 Jan 2026 11:31:58 +0800 [thread overview]
Message-ID: <202601141152.2TfkKMKv-lkp@intel.com> (raw)
In-Reply-To: <3535584.1768322992@warthog.procyon.org.uk>
Hi David,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
[also build test WARNING on net-next/main linus/master v6.19-rc5 next-20260113]
[cannot apply to horms-ipvs/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/David-Howells/rxrpc-Fix-data-race-warning-and-potential-load-store-tearing/20260114-005726
base: net/main
patch link: https://lore.kernel.org/r/3535584.1768322992%40warthog.procyon.org.uk
patch subject: [PATCH] rxrpc: Fix data-race warning and potential load/store tearing
config: x86_64-buildonly-randconfig-006-20260114 (https://download.01.org/0day-ci/archive/20260114/202601141152.2TfkKMKv-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/20260114/202601141152.2TfkKMKv-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/202601141152.2TfkKMKv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/rxrpc/proc.c:305:6: warning: format specifies type 'unsigned long long' but the argument has type 's32' (aka 'int') [-Wformat]
299 | "UDP %-47.47s %-47.47s %3u %4u %5u %6llus %8d %8d\n",
| ~~~~~
| %6d
300 | lbuff,
301 | rbuff,
302 | refcount_read(&peer->ref),
303 | peer->cong_ssthresh,
304 | peer->max_data,
305 | (s32)now - (s32)peer->last_tx_at,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +305 net/rxrpc/proc.c
274
275 /*
276 * generate a list of extant virtual peers in /proc/net/rxrpc/peers
277 */
278 static int rxrpc_peer_seq_show(struct seq_file *seq, void *v)
279 {
280 struct rxrpc_peer *peer;
281 time64_t now;
282 char lbuff[50], rbuff[50];
283
284 if (v == SEQ_START_TOKEN) {
285 seq_puts(seq,
286 "Proto Local Remote Use SST Maxd LastUse RTT RTO\n"
287 );
288 return 0;
289 }
290
291 peer = list_entry(v, struct rxrpc_peer, hash_link);
292
293 sprintf(lbuff, "%pISpc", &peer->local->srx.transport);
294
295 sprintf(rbuff, "%pISpc", &peer->srx.transport);
296
297 now = ktime_get_seconds();
298 seq_printf(seq,
299 "UDP %-47.47s %-47.47s %3u %4u %5u %6llus %8d %8d\n",
300 lbuff,
301 rbuff,
302 refcount_read(&peer->ref),
303 peer->cong_ssthresh,
304 peer->max_data,
> 305 (s32)now - (s32)peer->last_tx_at,
306 READ_ONCE(peer->recent_srtt_us),
307 READ_ONCE(peer->recent_rto_us));
308
309 return 0;
310 }
311
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-14 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 16:49 [PATCH] rxrpc: Fix data-race warning and potential load/store tearing David Howells
2026-01-13 16:52 ` David Howells
2026-01-14 2:49 ` kernel test robot
2026-01-14 3:31 ` kernel test robot [this message]
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=202601141152.2TfkKMKv-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=stable@kernel.org \
--cc=syzbot+6182afad5045e6703b3d@syzkaller.appspotmail.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