netdev - Re: [PATCH net-next v2 3/3] udp: keep the sk_receive

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1494943946.6465.5.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Tue, 16 May 2017 07:12:26 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Paolo Abeni <pabeni@...hat.com>
Cc:     netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next v2 3/3] udp: keep the sk_receive_queue held
 when splicing

On Tue, 2017-05-16 at 11:20 +0200, Paolo Abeni wrote:
> On packet reception, when we are forced to splice the
> sk_receive_queue, we can keep the related lock held, so
> that we can avoid re-acquiring it, if fwd memory
> scheduling is required.
> 
> v1 -> v2:
>   the rx_queue_lock_held param in udp_rmem_release() is
>   now a bool
> 
> Signed-off-by: Paolo Abeni <pabeni@...hat.com>

Acked-by: Eric Dumazet <edumazet@...gle.com>