From: Eric Biggers <ebiggers@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+2c93b863a7698df84bad@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org,
Stephen Brennan <stephen.s.brennan@oracle.com>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev
Subject: Re: [syzbot] WARNING: locking bug in truncate_inode_pages_final
Date: Tue, 7 Jun 2022 16:18:58 -0700 [thread overview]
Message-ID: <Yp/c4p4MSUyoFenY@sol.localdomain> (raw)
In-Reply-To: <20220607160020.c088f4d29929310f2a3c1c32@linux-foundation.org>
On Tue, Jun 07, 2022 at 04:00:20PM -0700, Andrew Morton wrote:
> Lots of cc's added.
>
> On Tue, 07 Jun 2022 00:16:29 -0700 syzbot <syzbot+2c93b863a7698df84bad@syzkaller.appspotmail.com> wrote:
>
> > Hello,
>
> Thanks.
>
> > syzbot found the following issue on:
>
> Oh dear.
>
> > HEAD commit: d1dc87763f40 assoc_array: Fix BUG_ON during garbage collect
>
> I think this bisection is wrong.
It's not a bisection; if it was, the report would say so. It's just the commit
that identifies the kernel version on which the problem was seen.
- Eric
next prev parent reply other threads:[~2022-06-08 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 7:16 [syzbot] WARNING: locking bug in truncate_inode_pages_final syzbot
2022-06-07 14:40 ` Matthew Wilcox
2022-06-07 23:00 ` Andrew Morton
2022-06-07 23:18 ` Eric Biggers [this message]
2022-06-08 0:23 ` Matthew Wilcox
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=Yp/c4p4MSUyoFenY@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ntfs3@lists.linux.dev \
--cc=stephen.s.brennan@oracle.com \
--cc=syzbot+2c93b863a7698df84bad@syzkaller.appspotmail.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 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).