From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeniv.linux.org.uk ([195.92.253.2]:41660 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754309AbeF2STB (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Fri, 29 Jun 2018 14:19:01 -0400
Date: Fri, 29 Jun 2018 19:19:00 +0100
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
Message-ID: <20180629181900.GP30522@ZenIV.linux.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

	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?