linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"selinux@vger.kernel.org" <selinux@vger.kernel.org>,
	"linux-security-module@vger.kernel.org" 
	<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] perf docs: introduce security.txt file to document related issues
Date: Mon, 18 May 2020 19:50:21 +0300	[thread overview]
Message-ID: <1f6eb4c7-dec1-355c-024e-8405f4ef7f3e@linux.intel.com> (raw)
In-Reply-To: <20200518155936.GG24211@kernel.org>


On 18.05.2020 18:59, Arnaldo Carvalho de Melo wrote:
> Em Thu, Apr 30, 2020 at 10:16:34AM +0300, Alexey Budankov escreveu:
>>
>> Publish instructions on how to apply LSM hooks for access control
>> to perf_event_open() syscall on Fedora distro with Targeted SELinux
>> policy and then manage access to the syscall.
> 
> I'm fixing these up:
> 
> [acme@five perf]$ am /wb/1.patch
> Applying: perf docs: introduce security.txt file to document related issues
> .git/rebase-apply/patch:46: space before tab in indent.
>  	wake_alarm
> .git/rebase-apply/patch:47: space before tab in indent.
>  	block_suspend
> .git/rebase-apply/patch:48: space before tab in indent.
>  	audit_read
> .git/rebase-apply/patch:51: trailing whitespace.
> 
> .git/rebase-apply/patch:54: trailing whitespace.

This is output of diff utility.
Hopefully it is still applicable after fixes.
I will test this either jointly with the changes at 2/3.

Thanks,
Alexey

  reply	other threads:[~2020-05-18 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  7:06 [PATCH v3 0/3] perf: make Perf tool aware of SELinux access control Alexey Budankov
2020-04-30  7:15 ` [PATCH v3 1/3] perf docs: extend CAP_SYS_ADMIN with CAP_PERFMON where needed Alexey Budankov
2020-04-30  7:15 ` [PATCH v3 2/3] perf tool: make Perf tool aware of SELinux access control Alexey Budankov
2020-05-18 15:58   ` Arnaldo Carvalho de Melo
2020-05-18 16:43     ` Alexey Budankov
2020-05-19  7:34       ` Alexey Budankov
2020-05-19 18:10         ` Arnaldo Carvalho de Melo
2020-04-30  7:16 ` [PATCH v3 3/3] perf docs: introduce security.txt file to document related issues Alexey Budankov
2020-05-18 15:59   ` Arnaldo Carvalho de Melo
2020-05-18 16:50     ` Alexey Budankov [this message]
2020-05-18 17:06       ` Arnaldo Carvalho de Melo
2020-05-18  8:07 ` [PATCH v3 0/3] perf: make Perf tool aware of SELinux access control Alexey Budankov
  -- strict thread matches above, loose matches on Subject: below --
2020-04-24  6:45 Alexey Budankov
2020-04-24  6:51 ` [PATCH v3 3/3] perf docs: introduce security.txt file to document related issues Alexey Budankov

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=1f6eb4c7-dec1-355c-024e-8405f4ef7f3e@linux.intel.com \
    --to=alexey.budankov@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=selinux@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;
as well as URLs for NNTP newsgroup(s).