From: David Ahern <dsahern@gmail.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Yajun Deng <yajun.deng@linux.dev>,
davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-decnet-user@lists.sourceforge.net
Subject: Re: [PATCH] net: convert fib_treeref from int to refcount_t
Date: Tue, 3 Aug 2021 08:43:41 -0600 [thread overview]
Message-ID: <43af9da8-9438-20eb-567b-4538e97d0389@gmail.com> (raw)
In-Reply-To: <14e0ec1c-0345-d5d4-769a-44ded33821e8@samsung.com>
On 8/3/21 5:08 AM, Marek Szyprowski wrote:
> Hi
>
> On 29.07.2021 09:13, Yajun Deng wrote:
>> refcount_t type should be used instead of int when fib_treeref is used as
>> a reference counter,and avoid use-after-free risks.
>>
>> Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
>
> This patch landed in linux-next 20210802 as commit 79976892f7ea ("net:
> convert fib_treeref from int to refcount_t"). It triggers the following
> warning on all my test systems (ARM32bit and ARM64bit based):
>
fixed in net-next.
prev parent reply other threads:[~2021-08-03 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 7:13 [PATCH] net: convert fib_treeref from int to refcount_t Yajun Deng
2021-07-29 14:55 ` David Ahern
2021-07-30 15:30 ` patchwork-bot+netdevbpf
2021-08-02 13:37 ` Ioana Ciornei
2021-08-02 14:36 ` David Ahern
2021-08-02 14:59 ` Ioana Ciornei
2021-08-03 11:17 ` Fwd: " yajun.deng
2021-08-03 11:24 ` Marek Szyprowski
[not found] ` <CGME20210803110803eucas1p276a0010caad8fc21a7ea5ca5543294f8@eucas1p2.samsung.com>
2021-08-03 11:08 ` Marek Szyprowski
2021-08-03 14:43 ` David Ahern [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=43af9da8-9438-20eb-567b-4538e97d0389@gmail.com \
--to=dsahern@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=yajun.deng@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).