netdev - Re: [PATCH net-next] net: Set tw refcount before dropping the ehash chain lock.

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: <CANn89iJE_rbZ5KAa+M-frNG6xECD7ma65Bv6NH+7Vj2d-w5n=Q@mail.gmail.com>
Date:   Thu, 20 Dec 2018 15:10:04 -0800
From:   Eric Dumazet <edumazet@...gle.com>
To:     jonathan.lemon@...il.com
Cc:     netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        kernel-team <kernel-team@...com>
Subject: Re: [PATCH net-next] net: Set tw refcount before dropping the ehash
 chain lock.

On Thu, Dec 20, 2018 at 3:05 PM Jonathan Lemon <jonathan.lemon@...il.com> wrote:
>

> This works too; I was considering doing it this way, but my initial
> approach
> was a simple fix for ec94c2696f0b (forgot to add Fixes: tag).
>

What about other kinds of sockets ?  SYN_RECV and ESTABLISHED ones ?

Your patch focused on the immediate problem you had, but the problem
was generic.

Anyway, thanks a lot for your help !