From: syzbot <syzbot+2373f6be3e6de4f92562@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andreyknvl@gmail.com, axboe@kernel.dk,
dvyukov@google.com, eadavis@qq.com, elver@google.com,
glider@google.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
pengfei.xu@intel.com, peterz@infradead.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [block?] [trace?] INFO: task hung in blk_trace_remove (2)
Date: Wed, 13 Nov 2024 09:22:04 -0800 [thread overview]
Message-ID: <6734e03c.050a0220.2a2fcc.0045.GAE@google.com> (raw)
In-Reply-To: <0000000000002b1fc7060fca3adf@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=174bc1a7980000
start commit: 7a396820222d Merge tag 'v6.8-rc-part2-smb-client' of git:/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4059ab9bf06b6ceb
dashboard link: https://syzkaller.appspot.com/bug?extid=2373f6be3e6de4f92562
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14669c6fe80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d23ae3e80000
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-11-13 17:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 19:31 [syzbot] [block?] [trace?] INFO: task hung in blk_trace_remove (2) syzbot
2024-01-30 1:00 ` Edward Adam Davis
2024-01-30 1:48 ` syzbot
2024-01-30 2:15 ` Edward Adam Davis
2024-01-30 6:40 ` syzbot
2024-01-30 6:48 ` Edward Adam Davis
2024-01-30 7:55 ` syzbot
2024-01-30 8:37 ` Edward Adam Davis
2024-01-30 9:18 ` syzbot
2024-01-30 9:56 ` Edward Adam Davis
2024-01-30 10:21 ` syzbot
2024-01-30 10:53 ` Edward Adam Davis
2024-01-30 11:41 ` syzbot
2024-01-30 13:38 ` Edward Adam Davis
2024-01-30 16:03 ` syzbot
2024-01-31 1:04 ` Edward Adam Davis
2024-01-31 7:54 ` syzbot
2024-01-31 8:18 ` Edward Adam Davis
2024-01-31 9:18 ` syzbot
2024-01-31 9:32 ` Edward Adam Davis
2024-01-31 10:00 ` syzbot
2024-01-31 9:38 ` Edward Adam Davis
2024-01-31 10:17 ` syzbot
2024-01-31 10:13 ` Edward Adam Davis
2024-01-31 10:42 ` syzbot
2024-01-31 10:14 ` Edward Adam Davis
2024-01-31 11:07 ` syzbot
2024-01-31 11:53 ` Edward Adam Davis
2024-01-31 12:40 ` syzbot
2024-01-31 13:28 ` [PATCH] trace/blktrace: fix task hung in blk_trace_remove Edward Adam Davis
2024-01-31 14:54 ` Jens Axboe
2024-11-13 17:22 ` 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=6734e03c.050a0220.2a2fcc.0045.GAE@google.com \
--to=syzbot+2373f6be3e6de4f92562@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=eadavis@qq.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pengfei.xu@intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.