From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Gowtham <trgowtham123@gmail.com>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: Re: Disk write deterioration in 5.x kernel
Date: Fri, 19 Jan 2024 13:58:52 +0700 [thread overview]
Message-ID: <ZaodrO8QjCqSXPHe@archie.me> (raw)
In-Reply-To: <CA+XNQ=hGxYsMAo6Gc+Up5QctbWjkER17uK97YXWc9uyx_7+3uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
[also Cc: btrfs maintainers]
On Fri, Jan 19, 2024 at 09:37:50AM +0530, Gowtham wrote:
> Hi
>
> Is there anything I can collect to debug what is the problem in the new kernel?
>
Please don't top-post, reply inline with appropriate context instead.
Since you have regression w.r.t. old LTS kernel (v5.4.y), can you check
current mainline (v6.7) to confirm or deny the regression? If the
regression still happens there, can you perform bisection (see
Documentation/admin-guide/bug-bisect.rst in the kernel sources for details)?
Also, it is also helpful to list SSD devices that you've tested.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-19 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 5:51 Disk write deterioration in 5.x kernel Gowtham
2024-01-19 4:07 ` Gowtham
2024-01-19 6:58 ` Bagas Sanjaya [this message]
2024-01-19 8:55 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-19 13:34 ` Bagas Sanjaya
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=ZaodrO8QjCqSXPHe@archie.me \
--to=bagasdotme@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=trgowtham123@gmail.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