From: Markus Elfring <Markus.Elfring@web.de>
To: Howard Chu <howardchu95@gmail.com>,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-security-module@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
"Günther Noack" <gnoack@google.com>,
"Ian Rogers" <irogers@google.com>,
"Ingo Molnar" <mingo@redhat.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Namhyung Kim" <namhyung@kernel.org>
Subject: Re: [PATCH] perf trace: Fix syscall untraceable bug
Date: Sun, 9 Jun 2024 21:10:25 +0200 [thread overview]
Message-ID: <d18a9606-ac9f-4ca7-afaf-fcf4c951cb90@web.de> (raw)
In-Reply-To: <20240608172147.2779890-1-howardchu95@gmail.com>
> This is a bug found when implementing pretty-printing for the
> landlock_add_rule system call, I decided to send this patch separately
> because this is a serious bug that should be fixed fast.
…
Would you like to add the tag “Fixes” accordingly?
Regards,
Markus
next prev parent reply other threads:[~2024-06-09 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 17:21 [PATCH] perf trace: Fix syscall untraceable bug Howard Chu
2024-06-09 19:10 ` Markus Elfring [this message]
2024-06-10 21:33 ` Ian Rogers
2024-06-11 10:22 ` Howard Chu
2024-06-11 14:53 ` Arnaldo Carvalho de Melo
2024-06-11 15:24 ` Arnaldo Carvalho de Melo
2024-06-11 15:43 ` Howard Chu
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=d18a9606-ac9f-4ca7-afaf-fcf4c951cb90@web.de \
--to=markus.elfring@web.de \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=gnoack@google.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mic@digikod.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).