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;
Message-ID: <1525165387.23227.44.camel@petrovitsch.priv.at>
Subject: Re: Suggested new user link command
From:   Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To:     Tony Wallace <tony@tony.gen.nz>, linux-kernel@vger.kernel.org
Date:   Tue, 01 May 2018 11:03:07 +0200
In-Reply-To: <decdbe00-2292-3012-d7ae-6bfa382fc74a@tony.gen.nz>
References: <decdbe00-2292-3012-d7ae-6bfa382fc74a@tony.gen.nz>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi 

On Tue, 2018-05-01 at 20:03 +1200, Tony Wallace wrote:
> I am suggesting a new command for linking files.  Currently there is
> no
> easy way to link a file with a known inode number to its correct
> position in the directory tree.  
> 
> 
> int ilink(const int inode, const char *newpath)

... avoiding any permission checks on all paths to the existing names.

> The current alternative to this command is to find the file path
> associated with an inode using the find command and then once found
> using a standard link command.  Obviously this is very inefficient.  

That's the price for security as it requires proper permissions.
Or is this a root-only syscall?

MfG,
	Bernd
-- 
Bernd Petrovitsch                  Email : bernd@petrovitsch.priv.at
                     LUGA : http://www.luga.at