From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Miklos Szeredi <miklos@szeredi.hu>,
Antonio SJ Musumeci <trapexit@spawn.link>
Cc: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [fuse-devel] Proxmox + NFS w/ exported FUSE = EIO
Date: Mon, 19 Feb 2024 20:55:33 +0100 [thread overview]
Message-ID: <8fd58ae6-164c-4653-a979-b12ee577fe65@fastmail.fm> (raw)
In-Reply-To: <CAJfpegvSuYPm-oZz8D3Vn-ovA6GXesXEiwvHTPeG5CzXQPQWDg@mail.gmail.com>
On 2/19/24 20:38, Miklos Szeredi wrote:
> On Mon, 19 Feb 2024 at 20:05, Antonio SJ Musumeci <trapexit@spawn.link> wrote:
>
>> This is what I see from the kernel:
>>
>> lookup(nodeid=3, name=.);
>> lookup(nodeid=3, name=..);
>> lookup(nodeid=1, name=dir2);
>> lookup(nodeid=1, name=..);
>> forget(nodeid=3);
>> forget(nodeid=1);
>
> This is really weird. It's a kernel bug, no arguments, because kernel
> should never send a forget against the root inode. But that
> lookup(nodeid=1, name=..); already looks bogus.
Why exactly bogus?
reconnect_path()
if (IS_ROOT(dentry))
parent = reconnect_one(mnt, dentry, nbuf);
reconnect_one()
if (mnt->mnt_sb->s_export_op->get_parent)
parent = mnt->mnt_sb->s_export_op->get_parent(dentry);
fuse_get_parent()
if (!fc->export_support)
return ERR_PTR(-ESTALE);
err = fuse_lookup_name(child_inode->i_sb, get_node_id(child_inode),
&dotdot_name, &outarg, &inode);
Thanks,
Bernd
next prev parent reply other threads:[~2024-02-19 19:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d997c02b-d5ef-41f8-92b6-8c6775899388@spawn.link>
2024-02-06 6:53 ` [fuse-devel] Proxmox + NFS w/ exported FUSE = EIO Amir Goldstein
2024-02-07 0:08 ` Antonio SJ Musumeci
2024-02-07 7:24 ` Amir Goldstein
[not found] ` <b9cec6b7-0973-4d61-9bef-120e3c4654d7@spawn.link>
[not found] ` <CAOQ4uxgZR4OtCkdrpcDGCK-MqZEHcrx+RY4G94saqaXVkL4cKA@mail.gmail.com>
2024-02-18 0:48 ` Antonio SJ Musumeci
2024-02-19 11:36 ` Bernd Schubert
2024-02-19 19:05 ` Antonio SJ Musumeci
2024-02-19 19:17 ` Bernd Schubert
2024-02-19 19:38 ` Miklos Szeredi
2024-02-19 19:54 ` Antonio SJ Musumeci
2024-02-20 8:35 ` Miklos Szeredi
2024-02-20 8:47 ` Miklos Szeredi
2024-02-22 1:25 ` Antonio SJ Musumeci
2024-02-22 11:09 ` Miklos Szeredi
2024-02-25 0:18 ` Antonio SJ Musumeci
2024-02-25 20:58 ` Antonio SJ Musumeci
2024-02-28 13:06 ` Miklos Szeredi
2024-02-28 13:16 ` Bernd Schubert
2024-02-28 14:14 ` Miklos Szeredi
2024-02-28 16:03 ` Miklos Szeredi
2024-02-19 19:55 ` Bernd Schubert [this message]
2024-02-19 19:58 ` Miklos Szeredi
2024-02-19 21:14 ` Bernd Schubert
2024-02-19 23:22 ` Bernd Schubert
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=8fd58ae6-164c-4653-a979-b12ee577fe65@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=amir73il@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=trapexit@spawn.link \
/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).