All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH 2/2] ext4: Remove array of buffer_heads from mext_page_mkuptodate()
Date: Thu, 27 Jun 2024 16:20:22 -0400	[thread overview]
Message-ID: <20240627202022.GC419129@mit.edu> (raw)
In-Reply-To: <20240516181651.2879778-2-willy@infradead.org>

On Thu, May 16, 2024 at 07:16:51PM +0100, Matthew Wilcox (Oracle) wrote:
> The current code iterates over the list of buffer_heads, finds the
> !uptodate ones and reads them, waiting for each one before submitting
> the next one.  Instead, submit all the read requests before waiting
> for each of the needed ones.
> 
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>

Hey Willy,

This patch is causing ext4/020 (which tests the EXT4_IOC_MOVE_EXT
ioctl used by e4defrag).  This can be easily reproduced via:
"kvm-xfstests -c ext4/4k ext4/020".  From
/results/ext4/results-4k/ext4/020.out.bad:

   QA output created by 020
   wrote 1048576/1048576 bytes at offset 0
   XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
   wrote 1023/1023 bytes at offset 0
   XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
   md5sum: WARNING: 1 computed checksum did NOT match
   SCRATCH_MNT/020.orig: FAILED

I'm going to drop both this patch and the preceeding patch in this
series ("ext4: reduce stack usage in ext4_mpage_readpages()") pending
further investigation.

							- Ted

  reply	other threads:[~2024-06-27 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 18:16 [PATCH 1/2] ext4: Reduce stack usage in ext4_mpage_readpages() Matthew Wilcox (Oracle)
2024-05-16 18:16 ` [PATCH 2/2] ext4: Remove array of buffer_heads from mext_page_mkuptodate() Matthew Wilcox (Oracle)
2024-06-27 20:20   ` Theodore Ts'o [this message]
2024-07-18 22:35     ` Matthew Wilcox

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=20240627202022.GC419129@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=hare@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.