From: "YoungJun.Park" <her0gyugyu@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: Question about ESTALE error whene deleting upper directory file.
Date: Sun, 6 Nov 2022 20:29:32 -0800 [thread overview]
Message-ID: <20221107042932.GB1843153@ubuntu> (raw)
Here is my curious scenario.
1. create a file on overlayfs.
2. delete a file on upper directory.
3. can see file contents using read sys call. (may file operations all success)
4. cannot remove, rename. it return -ESTALE error (may inode operations fail)
I understand this scenario onto the code level.
But I don't understand this situation itself.
I found a overlay kernel docs and it comments
Changes to underlying filesystems section
...
Changes to the underlying filesystems while part of a mounted overlay filesystem are not allowed.
If the underlying filesystem is changed, the behavior of the overlay is undefined,
though it will not result in a crash or deadlock.
....
So here is my question (may it is suggestion)
1. underlying file system change is not allowed, then how about implementing shadow upper directory from user?
2. if read, write system call is allowed, how about changing remove, rename(and more I does not percept) operation success?
Best Regards.
next reply other threads:[~2022-11-07 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 4:29 YoungJun.Park [this message]
2022-11-07 6:40 ` Question about ESTALE error whene deleting upper directory file Amir Goldstein
2022-11-07 7:06 ` YoungJun.Park
2022-11-07 8:49 ` Amir Goldstein
2022-11-08 8:14 ` YoungJun.Park
[not found] ` <CAOQ4uxi2aGUOCrPb55Q9LGVbqz4M9ZKOhNLnm8kKnsDQgdxYHQ@mail.gmail.com>
2022-11-08 12:37 ` YoungJun.Park
2022-11-08 19:22 ` Amir Goldstein
2022-11-09 4:16 ` YoungJun.Park
2022-11-09 9:16 ` Amir Goldstein
2022-11-09 9:34 ` YoungJun.Park
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=20221107042932.GB1843153@ubuntu \
--to=her0gyugyu@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).