[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170316.121032.405930218798336643.davem@davemloft.net>
Date: Thu, 16 Mar 2017 12:10:32 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: keescook@...omium.org
Cc: eric.dumazet@...il.com, peterz@...radead.org,
elena.reshetova@...el.com, netdev@...r.kernel.org,
bridge@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
kuznet@....inr.ac.ru, jmorris@...ei.org, kaber@...sh.net,
stephen@...workplumber.org, ishkamiel@...il.com, dwindsor@...il.com
Subject: Re: [PATCH 07/17] net: convert sock.sk_refcnt from atomic_t to
refcount_t
From: Kees Cook <keescook@...omium.org>
Date: Thu, 16 Mar 2017 11:38:25 -0600
> I am, of course, biased, but I think the evidence of actual
> refcounting attacks outweighs the theoretical performance cost of
> these changes.
This is not theoretical at all.
We count the nanoseconds that every packet takes to get processed and
you are adding quite a bit.
I understand your point of view, but this is knowingly going to add
performance regressions to the networking code.
Powered by blists - more mailing lists