From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: zyjzyj2000@gmail.com, jgg@ziepe.ca, rpearsonhpe@gmail.com
Cc: linux-rdma@vger.kernel.org
Subject: [PATCH 0/3] patches and bug report for rxe
Date: Thu, 10 Feb 2022 15:36:52 +0800 [thread overview]
Message-ID: <20220210073655.42281-1-guoqing.jiang@linux.dev> (raw)
Hi,
Recently, I am trying to run rnbd/rtrs on top of rxe, and get several
calltraces with 5.17-rc3 kernel (CONFIG_PROVE_LOCKING is enabled).
However, seems rnbd/rtrs over rxe still can't work with 5.17-rc3 kernel,
dmesg reports below.
1. server side
[ 440.723182] rdma_rxe: qp#17 moved to error state
[ 440.725300] rtrs_server L1205: <bla>: remote access error (wr_cqe: 000000003b14397c, type: 0, vendor_err: 0x0, len: 0)
[ 440.845926] rnbd_server L256: RTRS Session bla disconnected
2. client side
[ 997.817536] rnbd_client L596: Mapping device /dev/loop1 on session bla, (access_mode: rw, nr_poll_queues: 0)
[ 998.968810] rnbd_client L1213: [session=bla] mapped 8/8 default/read queues.
[ 999.017988] rtrs_client L610: <bla>: RDMA failed: remote access error
[ 1029.836943] rtrs_client L353: <bla>: Failed IB_WR_LOCAL_INV: WR flushe
Then I tried 5.16 and 5.15 version, seems 5.15 does work as follows.
1. server side
[ 333.076482] rnbd_server L800: </dev/loop1@bla>: Opened device 'loop1'
2. client side
[ 1584.325825] rnbd_client L596: Mapping device /dev/loop1 on session bla, (access_mode: rw, nr_poll_queues: 0)
[ 1585.268291] rnbd_client L1213: [session=bla] mapped 8/8 default/read queues.
[ 1585.349300] rnbd_client L1607: </dev/loop1@bla> map_device: Device mapped as rnbd0 (nsectors: 0, logical_block_size: 512, physical_block_size: 512, max_write_same_sectors: 0, max_discard_sectors: 0, discard_granularity: 0, discard_alignment: 0, secure_discard: 0, max_segments: 128, max_hw_sectors: 248, rotational: 1, wc: 0, fua: 0)
I would appreciate if someone shed light on why it doesn't work after 5.15,
And I am happy to test potential patch for it.
Guoqing Jiang (3):
RDMA/rxe: Replace write_{lock,unlock}_bh with
write_lock_irq{save,restore} in __rxe_add_index
RDMA/rxe: Replace write_{lock,unlock}_bh with
write_lock_irq{save,restore} in __rxe_drop_index
RDMA/rxe: Replace write_{lock,unlock}_bh with
write_lock_irq{save,restore} in post_one_send
drivers/infiniband/sw/rxe/rxe_pool.c | 10 ++++++----
drivers/infiniband/sw/rxe/rxe_verbs.c | 5 +++--
2 files changed, 9 insertions(+), 6 deletions(-)
--
2.26.2
next reply other threads:[~2022-02-10 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:36 Guoqing Jiang [this message]
2022-02-10 7:36 ` [PATCH 1/3] RDMA/rxe: Replace write_lock_bh with write_lock_irqsave in __rxe_add_index Guoqing Jiang
2022-02-10 13:29 ` Zhu Yanjun
2022-02-10 7:36 ` [PATCH 2/3] RDMA/rxe: Replace write_lock_bh with write_lock_irqsave in __rxe_drop_index Guoqing Jiang
2022-02-10 14:16 ` Zhu Yanjun
2022-02-10 15:49 ` Bob Pearson
2022-02-11 10:09 ` Guoqing Jiang
2022-02-11 17:37 ` Bob Pearson
2022-02-12 0:59 ` Guoqing Jiang
2022-02-10 7:36 ` [PATCH 3/3] RDMA/rxe: Replace spin_lock_bh with spin_lock_irqsave in post_one_send Guoqing Jiang
2022-02-10 14:18 ` Zhu Yanjun
2022-02-22 9:50 ` bug report for rxe Guoqing Jiang
2022-02-22 10:04 ` Zhu Yanjun
2022-02-22 16:58 ` Pearson, Robert B
2022-02-23 4:43 ` Guoqing Jiang
2022-02-23 5:01 ` Bob Pearson
2022-02-23 5:50 ` Guoqing Jiang
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=20220210073655.42281-1-guoqing.jiang@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=jgg@ziepe.ca \
--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).