From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: viro@ZenIV.linux.org.uk
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Do we need DCACHE_WHITEOUT_TYPE?
Date: Mon, 18 Jun 2018 07:27:09 -0500 [thread overview]
Message-ID: <20180618122709.2dims4vjfa26drb3@merlin> (raw)
Hi,
There are some DCACHE_*_TYPE which are not used. I assume they were
added during the development of overlayfs/unionfs and do not seem to
make sense to keep.
Should we revert the following commits?
155e35d4daa8 ("VFS: Introduce inode-getting helpers for layered/unioned fs environments")
e7f7d2253c05 ("VFS: Add a whiteout dentry type")
df1a085af1f6 ("VFS: Add a fallthrough flag for marking virtual dentries")
Are there any more commits related or during this merge which are not
relevant anymore?
Regards,
--
Goldwyn
next reply other threads:[~2018-06-18 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 12:27 Goldwyn Rodrigues [this message]
2018-06-18 15:29 ` Do we need DCACHE_WHITEOUT_TYPE? David Howells
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=20180618122709.2dims4vjfa26drb3@merlin \
--to=rgoldwyn@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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