netdev - Re: [RFC] folding socket->wq into struct socket

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]

Date:   Sun, 05 May 2019 10:04:21 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     viro@...iv.linux.org.uk
Cc:     netdev@...r.kernel.org
Subject: Re: [RFC] folding socket->wq into struct socket

From: Al Viro <viro@...iv.linux.org.uk>
Date: Thu, 2 May 2019 17:32:23 +0100

> it appears that we might take freeing the socket itself to the
> RCU-delayed part, along with socket->wq.  And doing that has
> an interesting benefit - the only reason to do two separate
> allocation disappears.

I'm pretty sure we looked into RCU freeing the socket in the
past but ended up not doing so.

I think it had to do with the latency in releasing sock related
objects.

However, I might be confusing "struct socket" with "struct sock"