From: Leon Romanovsky <leon@kernel.org>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"jhack@hpe.com" <jhack@hpe.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v5 for-next 1/2] RDMA/rxe: Set pd early in mr alloc routines
Date: Wed, 31 Aug 2022 11:46:01 +0300 [thread overview]
Message-ID: <Yw8fyUD0HK0Z6YEb@unreal> (raw)
In-Reply-To: <2124b2b6-8fd9-64a3-5c66-3e7ef7565606@fujitsu.com>
On Wed, Aug 31, 2022 at 04:05:57PM +0800, Li Zhijian wrote:
> Leon,
>
>
> On 31/08/2022 14:26, Leon Romanovsky wrote:
> > On Wed, Aug 31, 2022 at 01:48:08PM +0800, Li Zhijian wrote:
> > > BTW: this patch should be for-rc instead.
> > It can't be in -rc without Fixes line and more clear description.
>
> Fixes: cf40367961d8 ("RDMA/rxe: Move mr cleanup code to rxe_mr_cleanup()") ?
>
> IIRC, This patch fixes a kernel crash newly introduced by v6.0 merge window
> it's an alternative for my former patch: https://lore.kernel.org/all/42ec06bb-9e97-3b43-5fb9-9801407d301e@fujitsu.com/
> So if you agree it should go to for-rc, does Bob need to repost a new one with more details ?
Yes, please, especially kernel panic.
>
>
> >
> > Thanks
>
next prev parent reply other threads:[~2022-08-31 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 18:35 [PATCH v5 for-next 1/2] RDMA/rxe: Set pd early in mr alloc routines Bob Pearson
2022-08-22 5:46 ` lizhijian
2022-08-31 5:48 ` Li Zhijian
2022-08-31 6:26 ` Leon Romanovsky
2022-08-31 8:05 ` Li Zhijian
2022-08-31 8:46 ` Leon Romanovsky [this message]
2022-08-31 6:31 ` Leon Romanovsky
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=Yw8fyUD0HK0Z6YEb@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=jhack@hpe.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--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.