public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219283] kernel regression with ext4 and ea_inode mount flags and exercising xattrs (between Linux 6.8 and 6.11)
Date: Mon, 16 Sep 2024 18:09:23 +0000	[thread overview]
Message-ID: <bug-219283-13602-SwVDIh5nA4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219283-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219283

--- Comment #6 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Colin Ian King from comment #4)
> I'm doing some bisect builds, but my system is a bit slow, so may take a few
> days.

Use ext4 in RAM, e.g. using tmpfs.

For building the kernel you could use ccache.

To avoid reboots, have your root fs on any other FS, e.g. xfs and build ext4 as
a module.

Or even perform everything in a VM.

It's not a hardware module, so the whole test could be performed in a VM.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-09-16 18:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 13:30 [Bug 219283] New: kernel regression with ext4 and ea_inode mount flags and exercising xattrs (between Linux 6.8 and 6.11) bugzilla-daemon
2024-09-16 13:31 ` [Bug 219283] " bugzilla-daemon
2024-09-16 15:35 ` bugzilla-daemon
2024-09-16 17:03 ` bugzilla-daemon
2024-09-16 17:13 ` bugzilla-daemon
2024-09-16 17:51 ` bugzilla-daemon
2024-09-16 18:09 ` bugzilla-daemon [this message]
2024-09-17 18:13 ` bugzilla-daemon
2024-09-17 20:18 ` bugzilla-daemon
2024-09-18 13:43 ` bugzilla-daemon
2024-09-18 13:43 ` bugzilla-daemon
2024-09-18 15:35 ` bugzilla-daemon
2024-09-18 16:08 ` bugzilla-daemon

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=bug-219283-13602-SwVDIh5nA4@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.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