From: Norbert Szetei <norbert@doyensec.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org, Zhu Yanjun <zyjzyj2000@gmail.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Reject prefetch of a non-ODP MR
Date: Sun, 13 Sep 2026 13:53:17 +0200 [thread overview]
Message-ID: <744A1792-201E-4D0F-B423-4D4EDDD3DF72@doyensec.com> (raw)
In-Reply-To: <20260906090149.GB13683@unreal>
On Sep 6, 2026, at 11:01, Leon Romanovsky <leon@kernel.org> wrote:
>>>
>> Do you mean lookup_mr() should take IB_ACCESS_ON_DEMAND into account, so that
>> the existing (access & mr->access) != access test rejects the non-ODP MR?
>
> I expected lookup_mr(..., IB_ACCESS_ON_DEMAND) to be called and to
> perform all the necessary checks internally.
Done in v2.
>> rxe_rereg_user_mr() with IB_MR_REREG_ACCESS assigns mr->access directly, and
>> IB_ACCESS_ON_DEMAND is part of RXE_ACCESS_SUPPORTED_MR. So userspace can set
>> that flag on a plain MR after registration, without the umem changing. Am I
>> missing something there?
>
> I assume this is a bug that needs to be fixed.
OK, I just sent the series that includes that too. It depends on ae36a5b609ae
("RDMA/rxe: validate access flags before swapping the MR's PD"), which moved
the validation above the mr->ibmr.pd swap. v2 is based on for-rc.
N.
> Thanks
>
>>
>> Thanks.
>>
>>>
>>> Thanks.
prev parent reply other threads:[~2026-09-13 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 10:51 Norbert Szetei
2026-08-27 19:12 ` Zhu Yanjun
2026-09-01 7:56 ` Leon Romanovsky
2026-09-04 7:49 ` Norbert Szetei
2026-09-06 9:01 ` Leon Romanovsky
2026-09-13 11:53 ` Norbert Szetei [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=744A1792-201E-4D0F-B423-4D4EDDD3DF72@doyensec.com \
--to=norbert@doyensec.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@gmail.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
all inboxes | Powered by JetHome®