From: Jiri Olsa <olsajiri@gmail.com>
To: Edward Adam Davis <eadavis@qq.com>, Mark Rutland <mark.rutland@arm.com>
Cc: syzbot+07144c543a5c002c7305@syzkaller.appspotmail.com,
acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, irogers@google.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
netdev@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, xrivendell7@gmail.com
Subject: Re: [PATCH] perf: fix WARNING in perf_event_open
Date: Wed, 27 Dec 2023 08:34:57 +0100 [thread overview]
Message-ID: <ZYvTC90lyZdwJ8bB@krava> (raw)
In-Reply-To: <tencent_7FC26D7C2FA56EF89584E89EEE52CD20790A@qq.com>
On Tue, Dec 26, 2023 at 03:25:15PM +0800, Edward Adam Davis wrote:
> The new version of __perf_event_read_size() only has a read action and does not
> require a mutex, so the mutex assertion in the original loop is removed.
>
> Fixes: 382c27f4ed28 ("perf: Fix perf_event_validate_size()")
> Reported-and-tested-by: syzbot+07144c543a5c002c7305@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
hi,
Mark suggested another fix earlier [1], but I haven't seen the formal patch yet
jirka
[1] https://lore.kernel.org/linux-perf-users/ZXwubNIxKH9s7DWt@FVFF77S0Q05N/
> ---
> kernel/events/core.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 9efd0d7775e7..e71e61b46416 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -1924,6 +1924,10 @@ static void perf_event__id_header_size(struct perf_event *event)
> event->id_header_size = size;
> }
>
> +#define read_for_each_sibling_event(sibling, event) \
> + if ((event)->group_leader == (event)) \
> + list_for_each_entry((sibling), &(event)->sibling_list, sibling_list)
> +
> /*
> * Check that adding an event to the group does not result in anybody
> * overflowing the 64k event limit imposed by the output buffer.
> @@ -1957,7 +1961,7 @@ static bool perf_event_validate_size(struct perf_event *event)
> if (event == group_leader)
> return true;
>
> - for_each_sibling_event(sibling, group_leader) {
> + read_for_each_sibling_event(sibling, group_leader) {
> if (__perf_event_read_size(sibling->attr.read_format,
> group_leader->nr_siblings + 1) > 16*1024)
> return false;
> --
> 2.43.0
>
next prev parent reply other threads:[~2023-12-27 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 10:01 [syzbot] [perf?] WARNING in perf_event_open syzbot
2023-12-25 11:44 ` syzbot
2023-12-26 0:52 ` Edward Adam Davis
2023-12-26 2:28 ` syzbot
2023-12-25 17:31 ` syzbot
2023-12-26 7:25 ` [PATCH] perf: fix " Edward Adam Davis
2023-12-27 7:34 ` Jiri Olsa [this message]
2024-01-05 11:30 ` Mark Rutland
2024-01-05 11:32 ` Mark Rutland
2024-02-23 3:58 ` [syzbot] [perf?] " syzbot
2024-02-23 10:42 ` Mark Rutland
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=ZYvTC90lyZdwJ8bB@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eadavis@qq.com \
--cc=irogers@google.com \
--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=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+07144c543a5c002c7305@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.