linux-kernel - Re: Timer breakage in net-next

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: <CAGXu5jKxV9D+4fJhrnB=gnkeQP_G11L_qnpiC8vF5AS=VtFOSg@mail.gmail.com>
Date:   Fri, 27 Oct 2017 11:09:15 +0200
From:   Kees Cook <keescook@...omium.org>
To:     David Howells <dhowells@...hat.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Network Development <netdev@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Timer breakage in net-next

On Fri, Oct 27, 2017 at 10:05 AM, David Howells <dhowells@...hat.com> wrote:
> Hi Dave, Kees,
>
> Is it possible to get this timer fix:
>
>         https://patchwork.ozlabs.org/patch/828333/
>
>         timer: Provide wrappers safe for use with LOCKDEP
>
> included in net-next?

FWIW, the LOCKDEP warnings are false positives. The fix includes
updates to one new API function, which would be an additional patch.
When I talked with Thomas, it sounded like it was better just to wait
for the merge window instead of trying to figure out a way to land
this separately in other trees. Obviously this is up to Dave, but it
seemed like a merge of tip/timers/core into net-next would be
confusing.

> You can add my Tested-by line.

Thanks for checking it!

-Kees

-- 
Kees Cook
Pixel Security