From: Miklos Szeredi <miklos@szeredi.hu>
To: Lukasz Okraszewski <Lukasz.Okraszewski@arm.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Matthew Clarkson <Matthew.Clarkson@arm.com>,
Brandon Jones <Brandon.Jones@arm.com>, nd <nd@arm.com>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [overlay] [fuse] Potential bug with large file support for FUSE based lowerdir
Date: Thu, 1 Feb 2024 10:28:01 +0100 [thread overview]
Message-ID: <CAJfpegv+jknMnAAYKnZvemvjqi26X59HRRg7-JhDYVFe4MG93Q@mail.gmail.com> (raw)
In-Reply-To: <VI1PR08MB3101AA24E1406DBCA133DC7782432@VI1PR08MB3101.eurprd08.prod.outlook.com>
On Thu, 1 Feb 2024 at 10:24, Lukasz Okraszewski
<Lukasz.Okraszewski@arm.com> wrote:
>
>
> <miklos@szeredi.hu> wrote:
> > On Thu, 1 Feb 2024 at 09:01, Lukasz Okraszewski
> > <Lukasz.Okraszewski@arm.com> wrote:
> > >
> > > > So this is a FUSE_IOCTL/FS_IOC_GETFLAGS request for which the server
> > > > replies with EOVERFLOW. This looks like a server issue, but it would
> > > > be good to see the logs and/or strace related to this particular
> > > > request.
> > > >
> > > > Thanks,
> > > > Miklos
> > >
> > > Thanks for having a look!
> > >
> > > I have attached the logs. I am running two lower dirs but I don't think it should matter.
> > > For clarify the steps were:
> >
> > What kernel are you running?
> >
> > uname -r
>
> On this current machine it's pretty old: 5.15.0-89-generic (Ubuntu Jammy).
> We have seen this on Arch with 6.6.12-1-lts, if you give me some time I can set up the repro on that again and get the logs if that's helpful.
Please try on a recent vanilla kernel as distro kernels can have
patches that modify behavior.
Thanks,
Miklos
prev parent reply other threads:[~2024-02-01 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR08MB31011DF4722B9E720A251892827C2@VI1PR08MB3101.eurprd08.prod.outlook.com>
2024-01-31 19:49 ` [overlay] [fuse] Potential bug with large file support for FUSE based lowerdir Miklos Szeredi
2024-02-01 8:01 ` Lukasz Okraszewski
2024-02-01 8:23 ` Miklos Szeredi
2024-02-01 9:24 ` Lukasz Okraszewski
2024-02-01 9:28 ` Miklos Szeredi [this message]
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=CAJfpegv+jknMnAAYKnZvemvjqi26X59HRRg7-JhDYVFe4MG93Q@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=Brandon.Jones@arm.com \
--cc=Lukasz.Okraszewski@arm.com \
--cc=Matthew.Clarkson@arm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=nd@arm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).