From: Allison Henderson <achender@kernel.org>
To: Breno Leitao <leitao@debian.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kselftest@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v2 1/3] rds: mark snapshot pages dirty in rds_info_getsockopt()
Date: Fri, 05 Jun 2026 15:22:55 -0700 [thread overview]
Message-ID: <dea41eedebf284c2a57e75d1ca99b59a58863160.camel@kernel.org> (raw)
In-Reply-To: <20260605-getsock_more-v2-1-80f38cdb8706@debian.org>
On Fri, 2026-06-05 at 03:31 -0700, Breno Leitao wrote:
> rds_info_getsockopt() pins the destination user pages with FOLL_WRITE and
> the RDS_INFO_* producers memcpy the snapshot into them through
> kmap_atomic(). Because that copy goes through the kernel direct map, the
> dirty bit on the user PTE is never set, so unpin_user_pages() releases the
> pages without marking them dirty. A file-backed destination page can then
> be reclaimed without writeback, silently discarding the copied data.
>
> Use unpin_user_pages_dirty_lock() with make_dirty=true so the modified
> pages are marked dirty before they are unpinned.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Hi Breno,
Thanks for following up with the Sashiko report. Since this is a bug fix, it should carry a fixes tag. This is a long
standing bug that's been present since the codes original appearance in a8c879a7ee98 ("RDS: Info and stats"). So it
should carry that in a fixes tag:
Fixes: a8c879a7ee98 ("RDS: Info and stats")
Other than that it looks fine to me. Thanks for catching this.
Allison
> ---
> net/rds/info.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/rds/info.c b/net/rds/info.c
> index f1b29994934a..17061f6ff74e 100644
> --- a/net/rds/info.c
> +++ b/net/rds/info.c
> @@ -235,7 +235,7 @@ int rds_info_getsockopt(struct socket *sock, int optname, char __user *optval,
>
> out:
> if (pages)
> - unpin_user_pages(pages, nr_pages);
> + unpin_user_pages_dirty_lock(pages, nr_pages, true);
> kfree(pages);
>
> return ret;
>
next prev parent reply other threads:[~2026-06-05 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 10:31 [PATCH net-next v2 0/3] net: rds: convert rds to getsockopt_iter Breno Leitao
2026-06-05 10:31 ` [PATCH net-next v2 1/3] rds: mark snapshot pages dirty in rds_info_getsockopt() Breno Leitao
2026-06-05 22:22 ` Allison Henderson [this message]
2026-06-05 10:31 ` [PATCH net-next v2 2/3] selftests: net: rds: add getsockopt() conversion test Breno Leitao
2026-06-05 22:30 ` Allison Henderson
2026-06-05 10:31 ` [PATCH net-next v2 3/3] rds: convert to getsockopt_iter Breno Leitao
2026-06-05 22:31 ` Allison Henderson
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=dea41eedebf284c2a57e75d1ca99b59a58863160.camel@kernel.org \
--to=achender@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=shuah@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
all inboxes | Powered by JetHome®