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 50B9DC7618D for ; Wed, 15 Mar 2023 02:43:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229866AbjCOCn5 (ORCPT ); Tue, 14 Mar 2023 22:43:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229447AbjCOCny (ORCPT ); Tue, 14 Mar 2023 22:43:54 -0400 Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DC1DE4ED3 for ; Tue, 14 Mar 2023 19:43:52 -0700 (PDT) Received: by mail-ed1-x52c.google.com with SMTP id eg48so10765046edb.13 for ; Tue, 14 Mar 2023 19:43:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitmlabs-org.20210112.gappssmtp.com; s=20210112; t=1678848231; 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=Xv/KwFdMS345PsD2cRZ5r2isPNxArVDf2kl5yWiyxg4=; b=oSUr1P3Mh2bnvl5YbmLojhXl3hKajgoP4UUJ0h2WpN3yPv8TqkzQzzPDrI6BQcZ2ox 8KCJXE/bK6C/oROKXSw1AIo9GGzjuQTKbjgSN/fGtRAUhH0XcBkxEzc0NeDAAX0enBmA im/JL1xwbQmVTUGmLwvh6wTufkMwB11K0/8TMT64cflL1SjwUeemQ0QOIXSyknU0dc36 2jQS1p0QJPNiJmaqAH6qDlgpcLhcxvDD5gfrf8QYZgBOKhp2wJcGskAHLt9Ivg/0u52b NVKRtNTFLTRjvhLZA3m7YpHtwN+7jt8SrXMIX09E4HHZl6/ONYEVygfwpJ6/YF4I8o+2 T5nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678848231; 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=Xv/KwFdMS345PsD2cRZ5r2isPNxArVDf2kl5yWiyxg4=; b=BCP4A3RWf6W5o34fTtyHSW7sjy7B5mr2StgzLYVti8DiSO9YeOd/sBEKkM/DNT9Z/L vQTtoXZ3E+yZ3pTDPkbn96u1aaVPDtrYhuHbf8rtKCZkUHkG6oeIUwxJ0ESjQX9c18K9 uX0POsPfDmstpjU/+Q95p0c8fr4EfmhVQ5MtPkN0qVRrzfXjnxaherzMg6uRYDsohMaf ZYBXyFMJTYRhTIRAyfsx/c26nb/P+o5i5YMZLaYgAXMxENFkKNFR76/9Q2KiP0mvafIC 7HV2WlnEZFJtxQ5zH7Q/7A7KrihIRytTXefTkM3hhQ503FlkS/zWwq2yYYy8OmnAFxjS Dp+Q== X-Gm-Message-State: AO0yUKUlMLLiKGYw7ULdRYhGkdo8l3tSGf/qLjfvghW9H/XHhxxvreG6 YllWelU0DQTPF0jez6QldfYvfwj/Xeu2sFznX6sg2EmZMdpcoz+l6hgXOA== X-Google-Smtp-Source: AK7set8Icq2mcZlatdiH3bxNqw9x8fpR+kvFgydUcVFMGgpA698EXIWcPQ0r/BKLCPUo3rcc6VtjdlCvYpswKWOgsfc= X-Received: by 2002:a50:9f64:0:b0:4fa:71a2:982b with SMTP id b91-20020a509f64000000b004fa71a2982bmr597589edf.0.1678848231309; Tue, 14 Mar 2023 19:43:51 -0700 (PDT) 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, 14 Mar 2023 19:43:34 -0700 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 Thu, Mar 9, 2023 at 7:31=E2=80=AFAM Miklos Szeredi w= rote: > > On Tue, 7 Mar 2023 at 18:14, Jonathan Katz wrote: > > > > 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 pat= ch > > > > was never committed to the main source tree (sorry if my terminolog= y > > > > 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 i= f > > > > there was some reason that it was not applied (e.g. it introduces s= ome > > > > 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" > > Can you please run bindfs in debugging mode (-d) and send the > resulting log after reproducing the issue? > > Thanks, > Miklos OUCH -- MY LAST EMAIL WAS REJECTED FOR BEING TOO BIG I HOPE THAT I AM SUMMARIZING THE RELEVANT INFORMATION HERE: Hi Miklos, thank you.... I am sorry for the delay. The log is somewhat long and was sent in a separate email. I broke up the log into entries to try to match the chronology of actions: * ENTRY 1 nfs mount the external drive * ENTRY 2 perform the bind fs * ENTRY 3 perform the overlay * ENTRY 4 restart smb * ENTRY 5 mount the filesystem on a windows box * ENTRY 6 performing some navigation on the windows file explorer * ENTRY 7 attempt to open a data file with the windows application. The only place that generated a kernel error in dmesg was at ENTRY 7. Because the logs are so big, I tried to parse them, I may have made a mistake or omitted information -- if you think so, as mentioned, the full bindfs logs were sent separately Here is my attempt to parse out the errors associated with this dmesg entry= : [ 1925.705908] overlayfs: failed to retrieve lower fileattr (8020 MeOHH2O RecoverySample1-20221216-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1632.d/= chromatography-data.sqlite, err=3D-38) -- unique: 1550, opcode: GETXATTR (22), nodeid: 71, insize: 73, pid: 3458 getxattr /eimstims1/deleteme2/8020 MeOHH2O RecoverySample1-20221216-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1632.d/chromato= graphy-data-pre.sqlite trusted.overlay.metacopy 0 unique: 1550, error: -95 (Operation not supported), outsize: 16 -- unique: 3922, opcode: GETXATTR (22), nodeid: 71, insize: 72, pid: 3458 getxattr /eimstims1/deleteme2/8020 MeOHH2O RecoverySample1-20221216-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1632.d/chromato= graphy-data-pre.sqlite system.posix_acl_access 132 unique: 3922, error: -95 (Operation not supported), outsize: 16 -- unique: 3954, opcode: GETXATTR (22), nodeid: 71, insize: 72, pid: 3458 getxattr /eimstims1/deleteme2/8020 MeOHH2O RecoverySample1-20221216-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1632.d/chromato= graphy-data-pre.sqlite system.posix_acl_access 132 unique: 3954, error: -95 (Operation not supported), outsize: 16 -- unique: 3960, opcode: GETXATTR (22), nodeid: 71, insize: 72, pid: 3458 getxattr /eimstims1/deleteme2/8020 MeOHH2O RecoverySample1-20221216-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1632.d/chromato= graphy-data-pre.sqlite system.posix_acl_access 132 unique: 3960, error: -95 (Operation not supported), outsize: 16 Thank you again! -Jonathan