From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
yanjun.zhu@linux.dev, Jinpu Wang <jinpu.wang@ionos.com>
Subject: Re: Encountering errors while using RNBD over rxe for v5.14
Date: Thu, 5 May 2022 11:46:24 +0800 [thread overview]
Message-ID: <df08efe8-5914-e64b-3c18-4b5f906fcea1@linux.dev> (raw)
In-Reply-To: <CAJpMwyhuOOgub4xxd6nB64c37yC82ogZCX4LB6WkUb721odLjQ@mail.gmail.com>
On 5/4/22 10:22 PM, Haris Iqbal wrote:
>
>>> We observe the following error,
>>>
>>> [Fri Mar 25 19:08:03 2022] rtrs_client L353: <blya>: Failed
>>> IB_WR_LOCAL_INV: WR flushed
>>> [Fri Mar 25 19:08:03 2022] rtrs_client L333: <blya>: Failed
>>> IB_WR_REG_MR: WR flushed
>>> [Fri Mar 25 19:08:03 2022] rtrs_client L333: <blya>: Failed
>>> IB_WR_REG_MR: WR flushed
>>> [Fri Mar 25 19:08:34 2022] rtrs_client L353: <blya>: Failed
>>> IB_WR_LOCAL_INV: WR flushed
>>> [Fri Mar 25 19:08:34 2022] rtrs_client L353: <blya>:*Failed IB_WR_LOCAL_INV: WR flushed*
>> I got similar message but I am not certain it is the same one, pls see
>> the previous report,
>>
>> https://lore.kernel.org/linux-rdma/20220210073655.42281-1-guoqing.jiang@linux.dev/
> I went through the emails, and the error looks similar but I am not
> sure if its related. The change to write_lock_bh was done after v5.14
> I think, and the code where I am seeing this error still has irq
> versions of those lock (e.g. write_lock_irqsave).
The lock is irrelevant, pls check
https://lore.kernel.org/linux-rdma/473a53b6-9ab2-0d48-a9cf-c84b8dc4c3f3@linux.dev/
and
https://lore.kernel.org/linux-rdma/3b6ddb23-6dfa-29e2-27fd-741c1e3e576d@linux.dev/
But I am not certain it is the same issue.
Thanks,
Guoqing
next prev parent reply other threads:[~2022-05-05 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 10:28 Encountering errors while using RNBD over rxe for v5.14 Haris Iqbal
2022-04-27 11:49 ` Haris Iqbal
2022-04-29 8:26 ` Guoqing Jiang
2022-05-04 14:22 ` Haris Iqbal
2022-05-05 3:46 ` Guoqing Jiang [this message]
2022-05-05 11:20 ` Haris Iqbal
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=df08efe8-5914-e64b-3c18-4b5f906fcea1@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
/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