From: bo cao <treebacker@foxmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, srini@kernel.org, stable@vger.kernel.org
Subject: Re: fastrpc: use-after-free of fastrpc_invoke_ctx on duplicate glink responses in fastrpc_rpmsg_callback()
Date: Fri, 30 Oct 2026 16:55:24 +0800 [thread overview]
Message-ID: <tencent_D3A2B2E77AFCC54558476B28B595A9AB3A05@qq.com> (raw)
In-Reply-To: <2026103041-handrail-civic-a9fa@gregkh>
Hi Greg,
> These two messages are not "threaded" properly, sent as 2 separate
> emails. Is that intentional? It breaks our tooling :(
Not intentional -- I sent them individually instead of as a series.
Sorry about that. Resent as a properly threaded [PATCH v2 0/2]
series with git send-email (no code changes):
0/2: https://lore.kernel.org/all/tencent_AE37F59DA9A6DAB192F6BAFD054E584FAB05@qq.com/
1/2: https://lore.kernel.org/all/tencent_E9BD7808AB6A2DA5FA326D547F57D65D270A@qq.com/
2/2: https://lore.kernel.org/all/tencent_C7D71E2F51C2195A0CA91A4C11D51B957708@qq.com/
Thanks,
bo cao
prev parent reply other threads:[~2026-10-30 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:19 [PATCH 1/2] misc: fastrpc: pin invoke context at glink response lookup bo cao
2026-10-30 8:39 ` Greg KH
2026-10-30 8:55 ` bo cao [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=tencent_D3A2B2E77AFCC54558476B28B595A9AB3A05@qq.com \
--to=treebacker@foxmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®