public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Cc: ilubashe@akamai.com, stable-commits@vger.kernel.org
Subject: Re: Patch "perf ftrace: Use CAP_SYS_ADMIN instead of euid==0" has been added to the 5.3-stable tree
Date: Thu, 3 Oct 2019 09:50:06 +0200	[thread overview]
Message-ID: <20191003075006.GA1830608@kroah.com> (raw)
In-Reply-To: <20191001171555.9CBC6205C9@mail.kernel.org>

On Tue, Oct 01, 2019 at 01:15:54PM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     perf ftrace: Use CAP_SYS_ADMIN instead of euid==0
> 
> to the 5.3-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      perf-ftrace-use-cap_sys_admin-instead-of-euid-0.patch
> and it can be found in the queue-5.3 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 
> 
> 
> commit 54a277c389061fc501624f51a13426d7b797f5f7
> Author: Igor Lubashev <ilubashe@akamai.com>
> Date:   Wed Aug 7 10:44:17 2019 -0400
> 
>     perf ftrace: Use CAP_SYS_ADMIN instead of euid==0
>     
>     [ Upstream commit c766f3df635de14295e410c6dd5410bc416c24a0 ]


Sasha, this patch is breaking the build of perf in the stable branches.
Can you fix it up, or drop it?

thanks,

greg k-h

       reply	other threads:[~2019-10-03  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191001171555.9CBC6205C9@mail.kernel.org>
2019-10-03  7:50 ` Greg KH [this message]
2019-10-03 15:10   ` Patch "perf ftrace: Use CAP_SYS_ADMIN instead of euid==0" has been added to the 5.3-stable tree Lubashev, Igor
2019-10-03 15:34     ` Greg KH

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=20191003075006.GA1830608@kroah.com \
    --to=greg@kroah.com \
    --cc=ilubashe@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-commits@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