[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190822.120447.538380205267677448.davem@davemloft.net>
Date: Thu, 22 Aug 2019 12:04:47 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jan.dakinevich@...tuozzo.com
Cc: linux-kernel@...r.kernel.org, den@...tuozzo.com,
khorenko@...tuozzo.com, jan.dakinevich@...il.com,
kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org, pablo@...filter.org,
kadlec@...filter.org, fw@...len.de, johannes.berg@...el.com,
dsahern@...il.com, christian@...uner.io,
stephen@...workplumber.org, Jason@...c4.com,
jakub.kicinski@...ronome.com, willemb@...gle.com,
xiyou.wangcong@...il.com, simon.horman@...ronome.com,
john.hurley@...ronome.com, pabeni@...hat.com, brouer@...hat.com,
bigeasy@...utronix.de, edumazet@...gle.com, lirongqing@...du.com,
ap420073@...il.com, ptalbert@...hat.com,
herbert@...dor.apana.org.au, tglx@...utronix.de, dima@...sta.com,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
coreteam@...filter.org
Subject: Re: [PATCH 0/3] rework netlink skb allocation
From: Jan Dakinevich <jan.dakinevich@...tuozzo.com>
Date: Thu, 22 Aug 2019 10:48:08 +0000
> Currently, userspace is able to initiate costly high-order allocation in
> kernel sending large broadcast netlink message, which is considered
> undesirable. At the same time, unicast message are safe in this regard,
> because they uses vmalloc-ed memory.
>
> This series introduces changes, that allow broadcast messages to be
> allocated with vmalloc() as well as unicast.
I'm tossing this series for the same reason I tossed the AF_UNIX change.
Powered by blists - more mailing lists