From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-fsdevel@vger.kernel.org
Subject: Re: Question about overlayfs ovl_link
Date: Wed, 29 Feb 2012 14:09:27 +0900 [thread overview]
Message-ID: <25498.1330492167@jrobl> (raw)
In-Reply-To: <CAFZ0FUX0VFnKxYR0+tM4dM41u3fAZij0QRgqV=ms+9XO1JufRQ@mail.gmail.com>
Robin Dong:
> There are two ways to fix this problem.
> First, traverse all alias of inode to find a non-zero-d_count dentry,
> this may be inefficient
> Second, create a new overlayfs inode and a new overlayfs dentry in
> ovl_link, that will make the result of two actions
> ("create link" then "mount", or "mount" then "create link") consistent.
How about third one (as for the original "two inodes" problem)?
- create a table to convert the uppderdir (real) inode number into the
overlayfs (virtual) inode number.
- using the table, you can get the virtual inum from the real inum.
- as long as you have a single real inum (for hardlinks), you will get a
single virtual inum.
J. R. Okajima
next prev parent reply other threads:[~2012-02-29 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 3:57 Question about overlayfs ovl_link Robin Dong
2012-02-28 8:41 ` Miklos Szeredi
2012-02-29 3:47 ` Robin Dong
2012-02-29 5:09 ` J. R. Okajima [this message]
2012-03-01 19:51 ` 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=25498.1330492167@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=hao.bigrat@gmail.com \
--cc=linux-fsdevel@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