Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <a91ef2fb-09ed-51ae-5dfa-8f71ec81f20c@tony.gen.nz>
References: <decdbe00-2292-3012-d7ae-6bfa382fc74a@tony.gen.nz>
 <1525165387.23227.44.camel@petrovitsch.priv.at> <a91ef2fb-09ed-51ae-5dfa-8f71ec81f20c@tony.gen.nz>
From:   Richard Weinberger <richard.weinberger@gmail.com>
Date:   Tue, 1 May 2018 13:04:36 +0200
Message-ID: <CAFLxGvxpe78WhrEKcKRt5XRBMtT-mZUe9Bm=sQsn8-f1TnX0eQ@mail.gmail.com>
Subject: Re: Suggested new user link command
To:     Tony Wallace <tony@tony.gen.nz>
Cc:     Bernd Petrovitsch <bernd@petrovitsch.priv.at>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, May 1, 2018 at 12:58 PM, Tony Wallace <tony@tony.gen.nz> wrote:
> Good point.  But there are gid and uid fields in inode disc record.
>
> https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table
>
> I assume these can be use to ensure that the directory in which it is to
> be placed has permissions to accept the inode.  If that is not the case
> then it would have to be a root only syscall.

Before we dig into details, please come up with a very good use case. :-)
But I'm with Bernd, I don't think it is worth the permissions hassle.

-- 
Thanks,
//richard