From: "Lin Ma" <linma@zju.edu.cn>
To: "Nikolay Aleksandrov" <razor@blackwall.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, idosch@nvidia.com, jiri@resnulli.us,
lucien.xin@gmail.com, edwin.peer@broadcom.com,
amcohen@nvidia.com, pctammela@mojatatu.com, liuhangbin@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v1] rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back
Date: Tue, 27 Feb 2024 19:54:16 +0800 (GMT+08:00) [thread overview]
Message-ID: <302ac4d7.207e.18dea6a6103.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <2e8c704f-e6a6-40b8-8d4b-7c3a987c4839@blackwall.org>
Hello Nikolay,
>
> That fix is obviously broken, I don't know how I missed it back then.
> One comment below,
Guess is because this loop is so weird :(
I looked into the kernel and did not find other codes that refer to the
NLA pointer outside the `nla_for_each_nested` loop.
> ...
> > struct net *net = sock_net(skb->sk);
> > struct ifinfomsg *ifm;
> > struct net_device *dev;
> > - struct nlattr *br_spec, *attr = NULL;
> > + struct nlattr *br_spec, *attr, *br_flag = NULL;
>
> Please name the variable to something that describes it better, like
> br_flags_attr.
>
OK, I will rename the variable and send another version.
> > int rem, err = -EOPNOTSUPP;
> > u16 flags = 0;
> > - bool have_flags = false;
> >
> > if (nlmsg_len(nlh) < sizeof(*ifm))
> > return -EINVAL;
> > @@ -5190,11 +5189,11 @@ static int rtnl_bridge_setlink(struct sk_buff *skb, struct nlmsghdr *nlh,
> > br_spec = nlmsg_find_attr(nlh, sizeof(struct ifinfomsg), IFLA_AF_SPEC);
> > if (br_spec) {
prev parent reply other threads:[~2024-02-27 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 11:01 Lin Ma
2024-02-27 11:25 ` Nikolay Aleksandrov
2024-02-27 11:54 ` Lin Ma [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=302ac4d7.207e.18dea6a6103.Coremail.linma@zju.edu.cn \
--to=linma@zju.edu.cn \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edwin.peer@broadcom.com \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=razor@blackwall.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
all inboxes | Powered by JetHome®