Netdev List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tung Nguyen <tung.quang.nguyen@est.tech>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
	kuba@kernel.org, edumazet@kernel.org, pabeni@redhat.com,
	jmaloy@redhat.com, horms@kernel.org,
	tipc-discussion@lists.sourceforge.net,
	Tung Nguyen <tung.quang.nguyen@est.tech>,
	Chengfeng Ye <nicoyip.dev@gmail.com>
Subject: Re: [PATCH net] tipc: fix several race conditions caused by tipc_node_write_unlock()
Date: Tue, 6 Oct 2026 03:55:23 +0800	[thread overview]
Message-ID: <202610060355.bPzTfoXZ-lkp@intel.com> (raw)
In-Reply-To: <20261005041053.22695-1-tung.quang.nguyen@est.tech>

Hi Tung,

kernel test robot noticed the following build warnings:

[auto build test WARNING on net/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Tung-Nguyen/tipc-fix-several-race-conditions-caused-by-tipc_node_write_unlock/20261005-111023
base:   net/main
patch link:    https://lore.kernel.org/r/20261005041053.22695-1-tung.quang.nguyen%40est.tech
patch subject: [PATCH net] tipc: fix several race conditions caused by tipc_node_write_unlock()
config: parisc-randconfig-1001-20261006 (https://download.01.org/0day-ci/archive/20261006/202610060355.bPzTfoXZ-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261006/202610060355.bPzTfoXZ-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/202610060355.bPzTfoXZ-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: net/tipc/name_distr.c:281 function parameter 'publ_list' not described in 'tipc_update_nametbl'
>> Warning: net/tipc/name_distr.c:375 function parameter 'publ_list' not described in 'tipc_named_rcv'
>> Warning: net/tipc/name_distr.c:281 function parameter 'publ_list' not described in 'tipc_update_nametbl'
>> Warning: net/tipc/name_distr.c:375 function parameter 'publ_list' not described in 'tipc_named_rcv'
--
>> Warning: net/tipc/name_table.c:820 function parameter 'skb' not described in 'tipc_nametbl_withdraw'
>> Warning: net/tipc/name_table.c:820 function parameter 'rc_dests' not described in 'tipc_nametbl_withdraw'
>> Warning: net/tipc/name_table.c:820 function parameter 'skb' not described in 'tipc_nametbl_withdraw'
>> Warning: net/tipc/name_table.c:820 function parameter 'rc_dests' not described in 'tipc_nametbl_withdraw'

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

      parent reply	other threads:[~2026-10-05 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  4:10 [PATCH net] tipc: fix several race conditions caused by tipc_node_write_unlock() Tung Nguyen
2026-10-05  4:13 ` netdev-bot+sinfo
2026-10-05 19:55 ` 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=202610060355.bPzTfoXZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    /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