public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Michael Bommarito <michael.bommarito@gmail.com>,
	"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Leon Romanovsky <leon@kernel.org>,
	Xiao Yang <yangx.jy@fujitsu.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: reject non-8-byte ATOMIC_WRITE payloads
Date: Sat, 18 Apr 2026 20:34:33 -0700	[thread overview]
Message-ID: <7176fdf5-55ed-4e95-ba15-52286975eccb@linux.dev> (raw)
In-Reply-To: <CAJJ9bXxd5jzzGcsf-sTw-v2zk-9Q0AtDrNwXRtyh-m5O9tr-6Q@mail.gmail.com>


在 2026/4/18 18:57, Michael Bommarito 写道:
> On Sat, Apr 18, 2026 at 7:18 PM Zhu Yanjun <yanjun.zhu@linux.dev> wrote:
>> The fix should stand on its own, and the test case can be added as a
>> follow-up patch under tools/testing/selftests/rdma (or rdma-core if more appropriate).
>> This keeps each patch focused on a single logical change and makes review easier.
> It seems like mainlining rdma tests might not be a good idea.  I found
> the last time here:
> Kamal Heib, 23 Oct 2019 — [PATCH for-next] selftests: rdma: Add rdma tests
>
> I put the tests here and will PR it into linux-rdma/rdma-core tomorrow:
> https://github.com/mjbommar/rdma-core/blob/4104d991a764de4aad9f645a2f0ec723f6076209/tests/test_rxe_atomic_write_oob.py

Thanks a lot. I am fine with the above link.

Zhu Yanjun

>
> Thanks,
> Mike Bommarito

-- 
Best Regards,
Yanjun.Zhu


      reply	other threads:[~2026-04-19  3:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18 16:21 [PATCH] RDMA/rxe: reject non-8-byte ATOMIC_WRITE payloads Michael Bommarito
2026-04-18 22:49 ` Zhu Yanjun
2026-04-18 23:11   ` Michael Bommarito
     [not found]     ` <1bd36ce7-e3dd-4ff5-867a-b8b9ade90a1e@linux.dev>
2026-04-19  1:57       ` Michael Bommarito
2026-04-19  3:34         ` Zhu Yanjun [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=7176fdf5-55ed-4e95-ba15-52286975eccb@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michael.bommarito@gmail.com \
    --cc=yangx.jy@fujitsu.com \
    --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