All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Tony Wallace <tony@tony.gen.nz>, linux-kernel@vger.kernel.org
Subject: Re: Suggested new user link command
Date: Tue, 01 May 2018 11:03:07 +0200	[thread overview]
Message-ID: <1525165387.23227.44.camel@petrovitsch.priv.at> (raw)
In-Reply-To: <decdbe00-2292-3012-d7ae-6bfa382fc74a@tony.gen.nz>

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

  reply	other threads:[~2018-05-01  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  8:03 Suggested new user link command Tony Wallace
2018-05-01  9:03 ` Bernd Petrovitsch [this message]
2018-05-01 10:58   ` Tony Wallace
2018-05-01 11:04     ` Richard Weinberger
2018-05-01 12:17       ` Tony Wallace
2018-05-01 13:35         ` Bernd Petrovitsch
2018-05-01 18:41           ` Tony Wallace
2018-05-05  5:10             ` Eric W. Biederman

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=1525165387.23227.44.camel@petrovitsch.priv.at \
    --to=bernd@petrovitsch.priv.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@tony.gen.nz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.