Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp332235pxj; Fri, 14 May 2021 04:43:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyn7SjjZUOUY2RiwWNvLihLH2GTzbyzETPhnvyh8Acr4RvKM0gzLbE5NmoFNV9lu1OCbL9C X-Received: by 2002:a17:906:b315:: with SMTP id n21mr48283023ejz.219.1620992633743; Fri, 14 May 2021 04:43:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620992633; cv=none; d=google.com; s=arc-20160816; b=JwvymILTDJxE46OH5FL9Ih67k1oLhIp84t+Wn5G0C3i263gl/02KfMUussNtd6Xhgn BirSPtHlrh++v3hX3hmcxTncrSWmpKXcKjAPIQUkqC24PsZKidNJ2EW6Kls5GWJeN2Z1 aUKCVaW7kbNwVoS10ZdjYVryRFAmbKRFBwbc4XjYkuMAEofiRAJ22tg+YVsBVn3NJI0n kkSekJLaw4ginOyJHWg+c4gxop7Bc1/YB7CRcTr/WCtzx51TpB6R4UbLlb/GoJTgQ9cx NUMwCxhjD4LpChyc8OdibqFb2OPfvHYmUSDK+ZkLg/hYfa+qOcULa1CFcb5r7d2hVsF8 WSzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:to:subject:message-id :date:from:in-reply-to:references:mime-version:dkim-signature; bh=uBdbEWH3X+scS8Nyxw8OcymFh2SsY7MeUYXlJf//Dp0=; b=Vw0FYlovU6dkG+opQgxTlTR1drcokASofV9nXt6qC8VXbn9Wme46rv5iTh/8NdPDtp efQSbLhxGrxHcrsGpc0xLapaNEEdHlWENtyeEAb5LKY+uOJnQ7tYIFt5mMvUFrWLB0YI U2JdiDURkrC48slun/AhSJOty78bTvS7RDX1sydnSReVV2OlcBWANhHLDmQXSdtp14AG yMMxkiN04ceWeqc8VJIFOHEXk6cJjBBj/nE765kcET1P4t+NZut9+VgcI0kvRZpfvt9U lMCirHZeqwrr2lXJuP3ebQCQZAJuFUpdIwfZflx81W/nIWQ5ydMpCKkcoTRbrc5x5rD2 IQ6Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=uyQignAY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o3si6165997ejc.81.2021.05.14.04.43.29; Fri, 14 May 2021 04:43:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=uyQignAY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231645AbhENLnN (ORCPT + 99 others); Fri, 14 May 2021 07:43:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43008 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229445AbhENLnN (ORCPT ); Fri, 14 May 2021 07:43:13 -0400 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3935FC061574 for ; Fri, 14 May 2021 04:42:02 -0700 (PDT) Received: by mail-ed1-x533.google.com with SMTP id a25so10221141edr.12 for ; Fri, 14 May 2021 04:42:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=uBdbEWH3X+scS8Nyxw8OcymFh2SsY7MeUYXlJf//Dp0=; b=uyQignAYQ7SFA9aPkbXJ3JEYnSw8j8fcGGf6bhERQ+TZfYo+QUhwNme6jUNuJ0pDv+ 64k8yElvjX1YwkdKLD0J04StiU+eyro1gQ5g0qJ5WFmTW/Rz31ztcumVLq6L7N+4mGfF e7AESFy0xdo0+dZNZwPmBaQA4Kp/1KqeVJY6vBhpClKkPnk/FelGnJSaDzHcK3jPywo1 bonmsyFbqW8tyGhu4c/ROyNfcZ/eeUeVps0pgO+9AYpS6H1fkvVkm9jzYfvvDV53oOJy n+hPqaDmPYTS4WHKXGYUnqzOWWnsLpnAHYvUf8Ykmoqo7QLIpHCd0+CV8wHZ+LNA3Qtm Xj6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=uBdbEWH3X+scS8Nyxw8OcymFh2SsY7MeUYXlJf//Dp0=; b=iPVVWlWTh5SwYoZwZvl6m2rsw9e2zDPQe60CV5U36kN1mNbpUkF37jztwo8UDu3B0W ef5QTzFtCEhtICztRU/DCeoLcl8csec+VdPtBO3Ptx1Pn85h+8XvNEIXP3SiPU9q9nul 0AwwBfW7ck7uBP4KEcpby0KOEXowR2NyQPdUWndYl+mSupOfUtxsQX0Ncvgn3tZDRR6A onFBJl+MXTxL7puQywoAUkYIziV+EqKhdQvTfy3UcToVhPGAGgLRlhc9Smdd6ODSGtli SmPiYO+9hPXS4QymehPFyIwFGjfk6Z88MA1n4BhuXChbOF0BBapzhpL0Sz7k6QDIAU40 EE6Q== X-Gm-Message-State: AOAM531CSI0P0crGolXvGCPQ3LFZMZtQ50ItxFFDvQIjKfqMJ79dg6Yh qvVKBhhQ2XiuYCUihFANzh1V7CM50N34IQobbOg= X-Received: by 2002:a05:6402:11c7:: with SMTP id j7mr56476798edw.129.1620992520957; Fri, 14 May 2021 04:42:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pintu Agarwal Date: Fri, 14 May 2021 17:11:49 +0530 Message-ID: Subject: Re: Kernel 4.14: SQUASHFS error: unable to read xattr id index table To: phillip@squashfs.org.uk, linux-fsdevel@kvack.org, open list , sean@geanix.com, linux-mtd@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This is regarding the squashfs mount failure that I am getting on my device during boot time. I just wanted to know if someone else has come across this issue, or this issue is already fixed, or this is altogether a different issue? Here are more details: Kernel: 4.14.170 ; Qualcomm chipset (arm32 bit) Platform: busybox Storage: NAND 512MB Filesystem: ubifs + squashfs ubi0 : with 5 volumes (rootfs, usrfs, others) Kernel command line: ro rootwait console=3DttyMSM0,115200,n8 rootfstype=3Dsquashfs root=3D/dev/mtdblock34 ubi.mtd=3D30,0,30 .... Background: We are using ubifs filesystem with squashfs for rootfs (as ready only). First we tried to flash "usrfs" (data) volume (ubi0_1) and it worked fine (with device booting successfully). Next we are trying to flash "rootfs" volume (ubi0_0) now. The volume flashing is successful but after that when we reboot the system we are getting below errors. Logs: [....] [ 4.589340] vreg_conn_pa: dis=E2=96=92[ 4.602779] squashfs: SQUASHFS error: unable to read xattr id index table [...] [ 4.964083] No filesystem could mount root, tried: [ 4.964087] squashfs [ 4.966255] [ 4.973443] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,34) ----------- [ 4.246861] ubi0: attaching mtd30 [ 4.453241] ubi0: scanning is finished [ 4.460655] ubi0: attached mtd30 (name "system", size 216 MiB) [ 4.460704] ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 byt= es [ 4.465562] ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 409= 6 [ 4.472483] ubi0: VID header offset: 4096 (aligned 4096), data offset: 8= 192 [ 4.479295] ubi0: good PEBs: 864, bad PEBs: 0, corrupted PEBs: 0 [ 4.486067] ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128 [ 4.492311] ubi0: max/mean erase counter: 4/0, WL threshold: 4096, image sequence number: 1 [ 4.499333] ubi0: available PEBs: 0, total reserved PEBs: 864, PEBs reserved for bad PEB handling: 60 So, we just wanted to know if this issue is related to squashfs or if there is some issue with our volume flashing. Note: We are using fastboot mechanism to support UBI volume flashing. Observation: Recently I have seen some squashfs changes related to similar issues (xattr) so I wanted to understand if these changes are relevant to our issue or not ? Age Commit message(Expand) Author 2021-03-30 squashfs: fix xattr id and id lookup sanity checks Phillip Lougher 2021-03-30 squashfs: fix inode lookup sanity checks Sean Nyekjaer 2021-02-23 squashfs: add more sanity checks in xattr id lookup Phillip Lougher 2021-02-23 squashfs: add more sanity checks in inode lookup Phillip Lougher 2021-02-23 squashfs: add more sanity checks in id lookup Phillip Lougher Please let us know your opinion about this issue... It will help us to decide whether the issue is related to squashfs or not. Thanks, Pintu