From: "Yanjun.Zhu" <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>, Yi Liu <asatsuyu.liu@gmail.com>
Cc: linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] RDMA/rxe: fix null deref on srq->rq.queue after resize failure
Date: Mon, 27 Oct 2025 09:56:18 -0700 [thread overview]
Message-ID: <eb232c55-1307-473e-8620-4e277f28be4a@linux.dev> (raw)
In-Reply-To: <20251027133053.GK12554@unreal>
On 10/27/25 6:30 AM, Leon Romanovsky wrote:
>> err_free:
>> - rxe_queue_cleanup(q);
>> - srq->rq.queue = NULL;
>> return err;
>> }
> This patch is badly formatted and doesn't apply.
Sorry. I will send a new patch very soon.
Yanjun.Zhu
>
> Applying: RDMA/rxe: fix null deref on srq->rq.queue after resize failure
> Patch failed at 0001 RDMA/rxe: fix null deref on srq->rq.queue after resize failure
> error: git diff header lacks filename information when removing 1 leading pathname component (line 6)
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> hint: When you have resolved this problem, run "git am --continue".
> hint: If you prefer to skip this patch, run "git am --skip" instead.
> hint: To restore the original branch and stop patching, run "git am --abort".
> hint: Disable this message with "git config set advice.mergeConflict false"
> Press any key to continue...
>
>
>> --
>> 2.34.1
next prev parent reply other threads:[~2025-10-27 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 2:20 [PATCH] RDMA/rxe: fix null deref on srq->rq.queue after resize failure Yi Liu
2025-10-21 3:48 ` Zhu Yanjun
2025-10-21 13:42 ` Junxian Huang
2025-10-21 18:06 ` yanjun.zhu
2025-10-27 13:30 ` Leon Romanovsky
2025-10-27 16:56 ` Yanjun.Zhu [this message]
2025-10-28 2:31 ` Yi Liu
2025-10-28 4:19 ` Zhu Yanjun
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=eb232c55-1307-473e-8620-4e277f28be4a@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=asatsuyu.liu@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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