Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751778AbdHAKei (ORCPT ); Tue, 1 Aug 2017 06:34:38 -0400 Received: from mail-yw0-f195.google.com ([209.85.161.195]:34727 "EHLO mail-yw0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750852AbdHAKeg (ORCPT ); Tue, 1 Aug 2017 06:34:36 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Amir Goldstein Date: Tue, 1 Aug 2017 13:34:34 +0300 Message-ID: Subject: Re: xattr hash error in 4.13-rc with overlayfs over ext4 To: Miklos Szeredi Cc: Tahsin Erdogan , "Theodore Ts'o" , "linux-ext4@vger.kernel.org" , linux-fsdevel , lkml , "linux-unionfs@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 983 Lines: 26 On Mon, Jul 31, 2017 at 7:08 PM, Miklos Szeredi wrote: > On Thu, Jul 27, 2017 at 10:54 PM, Tahsin Erdogan wrote: >> Still no luck reproducing the error. I am using the test script below >> at v4.13-rc2. Do you mind checking my script to see what I am missing? > > Don't know. I can reliably reproduce it under UML, but not with a > VM. What the hell is going on? > Is it the same ext4 image for UML and VM? same image size? same mkfs version? What inode size do you have in UML setup? e.g.: dumpe2fs -h /dev/sda3|grep Inode.size dumpe2fs 1.42.13 (17-May-2015) Inode size: 256 have extra_isize feature? (not sure if that matters) dumpe2fs -h /dev/sda3|grep isize dumpe2fs 1.42.13 (17-May-2015) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Required extra isize: 28 Desired extra isize: 28