Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp4019822pxb; Tue, 2 Mar 2021 04:54:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJzDnIflerdiQ6WsGewhxXZ1QqTxnus6D7UH1Ri94hT0TxLcIOjTSeJboxsBU09PrxKnF00N X-Received: by 2002:a50:fe08:: with SMTP id f8mr17818989edt.217.1614689695687; Tue, 02 Mar 2021 04:54:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614689695; cv=none; d=google.com; s=arc-20160816; b=NF1r2crpb2LqOK6/vsqsAkrhUASUU5nxE8n5LhjytebXntCdAtLVaGkHIh95TNaOhz EN10iQAIHlOCrPkcf8XVYDf1ua/QTpYo5vfaxdHsl2BBuju95DdU2yBWACjVCiVZOAsx RxJIOsNSf2fAuAPjH1A3wfC0q6KpU65AMNumhy4EKkD/DrX7LkQkvLzHhSf/88aTx/PA zcuhju+Qmt+cZ//wF3qKwhBAbo4O0qOXSwjA//uwH1ca9iHbGkSSOXXhs59IF0TOLsa7 a43AB5KLszyuHN25PDhNCkrPWp/fEZ5sYuVvCL7a4aQoJiT0kt0xsmJM8BJ/Ylbmtls3 bGgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=f02JQUEYGG6gke1wHe+T0Mm0Cu0Dj66+JwVrQiBgBuA=; b=hF/0n1l8/htqNaGpzpT+Gnitvienur5iCsCES2XWMSiNhtdqTZmJsXulCr4m8UZD8u cCbG836uT85SAyDep3KKS9RZFHbDly36TQ++P6C86QVSBQUYbdBBcAEavsK40IwqRMQK gCbrXcBOIMPU6mdQ/uahIdysOx8vUm+NEnkSC8x1LSu40UlMMdioujhsGg80MM0HhNgQ VjC+vRBtAjerb/+M/V6A9ZcPDUfJws+7h7nsAv6tnKdoni27ZgefjFLvH3FBoe7/9R5I nIkGHNBolz/V1FhY0nJ/8eSxH5KVV9EfHSLMV3r/p3s04GpyoxdGDfzCILdpv5lx+7rr rNHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=LHInl2o7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c10si3671950edv.12.2021.03.02.04.54.30; Tue, 02 Mar 2021 04:54:55 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=LHInl2o7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1443340AbhCBCUw (ORCPT + 99 others); Mon, 1 Mar 2021 21:20:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:55186 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241943AbhCATrp (ORCPT ); Mon, 1 Mar 2021 14:47:45 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id A445B652A4; Mon, 1 Mar 2021 17:33:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614619993; bh=xi5ywds6ndsXtsKWJum0i7HlDnfoIIj9ew9zl1zd5Q8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=LHInl2o7+LxbONXu89ohKFJ2/fqVU2jQ5S4/15XRpAXLDNKdw7jSZCremwuCBPaO8 3YtvUS+g3LDuG55OufuT1X4QY0PWsIK5t0sUJD/9zRtZcK/yE1LUcEZskry6yyc5OB sWAwdWYGztVkBjisWI59Xt9w19RXcrFhhGSl7rMo= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Eric W. Biederman" , Jens Axboe Subject: [PATCH 5.10 625/663] proc: dont allow async path resolution of /proc/thread-self components Date: Mon, 1 Mar 2021 17:14:33 +0100 Message-Id: <20210301161212.773203810@linuxfoundation.org> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210301161141.760350206@linuxfoundation.org> References: <20210301161141.760350206@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jens Axboe commit 0d4370cfe36b7f1719123b621a4ec4d9c7a25f89 upstream. If this is attempted by an io-wq kthread, then return -EOPNOTSUPP as we don't currently support that. Once we can get task_pid_ptr() doing the right thing, then this can go away again. Use PF_IO_WORKER for this to speciically target the io_uring workers. Modify the /proc/self/ check to use PF_IO_WORKER as well. Cc: stable@vger.kernel.org Fixes: 8d4c3e76e3be ("proc: don't allow async path resolution of /proc/self components") Reported-by: Eric W. Biederman Signed-off-by: Jens Axboe Signed-off-by: Greg Kroah-Hartman --- fs/proc/self.c | 2 +- fs/proc/thread_self.c | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) --- a/fs/proc/self.c +++ b/fs/proc/self.c @@ -20,7 +20,7 @@ static const char *proc_self_get_link(st * Not currently supported. Once we can inherit all of struct pid, * we can allow this. */ - if (current->flags & PF_KTHREAD) + if (current->flags & PF_IO_WORKER) return ERR_PTR(-EOPNOTSUPP); if (!tgid) --- a/fs/proc/thread_self.c +++ b/fs/proc/thread_self.c @@ -17,6 +17,13 @@ static const char *proc_thread_self_get_ pid_t pid = task_pid_nr_ns(current, ns); char *name; + /* + * Not currently supported. Once we can inherit all of struct pid, + * we can allow this. + */ + if (current->flags & PF_IO_WORKER) + return ERR_PTR(-EOPNOTSUPP); + if (!pid) return ERR_PTR(-ENOENT); name = kmalloc(10 + 6 + 10 + 1, dentry ? GFP_KERNEL : GFP_ATOMIC);