From: Greg KH <gregkh@linuxfoundation.org>
To: Xiangyu Chen <xiangyu.chen@eng.windriver.com>
Cc: mqaio@linux.alibaba.com, mhiramat@kernel.org,
stable@vger.kernel.org, zhe.he@windriver.com
Subject: Re: [RFC PATCH 5.15/5.10] uprobe: avoid out-of-bounds memory access of fetching args
Date: Mon, 17 Mar 2025 07:57:38 +0100 [thread overview]
Message-ID: <2025031710-plexiglas-siding-d0e8@gregkh> (raw)
In-Reply-To: <20250317065429.490373-1-xiangyu.chen@eng.windriver.com>
On Mon, Mar 17, 2025 at 02:54:29PM +0800, Xiangyu Chen wrote:
> From: Qiao Ma <mqaio@linux.alibaba.com>
>
> [ Upstream commit 373b9338c9722a368925d83bc622c596896b328e ]
<snip>
Why is this an RFC? What needs to be done to make it "real" and ready
for you to submit it for actual inclusion?
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-17 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 6:54 [RFC PATCH 5.15/5.10] uprobe: avoid out-of-bounds memory access of fetching args Xiangyu Chen
2025-03-17 6:57 ` Greg KH [this message]
2025-03-17 7:09 ` Xiangyu Chen
2025-03-17 7:11 ` Greg KH
2025-03-17 8:01 ` Xiangyu Chen
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=2025031710-plexiglas-siding-d0e8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=mhiramat@kernel.org \
--cc=mqaio@linux.alibaba.com \
--cc=stable@vger.kernel.org \
--cc=xiangyu.chen@eng.windriver.com \
--cc=zhe.he@windriver.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