netdev - Re: [PATCH 00/58] networking: Convert timers to use timer

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: <20171018.124219.174286495547300072.davem@davemloft.net>
Date:   Wed, 18 Oct 2017 12:42:19 +0100 (WEST)
From:   David Miller <davem@...emloft.net>
To:     keescook@...omium.org
Cc:     netdev@...r.kernel.org, tglx@...utronix.de,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/58] networking: Convert timers to use timer_setup()

From: Kees Cook <keescook@...omium.org>
Date: Mon, 16 Oct 2017 17:28:44 -0700

> This is the current set of outstanding networking patches to perform
> conversions to the new timer interface (rebased to -next). This is not
> all expected conversions, but it contains everything needed in networking
> to eliminate init_timer(), and all the non-standard setup_*_timer() uses.

I've applied this except:

1) the IRDA stuff, it's staging and needs to go via Greg KH

2) the MPC ATM didn't apply at all to net-next

Such a huge patch series like this is a huge burdon upon
a subsystem maintainer.

Split this kind of stuff up into manageable chunks next time,
maybe a dozen patches at a time.  Do not submit multiple
series at once to get around this size limit.  Submit one
at a time, wait for it to get applied, and then after that
you can submit the next one.

Thanks.