public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas D Steeves <sten@debian.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Bruno Damasceno Freire <bdamasceno@hotmail.com.br>,
	Filipe Manana <fdmanana@kernel.org>,
	"dsterba@suse.cz" <dsterba@suse.cz>, Chris Mason <clm@fb.com>,
	Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	"fdmanana@suse.com" <fdmanana@suse.com>
Subject: Re: [regression] 5.15 kernel triggering 100x more inode evictions
Date: Tue, 12 Apr 2022 20:15:47 -0400	[thread overview]
Message-ID: <87r161zvm4.fsf@DigitalMercury.freeddns.org> (raw)
In-Reply-To: <3ab10248-be14-d161-14e6-bf19ac8cd998@leemhuis.info>

[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]

Hi Bruno,

Thorsten Leemhuis <regressions@leemhuis.info> writes:

> On 09.04.22 19:12, Bruno Damasceno Freire wrote:
>> On 08.04.22 04:50, Thorsten Leemhuis wrote:
>>> On 08.04.22 17:55, Filipe Manana wrote:
>>>> On Fri, Apr 08, 2022 at 04:52:22PM +0200, David Sterba wrote:
>>>>> On Fri, Apr 08, 2022 at 12:32:20PM +0200, Thorsten Leemhuis wrote:
>>> Bruno, under these circumstances I'd say you need to bisect this to get
>>> us closer to the root of the problem (and a fix for it). Sadly that how
>>> it is sometimes, as briefly explained here:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/admin-guide/reporting-regressions.rst#n140
>> 
>> Ok Thorsten.
>> 
>> It's not sad at all: I had a great time researching this regression and
>> gained a lot of knowledge while doing so. The problem is that I am just a
>> simple user at its limits here and additional bisection is probably beyond my
>> abilities.
>
> Maybe, but I think you underestimate yourself here. Give it a try, it's
> not that hard once you figured out how to build and install a vanilla
> kernel (which you did already afaics; and if not: it's not that hard and
> you learn new stuff, too) and have some test case to check if the
> problem is there or now (which you already have afaics).
>

I also think it's something you can manage :-)

Something like:

1. Use the .config from /boot/config-ubuntu_5.14.x
2. git bisect start
3. git bisect good v5.14 (7d2a07b)
4. git bisect bad v5.15 (8bb7eca)
5. Open a guide like these ones on another device, or print it out:
  https://www.metaltoad.com/blog/beginners-guide-git-bisect-process-elimination
  https://wiki.gentoo.org/wiki/Kernel_git-bisect
  https://wiki.ubuntu.com/Kernel/KernelBisection
  https://ldpreload.com/blog/git-bisect-run ("Finding a kernel
  regression in half an hour with git bisect run")
6. make oldconfig
7. make bindeb-pkg
8. Deb packages are in ../
9. Install, reboot, run tests, confirm logs, iterate

Thank you for running these tests.  By chance, would you have time to
compare 5.10.x to 5.15.x, or have you already compared them?  I'm
always the most curious about how the latest LTS kernel compares to
latest_LTS-1 ;-)

Regards,
Nicholas

P.S. I'm sure you'll be able to find someone on IRC who'd be willing to
help you, should any help be necessary!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

  reply	other threads:[~2022-04-13  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MN2PR20MB2512314446801B92562E26B5D2169@MN2PR20MB2512.namprd20.prod.outlook.com>
     [not found] ` <07bb78be-1d58-7d88-288b-6516790f3b5d@leemhuis.info>
     [not found]   ` <MN2PR20MB251203B4B5445B4B0C4148C9D21D9@MN2PR20MB2512.namprd20.prod.outlook.com>
2022-03-28 11:28     ` [regression] 5.15 kernel triggering 100x more inode evictions Thorsten Leemhuis
2022-04-04  5:29       ` Bruno Damasceno Freire
2022-04-08 10:32         ` Thorsten Leemhuis
2022-04-08 14:52           ` David Sterba
2022-04-08 15:55             ` Filipe Manana
2022-04-08 16:50               ` Thorsten Leemhuis
2022-04-09 17:12                 ` Bruno Damasceno Freire
2022-04-10  7:27                   ` Thorsten Leemhuis
2022-04-13  0:15                     ` Nicholas D Steeves [this message]
2022-04-09 17:07               ` Bruno Damasceno Freire

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=87r161zvm4.fsf@DigitalMercury.freeddns.org \
    --to=sten@debian.org \
    --cc=bdamasceno@hotmail.com.br \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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