linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
	syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com
Subject: Re: [PATCHv3 1/1] RDMA/rxe: Fix qp error handler
Date: Sat, 30 Jul 2022 22:01:51 +0800	[thread overview]
Message-ID: <37d1ec16-e642-eaa8-3aa1-35317c17ce28@linux.dev> (raw)
In-Reply-To: <YuK7lpdGA3e+1jBs@nvidia.com>


在 2022/7/29 0:38, Jason Gunthorpe 写道:
> On Tue, Jul 26, 2022 at 12:56:31AM -0400, yanjun.zhu@linux.dev wrote:
>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>>
>> About 7 spin locks in qp creation needs to be initialized. Now these
>> spin locks are initialized in the function rxe_qp_init_misc. This
>> will avoid the error "initialize spin locks before use".
> Explain the problem completely please, is this triggered in an error
> unwind case?
>   
>> Reported-by: syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com

In this link 
news://nntp.lore.kernel.org:119/0000000000006ed46805dfaded18@google.com,

"

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com
"
Zhu Yanjun

> This isn't the right format for reported by
>
> Jason

      parent reply	other threads:[~2022-07-30 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  4:56 [PATCHv3 1/1] RDMA/rxe: Fix qp error handler yanjun.zhu
2022-07-27  9:16 ` Leon Romanovsky
2022-07-27 12:38   ` Yanjun Zhu
2022-07-28 16:38 ` Jason Gunthorpe
2022-07-30 13:14   ` Yanjun Zhu
2022-07-30 14:01   ` Yanjun Zhu [this message]

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=37d1ec16-e642-eaa8-3aa1-35317c17ce28@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=syzbot+833061116fa28df97f3b@syzkaller.appspotmail.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).