Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Allison Henderson <achender@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	pabeni@redhat.com,  edumazet@google.com, horms@kernel.org,
	jhubbard@nvidia.com, leon@kernel.org
Subject: Re: [PATCH net v4 0/4] net/rds: Bug fix ports
Date: Tue, 04 Aug 2026 21:30:48 -0700	[thread overview]
Message-ID: <91d50a922e04c108506ab7e958d62df300ffe5a1.camel@kernel.org> (raw)
In-Reply-To: <20260804180203.3413c381@kernel.org>

On Tue, 2026-08-04 at 18:02 -0700, Jakub Kicinski wrote:
> On Wed, 29 Jul 2026 21:16:25 -0700 Allison Henderson wrote:
> > This is a small set of net/rds bug fixes and ports from uek to upstream
> > rds.  I've been working on extending the rds selftest case, but need to
> > stabilize a few more bugs and the first few fall into net with Fixes
> > tags. I decided to leverage fable for this set and I thought the ports we
> > clean and well explained.
> > 
> > This series fixes a sleeping-in-softirq bug in the RDS message free
> > path, a use-after-free of the RDS socket through long-lived MR
> > references, a message leak in the rds_send_xmit() drop path, and - new
> > in v4 - a pinned-page leak in the IB transport's MR teardown.
> > 
> > The first three patches are ports of fixes carried in the Oracle UEK
> > kernel, reworked where the UEK approach no longer applies upstream.
> 
> I don't have much confidence in my ability to review this,
> so let's queue this for -next. Hope that's okay with you.

Sure, that's fine. I just sent them to net because of the Fixes tags, but there's
no rush.  They're not simple bugs, I usually end up spending quite a bit of time
reviewing them too, but they're also really old bugs. I have quite a few I'd like
to get through, so I'll target them to net-next going forward.

Thank you!
Allison



  reply	other threads:[~2026-08-05  4:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  4:16 [PATCH net v4 0/4] net/rds: Bug fix ports Allison Henderson
2026-07-30  4:16 ` [PATCH net v4 1/4] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context Allison Henderson
2026-07-30  4:16 ` [PATCH net v4 2/4] net/rds: hold the socket while an rds_mr references it Allison Henderson
2026-07-30  4:16 ` [PATCH net v4 3/4] net/rds: fix rds_message leak in the rds_send_xmit() drop path Allison Henderson
2026-07-30  4:16 ` [PATCH net v4 4/4] net/rds: unpin MR pages with unpin_user_pages_dirty_lock() Allison Henderson
2026-08-05  1:02 ` [PATCH net v4 0/4] net/rds: Bug fix ports Jakub Kicinski
2026-08-05  4:30   ` Allison Henderson [this message]
2026-08-05  1:10 ` 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=91d50a922e04c108506ab7e958d62df300ffe5a1.camel@kernel.org \
    --to=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox