From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2BDBC74A41 for ; Sun, 14 Jul 2019 07:11:54 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CACDD20C01 for ; Sun, 14 Jul 2019 07:11:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="Sxv+3gFj" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CACDD20C01 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=cyphar.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=G0czcRKxhvwb5XCm6dmcjqnlihfhGB+UoXi68T0UTf0=; b=Sxv+3gFjhV0b/16A42KTrGZze E/VHOe59bBIYeZ0KkbuY5le9FPdv+c3YUWWH2GD/RaZ/OJ/dOopS5G4kw5AyNeOjHoef3+XriOoey Kf1pSA8OYqleTLVXqaUxNFvk46CuiKeMspVa5bnOJtIMs/vb2NcEyg/BPaxUWPyLCR7hXvSzxkvje 19JWEAYvxfUKzWiUWp+mq/pEH4uAdi1UmQMh+PVIIIO7hpV7XQ0qdjtg2yhvQIHZ151w5QpdPhXv/ 1UkBJ8mBqAlFrx9X5SJib6Og9bBztjByRwHx2DFTmqXDpoO1tltF8/MC+SBw9MBEGx0JRpFrvii2y iOd/8e1bw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hmYfm-0002H5-2f; Sun, 14 Jul 2019 07:11:50 +0000 Received: from mx1.mailbox.org ([80.241.60.212]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hmYfj-0002GO-1A for linux-arm-kernel@lists.infradead.org; Sun, 14 Jul 2019 07:11:48 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:105:465:1:1:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id E49974EC6D; Sun, 14 Jul 2019 09:11:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter02.heinlein-hosting.de (spamfilter02.heinlein-hosting.de [80.241.56.116]) (amavisd-new, port 10030) with ESMTP id so9n73IONPC7; Sun, 14 Jul 2019 09:11:17 +0200 (CEST) Date: Sun, 14 Jul 2019 17:11:02 +1000 From: Aleksa Sarai To: Al Viro Subject: Re: [PATCH v9 01/10] namei: obey trailing magic-link DAC permissions Message-ID: <20190714071102.gsc3kqpakz7chqt6@yavin> References: <20190706145737.5299-1-cyphar@cyphar.com> <20190706145737.5299-2-cyphar@cyphar.com> <20190712041454.GG17978@ZenIV.linux.org.uk> <20190712122017.xkowq2cjreylpotm@yavin> <20190712131005.GM17978@ZenIV.linux.org.uk> MIME-Version: 1.0 In-Reply-To: <20190712131005.GM17978@ZenIV.linux.org.uk> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190714_001147_379128_B21DDCC2 X-CRM114-Status: GOOD ( 27.47 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, Alexei Starovoitov , linux-kernel@vger.kernel.org, David Howells , linux-kselftest@vger.kernel.org, sparclinux@vger.kernel.org, Shuah Khan , linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, Tycho Andersen , Aleksa Sarai , linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, linux-xtensa@linux-xtensa.org, Kees Cook , Arnd Bergmann , Jann Horn , linuxppc-dev@lists.ozlabs.org, linux-m68k@lists.linux-m68k.org, Andy Lutomirski , Shuah Khan , David Drysdale , Christian Brauner , "J. Bruce Fields" , linux-parisc@vger.kernel.org, linux-api@vger.kernel.org, Chanho Min , Jeff Layton , Oleg Nesterov , Eric Biederman , linux-alpha@vger.kernel.org, linux-fsdevel@vger.kernel.org, Andrew Morton , Linus Torvalds , containers@lists.linux-foundation.org Content-Type: multipart/mixed; boundary="===============7211031494562983831==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============7211031494562983831== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gghwwblfl4frle37" Content-Disposition: inline --gghwwblfl4frle37 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-07-12, Al Viro wrote: > On Fri, Jul 12, 2019 at 10:20:17PM +1000, Aleksa Sarai wrote: > > On 2019-07-12, Al Viro wrote: > > > On Sun, Jul 07, 2019 at 12:57:28AM +1000, Aleksa Sarai wrote: > > > > @@ -514,7 +516,14 @@ static void set_nameidata(struct nameidata *p,= int dfd, struct filename *name) > > > > p->stack =3D p->internal; > > > > p->dfd =3D dfd; > > > > p->name =3D name; > > > > - p->total_link_count =3D old ? old->total_link_count : 0; > > > > + p->total_link_count =3D 0; > > > > + p->acc_mode =3D 0; > > > > + p->opath_mask =3D FMODE_PATH_READ | FMODE_PATH_WRITE; > > > > + if (old) { > > > > + p->total_link_count =3D old->total_link_count; > > > > + p->acc_mode =3D old->acc_mode; > > > > + p->opath_mask =3D old->opath_mask; > > > > + } > > >=20 > > > Huh? Could somebody explain why traversals of NFS4 referrals should = inherit > > > ->acc_mode and ->opath_mask? > >=20 > > I'll be honest -- I don't understand what set_nameidata() did so I just > > did what I thought would be an obvious change (to just copy the > > contents). I thought it was related to some aspect of the symlink stack > > handling. >=20 > No. It's handling of (very rare) nested pathwalk. The only case I can t= hink > of is handling of NFS4 referrals - they are triggered by ->d_automount() > and include NFS4 mount. Which does internal pathwalk of its own, to get > to the root of subtree being automounted. >=20 > NFS has its own recursion protection on that path (no deeper nesting than > one level of referral traversals), but there some nesting is inevitable; > we do get another nameidata instance on stack. And for nd_jump_link() we > need to keep track of the innermost one. >=20 > For symlinks nothing of that sort happens - they are dealt with on the sa= me > struct nameidata. ->total_link_count copying is there for one reason onl= y - > we want the total amount of symlinks traversed during the pathwalk (inclu= ding > the referral processing, etc.) to count towards MAXSYMLINKS check. It co= uld've > been moved from nameidata to task_struct, but it's cheaper to handle it t= hat > way. >=20 > Again, nesting is *rare*. Thanks for the explanation, much appreciated. I will drop the old->... copying hunk. > > In that case, should they both be set to 0 on set_nameidata()? This will > > mean that fd re-opening (or magic-link opening) through a > > set_nameidata() would always fail. >=20 > Huh? set_nameidata() is done for *all* instances - it's pretty much the > constructor of that object (and restore_nameidata() - a destructor). > Everything goes through it. Sorry, I meant to drop the copy-from-old logic -- not set it to zero explicitly in set_nameidata(). > And again, I'm not sure we want these fields in nameidata - IMO they belo= ng > in open_flags. Things like e.g. stat() don't need them at all. Yup, I'll work up a version that does the consolidation you mentioned in your other mail. > Incidentally, O_PATH opening of symlinks combined with subsequent procfs > symlink traversals is worth testing - that's where the things get subtle > and that's where it's easy to get in trouble on modifications. I have some self-tests of a symlink-to-a-magic-link in the last patch of the series. Did you mean something even more chained like a symlink to a /proc/self/fd/$n of an O_NOFOLLOW|O_PATH of a symlink? --=20 Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH --gghwwblfl4frle37 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQSxZm6dtfE8gxLLfYqdlLljIbnQEgUCXSrVgAAKCRCdlLljIbnQ EupPAQDpi9m99/xBGy4or9AS/LoRkr4tSLDlWlOsdCn0tZ52WAEAqoZwgZWyT46F mjKoRQeNjgtDk5jRNWbrwkJAMPXy2AE= =GnH+ -----END PGP SIGNATURE----- --gghwwblfl4frle37-- --===============7211031494562983831== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============7211031494562983831==--