All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>, Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: 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 20:31:22 +0800	[thread overview]
Message-ID: <ff097539-3359-cf8a-14fd-7b0d460e8451@linux.dev> (raw)
In-Reply-To: <20220509115233.GI49344@nvidia.com>


在 2022/5/9 19:52, Jason Gunthorpe 写道:
> 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.


Can you explain "a hacky patch like that"?  Thanks.


>   
>> 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?

The oops is like the following:

[   36.700281] Call Trace:

[   36.700285]  <TASK>
[   36.700291]  dump_stack_lvl+0x70/0xa0
[   36.700323]  dump_stack+0x10/0x12
[   36.700329]  __might_resched.cold+0x102/0x13a
[   36.700350]  __might_sleep+0x43/0x70
[   36.700368]  wait_for_completion_timeout+0x40/0x160
[   36.700373]  ? _raw_spin_unlock_irqrestore+0x4f/0x80
[   36.700381]  ? complete+0x4c/0x60
[   36.700403]  __rxe_cleanup+0xaf/0xc0 [rdma_rxe]
[   36.700431]  rxe_destroy_ah+0x12/0x20 [rdma_rxe]
[   36.700440]  rdma_destroy_ah_user+0x3a/0x80 [ib_core]
[   36.700464]  cm_free_priv_msg+0x44/0xf0 [ib_cm]
[   36.700477]  cm_send_handler+0x10b/0x2f0 [ib_cm]
[   36.700510]  timeout_sends+0x1aa/0x230 [ib_core]
[   36.700544]  process_one_work+0x2a9/0x5e0
[   36.700567]  worker_thread+0x4d/0x3c0
[   36.700582]  ? process_one_work+0x5e0/0x5e0
[   36.700588]  kthread+0x10a/0x130
[   36.700594]  ? kthread_complete_and_exit+0x20/0x20
[   36.700604]  ret_from_fork+0x22/0x30

[   36.700650]  </TASK>

Zhu Yanjun

>
> Jason

  reply	other threads:[~2022-05-09 12:31 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
2022-05-09 12:31           ` Yanjun Zhu [this message]
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=ff097539-3359-cf8a-14fd-7b0d460e8451@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=bmt@zurich.ibm.com \
    --cc=bvanassche@acm.org \
    --cc=jgg@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.