Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp7185892yba; Thu, 2 May 2019 05:53:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqwcrkhZXYnZrd4ZDWbzjCeiW0MTY5Cy9yXdireA73ORtXfawCIdZ8yI+ncG+q+gp09ksvNo X-Received: by 2002:aa7:8589:: with SMTP id w9mr3995908pfn.97.1556801612525; Thu, 02 May 2019 05:53:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556801612; cv=none; d=google.com; s=arc-20160816; b=Y7b+zJKpypAzQ6459exYFgR6Obxugq08KufBIzWGBpZ65t3YR/3Asixzcfp8k2kIbw ZrxkZ8NJVLoAcG7mVpVNkRdzftwPPTrIrH/rij3EPnaDONYOeX+lfvPOqFTQ/CfqvytY 9LG8tWIUvCtDuIoIbt6paLi0ZtaT2OkFjaIvHWgn7zk8Db7Qj5EKNmkV3VgE5zzXKRzD kCbAqQuXgwNI10w/bBVvDQgq8Es3Ua0QFpqRdQIcoPXko8mKP+9hhWHhhPJXqmtG2PfN LzBGK/o2cc++Uh+JhsT29m4GO7tdENzKuwDB/VhE/Rru8YYIYjA4cBTUQgVG80Qfv/my A+Uw== 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:date:subject:cc:to:from; bh=05duYDah7+aoFQu7zJfyawnp25zSjdLxSn5XdE6yKZI=; b=TtaT6BSFm6e+9dynS5Nj0opIVB5f4IbWyM5TvMN4NwsM909h36UG0dvZPUHm0cSjTt 37xcdVAyYXOFymTctRTTExLEjUhHyQZsFY/ygbpT4p3CKjXLkMQ9ffksgfywHY3AB+4V wgzt2qyKNl8AS6TsXFUrNzkwUXNM+qf/nfxu+lQpA4gXwWy0ss57rvyx4QWieyzciMLu 2zHZ89i6vrSNB/kS1iqrDdGHlyTWDcFr52glvi0Wd9qt6z8PY7/I7+0qlrtyE5/MX12G MlX9urkVk3nhEZK2eRYkiKoZmtcsU5ytvEDxIq7dvgv3D5gkwzRAGQmmGP3V2KOcdvjZ 1FUw== 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 c13si15609866plo.175.2019.05.02.05.53.17; Thu, 02 May 2019 05:53:32 -0700 (PDT) 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 S1726557AbfEBMwV (ORCPT + 99 others); Thu, 2 May 2019 08:52:21 -0400 Received: from mx2.suse.de ([195.135.220.15]:34622 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726506AbfEBMwR (ORCPT ); Thu, 2 May 2019 08:52:17 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 916A7AEDB; Thu, 2 May 2019 12:52:16 +0000 (UTC) From: =?UTF-8?q?Michal=20Koutn=C3=BD?= To: gorcunov@gmail.com Cc: akpm@linux-foundation.org, arunks@codeaurora.org, brgl@bgdev.pl, geert+renesas@glider.be, ldufour@linux.ibm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, mguzik@redhat.com, mhocko@kernel.org, mkoutny@suse.com, rppt@linux.ibm.com, vbabka@suse.cz, ktkhai@virtuozzo.com Subject: [PATCH v3 2/2] prctl_set_mm: downgrade mmap_sem to read lock Date: Thu, 2 May 2019 14:52:03 +0200 Message-Id: <20190502125203.24014-3-mkoutny@suse.com> X-Mailer: git-send-email 2.16.4 In-Reply-To: <20190502125203.24014-1-mkoutny@suse.com> References: <0a48e0a2-a282-159e-a56e-201fbc0faa91@virtuozzo.com> <20190502125203.24014-1-mkoutny@suse.com> 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 The commit a3b609ef9f8b ("proc read mm's {arg,env}_{start,end} with mmap semaphore taken.") added synchronization of reading argument/environment boundaries under mmap_sem. Later commit 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|end and env_start|end in mm_struct") avoided the coarse use of mmap_sem in similar situations. But there still remained two places that (mis)use mmap_sem. get_cmdline should also use arg_lock instead of mmap_sem when it reads the boundaries. The second place that should use arg_lock is in prctl_set_mm. By protecting the boundaries fields with the arg_lock, we can downgrade mmap_sem to reader lock (analogous to what we already do in prctl_set_mm_map). v2: call find_vma without arg_lock held v3: squashed get_cmdline arg_lock patch Fixes: 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|end and env_start|end in mm_struct") Cc: Yang Shi Cc: Mateusz Guzik CC: Cyrill Gorcunov Co-developed-by: Laurent Dufour Signed-off-by: Laurent Dufour Signed-off-by: Michal Koutný --- kernel/sys.c | 10 ++++++++-- mm/util.c | 4 ++-- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/kernel/sys.c b/kernel/sys.c index 5e0a5edf47f8..14be57840511 100644 --- a/kernel/sys.c +++ b/kernel/sys.c @@ -2122,9 +2122,14 @@ static int prctl_set_mm(int opt, unsigned long addr, error = -EINVAL; - down_write(&mm->mmap_sem); + /* + * arg_lock protects concurent updates of arg boundaries, we need mmap_sem for + * a) concurrent sys_brk, b) finding VMA for addr validation. + */ + down_read(&mm->mmap_sem); vma = find_vma(mm, addr); + spin_lock(&mm->arg_lock); prctl_map.start_code = mm->start_code; prctl_map.end_code = mm->end_code; prctl_map.start_data = mm->start_data; @@ -2212,7 +2217,8 @@ static int prctl_set_mm(int opt, unsigned long addr, error = 0; out: - up_write(&mm->mmap_sem); + spin_unlock(&mm->arg_lock); + up_read(&mm->mmap_sem); return error; } diff --git a/mm/util.c b/mm/util.c index 43a2984bccaa..5cf0e84a0823 100644 --- a/mm/util.c +++ b/mm/util.c @@ -758,12 +758,12 @@ int get_cmdline(struct task_struct *task, char *buffer, int buflen) if (!mm->arg_end) goto out_mm; /* Shh! No looking before we're done */ - down_read(&mm->mmap_sem); + spin_lock(&mm->arg_lock); arg_start = mm->arg_start; arg_end = mm->arg_end; env_start = mm->env_start; env_end = mm->env_end; - up_read(&mm->mmap_sem); + spin_unlock(&mm->arg_lock); len = arg_end - arg_start; -- 2.16.4