Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B471EC6FD1D for ; Tue, 7 Mar 2023 17:19:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231310AbjCGRT2 (ORCPT ); Tue, 7 Mar 2023 12:19:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59666 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231272AbjCGRSx (ORCPT ); Tue, 7 Mar 2023 12:18:53 -0500 Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D63BD97FCA for ; Tue, 7 Mar 2023 09:14:26 -0800 (PST) Received: by mail-ed1-x532.google.com with SMTP id ec29so24400071edb.6 for ; Tue, 07 Mar 2023 09:14:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitmlabs-org.20210112.gappssmtp.com; s=20210112; t=1678209265; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uwDUxJcDJcMxnTkL2V+YwQldX6E+/2r615N9qnjsQ5k=; b=loV6EpaQge6cTIm0ELzvl+6/bRyrJcc6FOYdFs0TRbxcEZGfB54dpAEyz14LRrDp50 P4H64uZoqdhR0rZE2NHKOe0NtYGy7ifOi/XD8e15TdxPvtPrIvHtR9+5xSssfxZiv1N0 EXIkf3Egrn1M8zOzQYhhfhKBFlqIhOZe1gSVeRAaZ+9fS4wJgL8XgqlNCXbiwGv6Hzcr m/CrckAS/z3o1tWyQyDSo0Zh+ASo6JuCnqud7J2RSwVzwI69IIHm7axl8kSorq+ws5pg uFqX9/V2NfyADasJ19Uzd3txoFCkMHnUxJEngMSTpmZ/XJ8mRyERbi4fEGqBWb6k9Khs MEJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678209265; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=uwDUxJcDJcMxnTkL2V+YwQldX6E+/2r615N9qnjsQ5k=; b=l4vnu2uezCYdlU+xdt/wF4XHHztsWGGJJ0hcf1Bctb+VXZ+otXkCqZcsqdI7cXORbX TnUrqaVYigCvMfirC+lnn7HSqhyD1IBU45V52UcIzQYeDYJetO1icaPwLyGGL1c3rZOE WEUyoiBESxkICgcMTRDAczljdyHkzjMNnJjFwlIEOI0LRRfm5ekGgoVVcE5z9/7kEdWb +Na3wmg4MO6C5oBEh1u2Myctq5hVqO5bGEwyBp6yv11LpYZU3I/OAm3Ig4uvm26wQhEu Tv9UckI8tWrH2R6tAwiNmlsAY03rCSIAB+9deHQlfDmkis02hsPjR9r+ZznpQNxosFS1 37Ow== X-Gm-Message-State: AO0yUKWXD5KHSu0XERhzMPt6F1OvQ6pMognBqYwkNaR2Hi4j1WJK4Hl7 nWmQGtNFoCahu4+Go6m5kJxgPwPhiAls7GJj3YHYNw== X-Google-Smtp-Source: AK7set/GhvrPLHOVoQw/QGOLf9lH9Ub7ISmxaTsewUUiP9pF0QT7WJRKuFmAjXI6QVFX7jksBphHX/IUgB80KGDUkME= X-Received: by 2002:a17:906:fcb9:b0:883:ba3b:eb94 with SMTP id qw25-20020a170906fcb900b00883ba3beb94mr7566442ejb.3.1678209265306; Tue, 07 Mar 2023 09:14:25 -0800 (PST) MIME-Version: 1.0 References: <4B9D76D5-C794-4A49-A76F-3D4C10385EE0@kohlschutter.com> <83A29F9C-1A91-4753-953A-0C98E8A9832C@kohlschutter.com> <56E6CAAE-FF25-4898-8F9D-048164582E7B@kohlschutter.com> <490c5026-27bd-1126-65dd-2ec975aae94c@eitmlabs.org> In-Reply-To: Reply-To: jonathan@eitm.org From: Jonathan Katz Date: Tue, 7 Mar 2023 09:14:08 -0800 Message-ID: Subject: Re: [PATCH] [REGRESSION] ovl: Handle ENOSYS when fileattr support is missing in lower/upper fs To: Miklos Szeredi Cc: jonathan@eitm.org, =?UTF-8?Q?Christian_Kohlsch=C3=BCtter?= , Linus Torvalds , overlayfs , linux-kernel , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 7, 2023 at 12:38=E2=80=AFAM Miklos Szeredi = wrote: > > On Tue, 7 Mar 2023 at 02:12, Jonathan Katz wrote: > > > > Hi all, > > > > In pursuing this issue, I downloaded the kernel source to see if I > > could debug it further. In so doing, it looks like Christian's patch > > was never committed to the main source tree (sorry if my terminology > > is wrong). This is up to and including the 6.3-rc1. I could also > > find no mention of the fix in the log. > > > > I am trying to manually apply this patch now, but, I am wondering if > > there was some reason that it was not applied (e.g. it introduces some > > instability?)? > > It's fixing the bug in the wrong place, i.e. it's checking for an > -ENOSYS return from vfs_fileattr_get(), but that return value is not > valid at that point. > > The right way to fix this bug is to prevent -ENOSYS from being > returned in the first place. > > Commit 02c0cab8e734 ("fuse: ioctl: translate ENOSYS") fixes one of > those bugs, but of course it's possible that I missed something in > that fix. > > Can you please first verify that an upstream kernel (>v6.0) can also > reproduce this issue? Got ya. that makes a lot of sense, thank you. I have confirmed that I continue to get the error with 6.2 . quick summary of the lowerdir: server ---- NFS(ro) ---- > client "/nfs" client "/nfs" --- bindfs(uidmap) --- > client "/lower" > > Thanks, > Miklos > > > > > > > Thank you, > > Jonathan > > > > > > > > On Thu, Feb 23, 2023 at 3:11=E2=80=AFPM Jonathan Katz wrote: > > > > > > Hi all, > > > > > > Problem persists with me with 6.2.0 > > > # mainline --install-latest > > > # reboot > > > > > > # uname -r > > > 6.2.0-060200-generic > > > > > > > > > Representative log messages when mounting: > > > Feb 23 22:50:43 instance-20220314-1510-fileserver-for-overlay kernel: > > > [ 44.641683] overlayfs: null uuid detected in lower fs '/', falling > > > back to xino=3Doff,index=3Doff,nfs_export=3Doff. > > > > > > > > > > > > Representative log messages when accessing files: > > > eb 23 23:06:31 instance-20220314-1510-fileserver-for-overlay kernel: = [ > > > 992.505357] overlayfs: failed to retrieve lower fileattr (8020 > > > MeOHH2O RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1= 722.d/Storage.mcf_idx, > > > err=3D-38) > > > Feb 23 23:06:32 instance-20220314-1510-fileserver-for-overlay kernel: > > > [ 993.523712] overlayfs: failed to retrieve lower fileattr (8020 > > > MeOHH2O RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1= 722.d/Storage.mcf_idx, > > > err=3D-38) > > > > > > > > > On Mon, Jan 30, 2023 at 11:27 AM Jonathan Katz w= rote: > > > > > > > > On Thu, Jan 26, 2023 at 5:26 AM Miklos Szeredi = wrote: > > > > > > > > > > On Wed, 18 Jan 2023 at 04:41, Jonathan Katz = wrote: > > > > > > > > > > > I believe that I am still having issues occur within Ubuntu 22.= 10 with > > > > > > the 5.19 version of the kernel that might be associated with th= is > > > > > > discussion. I apologize up front for any faux pas I make in wr= iting > > > > > > this email. > > > > > > > > > > No need to apologize. The fix in question went into v6.0 of the > > > > > upstream kernel. So apparently it's still missing from the distr= o you > > > > > are using. > > > > > > > > Thank you for the reply! --- I have upgraded the Kernel and it sti= ll > > > > seems to be throwing errors. Details follow: > > > > > > > > Distro: Ubuntu 22.10. > > > > Upgraded kernel using mainline (mainline --install-latest) > > > > > > > > # uname -a > > > > Linux instance-20220314-1510-fileserver-for-overlay > > > > 6.1.8-060108-generic #202301240742 SMP PREEMPT_DYNAMIC Tue Jan 24 > > > > 08:13:53 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > On mount I still get the following notice in syslog (representative= ): > > > > Jan 30 19:11:46 instance-20220314-1510-fileserver-for-overlay kerne= l: > > > > [ 71.613334] overlayfs: null uuid detected in lower fs '/', falli= ng > > > > back to xino=3Doff,index=3Doff,nfs_export=3Doff. > > > > > > > > And on access (via samba) I still see the following errors in the > > > > syslog (representative): > > > > Jan 30 19:19:34 instance-20220314-1510-fileserver-for-overlay kerne= l: > > > > [ 539.181858] overlayfs: failed to retrieve lower fileattr (8020 > > > > MeOHH2O RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg= -1722.d/Storage.mcf_idx, > > > > err=3D-38) > > > > > > > > And on the Windows client, the software still fails with the same s= ymptomology. > > > > > > > > > > > > > > > > > > > > > > > > > > > An example error from our syslog: > > > > > > > > > > > > kernel: [2702258.538549] overlayfs: failed to retrieve lower fi= leattr > > > > > > (8020 MeOHH2O > > > > > > RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg-172= 2.d/analysis.tsf, > > > > > > err=3D-38) > > > > > > > > > > Yep, looks like the same bug. > > > > > > > > > > Thanks, > > > > > Miklos