linux-kernel - Re: [git pull] epoll fixes

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: <CAHk-=wiHFbAaqS0h_D-9d1=Yc-iq96wE-hrrqOfptGNUZx-GRg@mail.gmail.com>
Date:   Fri, 2 Oct 2020 10:44:29 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] epoll fixes

On Fri, Oct 2, 2020 at 10:20 AM Al Viro <viro@...iv.linux.org.uk> wrote:
>
>         Several race fixes in epoll.

Fudge. I screwed up the commit message due to a cut-and-paste error
(don't ask - sometimes google chrome and gnome-terminal seem to stop
agreeing about the normal X paste buffer)

And I extra stupidly pushed the thing out after the build succeeded,
not having noticed how I screwed up the trivial commit message.

I've force-updated the public sites, and I really hope nobody pulled
in that (very short) time when my tree had a bogus commit message.

(In case anybody cares, the commit message said "SEQCNT_MUTEX_ZERO"
instead of "Several race fixes in epoll" because that's what I had
looked at in another terminal. So it was a very WTF message)

I think this was only the second time I had a forced push to fix some
stupidity of mine. So it's not exactly _common_, but it's
embarrassing.

                    Linus