All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
	horms@kernel.org, oleg@redhat.com, joel.granados@kernel.org
Subject: Re: [PATCH net 0/2] net/rds: fix init failures leaving built-in transports on a dead core
Date: Tue, 27 Oct 2026 10:40:06 +0000	[thread overview]
Message-ID: <179309760607.3719222.9152357183301590944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021195837.142802-1-achender@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 21 Oct 2026 12:58:35 -0700 you wrote:
> The kernel test robot hit a slab-use-after-free on rds_wq at boot with
> CONFIG_SYSCTL=n and RDS, RDS_RDMA and RDS_TCP built in [1].  Two
> separate bugs are involved.
> 
> With CONFIG_SYSCTL=n, register_net_sysctl() is a stub that returns
> NULL, and RDS treats that as -ENOMEM, so rds_init() fails even though
> every tunable has a usable default.  Patch 1 only treats NULL as a
> failure when sysctl support is built in.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net/rds: do not fail init when CONFIG_SYSCTL=n
    https://git.kernel.org/netdev/net/c/fbea154a8664
  - [net,2/2] net/rds: do not initialize transports after rds_init() failed
    https://git.kernel.org/netdev/net/c/ffbbc315b8b8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-27 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 19:58 [PATCH net 0/2] net/rds: fix init failures leaving built-in transports on a dead core Allison Henderson
2026-10-21 19:58 ` [PATCH net 1/2] net/rds: do not fail init when CONFIG_SYSCTL=n Allison Henderson
2026-10-21 20:03   ` sashiko-bot
2026-10-22  7:22   ` Joel Granados
2026-10-22 12:33   ` Oleg Nesterov
2026-10-21 19:58 ` [PATCH net 2/2] net/rds: do not initialize transports after rds_init() failed Allison Henderson
2026-10-21 20:03   ` sashiko-bot
2026-10-27 10:40 ` patchwork-bot+netdevbpf [this message]

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=179309760607.3719222.9152357183301590944.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=joel.granados@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.