Linux kernel -stable discussions
 help / color / mirror / Atom feed
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 08:11:20 +0100	[thread overview]
Message-ID: <2025031710-mandarin-upbeat-22ff@gregkh> (raw)
In-Reply-To: <3fd37132-0162-43a3-9543-f26ecec9a7c0@eng.windriver.com>

On Mon, Mar 17, 2025 at 03:09:50PM +0800, Xiangyu Chen wrote:
> 
> On 3/17/25 14:57, Greg KH wrote:
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and know the content is safe.
> > 
> > On Mon, Mar 17, 2025 at 02:54:29PM +0800, Xiangyu Chen wrote:
> > > From: Qiao Ma <mqaio@linux.alibaba.com>
> > > 
> > > [ Upstream commit 373b9338c9722a368925d83bc622c596896b328e ]
> Hi Greg,
> > <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?
> 
> We try to backport the fix to 5.15/5.10, but some logic functions are
> different, the prepare_uprobe_buffer() in original
> 
> commit is not exists on 5.15/5.10,  we moved the fix to uprobe_dispatcher()
> and uretprobe_dispatcher().
> 
> It has been tested in our local environment, the issue was fixed, but due to
> it different from original commit,
> 
> this might still need to author help to review, so I added a RFC label.

If you want people to do reviews / work / etc, then you explicitly need
to ask for that.  Otherwise we all have no idea what problems you have
with this change, nor what you expect for anyone else to do.

First off, why do you think this needs to be backported here at all?  Do
that research and work first, and figure it out with your own testing
and evaluation before asking others to do any work for you.

good luck!

greg k-h

  reply	other threads:[~2025-03-17  7:12 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
2025-03-17  7:09   ` Xiangyu Chen
2025-03-17  7:11     ` Greg KH [this message]
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-mandarin-upbeat-22ff@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