public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz, harshads@google.com
Subject: Re: [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset
Date: Thu, 24 Apr 2025 09:59:11 -0500	[thread overview]
Message-ID: <20250424145911.GC765145@mit.edu> (raw)
In-Reply-To: <20250414165416.1404856-1-harshadshirwadkar@gmail.com>

On Mon, Apr 14, 2025 at 04:54:07PM +0000, Harshad Shirwadkar wrote:
> V8 Cover Letter
> ---------------
> 
> This is the V8 of the patch series. This patch series contains fixes to
> review comments by Jan Kara (<jack@suse.cz>). The main changes are as
> follows:

Hi Harshad,

I tried applying your patch set on top of 6.15-rc3, and a number of
tests: generic/127, generic/231, generic/241, generic/418, and
generic/589 are causing the kernel to OOPS, wedge, or reboot.  Most of
the test flakes and test failures were there without your patch set,
and we need to figure them out.... but Errors are new, and are
regressions.

I can send you the test artifacts under separate cover, or you can
just try running those tests using kvm-xfstests or gce-xfstests.

Thanks,

							- Ted

TESTRUNID: ltm-20250423233632
KERNEL:    kernel 6.15.0-rc3-xfstests-00009-gac4ab1811bb3 #22 SMP PREEMPT_DYNAMIC Wed Apr 23 14:28:04 EDT 2025 x86_64
CMDLINE:   --kernel gs://gce-xfstests/kernel.deb -c ext4/4k,ext4/fast_commit,ext4/fast_commit_1k -g auto
CPUS:      2
MEM:       7680

ext4/4k: 587 tests, 55 skipped, 5243 seconds
ext4/fast_commit: 602 tests, 20 failures, 3 errors, 55 skipped, 4564 seconds
  Failures: generic/506 generic/737 generic/757 generic/764
  Errors: generic/127 generic/241 generic/418
ext4/fast_commit_1k: 616 tests, 39 failures, 5 errors, 59 skipped, 6169 seconds
  Failures: generic/047 generic/051 generic/455 generic/475 generic/506 
    generic/757 generic/764
  Flaky: generic/627: 80% (4/5)
  Errors: generic/127 generic/231 generic/241 generic/418 generic/589
Totals: 1805 tests, 169 skipped, 59 failures, 8 errors, 15637s


  parent reply	other threads:[~2025-04-26  0:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 16:54 [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 1/9] ext4: convert i_fc_lock to spinlock Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 2/9] ext4: for committing inode, make ext4_fc_track_inode wait Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 3/9] ext4: mark inode dirty before grabbing i_data_sem in ext4_setattr Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 4/9] ext4: rework fast commit commit path Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 5/9] ext4: drop i_fc_updates from inode fc info Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 6/9] ext4: update code documentation Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 7/9] ext4: temporarily elevate commit thread priority Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 8/9] ext4: convert s_fc_lock to mutex type Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 9/9] ext4: hold s_fc_lock while during fast commit Harshad Shirwadkar
2025-04-24 14:59 ` Theodore Ts'o [this message]
2025-04-30 18:55   ` [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset harshad shirwadkar
2025-05-01  4:14     ` Theodore Ts'o
2025-05-01 13:37       ` Theodore Ts'o

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=20250424145911.GC765145@mit.edu \
    --to=tytso@mit.edu \
    --cc=harshads@google.com \
    --cc=harshadshirwadkar@gmail.com \
    --cc=jack@suse.cz \
    --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