netdev - Re: [Patch net] socket: close race condition between sock_close() and sockfs

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] [day] [month] [year] [list]

Message-ID: <CAM_iQpWwFO7tRfr9HrpCg1wi8kNqxPGN+APTMk3+JMDk6LM47w@mail.gmail.com>
Date:   Sun, 10 Jun 2018 12:43:11 -0700
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        shankarapailoor <shankarapailoor@...il.com>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        Lorenzo Colitti <lorenzo@...gle.com>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [Patch net] socket: close race condition between sock_close() and sockfs_setattr()

On Sun, Jun 10, 2018 at 12:27 PM, David Miller <davem@...emloft.net> wrote:
> I'm applying this for now, it is at least a step towards fixing
> all of these issues.
>
> If it is really offensive, I can revert, just tell me.

Thanks, David!

Unless there is something fundamentally broken, there is no
reason to revert it. The only risk here is some possible deadlock,
but I am ready to fix any deadlock report caused by this
patch. :)