Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751871AbdIJU0n convert rfc822-to-8bit (ORCPT ); Sun, 10 Sep 2017 16:26:43 -0400 Received: from nov-007-i584.relay.mailchannels.net ([46.232.183.138]:3265 "EHLO nov-007-i584.relay.mailchannels.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751438AbdIJU0l (ORCPT ); Sun, 10 Sep 2017 16:26:41 -0400 X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch X-MC-Relay: Neutral X-MailChannels-SenderId: novatrend|x-authuser|juerg@bitron.ch X-MailChannels-Auth-Id: novatrend X-Spicy-Illustrious: 7ae0f6d8730eb651_1505075196051_792186880 X-MC-Loop-Signature: 1505075196051:3570562594 X-MC-Ingress-Time: 1505075196051 Message-ID: <1505075168.5111.45.camel@bitron.ch> Subject: Re: new ...at() flag: AT_NO_JUMPS From: =?ISO-8859-1?Q?J=FCrg?= Billeter To: Al Viro Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Date: Sun, 10 Sep 2017 22:26:08 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.5 Mime-Version: 1.0 X-AuthUser: juerg@bitron.ch Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 460 Lines: 13 Hi Al, Might it make sense to specify these lookup restrictions when opening the directory (O_ROOT?) instead of specifying it for each lookup with AT_* (or supporting both)? This might make it more useful when passing directory fds between processes that do not use seccomp (where AT_BENEATH could be enforced). For my sandboxing use case, I'd be happy with either solution, though. Is there anything I can do to help move this forward? Best regards, Jürg