From: "Ziyang Xuan (William)" <william.xuanziyang@huawei.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: <jiri@resnulli.us>, <davem@davemloft.net>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] team: fix null-ptr-deref when team device type is changed
Date: Tue, 5 Sep 2023 19:43:18 +0800 [thread overview]
Message-ID: <ecd693a5-105b-d2b8-5f6d-618d14b491dd@huawei.com> (raw)
In-Reply-To: <ZPbsW/bOGeO9Ww8+@Laptop-X1>
> On Tue, Sep 05, 2023 at 03:46:38PM +0800, Ziyang Xuan wrote:
>> diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c
>> index d3dc22509ea5..12fb5f4cff06 100644
>> --- a/drivers/net/team/team.c
>> +++ b/drivers/net/team/team.c
>> @@ -2127,7 +2127,10 @@ static const struct ethtool_ops team_ethtool_ops = {
>> static void team_setup_by_port(struct net_device *dev,
>> struct net_device *port_dev)
>> {
>> - dev->header_ops = port_dev->header_ops;
>> + if (port_dev->type == ARPHRD_ETHER)
>> + dev->header_ops = ð_header_ops;
>> + else
>> + dev->header_ops = port_dev->header_ops;
>> dev->type = port_dev->type;
>> dev->hard_header_len = port_dev->hard_header_len;
>> dev->needed_headroom = port_dev->needed_headroom;
>
> Hmm.. Do we need to export eth_header_ops? I got error like
> ERROR: modpost: "eth_header_ops" [drivers/net/team/team.ko] undefined!
>
> But I saw function loopback_setup() could reference this. Not sure what
> I missed here.
Yes, I also got the same error, and gave v3 patch with exporting eth_header_ops.
drivers/net/loopback.o controlled by CONFIG_NET, CONFIG_NET is bool type and usually Y.
So drivers/net/loopback.o does not need to export eth_header_ops.
>
> Thanks
> Hangbin
>
> .
>
prev parent reply other threads:[~2023-09-05 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 7:46 Ziyang Xuan
2023-09-05 8:52 ` Hangbin Liu
2023-09-05 11:43 ` Ziyang Xuan (William) [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=ecd693a5-105b-d2b8-5f6d-618d14b491dd@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®