Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 20 Feb 2020 01:14:28 -0500
From:   "Theodore Y. Ts'o" <tytso@mit.edu>
To:     Suraj Jitindar Singh <surajjs@amazon.com>
Cc:     linux-ext4@vger.kernel.org, sblbir@amazon.com,
        sjitindarsingh@gmail.com
Subject: Re: [PATCH 0/3] ext4: Fix potential races when performing online
 resizing
Message-ID: <20200220061428.GG476845@mit.edu>
References: <20200219030851.2678-1-surajjs@amazon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200219030851.2678-1-surajjs@amazon.com>
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

Hi Suraj,

All of the patches to fix BZ 206443 are now on the ext4 git tree:

https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/log/?h=dev

I'm currently giving them a full regression test set using xfstests.
Could you run your tests to make sure it looks good for you?

I'm hoping to issue a pull request to Linus in time for 5.6-rc3 by
this weekend.

Also, if you can figure out a way to package up the repro as an
xfstests test case, that would be really excellent.  I think the
challenge is that some of them took a *huge* amount of pounding before
they repro'ed, correct?  I wasn't actually able to trigger the repro
using kvm, but I was only using a 2 CPU configuration.

Thanks,

						- Ted