From: Markus Elfring <Markus.Elfring@web.de>
To: Xiyu Yang <xiyuyang19@fudan.edu.cn>,
Xin Tan <tanxin.ctf@gmail.com>,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"David S. Miller" <davem@davemloft.net>,
Hideaki Yoshifuji <yoshfuji@linux-ipv6.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] ipv6: Fix nexthop reference count in ip6_route_info_create()
Date: Sat, 25 Jul 2020 11:34:07 +0200 [thread overview]
Message-ID: <2ac42db4-96e1-298d-4100-beb95d7c91e1@web.de> (raw)
…
> When ip6_route_info_create() returns, local variable "nh" becomes
> invalid, so the refcount should be decreased to keep refcount balanced.
Can it be helpful to use the term “reference count” in consistent ways?
> Fix this issue
How do you think about to replace this wording by the tag “Fixes”?
> by pulling up the error source routing handling when
> nexthops can not be used with source routing.
Does the movement of an if statement according to the check of the
data structure member “rt->fib6_src.plen” in an if branch really help here?
Regards,
Markus
reply other threads:[~2020-07-25 9:34 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=2ac42db4-96e1-298d-4100-beb95d7c91e1@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tanxin.ctf@gmail.com \
--cc=xiyuyang19@fudan.edu.cn \
--cc=yoshfuji@linux-ipv6.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®