Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: cixi.geng@linux.dev
Cc: peterz@infradead.org, stable@vger.kernel.org, enlin.mu@unisoc.com
Subject: Re: [PATCH] perf: Fix function pointer case
Date: Fri, 4 Aug 2023 12:42:50 +0200	[thread overview]
Message-ID: <2023080443-lance-bolt-0e7b@gregkh> (raw)
In-Reply-To: <840c9ebf1d741de735b3a1d882364ff0f3904bdd@linux.dev>

On Thu, Aug 03, 2023 at 01:28:32AM +0000, cixi.geng@linux.dev wrote:
> 2023年8月2日 19:47, "Greg KH" <gregkh@linuxfoundation.org> 写到:
> 
> 
> > 
> > On Wed, Aug 02, 2023 at 07:40:53PM +0800, Cixi Geng wrote:
> > 
> > > 
> > > From: Peter Zijlstra <peterz@infradead.org>
> > >  
> > >  commit 1af6239d1d3e61d33fd2f0ba53d3d1a67cc50574 upstream.
> > >  With the advent of CFI it is no longer acceptible to cast function
> > >  pointers.
> > >  
> > >  The robot complains thusly:
> > >  
> > >  kernel-events-core.c:warning:cast-from-int-(-)(struct-perf_cpu_pmu_context-)-to-remote_function_f-(aka-int-(-)(void-)-)-converts-to-incompatible-function-type
> > >  
> > >  Reported-by: kernel test robot <lkp@intel.com>
> > >  Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > >  Signed-off-by: Cixi Geng <cixi.geng1@unisoc.com>
> > >  ---
> > >  kernel/events/core.c | 8 ++++++--
> > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > > 
> > 
> > What stable tree(s) is this for?
> >
> Hi Greg
> I want to apply this patch for linux-5.15-y and linux-6.1-y, 
> the other stable trees not requred for me, thanks!

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-08-04 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 11:40 [PATCH] perf: Fix function pointer case Cixi Geng
2023-08-02 11:47 ` Greg KH
2023-08-03  1:28   ` cixi.geng
2023-08-04 10:42     ` Greg KH [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=2023080443-lance-bolt-0e7b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cixi.geng@linux.dev \
    --cc=enlin.mu@unisoc.com \
    --cc=peterz@infradead.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