From: Bagas Sanjaya <bagasdotme@gmail.com>
To: dianlujitao@gmail.com, Matthew Wilcox <willy@infradead.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
Linux Filesystem Development <linux-fsdevel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Fwd: kernel bug when performing heavy IO operations
Date: Sun, 8 Oct 2023 21:07:04 +0700 [thread overview]
Message-ID: <ZSK3iAX0LASTiczY@debian.me> (raw)
In-Reply-To: <162d90ab-e538-402e-90f1-304183bf6e76@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
On Sun, Oct 08, 2023 at 09:35:58PM +0800, dianlujitao@gmail.com wrote:
> The problem does not occur with 6.1.56 lts kernel, not that old as you
> expected.
>
Please don't top-post; reply inline with appropriate context instead.
OK, now please find the culprit by bisection (see
Documentation/admin-guide/bug-bisect.rst in the kernel sources for how).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-10-08 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 3:20 Fwd: kernel bug when performing heavy IO operations Bagas Sanjaya
2023-08-27 3:45 ` Matthew Wilcox
[not found] ` <7d8b4679-5cd5-4ba1-9996-1a239f7cb1c5@gmail.com>
2023-08-27 11:54 ` Matthew Wilcox
2023-09-27 5:36 ` dianlujitao
2023-09-27 7:19 ` Matthew Wilcox
2023-10-08 13:35 ` dianlujitao
2023-10-08 14:07 ` Bagas Sanjaya [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=ZSK3iAX0LASTiczY@debian.me \
--to=bagasdotme@gmail.com \
--cc=clm@fb.com \
--cc=dianlujitao@gmail.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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