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
| ||
|
Message-ID: <CANn89iKZhMCmPJ5BFzMGgLNv+PxGkUP6sgZVO+BBYLx4wpmEkQ@mail.gmail.com> Date: Tue, 19 Dec 2023 16:23:05 +0100 From: Eric Dumazet <edumazet@...gle.com> To: Kuniyuki Iwashima <kuniyu@...zon.com> Cc: "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, David Ahern <dsahern@...nel.org>, Kuniyuki Iwashima <kuni1840@...il.com>, netdev@...r.kernel.org Subject: Re: [PATCH RESEND v2 net-next 05/12] tcp: Rename tb in inet_bind2_bucket_(init|create)(). On Tue, Dec 19, 2023 at 1:21 AM Kuniyuki Iwashima <kuniyu@...zon.com> wrote: > > Later, we no longer link sockets to bhash. Instead, each bhash2 > bucket is linked to the corresponding bhash bucket. > > Then, we pass the bhash bucket to bhash2 allocation functions as > tb. However, tb is already used in inet_bind2_bucket_create() and > inet_bind2_bucket_init() as the bhash2 bucket. > > To make the following diff clear, let's use tb2 for the bhash2 bucket > there. > > Signed-off-by: Kuniyuki Iwashima <kuniyu@...zon.com> Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists