From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0C16A33B6E6 for ; Wed, 12 Nov 2025 15:30:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=18.9.28.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762961455; cv=none; b=M2eo7iajrFeu6GRCKamoMUnwseCK28xSyJtP2GDSuh0ssfyK1mGIeSGe6AAu5KShNRxLw4bpy91HXiU2KfQx7/GuRNGWcnS0RNxYxX1A01CkplJ7Goyz461aQE3nsBeA6wORYavzP0G24L71djAgQNUE9LFbubPfgJpFwr0Z0KU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762961455; c=relaxed/simple; bh=jti/WDC1KJeLUCxADdUS9GjNHsV+LzcXVJp+I1E5YvA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=C1sYBQhNT6/7BLEWhzKy1wz76gPQOJdD6tkjgPhmWGVisVxyPVhR1ArlbXJ+uhzo12c897r9PjfAEAZfWNycqvJzQFXU1w5g9FBQo8ydI2hI2sb8XHbi5oCqXnlB8VWcZWY/xJbUUQ9Ik788++WDmyHvqpSe7THv7lmwFdI4qPI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mit.edu; spf=pass smtp.mailfrom=mit.edu; dkim=pass (2048-bit key) header.d=mit.edu header.i=@mit.edu header.b=bVHixlYn; arc=none smtp.client-ip=18.9.28.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mit.edu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mit.edu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mit.edu header.i=@mit.edu header.b="bVHixlYn" Received: from trampoline.thunk.org (pool-173-48-82-200.bstnma.fios.verizon.net [173.48.82.200]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 5ACFTXXi022626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Nov 2025 10:29:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1762961379; bh=fFEV1yEu0f2ULh0OpDxAMyYySFsuiDTjToDP1kfqcxE=; h=Date:From:Subject:Message-ID:MIME-Version:Content-Type; b=bVHixlYnoXOntlmD86NN2BdGh+eHnNuVozQh1KtMaDTh8lG0lFAxzabpXEjHhf/Pb TF5YNFgPA4iGPyQaBJjd4wDdDZXlS4U/pQENXWH7uxKSzC/AJy6LoDKEwwHkA86HgX 4P5Efgltsm5SE9Mze0T8fl3yiePumdgNXjCpDSF/Q49tYHu7vEOvMPRxU8PCBVT3KS vGKMcEXZMTMCSQnNL1Fzg1cl4LDqkAYOb4ncyoHN65IMJ3DDDV8R9wbSgpL/mE9jWi 7t42GUyZczx5rSeDGCKG50K8Oxiyh9qMdNCbT//KVWm7AnmV2VMwMne43aXlhDsmj5 k5XO7rEC02AWA== Received: by trampoline.thunk.org (Postfix, from userid 15806) id 0A5342E00D9; Wed, 12 Nov 2025 10:29:33 -0500 (EST) Date: Wed, 12 Nov 2025 10:29:33 -0500 From: "Theodore Ts'o" To: Baokun Li Cc: linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca, jack@suse.cz, linux-kernel@vger.kernel.org, kernel@pankajraghav.com, mcgrof@kernel.org, ebiggers@kernel.org, willy@infradead.org, yi.zhang@huawei.com, yangerkun@huawei.com, chengzhihao1@huawei.com, Baokun Li , "Darrick J. Wong" Subject: Re: [PATCH v2 00/24] ext4: enable block size larger than page size Message-ID: <20251112152933.GC3131573@mit.edu> References: <20251112040220.GO2988753@mit.edu> <21efa577-a577-48ce-a82b-bce446539fba@huawei.com> Precedence: bulk X-Mailing-List: linux-ext4@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <21efa577-a577-48ce-a82b-bce446539fba@huawei.com> On Wed, Nov 12, 2025 at 02:27:19PM +0800, Baokun Li wrote: > Darrick’s reply in another thread has already made a similar change, > so we can apply that patch first for testing. I'll give that a try when I have a chance. For now, here's a test run using a version of my test appliance which excludes the way group for the config ext4/lbs, and which has a modified e2fsprogs (built from the latest e2fsprogs git repo) which suppresses both warnings when using large block sizes if the kernel has the blocksize_gt_pagesize feature detected. ext4/lbs: 595 tests, 6 failures, 101 skipped, 6656 seconds Failures: ext4/033 generic/620 generic/759 generic/760 Flaky: generic/251: 60% (3/5) generic/645: 40% (2/5) Totals: 619 tests, 101 skipped, 25 failures, 0 errors, 6291s Fixing all of these filures is not a blocker for getting this patchset upstream, but it would be nice for us to figure out the root cause for them, so we can decide whether it's better to exclude the tests for now, or whether there's an easy fix. Thanks, - Ted