netdev - Re: [PATCH net-next] bpf, inode: allow for rename and link ops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 12 Dec 2015 19:06:15 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	daniel@...earbox.net
Cc:	ast@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] bpf, inode: allow for rename and link ops

From: Daniel Borkmann <daniel@...earbox.net>
Date: Thu, 10 Dec 2015 22:33:49 +0100

> Add support for renaming and hard links to the fs. Most of this can be
> implemented by using simple library operations under the same constraints
> that we don't use a reserved name like elsewhere. Linking can be useful
> to share/manage things like maps across subsystem users. It works within
> the file system boundary, but is not allowed for directories.
> 
> Symbolic links are explicitly not implemented here, as it can be better
> done already by doing bind mounts inside bpf fs to set up shared directories
> f.e. useful when using volumes in docker containers that map a private
> working directory into /sys/fs/bpf/ which contains itself a bind mounted
> path from the host's /sys/fs/bpf/ mount that is shared among multiple
> containers. For single maps instead of whole directory, hard links can
> be easily used to do the same.
> 
> Signed-off-by: Daniel Borkmann <daniel@...earbox.net>
> Acked-by: Alexei Starovoitov <ast@...nel.org>

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html