mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yuqi Xu <xuyuqiabc@gmail.com>, Aaron Conole <aconole@redhat.com>,
	Eelco Chaudron <echaudro@redhat.com>,
	Ilya Maximets <i.maximets@ovn.org>,
	Pravin B Shelar <pshelar@ovn.org>,
	Jakub Kicinski <kuba@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Yi-Hung Wei <yihung.wei@gmail.com>,
	netdev@vger.kernel.org, dev@openvswitch.org,
	linux-kernel@vger.kernel.org, Vega <vega@nebusec.ai>,
	Nan Li <tonanli66@gmail.com>, Ren Wei <enjou1224z@gmail.com>
Subject: Re: [PATCH net v8 1/1] openvswitch: Fix CT limit teardown use-after-free
Date: Fri, 21 Aug 2026 17:41:25 +0800	[thread overview]
Message-ID: <202608211727.eYRZFh9r-lkp@intel.com> (raw)
In-Reply-To: <d9687780533d0b257e01ab792c8206a69beb281e.1787129643.git.xuyuqiabc@gmail.com>

Hi Yuqi,

kernel test robot noticed the following build errors:

[auto build test ERROR on 564973a259ec76f2dad0853420e7034cc43994c4]

url:    https://github.com/intel-lab-lkp/linux/commits/Yuqi-Xu/openvswitch-Fix-CT-limit-teardown-use-after-free/20260819-172433
base:   564973a259ec76f2dad0853420e7034cc43994c4
patch link:    https://lore.kernel.org/r/d9687780533d0b257e01ab792c8206a69beb281e.1787129643.git.xuyuqiabc%40gmail.com
patch subject: [PATCH net v8 1/1] openvswitch: Fix CT limit teardown use-after-free
config: i386-buildonly-randconfig-005-20260821 (https://download.01.org/0day-ci/archive/20260821/202608211727.eYRZFh9r-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260821/202608211727.eYRZFh9r-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/202608211727.eYRZFh9r-lkp@intel.com/

All errors (new ones prefixed by >>):

>> net/openvswitch/datapath.c:2777:36: error: no member named 'ct_exit_data' in 'struct ovs_net'
    2777 |         ovs_ct_exit_finish(dnet, ovs_net->ct_exit_data);
         |                                  ~~~~~~~  ^
   1 error generated.


vim +2777 net/openvswitch/datapath.c

  2766	
  2767	static void __net_exit ovs_exit_net(struct net *dnet)
  2768	{
  2769		struct ovs_net *ovs_net = net_generic(dnet, ovs_net_id);
  2770		struct vport *vport, *vport_next;
  2771		struct datapath *dp, *dp_next;
  2772		struct net *net;
  2773		LIST_HEAD(head);
  2774	
  2775		ovs_lock();
  2776	
> 2777		ovs_ct_exit_finish(dnet, ovs_net->ct_exit_data);
  2778	
  2779		list_for_each_entry_safe(dp, dp_next, &ovs_net->dps, list_node)
  2780			__dp_destroy(dp);
  2781	
  2782		down_read(&net_rwsem);
  2783		for_each_net(net)
  2784			list_vports_from_net(net, dnet, &head);
  2785		up_read(&net_rwsem);
  2786	
  2787		/* Detach all vports from given namespace. */
  2788		list_for_each_entry_safe(vport, vport_next, &head, detach_list) {
  2789			list_del(&vport->detach_list);
  2790			ovs_dp_detach_port(vport);
  2791		}
  2792	
  2793		ovs_unlock();
  2794	
  2795		cancel_delayed_work_sync(&ovs_net->masks_rebalance);
  2796		cancel_work_sync(&ovs_net->dp_notify_work);
  2797	}
  2798	

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

  parent reply	other threads:[~2026-08-21  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  9:24 [PATCH net v8 0/1] " Yuqi Xu
2026-08-19  9:24 ` [PATCH net v8 1/1] " Yuqi Xu
2026-08-20 16:00   ` Ilya Maximets
2026-08-21  9:41   ` kernel test robot [this message]
2026-08-21 12: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=202608211727.eYRZFh9r-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aconole@redhat.com \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=enjou1224z@gmail.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.org \
    --cc=tonanli66@gmail.com \
    --cc=vega@nebusec.ai \
    --cc=xuyuqiabc@gmail.com \
    --cc=yihung.wei@gmail.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®