From: Steven Rostedt <rostedt@goodmis.org>
To: syzbot <syzbot+3ef80b4ed02226d04a06@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, kartikey406@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rostedt@kernel.org, sh_def@163.com, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vdonnefort@google.com,
vulab@iscas.ac.cn
Subject: Re: [syzbot] [fs?] [trace?] WARNING in eventfs_create_events_dir
Date: Fri, 28 Aug 2026 09:50:52 -0400 [thread overview]
Message-ID: <20260828095052.442529a5@gandalf.local.home> (raw)
In-Reply-To: <6a91709f.4d659fcc.734b4.001c.GAE@google.com>
On Fri, 28 Aug 2026 04:27:27 -0700
syzbot <syzbot+3ef80b4ed02226d04a06@syzkaller.appspotmail.com> wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 818bebeb63dd drm/xe: Don't hand out the flat CCS storage a..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> console output: https://syzkaller.appspot.com/x/log.txt?x=16eddd49580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ccca94d2c01b9e78
> dashboard link: https://syzkaller.appspot.com/bug?extid=3ef80b4ed02226d04a06
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17986d79580000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+3ef80b4ed02226d04a06@syzkaller.appspotmail.com
>
> R10: 0000000000000000 R11: 0000000000000202 R12: 00007fae2ca35a9f
> R13: 00007fae2ca35adb R14: 00007fae2ca5ccc0 R15: 0000000000000002
> </TASK>
> ------------[ cut here ]------------
> !list_empty(&ei->children)
> WARNING: fs/tracefs/event_inode.c:128 at free_ei fs/tracefs/event_inode.c:128 [inline], CPU#0: syz-executor340/6037
> WARNING: fs/tracefs/event_inode.c:128 at cleanup_ei fs/tracefs/event_inode.c:150 [inline], CPU#0: syz-executor340/6037
> WARNING: fs/tracefs/event_inode.c:128 at cleanup_ei fs/tracefs/event_inode.c:145 [inline], CPU#0: syz-executor340/6037
> WARNING: fs/tracefs/event_inode.c:128 at eventfs_create_events_dir+0xa3d/0xbe0 fs/tracefs/event_inode.c:838, CPU#0: syz-executor340/6037
This should be fixed by: https://lore.kernel.org/all/20260827151011.389282397@kernel.org/
Which is in my queue to send to Linus (and currently in my "fixes" branch).
I have some more patches to process before I send Linus my pull request.
-- Steve
prev parent reply other threads:[~2026-08-28 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a8c13ee.91706f20.16b6e3.02d5.GAE@google.com>
2026-08-28 11:27 ` [syzbot] [fs?] [trace?] WARNING in eventfs_create_events_dir syzbot
2026-08-28 13:50 ` Steven Rostedt [this message]
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=20260828095052.442529a5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=kartikey406@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@kernel.org \
--cc=sh_def@163.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+3ef80b4ed02226d04a06@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdonnefort@google.com \
--cc=vulab@iscas.ac.cn \
/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