From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
Leon Romanovsky <leon@kernel.org>,
zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
matsuda-daisuke@fujitsu.com, shinichiro.kawasaki@wdc.com,
linux-scsi@vger.kernel.org, Zhu Yanjun <yanjun.zhu@intel.com>
Cc: Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCH 1/1] Revert "RDMA/rxe: Add workqueue support for rxe tasks"
Date: Tue, 26 Sep 2023 13:34:02 -0500 [thread overview]
Message-ID: <b7b365e3-dd11-bc66-dace-05478766bf41@gmail.com> (raw)
In-Reply-To: <d3c05064-a88b-4719-a390-6bf9ae01fba5@acm.org>
On 9/26/23 12:05, Bart Van Assche wrote:
> On 9/26/23 07:06, Leon Romanovsky wrote:
>> On Tue, Sep 26, 2023 at 12:43:57PM +0300, Leon Romanovsky wrote:
>>>
>>> On Fri, 22 Sep 2023 12:32:31 -0400, Zhu Yanjun wrote:
>>>> This reverts commit 9b4b7c1f9f54120940e243251e2b1407767b3381.
>>>>
>>>> This commit replaces tasklet with workqueue. But this results
>>>> in occasionally pocess hang at the blktests test case srp/002.
>>>> After the discussion in the link[1], this commit is reverted.
>>>>
>>>>
>>>> [...]
>>>
>>> Applied, thanks!
>>>
>>> [1/1] Revert "RDMA/rxe: Add workqueue support for rxe tasks"
>>> https://git.kernel.org/rdma/rdma/c/e710c390a8f860
>>
>> I applied this patch, but will delay it for some time with a hope that
>> fix will arrive in the near future.
>
> Thank you Leon. With this revert applied on top of the rdma for-next branch, I
> don't see the KASAN complaint anymore that I reported yesterday. I think this
> is more evidence that the KASAN complaint was caused by the RXE driver.
>
> Bart.
Bart,
I am working to try to reproduce the KASAN warning. Unfortunately, so far I am not able to see it
in Ubuntu + Linus' kernel (as you described) on metal. The config file is different but copies
the CONFIG_KASAN_xxx exactly as yours. With KASAN enabled it hangs on every iteration of srp/002
but without a KASAN warning. I am now building an openSuSE VM for qemu and will see if that
causes the warning.
Thanks for the support,
Bob
next prev parent reply other threads:[~2023-09-26 18:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 16:32 [PATCH 1/1] Revert "RDMA/rxe: Add workqueue support for rxe tasks" Zhu Yanjun
2023-09-22 16:42 ` Bart Van Assche
2023-09-26 9:43 ` Leon Romanovsky
2023-09-26 9:43 ` Leon Romanovsky
2023-09-26 14:06 ` Leon Romanovsky
2023-09-26 17:05 ` Bart Van Assche
2023-09-26 18:34 ` Bob Pearson [this message]
2023-09-26 20:24 ` Bart Van Assche
2023-09-27 0:08 ` Rain River
2023-09-27 16:36 ` Bob Pearson
2023-09-27 16:51 ` Bob Pearson
2023-10-01 6:30 ` Leon Romanovsky
2023-10-04 17:44 ` Bart Van Assche
2023-10-04 3:41 ` Zhu Yanjun
2023-10-04 17:43 ` Bart Van Assche
2023-10-04 18:38 ` Jason Gunthorpe
2023-10-05 9:25 ` Zhu Yanjun
2023-10-05 14:21 ` Jason Gunthorpe
2023-10-05 14:50 ` Bart Van Assche
2023-10-05 15:56 ` Jason Gunthorpe
2023-10-06 15:58 ` Bob Pearson
2023-10-07 0:35 ` Zhu Yanjun
2023-10-08 16:01 ` Zhu Yanjun
2023-10-08 17:09 ` Leon Romanovsky
2023-10-10 4:53 ` Daisuke Matsuda (Fujitsu)
2023-10-10 16:09 ` Jason Gunthorpe
2023-10-10 21:29 ` Bart Van Assche
2023-10-11 15:51 ` Jason Gunthorpe
2023-10-11 20:14 ` Bart Van Assche
2023-10-11 23:12 ` Jason Gunthorpe
2023-10-12 11:49 ` Zhu Yanjun
2023-10-12 15:38 ` Bob Pearson
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=b7b365e3-dd11-bc66-dace-05478766bf41@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yanjun.zhu@intel.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).