netdev - Re: [GIT PULL] Networking for 5.10-rc7

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: <CAHk-=wgBDP8WwpO-yyv0fvdc0w9qoQwugywvwsARp4HMfUkD1g@mail.gmail.com>
Date:   Thu, 3 Dec 2020 13:18:13 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     David Miller <davem@...emloft.net>,
        Netdev <netdev@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Networking for 5.10-rc7

On Thu, Dec 3, 2020 at 12:45 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> Networking fixes for 5.10-rc7, including fixes from bpf, netfilter,
> wireless drivers, wireless mesh and can.

Thanks, pulled.

And btw - maybe I've already talked about this, but since next week is
(hopefully) going to be the last week of rc release: since the
networking pulls tend to be some of the bigger ones, one thing I've
asked David to do in the past is to (a) not send a big networking pull
request right before the final release and (b) let me know whether
there is anything worrisome going on in networking.

So if you send it on a Thursday (like this one), then that's all good
- it's the "Oh, it's Sunday noon, I was planning on a final release in
the afternoon, and I have a big networking fix pull request in my
mailbox" that I'd prefer to not see.

A heads up on the "Uhhuh - we have something bad going in the
networking tree" kind of situation you can obviously send at any time.
If there are known issues, I'll just make an rc8 - I prefer not to
_have_ to, of course, but I'd always much rather be safe than release
the final kernel just because I didn't know of some pending issue.

(And the reverse - just a note saying "everything looks fine, none of
this is scary and there's nothing pending that looks at all worrisome
either" - for the last rc pull is obviously also always appreciated,
but generally I'll assume that unless something else is said, we're in
good shape).

            Linus