From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH 4/6] tcp: Repair socket queues Date: Thu, 03 May 2012 11:08:40 +0200 Message-ID: <1336036120.10187.7.camel@edumazet-glaptop> References: <4F901572.4040009@parallels.com> <4F9015ED.7020607@parallels.com> <1335957064.22133.428.camel@edumazet-glaptop> <4FA248E4.7060501@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Linux Netdev List , David Miller To: Pavel Emelyanov Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:52518 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756610Ab2ECJIo (ORCPT ); Thu, 3 May 2012 05:08:44 -0400 Received: by eekc41 with SMTP id c41so435084eek.19 for ; Thu, 03 May 2012 02:08:43 -0700 (PDT) In-Reply-To: <4FA248E4.7060501@parallels.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 2012-05-03 at 12:59 +0400, Pavel Emelyanov wrote: > On 05/02/2012 03:11 PM, Eric Dumazet wrote: > > I am not sure any check is performed on 'size' ? > > No, no checks here. > > > A caller might trigger OOM or wrap bug. > > Well, yes, but this ability is given to CAP_SYS_NET_ADMIN users only. > Do you think it's nonetheless worth accounting this allocation into > the socket's rmem? Yes, something must be done... Might be a good reason to un-inline tcp_try_rmem_schedule(), this fat thing...