Re: [PATCH V17 00/18] Allow I/O on blocks whose size is less than page size

From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, clm@fb.com, jbacik@fb.com, chandan@mykolab.com,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH V17 00/18] Allow I/O on blocks whose size is less than page size
Date: Sun, 17 Apr 2016 18:02:40 +0530	[thread overview]
Message-ID: <1895026.yWZ6EYWqV5@localhost.localdomain> (raw)
In-Reply-To: <1460641107-13834-1-git-send-email-chandan@linux.vnet.ibm.com>

On Thursday 14 Apr 2016 19:08:09 Chandan Rajendra wrote:
> Btrfs assumes block size to be the same as the machine's page
> size. This would mean that a Btrfs instance created on a 4k page size
> machine (e.g. x86) will not be mountable on machines with larger page
> sizes (e.g. PPC64/AARCH64). This patchset aims to resolve this
> incompatibility.
> 
> This patchset continues with the work posted previously at
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/53073.
> 
> I have reverted the upstream commit "btrfs: fix lockups from
> btrfs_clear_path_blocking" (f82c458a2c3ffb94b431fc6ad791a79df1b3713e)
> since this led to soft-lockups when the patch "Btrfs:
> subpagesize-blocksize: Prevent writes to an extent buffer when
> PG_writeback flag is set" is applied. During 2015's Vault Conference
> Btrfs meetup, Chris Mason had suggested that he will write up a
> suitable locking function to be used when writing dirty pages that map
> metadata blocks. Until we have a suitable locking function available,
> this patchset temporarily disables the commit
> f82c458a2c3ffb94b431fc6ad791a79df1b3713e.
> 
> The commits for the Btrfs kernel module can be found at
> https://github.com/chandanr/linux/tree/btrfs/subpagesize-blocksize.
> 
> To create a filesystem with block size < page size, a patched version
> of the Btrfs-progs package is required. The corresponding fixes for
> Btrfs-progs can be found at
> https://github.com/chandanr/btrfs-progs/tree/btrfs/subpagesize-blocksize.
> 
> Fstests run status:
> 1. x86_64
>    - With 4k sectorsize, all the tests that succeed with the master
>      branch at git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
> branch also do so with the patches applied.
> 2. ppc64
>    - With 4k sectorsize, 16k nodesize and with "nospace_cache" mount
>      option, except for scrub and compression tests, all the tests
>      that succeed with the master branch at
>      git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
>      branch also do so with the patches applied.
>    - With 64k sectorsize & nodesize, all the tests that succeed with
>      the master branch at
>      git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
>      branch also do so with the patches applied.
> 
> TODO:
> 1. The selftests code needs to be fixed to work in subpage-blocksize
>    scenario.
> 2. I am planning to fix Scrub & Compression via a separate patchset.
>

Hi,

I had messed up the following four patches during rebase operations.
[PATCH] Btrfs: subpage-blocksize: btrfs_punch_hole: Fix uptodate blocks check
[PATCH] Btrfs: subpage-blocksize: Define extent_buffer_head.
[PATCH] Btrfs: subpage-blocksize: Make sure delalloc range intersects with the
locked page's range 
[PATCH] Btrfs: subpage-blocksize: Prevent writes to an extent buffer when
PG_writeback flag is set

Instead of sending the complete patchset once again, I have resent only the
above listed patches as replies to the corresponding mails. Please use the
new patches instead of the corresponding old ones.

-- 
chandan