From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
horms@kernel.org
Cc: jhubbard@nvidia.com, leon@kernel.org
Subject: Re: [PATCH net-next 0/3] net/rds: Bug fix ports
Date: Sat, 25 Jul 2026 09:25:21 -0700 [thread overview]
Message-ID: <e770554d9ca05784abb3c9d1ccd378295f46fa08.camel@kernel.org> (raw)
In-Reply-To: <20260725082939.2546624-1-achender@kernel.org>
On Sat, 2026-07-25 at 01:29 -0700, Allison Henderson wrote:
> Hi all,
>
Apologies, this should have been a v2. Let me know if folks want the resend for the book keeping or would rather forgo
the spam.
Thank you,
Allison
> This is a small set of net/rds bug fixes ported 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.
>
> [PATCH net 1/3] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context
> Avoids potentially sleeping in an atomic context by queueing page dirtying in a work
> item, which is then completed in a process context.
>
> [PATCH net 2/3] net/rds: hold the socket while an rds_mr references it
> Port: commit c4d69e511f3b ("rds: Add proper refcnt when an RDS MR references an RDS Socket")
> https://github.com/oracle/linux-uek/commit/94549e4732d8
>
> [PATCH net-next 3/3] net/rds: fix rds_message leak in the rds_send_xmit() drop path
> Port: commit 94549e4732d8 ("net/rds: fix rds_message memleak in rds_send_xmit")
> https://github.com/oracle/linux-uek/commit/94549e4732d8
>
> These were carved out of a larger porting effort, but I'll follow up with a few more
> targeted for net-net after these land in net.
>
> Question and comments appreciated!
>
> Thanks,
> Allison
>
> Changes since v1:
> - Patch 1/3: re-written to delay ditying through queued work items
> - Patch 3/3: fixed check patch nits
>
> Allison Henderson (1):
> net/rds: don't use unpin_user_pages_dirty_lock() from atomic context
>
> Håkon Bugge (1):
> net/rds: hold the socket while an rds_mr references it
>
> Sharath Srinivasan (1):
> net/rds: fix rds_message leak in the rds_send_xmit() drop path
>
> net/rds/ib.c | 7 +++++++
> net/rds/message.c | 34 ++++++++++++++++++++++++++++++++++
> net/rds/rdma.c | 18 ++++++++++++++++--
> net/rds/rds.h | 6 ++++++
> net/rds/send.c | 18 +++++++++++++++---
> 5 files changed, 78 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2026-07-25 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 8:29 [PATCH net-next 0/3] net/rds: Bug fix ports Allison Henderson
2026-07-25 8:29 ` [PATCH net-next 1/3] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context Allison Henderson
2026-07-25 8:29 ` [PATCH net-next 2/3] net/rds: hold the socket while an rds_mr references it Allison Henderson
2026-07-25 8:29 ` [PATCH net-next 3/3] net/rds: fix rds_message leak in the rds_send_xmit() drop path Allison Henderson
2026-07-25 16:25 ` Allison Henderson [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=e770554d9ca05784abb3c9d1ccd378295f46fa08.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 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.