Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp151909imu; Wed, 7 Nov 2018 14:38:38 -0800 (PST) X-Google-Smtp-Source: AJdET5cxnbOEK3WiLaooCOtnFLStngPFQFndqstpENz0norCbSyPqwGtFIAL0D5mFt3iZrotroWB X-Received: by 2002:a17:902:780f:: with SMTP id p15-v6mr2084639pll.197.1541630318788; Wed, 07 Nov 2018 14:38:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541630318; cv=none; d=google.com; s=arc-20160816; b=ru6reV9Nwt90xhUFLrCD1FhY69s4JjGHkL+TDmaMwBLB6fJWYSJ8asQiWToRzB4DQf RrGPI7ojt1zwM2yE1nDhmpo49fRcru9GCTQVQwDg9BQmFi5HD40hWBwoPuf+PLPZx+U/ umNeFD2anzYvpfP7usBN+s2JW5tODtUqwAcHSSfPlfe864rl2wkIztidE8t0+1LfuN/M jElXdwSBW3v8tEcwr+BWFIkD5e2YhlTTdDnCZEpVhmAbgNjb08RSFp0cOq2hsVbBfc1U GFhh9lAVfbLWNZ67b1ANwFjjqEFi6um6rp1yZ2L4YgKcQ2dpSvMA+MdhfgORCqUzzmui i6Kw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=LZZlowt5Ane5vAuok+dg7Z7vrqmYwYKKyfNpAP3eJCU=; b=yK5fOHus6HIxt1tPyKiwC2SgEwVoskAyeeGb9XkfXn4/jHnkPoPTbOOvH4d8xR5ppe HN/FR72UCVd8eZ7bfFfbuAeyCeNl+o2CT5Ks0eEIOm+C1GTK3+qDuNNu7OxoiPuHSCS2 lul6C5E4fQMx0DvV63XE+WNHAkWLpSgRhzzE781f230Pr9YI6UWCy54yt4l/hcjQCGi1 0PGV14A1YaDekTUtelrfz25WJVpTj4NlN4o9Q2SHaofI9cDdVq1dr5u+2hDzGtxl7ipu NVCjoLa5Gm5CK6Iuz/GneJ8xDqGIdm5khxn3INxU1ZMJ6cKjOg7Y/zio1V4YL5UG4s1a 9+AQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e39-v6si1463432plb.369.2018.11.07.14.38.23; Wed, 07 Nov 2018 14:38:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728164AbeKHIKO (ORCPT + 99 others); Thu, 8 Nov 2018 03:10:14 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:47788 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727454AbeKHIKO (ORCPT ); Thu, 8 Nov 2018 03:10:14 -0500 Received: from akpm3.svl.corp.google.com (unknown [104.133.8.65]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 71C1F891; Wed, 7 Nov 2018 22:37:45 +0000 (UTC) Date: Wed, 7 Nov 2018 14:37:44 -0800 From: Andrew Morton To: =?UTF-8?B?Y2hvdXJ5emhvdQ==?= (=?UTF-8?B?5ZGo5aiB?=) Cc: "gregkh@linuxfoundation.org" , "arve@android.com" , "tkjos@android.com" , "dave@stgolabs.net" , "devel@driverdev.osuosl.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH V2] binder: ipc namespace support for android binder Message-Id: <20181107143744.2dd91690aad06ab1d678dfe8@linux-foundation.org> In-Reply-To: <5FBCBE569E134E4CA167B91C0A77FD610198F816F8@EXMBX-SZMAIL022.tencent.com> References: <5FBCBE569E134E4CA167B91C0A77FD610198F816F8@EXMBX-SZMAIL022.tencent.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Nov 2018 01:48:12 +0000 chouryzhou(周威) wrote: > > > --- a/ipc/namespace.c > > > +++ b/ipc/namespace.c > > > @@ -56,6 +56,9 @@ static struct ipc_namespace *create_ipc_ns(struct > > user_namespace *user_ns, > > > ns->ucounts = ucounts; > > > > > > err = mq_init_ns(ns); > > > + if (err) > > > + goto fail_put; > > > + err = binder_init_ns(ns); > > > if (err) > > > goto fail_put; > > > > > > > Don't we need an mq_put_mnt() if binder_init_ns() fails? > > > > free_ipc_ns() seems to have forgotten about that too. In which case it > > must be madly leaking mounts so probably I'm wrong. Confused. > > > > mq_init_ns will do clean job if it failed, and as do binder_init_ns. My point is that if mq_init_ns() succeeds and binder_init_ns() fails, we don't undo the effects of mq_init_ns()?