From: syzbot <syzbot+9c703233282a4a1a6749@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, andreyknvl@gmail.com,
dvyukov@google.com, elver@google.com, glider@google.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tytso@mit.edu
Subject: Re: [syzbot] [ext4?] [mm?] INFO: rcu detected stall in ext4_release_file (2)
Date: Tue, 01 Oct 2024 08:05:04 -0700 [thread overview]
Message-ID: <66fc0fa0.050a0220.f28ec.04ab.GAE@google.com> (raw)
In-Reply-To: <00000000000032fa460619a3725d@google.com>
syzbot suspects this issue was fixed by commit:
commit ae94b263f5f69c180347e795fbefa051b65aacc3
Author: Dmitry Vyukov <dvyukov@google.com>
Date: Tue Jun 11 07:50:33 2024 +0000
x86: Ignore stack unwinding in KCOV
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17353dd0580000
start commit: 56fb6f92854f Merge tag 'drm-next-2024-05-25' of https://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=966dbeb548ca6926
dashboard link: https://syzkaller.appspot.com/bug?extid=9c703233282a4a1a6749
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e7abe0980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b23f6c980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: x86: Ignore stack unwinding in KCOV
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-01 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 3:27 [syzbot] [mm?] [ext4?] INFO: rcu detected stall in ext4_release_file (2) syzbot
2024-10-01 15:05 ` syzbot [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=66fc0fa0.050a0220.f28ec.04ab.GAE@google.com \
--to=syzbot+9c703233282a4a1a6749@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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).