Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752944AbbH1VIH (ORCPT ); Fri, 28 Aug 2015 17:08:07 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:34310 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752865AbbH1VID (ORCPT ); Fri, 28 Aug 2015 17:08:03 -0400 MIME-Version: 1.0 In-Reply-To: <20150828204413.GB23326@fieldses.org> References: <1438689218-6921-1-git-send-email-agruenba@redhat.com> <1438689218-6921-4-git-send-email-agruenba@redhat.com> <20150828204413.GB23326@fieldses.org> Date: Fri, 28 Aug 2015 23:08:00 +0200 Message-ID: Subject: Re: [RFC v6 03/40] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags From: Andreas Gruenbacher To: "J. Bruce Fields" Cc: Andreas Gruenbacher , linux-kernel@vger.kernel.org, linux-fsdevel , linux-nfs@vger.kernel.org, linux-api@vger.kernel.org, linux-cifs@vger.kernel.org, linux-security-module@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 755 Lines: 17 2015-08-28 22:44 GMT+02:00 J. Bruce Fields : >> The MAY_DELETE_SELF permission does not override the sticky >> directory check. It probably should. > > I guess it would basically just let the file owner delegate permission > to delete your file to a non-owner? Makes sense to me to allow that. Yes, independent of whether or not the process has MAY_DELETE_CHILD access on the directory but not independent of the sticky directory check, which is a bit of a weird combination. Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/