All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Bob Pearson <rpearsonhpe@gmail.com>, Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 2/3] RDMA/rxe: Replace write_lock_bh with write_lock_irqsave in __rxe_drop_index
Date: Sat, 12 Feb 2022 08:59:26 +0800	[thread overview]
Message-ID: <1452f4e8-454e-665e-4967-dc081efc1cb5@linux.dev> (raw)
In-Reply-To: <0bfd4e4f-0311-ed02-d23e-7bd5a2a9750b@gmail.com>



On 2/12/22 1:37 AM, Bob Pearson wrote:
> Guoqing,
>
> It would help to know more about the test setup you are using. I.e. which NIC/driver.
> I mostly test on head of tree and things seem to be working.

I runs a  5.17-rc3 inside VM which was configured with e1000e NIC, and 
the three calltraces
can be reproduced 100%, as said, CONFIG_PROVE_LOCKING is enabled.

Thanks,
Guoqing

  reply	other threads:[~2022-02-12  0:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  7:36 [PATCH 0/3] patches and bug report for rxe Guoqing Jiang
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 [this message]
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=1452f4e8-454e-665e-4967-dc081efc1cb5@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 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.