linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: v5.14 RXE driver broken?
Date: Wed, 25 Aug 2021 09:46:58 -0700	[thread overview]
Message-ID: <98fb7274-8563-e54b-3c6d-c99d3f3e68bf@acm.org> (raw)
In-Reply-To: <CAD=hENcriq-mwnvzY3UdowuGpKb=Uekvk-v8Lj0G=QB-qK0kJg@mail.gmail.com>

On 8/24/21 8:02 PM, Zhu Yanjun wrote:
> On Tue, Aug 24, 2021 at 11:02 AM Bart Van Assche <bvanassche@acm.org> wrote:
>>
>> Hi Bob,
>>
>> If I run the following test against Linus' master branch then that test
>> passes (commit d5ae8d7f85b7 ("Revert "media: dvb header files: move some
>> headers to staging"")):
>>
>> # export use_siw=1 && modprobe brd && (cd blktests && ./check -q srp/002)
>> srp/002 (File I/O on top of multipath concurrently with logout and login (mq)) [passed]
>>      runtime    ...  48.849s
>>
>> The following test fails:
>>
>> # export use_siw= && modprobe brd && (cd blktests && ./check -q srp/002)
>> srp/002 (File I/O on top of multipath concurrently with logout and login (mq)) [failed]
>>      runtime  48.849s  ...  15.024s
>>      --- tests/srp/002.out       2018-09-08 19:43:42.291664821 -0700
>>      +++ /home/bart/software/blktests/results/nodev/srp/002.out.bad      2021-08-23 19:51:05.182958728 -0700
>>      @@ -1,2 +1 @@
>>       Configured SRP target driver
>>      -Passed
> 
> Can this commit "RDMA/rxe: Zero out index member of struct rxe_queue"
> in the link https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=wip/jgg-for-rc
> fix this problem?
> 
> And the commit will be merged into linux upstream very soon.

Hi Zhu,

Thanks for having taken a look.

Isn't commit cc4f596cf85e ("RDMA/rxe: Zero out index member of struct
rxe_queue") already in Linus' tree? I think it was merged yesterday (August
24). Unfortunately the test I mentioned still fails on top of that patch.

Thanks,

Bart.


      parent reply	other threads:[~2021-08-25 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24  3:01 v5.14 RXE driver broken? Bart Van Assche
2021-08-25  3:02 ` Zhu Yanjun
2021-08-25 16:32   ` Jason Gunthorpe
2021-08-25 18:03     ` Bob Pearson
2021-08-25 18:22     ` Bart Van Assche
2021-08-25 20:58       ` Bart Van Assche
2021-08-25 21:09         ` Bob Pearson
2021-08-25 21:44           ` Bart Van Assche
2021-08-26 19:03     ` Bob Pearson
2021-08-26 20:03       ` Bob Pearson
2021-08-27  3:18       ` Zhu Yanjun
2021-08-25 16:46   ` Bart Van Assche [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=98fb7274-8563-e54b-3c6d-c99d3f3e68bf@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.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;
as well as URLs for NNTP newsgroup(s).