From: Shuai Xue <xueshuai@linux.alibaba.com>
To: alexander.shishkin@linux.intel.com, peterz@infradead.org,
james.clark@arm.com, leo.yan@linaro.org
Cc: mingo@redhat.com, baolin.wang@linux.alibaba.com, acme@kernel.org,
mark.rutland@arm.com, jolsa@kernel.org, namhyung@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, bpf@vger.kernel.org
Subject: [PATCH v4 0/2] perf/core: Bail out early if the request AUX area is out of bound
Date: Fri, 4 Aug 2023 15:29:43 +0800 [thread overview]
Message-ID: <20230804072945.85731-1-xueshuai@linux.alibaba.com> (raw)
changes since v3 (per James):
- change to return with existing value -ENOMEM
- split doc part to a separate patch since they are going to be merged through
separate trees.
changes since v2:
- remove unnecessary overflow check (per Peter)
changes since v1:
- drop out patch2 because it has been fixed on upstream (Thanks James for reminding)
- move sanity check into rb_alloc_aux (per Leo)
- add overflow check (per James)
Shuai Xue (2):
perf/core: Bail out early if the request AUX area is out of bound
perf record: Update docs regarding the maximum limitation of AUX area
kernel/events/ring_buffer.c | 3 +++
tools/perf/Documentation/perf-record.txt | 3 +++
2 files changed, 6 insertions(+)
--
2.39.3
next reply other threads:[~2023-08-04 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 7:29 Shuai Xue [this message]
2023-08-04 7:29 ` [PATCH v4 1/2] " Shuai Xue
2023-08-04 8:59 ` Leo Yan
2023-08-04 11:24 ` Shuai Xue
2023-09-06 3:27 ` Shuai Xue
2023-09-06 7:02 ` Leo Yan
2023-09-06 7:07 ` Shuai Xue
2023-08-04 7:29 ` [PATCH v4 2/2] perf record: Update docs regarding the maximum limitation of AUX area Shuai Xue
2023-08-04 8:46 ` Leo Yan
2023-08-04 11:47 ` Shuai Xue
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=20230804072945.85731-1-xueshuai@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nathan@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
all inboxes | Powered by JetHome®