Re: [PATCH for-4.19] erofs: fix extended inode could cross boundary

2021-04-26 Thread Gao Xiang
On Mon, Apr 26, 2021 at 10:39:44AM +0200, Greg Kroah-Hartman wrote: > On Mon, Apr 26, 2021 at 04:29:33PM +0800, Gao Xiang wrote: > > commit 0dcd3c94e02438f4a571690e26f4ee997524102a upstream. > > > > Each ondisk inode should be aligned with inode slot boundary > > (32-byte alignment) because of

Re: [PATCH for-4.19] erofs: fix extended inode could cross boundary

2021-04-26 Thread Greg Kroah-Hartman
On Mon, Apr 26, 2021 at 04:29:33PM +0800, Gao Xiang wrote: > commit 0dcd3c94e02438f4a571690e26f4ee997524102a upstream. > > Each ondisk inode should be aligned with inode slot boundary > (32-byte alignment) because of nid calculation formula, so all > compact inodes (32 byte) cannot across page

[PATCH for-4.19] erofs: fix extended inode could cross boundary

2021-04-26 Thread Gao Xiang
commit 0dcd3c94e02438f4a571690e26f4ee997524102a upstream. Each ondisk inode should be aligned with inode slot boundary (32-byte alignment) because of nid calculation formula, so all compact inodes (32 byte) cannot across page boundary. However, extended inode is now 64-byte form, which can across