linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Katz <jkatz@eitmlabs.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: jonathan@eitm.org,
	"Christian Kohlschütter" <christian@kohlschutter.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] [REGRESSION] ovl: Handle ENOSYS when fileattr support is missing in lower/upper fs
Date: Tue, 7 Mar 2023 09:14:08 -0800	[thread overview]
Message-ID: <CALKgVmcC1VUV_gJVq70n--omMJZUb4HSh_FqvLTHgNBc+HCLFQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfpeguKVzCyUraDQPGw6vdQFfPwTCuZv0JkMxNA69AiRib3kg@mail.gmail.com>

On Tue, Mar 7, 2023 at 12:38 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Tue, 7 Mar 2023 at 02:12, Jonathan Katz <jkatz@eitmlabs.org> 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 PM Jonathan Katz <jkatz@eitmlabs.org> 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=off,index=off,nfs_export=off.
> > >
> > >
> > >
> > > 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-1722.d/Storage.mcf_idx,
> > > err=-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-1722.d/Storage.mcf_idx,
> > > err=-38)
> > >
> > >
> > > On Mon, Jan 30, 2023 at 11:27 AM Jonathan Katz <jkatz@eitmlabs.org> wrote:
> > > >
> > > > On Thu, Jan 26, 2023 at 5:26 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
> > > > >
> > > > > On Wed, 18 Jan 2023 at 04:41, Jonathan Katz <jkatz@eitmlabs.org> 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 this
> > > > > > discussion.  I apologize up front for any faux pas I make in writing
> > > > > > 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 distro you
> > > > > are using.
> > > >
> > > > Thank you for the reply! ---  I have upgraded the Kernel and it still
> > > > 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 kernel:
> > > > [   71.613334] overlayfs: null uuid detected in lower fs '/', falling
> > > > back to xino=off,index=off,nfs_export=off.
> > > >
> > > > 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 kernel:
> > > > [  539.181858] overlayfs: failed to retrieve lower fileattr (8020
> > > > MeOHH2O RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1722.d/Storage.mcf_idx,
> > > > err=-38)
> > > >
> > > > And on the Windows client, the software still fails with the same symptomology.
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > > An example error from our syslog:
> > > > > >
> > > > > > kernel: [2702258.538549] overlayfs: failed to retrieve lower fileattr
> > > > > > (8020 MeOHH2O
> > > > > > RecoverySample2-20221219-A-JJL-WebinarHilic10C-TOF-TT54-Neg-1722.d/analysis.tsf,
> > > > > > err=-38)
> > > > >
> > > > > Yep, looks like the same bug.
> > > > >
> > > > > Thanks,
> > > > > Miklos

  reply	other threads:[~2023-03-07 17:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 18:36 [PATCH] ovl: Handle ENOSYS when fileattr support is missing in lower/upper fs Christian Kohlschütter
2022-07-18  9:14 ` Miklos Szeredi
2022-07-18 10:10   ` Christian Kohlschütter
2022-07-18 10:31     ` Miklos Szeredi
2022-07-18 10:56       ` Christian Kohlschütter
2022-07-18 12:21         ` Miklos Szeredi
2022-07-18 13:03           ` [PATCH] [REGRESSION] " Christian Kohlschütter
2022-07-18 13:13             ` Miklos Szeredi
2022-07-18 14:25               ` Christian Kohlschütter
2022-07-18 15:02                 ` Antonio SJ Musumeci
2022-07-18 17:23                 ` Miklos Szeredi
2022-07-18 18:29               ` Linus Torvalds
2022-07-18 19:04                 ` Christian Kohlschütter
2022-07-18 19:17                   ` Linus Torvalds
2022-07-18 19:27                     ` Miklos Szeredi
2022-07-18 20:12                       ` Linus Torvalds
2022-07-18 20:33                         ` Christian Kohlschütter
2023-01-18  3:41                           ` Jonathan Katz
2023-01-26 13:26                             ` Miklos Szeredi
2023-01-30 19:27                               ` Jonathan Katz
2023-02-23 23:11                                 ` Jonathan Katz
2023-03-07  1:12                                   ` Jonathan Katz
2023-03-07  8:38                                     ` Miklos Szeredi
2023-03-07 17:14                                       ` Jonathan Katz [this message]
2023-03-09 15:31                                         ` Miklos Szeredi
2023-03-15  2:43                                           ` Jonathan Katz
2023-03-22 18:42                                             ` Jonathan Katz
2023-04-21 14:26                                               ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALKgVmcC1VUV_gJVq70n--omMJZUb4HSh_FqvLTHgNBc+HCLFQ@mail.gmail.com \
    --to=jkatz@eitmlabs.org \
    --cc=christian@kohlschutter.com \
    --cc=jonathan@eitm.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).