kbuild Development List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Weiming Shi <bestswngs@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
	Tung Nguyen <tung.quang.nguyen@est.tech>
Subject: Warning: net/tipc/node.c:149 struct member 'work' not described in 'tipc_node'
Date: Sat, 18 Jul 2026 07:39:35 +0200	[thread overview]
Message-ID: <202607180730.TwVgASDI-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Weiming-Shi/tipc-fix-NULL-deref-in-tipc_named_node_up-on-empty-publication-list/20260718-030322
head:   e94537041399c865695c83dbb9c1e7df6f8c0e5e
commit: 94540b49437176024eb3fef1947e64f96994b340 tipc: fix NULL deref in tipc_named_node_up() on empty publication list
date:   10 hours ago
config: x86_64-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260718/202607180730.TwVgASDI-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/20260718/202607180730.TwVgASDI-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/202607180730.TwVgASDI-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: net/tipc/node.c:149 struct member 'work' not described in 'tipc_node'
>> Warning: net/tipc/node.c:149 struct member 'work' not described in 'tipc_node'

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

                 reply	other threads:[~2026-07-18  5:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202607180730.TwVgASDI-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bestswngs@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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