public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-2025-07-10
Date: Fri, 11 Jul 2025 14:03:24 -0700	[thread overview]
Message-ID: <20250711140324.65386022@kernel.org> (raw)
In-Reply-To: <934e5e1e253ee3025f617cc38ce6fc15e0619d6c.camel@sipsolutions.net>

On Fri, 11 Jul 2025 08:41:28 +0200 Johannes Berg wrote:
> > Some good news and some bad news. Bad news is that this missed today's
> > PR. Good news is that we shipped a bug to Linus which is likely to
> > break nl80211 users:
> > https://lore.kernel.org/all/20250711001121.3649033-1-kuba@kernel.org/
> > so I'm gonna send a second PR tomorrow, with the netlink fix and I'll
> > include your fixes in it. I suppose you may want to wait with the fast
> > forward until then. 
> > Now that I typed this I guess it may be two pieces of bad news..  
> 
> No worries, and thanks for the heads-up, I can wait. I actually really
> hope this was the last pull request for the current -rc cycle anyway,
> but of course now that I said it someone's going to come out of the
> woodwork with a fix ;)
> 
> Re the size problem, nl80211 can indeed create and fill really big SKBs
> if userspace gives a big buffer, which it often does. Looking at it now,
> I'm not sure why we set the rcvbuf to 8KiB in iw? That seems ... odd. It
> looks like I originally did that to _increase_ it, but that seems
> completely off, and my first fix didn't even do anything. Then we fixed
> the call but ...
> 
> Looks like the problem is entirely self-made there, but I guess we still
> have to live with stupid userspace, sorry about that. I can take a
> closer look at it all and try to fix things there, if you think it's
> worth it?

Probably not, unless it's hurting in another way. The well maintained
userspace is usually not what we have to worry about the most with
netlink.

I was holding off replying until the dust has fully settled but it
sounds like Linus is still hitting some hard to pin down regression. 
I don't _think_ it's us any more, so I reckon you're safe to fast
forward.

  parent reply	other threads:[~2025-07-11 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 12:21 [GIT PULL] wireless-2025-07-10 Johannes Berg
2025-07-11  0:23 ` Jakub Kicinski
2025-07-11  6:41   ` Johannes Berg
2025-07-11 20:55     ` Jeff Johnson
2025-07-11 21:03     ` Jakub Kicinski [this message]
2025-07-11  0:30 ` patchwork-bot+netdevbpf

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=20250711140324.65386022@kernel.org \
    --to=kuba@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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