netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PULL] Networking for v6.2-rc1
Date: Wed, 21 Dec 2022 10:16:40 -0800	[thread overview]
Message-ID: <20221221101640.136fda18@kernel.org> (raw)
In-Reply-To: <CAHk-=wg-W+0gh-XeUrN409RvdOO=VpcWiiPUNm2=Jru5bKWRDQ@mail.gmail.com>

On Wed, 21 Dec 2022 09:16:35 -0800 Linus Torvalds wrote:
> On Tue, Dec 20, 2022 at 12:30 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > Traffic is winding down significantly so let us pass our fixes to you
> > earlier than the usual Thu schedule.
> >
> > We have a fix for the BPF issue we were looking at before 6.1 final,
> > no surprises there. RxRPC fixes were merged relatively late so there's
> > an outpour of follow ups. Last one worth mentioning is the tree-wide
> > fix for network file systems / in-tree socket users, to prevent nested
> > networking calls from corrupting socket memory allocator.  
> 
> The  biggest changes seem to be to the intel 2.5Gb driver ("igc"), but
> they weren't mentioned...

Right, it was an odd is-it-a-fix-or-is-it-a-feature series,
if I'm completely honest I wasn't sure what to say about it.
It seemed safe to merge either way - it only changes the TSN parts
of igc, so the stuff very embedded users would care about.
It's somewhat interesting how Intel uses similar parts for embedded 
and client platforms. There are features which are supported on laptops
(due to being embedded-adjacent) which I'd really like to see in servers
but they are not there :S

> Also, maybe more people should look at this one:
> 
>    https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@kernel.org/
> 
> which seems to be a regression in 6.1 (and still present, afaik).

Ah, yes, the bhash2 conversion, the gift that keeps giving...
Kuniyuki seems to be on top of it:

https://lore.kernel.org/all/20221221151258.25748-1-kuniyu@amazon.com/

we should have a fix for rc2, rc3 worst case.

FWIW this is completely different to the previous python test problem.

  reply	other threads:[~2022-12-21 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 20:30 [PULL] Networking for v6.2-rc1 Jakub Kicinski
2022-12-21 17:16 ` Linus Torvalds
2022-12-21 18:16   ` Jakub Kicinski [this message]
2022-12-21 17:18 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221221101640.136fda18@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).