From: syzbot <syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, leon@kernel.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
sagi@grimberg.me, saravanan.vajravel@broadcom.com,
selvin.xavier@broadcom.com, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [block] INFO: task hung in __filemap_get_folio
Date: Tue, 03 Oct 2023 13:11:32 -0700 [thread overview]
Message-ID: <00000000000035587d0606d57fec@google.com> (raw)
In-Reply-To: <0000000000002709ae05e5b6474c@google.com>
syzbot suspects this issue was fixed by commit:
commit 699826f4e30ab76a62c238c86fbef7e826639c8d
Author: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
Date: Tue Jun 6 10:25:31 2023 +0000
IB/isert: Fix incorrect release of isert connection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144a99be680000
start commit: 105a36f3694e Merge tag 'kbuild-fixes-v6.0-3' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=122d7bd4fc8e0ecb
dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10174404880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169f552f080000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: IB/isert: Fix incorrect release of isert connection
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-03 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:05 [syzbot] INFO: task hung in __filemap_get_folio syzbot
2022-09-10 7:06 ` syzbot
2022-09-23 18:45 ` syzbot
2022-09-24 22:25 ` Matthew Wilcox
2023-10-03 20:11 ` 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=00000000000035587d0606d57fec@google.com \
--to=syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sagi@grimberg.me \
--cc=saravanan.vajravel@broadcom.com \
--cc=selvin.xavier@broadcom.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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.