[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <227eb61b-8068-001e-47fa-b65104b3b226@maine.edu>
Date: Wed, 13 Dec 2023 09:54:09 -0500 (EST)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: xingwei lee <xrivendell7@...il.com>
cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...nel.org, namhyung@...nel.org, irogers@...gle.com,
adrian.hunter@...el.com, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: possible deadlock in down_trylock/perf_event_open
On Mon, 11 Dec 2023, xingwei lee wrote:
> Hello I found a bug in kernel/perf in the lastest upstream linux 6.7.rc5
> possible deadlock in down_trylock/perf_event_open
>
> If you fix this issue, please add the following tag to the commit:
> Reported-by: xingwei Lee <xrivendell7@...il.com>
>
>
> syzkaller login: root
> Linux syzkaller 6.7.0-rc5 #3 SMP PREEMPT_DYNAMIC Mon Dec 11 17:02:24
> HKT 2023 x86_64
> root@...kaller:~# ./572
> [ 113.795108][ T8266] ------------[ cut here ]------------
> [ 113.795707][ T8266] WARNING: CPU: 1 PID: 8266 at
> kernel/events/core.c:1950 __do_sys_perf_event_open0
Just wanted to add that the perf_fuzzer will trigger this warning more or
less immediately as well.
Vince
Powered by blists - more mailing lists