From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+0adf31ecbba886ab504f@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, davem@davemloft.net,
dvyukov@google.com, edumazet@google.com, elver@google.com,
glider@google.com, hdanton@sina.com, kasan-dev@googlegroups.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] INFO: task hung in write_cache_pages (2)
Date: Thu, 2 Mar 2023 13:23:01 +0000 [thread overview]
Message-ID: <ZACjNSxGlVX6l39S@casper.infradead.org> (raw)
In-Reply-To: <00000000000099b9c905f5e9a820@google.com>
On Thu, Mar 02, 2023 at 04:06:28AM -0800, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 17bb55487988c5dac32d55a4f085e52f875f98cc
> Author: Matthew Wilcox (Oracle) <willy@infradead.org>
> Date: Tue May 17 22:12:25 2022 +0000
>
> ntfs: Remove check for PageError
Syzbot has bisected to the wrong commit. That code (a) isn't going
to be executed by this test, since it doesn't have an ntfs image and
(b) was dead. Never could have been executed.
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13fd6e54c80000
> start commit: 489fa31ea873 Merge branch 'work.misc' of git://git.kernel...
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=10036e54c80000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17fd6e54c80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cbfa7a73c540248d
> dashboard link: https://syzkaller.appspot.com/bug?extid=0adf31ecbba886ab504f
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16dc6960c80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f39d50c80000
>
> Reported-by: syzbot+0adf31ecbba886ab504f@syzkaller.appspotmail.com
> Fixes: 17bb55487988 ("ntfs: Remove check for PageError")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-03-02 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 0:35 syzbot
2023-03-02 12:06 ` syzbot
2023-03-02 13:23 ` Matthew Wilcox [this message]
2023-03-02 20:10 ` Yang Shi
2023-03-02 23:42 ` Huang, Ying
2023-03-03 5:38 ` Dmitry Vyukov
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=ZACjNSxGlVX6l39S@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hdanton@sina.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+0adf31ecbba886ab504f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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