From: Jason Gunthorpe <jgg@nvidia.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Yanjun Zhu <yanjun.zhu@linux.dev>,
Bart Van Assche <bvanassche@acm.org>,
Bob Pearson <rpearsonhpe@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Bernard Metzler <bmt@zurich.ibm.com>
Subject: Re: Apparent regression in blktests since 5.18-rc1+
Date: Mon, 9 May 2022 08:52:33 -0300 [thread overview]
Message-ID: <20220509115233.GI49344@nvidia.com> (raw)
In-Reply-To: <CAD=hENd1kTsy42qDmMjcAhB_rO7aa7eP-G377R2DDE7qkqRB3Q@mail.gmail.com>
On Mon, May 09, 2022 at 04:01:19PM +0800, Zhu Yanjun wrote:
> I delved into the above calltrace. It is the same with the problem in
> the link https://www.spinics.net/lists/linux-rdma/msg109875.html
Yes
> So IMHO, the fix in this link
> https://patchwork.kernel.org/project/linux-rdma/patch/20220422194416.983549-1-yanjun.zhu@linux.dev/
> should fix this problem.
I'm not going to apply a hacky patch like that, it needs proper fixing.
> And if we want to use BH, it is very possible that the problem in the
> link https://patchwork.kernel.org/project/linux-rdma/patch/20220210073655.42281-4-guoqing.jiang@linux.dev/
> will occur.
>
> And to the RCU patch series in the link
> https://patchwork.kernel.org/project/linux-rdma/patch/20220421014042.26985-2-rpearsonhpe@gmail.com/
> I also delved into this patch series. And I found that an atomic
> problem will occur if we apply RCU patches onto V5.18-rc5.
> And because of the atomic problem, I can not verify that this RCU
> patches can fix this problem currently.
What is the oops?
Jason
next prev parent reply other threads:[~2022-05-09 11:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 18:11 Apparent regression in blktests since 5.18-rc1+ Bob Pearson
2022-05-07 0:10 ` Bart Van Assche
2022-05-07 0:29 ` Yanjun Zhu
2022-05-07 1:29 ` Jason Gunthorpe
2022-05-07 1:55 ` Yanjun Zhu
2022-05-07 13:43 ` Bob Pearson
2022-05-08 4:13 ` Bart Van Assche
2022-05-10 15:24 ` Pearson, Robert B
2022-05-12 21:57 ` Bob Pearson
2022-05-12 22:25 ` Bart Van Assche
2022-05-13 0:41 ` Bob Pearson
2022-05-13 3:40 ` Bart Van Assche
2022-05-17 15:21 ` Bob Pearson
2022-05-17 20:44 ` Bart Van Assche
2022-05-17 20:54 ` Bob Pearson
2022-05-17 20:59 ` Bob Pearson
2022-05-08 8:43 ` Yanjun Zhu
2022-05-09 8:01 ` Zhu Yanjun
2022-05-09 11:52 ` Jason Gunthorpe [this message]
2022-05-09 12:31 ` Yanjun Zhu
2022-05-09 12:33 ` Jason Gunthorpe
2022-05-09 12:42 ` Yanjun Zhu
2022-05-07 13:40 ` Bob Pearson
2022-05-09 6:56 ` Thorsten Leemhuis
2022-05-10 3:53 ` Bart Van Assche
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=20220509115233.GI49344@nvidia.com \
--to=jgg@nvidia.com \
--cc=bmt@zurich.ibm.com \
--cc=bvanassche@acm.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@linux.dev \
--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).