From: Al Viro <viro@ZenIV.linux.org.uk>
To: linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [RFC] open_by_handle() vs. EA inodes
Date: Fri, 29 Jun 2018 19:19:00 +0100 [thread overview]
Message-ID: <20180629181900.GP30522@ZenIV.linux.org.uk> (raw)
On ea_inode-enabled ext4 open_by_handle() (as well as knfsd, etc.)
can get to EA inodes as long as it knows their inumbers - just pass it
an fhandle with zeroed version bytes and the right inumber in it.
AFAICS, it's Not Nice(tm), especially since you can write to those,
whether they are shared or not.
Should we make ext4_nfs_get_inode() check for EXT4_EA_INODE_FL
and fail if it's set?
next reply other threads:[~2018-06-29 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 18:19 Al Viro [this message]
2018-06-29 19:38 ` [RFC] open_by_handle() vs. EA inodes Trond Myklebust
2018-06-29 19:57 ` Al Viro
2018-06-29 20:15 ` Al Viro
2018-07-03 16:46 ` Darrick J. Wong
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=20180629181900.GP30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).