From: Zheng Yejian <zhengyejian1@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Ajay Kaher <akaher@vmware.com>, <shuah@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Ye Weihua <yeweihua4@huawei.com>
Subject: Re: [PATCH] selftests/ftrace: Correctly enable event in instance-event.tc
Date: Wed, 6 Sep 2023 09:42:44 +0800 [thread overview]
Message-ID: <9cad73cd-1f8b-2f3f-cda4-99b89a87b931@huawei.com> (raw)
In-Reply-To: <20230905183638.2b539fae@gandalf.local.home>
On 2023/9/6 06:36, Steven Rostedt wrote:
> On Tue, 5 Sep 2023 20:54:40 +0800
> Zheng Yejian <zhengyejian1@huawei.com> wrote:
>
>> Hi, Steve, Ajay,
>>
>> After this patch and run this testcase, I got an use-after-free report
>> by KASAN. Short log see [1], full logs see attach "panic.log".
>>
>> And by simple bisect, I found it may be introduced by:
>>
>> 27152bceea1d ("eventfs: Move tracing/events to eventfs")
>>
>> Link:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=27152bceea1df27ffebb12ac9cd9adbf2c4c3f35
>
> Hi Zheng,
>
> Can you test:
>
> https://lore.kernel.org/all/20230905183332.628d7cc0@gandalf.local.home/
>
> and see if it fixes the KASAN issue for you?
Hi, Steve, your new patch seems not fixes the KASAN issue.
I run the instance-event.tc with your patch again and get same KASAN
report.
My config is in:
https://lore.kernel.org/all/da5495b5-cdb5-cb82-dd9b-37e7a87ed97d@huawei.com/
>
> Thanks!
>
> -- Steve
>
next prev parent reply other threads:[~2023-09-06 1:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 0:11 [PATCH] selftests/ftrace: Correctly enable event in instance-event.tc Zheng Yejian
2023-06-26 10:11 ` Masami Hiramatsu
2023-06-26 10:12 ` Masami Hiramatsu
2023-07-10 22:37 ` Steven Rostedt
2023-09-05 12:54 ` Zheng Yejian
2023-09-05 16:25 ` Steven Rostedt
2023-09-05 16:49 ` Steven Rostedt
2023-09-05 18:45 ` Steven Rostedt
2023-09-05 20:32 ` Steven Rostedt
2023-09-05 22:36 ` Steven Rostedt
2023-09-06 1:42 ` Zheng Yejian [this message]
2023-09-06 11:27 ` Steven Rostedt
2023-09-06 11:57 ` Zheng Yejian
2023-09-06 12:56 ` Steven Rostedt
2023-09-06 13:02 ` Steven Rostedt
2023-09-06 13:31 ` Zheng Yejian
2023-09-06 13:43 ` Steven Rostedt
2023-09-06 13:45 ` Steven Rostedt
2023-09-06 14:01 ` Zheng Yejian
2023-09-06 14:04 ` Steven Rostedt
2023-09-05 22:43 ` Shuah Khan
2023-09-06 1:45 ` Zheng Yejian
2023-09-06 14:26 ` "[PATCH] selftests/ftrace: Correctly enable event in instance-event.tc" Naresh Kamboju
2023-09-06 14:37 ` Steven Rostedt
2023-09-06 21:37 ` Steven Rostedt
2023-09-07 1:01 ` Zheng Yejian
2023-09-06 18:50 ` Steven Rostedt
2023-09-06 22:46 ` Steven Rostedt
2023-09-07 1:39 ` Zheng Yejian
2023-09-07 1:44 ` Steven Rostedt
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=9cad73cd-1f8b-2f3f-cda4-99b89a87b931@huawei.com \
--to=zhengyejian1@huawei.com \
--cc=akaher@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yeweihua4@huawei.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 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).