[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170704.013938.680822769277278352.davem@davemloft.net>
Date: Tue, 04 Jul 2017 01:39:38 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: elena.reshetova@...el.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
jmorris@...ei.org, kaber@...sh.net, yoshfuji@...ux-ipv6.org,
steffen.klassert@...unet.com, kuznet@....inr.ac.ru,
peterz@...radead.org, keescook@...omium.org
Subject: Re: [PATCH 0/9] v2 ipv4/ipv6 refcount conversions
From: Elena Reshetova <elena.reshetova@...el.com>
Date: Tue, 4 Jul 2017 09:34:53 +0300
> Changes in v2:
> * rebase on top of net-next
> * currently by default refcount_t = atomic_t (*) and uses all
> atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled.
> This is a compromise for the systems that are critical on
> performance (such as net) and cannot accept even slight delay
> on the refcounter operations.
>
> This series, for ipv4/ipv6 network components, replaces atomic_t reference
> counters with the new refcount_t type and API (see include/linux/refcount.h).
> By doing this we prevent intentional or accidental
> underflows or overflows that can led to use-after-free vulnerabilities.
>
> The patches are fully independent and can be cherry-picked separately.
> In order to try with refcount functionality enabled in run-time,
> CONFIG_REFCOUNT_FULL must be enabled.
...
Series applied, thanks.
Powered by blists - more mailing lists