From: Ilya Maximets <i.maximets@ovn.org>
To: netdev@vger.kernel.org
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Shuah Khan <shuah@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Petr Machata <petrm@nvidia.com>,
Fernando Fernandez Mancera <fmancera@suse.de>,
Antoine Tenart <atenart@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
linux-kernel@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org,
Ilya Maximets <i.maximets@ovn.org>
Subject: [RFC net-next 3/6] openvswitch: vport: remove infrastructure for separate modules
Date: Wed, 13 May 2026 20:35:23 +0200 [thread overview]
Message-ID: <20260513183559.2141010-4-i.maximets@ovn.org> (raw)
In-Reply-To: <20260513183559.2141010-1-i.maximets@ovn.org>
Since removal of legacy tunnel vport types only the built-in ones
remain. So, there is no need for the extra infrastructure for dynamic
module loading. Can be reinstated in the future if we need a new
vport type.
Note: It is technically possible that someone has an out-of-tree
module named vport-type-N that implements a different vport type.
At this time we're not aware of anyone doing that. People running
out-of-tree modules normally just have an out-of-tree openvswitch
module as a whole. And there are actually no supported out-of-tree
implementations of the openvswitch module known to the community.
Alternative to immediate removal would be printing out a deprecation
warning whenever a vport module is loaded, but I'm not sure if we
need it at this time.
Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
---
net/openvswitch/vport.c | 22 ++--------------------
net/openvswitch/vport.h | 9 +--------
2 files changed, 3 insertions(+), 28 deletions(-)
diff --git a/net/openvswitch/vport.c b/net/openvswitch/vport.c
index 7a9caacfd6ac2..ef2fff4353c0a 100644
--- a/net/openvswitch/vport.c
+++ b/net/openvswitch/vport.c
@@ -57,7 +57,7 @@ static struct hlist_head *hash_bucket(const struct net *net, const char *name)
return &dev_table[hash & (VPORT_HASH_BUCKETS - 1)];
}
-int __ovs_vport_ops_register(struct vport_ops *ops)
+int ovs_vport_ops_register(struct vport_ops *ops)
{
int err = -EEXIST;
struct vport_ops *o;
@@ -73,7 +73,6 @@ int __ovs_vport_ops_register(struct vport_ops *ops)
ovs_unlock();
return err;
}
-EXPORT_SYMBOL_GPL(__ovs_vport_ops_register);
void ovs_vport_ops_unregister(struct vport_ops *ops)
{
@@ -81,7 +80,6 @@ void ovs_vport_ops_unregister(struct vport_ops *ops)
list_del(&ops->list);
ovs_unlock();
}
-EXPORT_SYMBOL_GPL(ovs_vport_ops_unregister);
/**
* ovs_vport_locate - find a port that has already been created
@@ -210,12 +208,8 @@ struct vport *ovs_vport_add(const struct vport_parms *parms)
if (ops) {
struct hlist_head *bucket;
- if (!try_module_get(ops->owner))
- return ERR_PTR(-EAFNOSUPPORT);
-
vport = ops->create(parms);
if (IS_ERR(vport)) {
- module_put(ops->owner);
return vport;
}
@@ -225,18 +219,7 @@ struct vport *ovs_vport_add(const struct vport_parms *parms)
return vport;
}
- /* Unlock to attempt module load and return -EAGAIN if load
- * was successful as we need to restart the port addition
- * workflow.
- */
- ovs_unlock();
- request_module("vport-type-%d", parms->type);
- ovs_lock();
-
- if (!ovs_vport_lookup(parms))
- return ERR_PTR(-EAFNOSUPPORT);
- else
- return ERR_PTR(-EAGAIN);
+ return ERR_PTR(-EAFNOSUPPORT);
}
/**
@@ -250,7 +233,6 @@ struct vport *ovs_vport_add(const struct vport_parms *parms)
void ovs_vport_del(struct vport *vport)
{
hlist_del_rcu(&vport->hash_node);
- module_put(vport->ops->owner);
vport->ops->destroy(vport);
}
diff --git a/net/openvswitch/vport.h b/net/openvswitch/vport.h
index 636788b59907c..930f1ccc85581 100644
--- a/net/openvswitch/vport.h
+++ b/net/openvswitch/vport.h
@@ -116,7 +116,6 @@ struct vport_parms {
* before an RCU grace period has elapsed.
* @send: Send a packet on the device.
* zero for dropped packets or negative for error.
- * @owner: Module that implements this vport type.
* @list: List entry in the global list of vport types.
*/
struct vport_ops {
@@ -127,7 +126,6 @@ struct vport_ops {
void (*destroy)(struct vport *);
int (*send)(struct sk_buff *skb);
- struct module *owner;
struct list_head list;
};
@@ -191,12 +189,7 @@ static inline const char *ovs_vport_name(struct vport *vport)
return vport->dev->name;
}
-int __ovs_vport_ops_register(struct vport_ops *ops);
-#define ovs_vport_ops_register(ops) \
- ({ \
- (ops)->owner = THIS_MODULE; \
- __ovs_vport_ops_register(ops); \
- })
+int ovs_vport_ops_register(struct vport_ops *ops);
void ovs_vport_ops_unregister(struct vport_ops *ops);
void ovs_vport_send(struct vport *vport, struct sk_buff *skb, u8 mac_proto);
--
2.53.0
next prev parent reply other threads:[~2026-05-13 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 18:35 [RFC net-next 0/6] openvswitch: remove support for legacy tunnel ports Ilya Maximets
2026-05-13 18:35 ` [RFC net-next 1/6] openvswitch: remove support for legacy tunnel types Ilya Maximets
2026-05-13 18:35 ` [RFC net-next 2/6] openvswitch: vport: remove infrastructure for vport options Ilya Maximets
2026-05-13 18:35 ` Ilya Maximets [this message]
2026-05-13 18:35 ` [RFC net-next 4/6] net: geneve: remove unused geneve_dev_create_fb Ilya Maximets
2026-05-13 18:35 ` [RFC net-next 5/6] net: gre: remove unused gretap_fb_dev_create Ilya Maximets
2026-05-13 18:35 ` [RFC net-next 6/6] net: vxlan: remove unused vxlan_dev_create Ilya Maximets
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=20260513183559.2141010-4-i.maximets@ovn.org \
--to=i.maximets@ovn.org \
--cc=aconole@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dsahern@kernel.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
/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