From: syzbot <syzbot+38d04642cea49f3a3d2e@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linkinjeon@kernel.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_pkondeti@quicinc.com,
rafael.j.wysocki@intel.com, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
wendy.wang@intel.com, yu.c.chen@intel.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in __writeback_inodes_sb_nr (6)
Date: Fri, 18 Aug 2023 06:10:41 -0700 [thread overview]
Message-ID: <000000000000761f5f0603324129@google.com> (raw)
In-Reply-To: <000000000000f59fa505fe48748f@google.com>
syzbot has bisected this issue to:
commit 5904de0d735bbb3b4afe9375c5b4f9748f882945
Author: Chen Yu <yu.c.chen@intel.com>
Date: Fri Apr 14 12:10:42 2023 +0000
PM: hibernate: Do not get block device exclusively in test_resume mode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1275be4ba80000
start commit: 4853c74bd7ab Merge tag 'parisc-for-6.5-rc7' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1175be4ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1675be4ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa796b6080b04102
dashboard link: https://syzkaller.appspot.com/bug?extid=38d04642cea49f3a3d2e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171242cfa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17934703a80000
Reported-by: syzbot+38d04642cea49f3a3d2e@syzkaller.appspotmail.com
Fixes: 5904de0d735b ("PM: hibernate: Do not get block device exclusively in test_resume mode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-18 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 0:33 [syzbot] [ext4?] INFO: task hung in __writeback_inodes_sb_nr (6) syzbot
2023-08-16 23:27 ` syzbot
2023-08-18 13:10 ` syzbot [this message]
2023-08-18 16:50 ` Chen Yu
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=000000000000761f5f0603324129@google.com \
--to=syzbot+38d04642cea49f3a3d2e@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_pkondeti@quicinc.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=wendy.wang@intel.com \
--cc=yu.c.chen@intel.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).