From: Matthew Wilcox <willy@infradead.org>
To: Hao Sun <sunhao.th@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: kernel BUG in block_invalidatepage
Date: Thu, 7 Oct 2021 15:19:37 +0100 [thread overview]
Message-ID: <YV8B+VGQ7TZoeJ8W@casper.infradead.org> (raw)
In-Reply-To: <CACkBjsb0Hxam_e5+vOOanF_BfGAcf5UY+=Cc-pyphQftETTe8Q@mail.gmail.com>
On Thu, Oct 07, 2021 at 02:40:29PM +0800, Hao Sun wrote:
> Hello,
>
> This crash can still be triggered repeatedly on the latest kernel.
I asked you three days ago to try a patch and report the results:
https://lore.kernel.org/linux-mm/YVtWhVNFhLbA9+Tl@casper.infradead.org/
next prev parent reply other threads:[~2021-10-07 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 7:19 kernel BUG in block_invalidatepage Hao Sun
2021-10-07 6:40 ` Hao Sun
2021-10-07 12:23 ` Jens Axboe
2021-10-07 14:19 ` Matthew Wilcox [this message]
2021-10-08 3:02 ` Hao Sun
2021-10-08 3:31 ` 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=YV8B+VGQ7TZoeJ8W@casper.infradead.org \
--to=willy@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunhao.th@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).