Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp263063yba; Thu, 25 Apr 2019 22:51:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqzjbyeqXcu8DLlEn0pKuXM/pM0HurqfSKsz9saLm1zGLZ/3rn8VzvoRPAASyWpHsbzBIpgp X-Received: by 2002:a65:6282:: with SMTP id f2mr19739091pgv.152.1556257904077; Thu, 25 Apr 2019 22:51:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556257904; cv=none; d=google.com; s=arc-20160816; b=SX7DHIztfDk8tHfISHeoirrHwh7Y7ePDSg+1OG5iBEl/mFb7AOeEvfB33DAcA2DX8W Cy18/cC7FwJdf+8zzvNQA41fG9Ac0VUWxwwU4sLr2qDuCGZoVMcgfQaOQ9WLJ9TyPWLm CPBFrp3yap4KwUm4pmgSsryIvaczTi9sT1dDUVHgdnbiuArRMoMkyb/K9/yn7mh3u0+x xn1bWnTAhN8Pg9O7x/a8gzikUOfR4mEm06bFzLXJ/jn8sucuIyOCpmMFbDxVWldrOwmV aVKReAHWwr9aGlDHhhFFU6BRv6KaEGJ9OJmzBdwVfOqlccWPx0YIqOFRw2AG7ouSuIq8 9VcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=pLokakutnZIuZ75LtbduiMmabFTZGNAssEYKu5vYyto=; b=Wkqp9nxMLiXLsv79w+k2+U+WY1tPsTDwbnzrPbX2FQifxSYdp0YQq8Awulq9vpPGRQ y1IBYNW59m3hqAK/hJGwGW2jZZzVyoZXeMOGpic8dSu+R+nih1jgItMDIUDZxgEAaATC l5bdZQjZ/1Mpdh7cSI5rs4N8Gx6SMh2rIAuFAqZoz6iQDe4AlSMjuxv7EKZ16E+9zGgx BhcUwSp/ZXadBtoboFA8mS3c//qBUl3+2sr3auAeELdxhPc/ZcJ7YuoUfikOf5/+LbH6 yPKw6zFNOvdhyQPiNIunymh5Voa6bPPhkGGHUq5EpZZiHY4JchY1lVzh5KdVM/tzqU6y jupw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r12si24405065pfn.135.2019.04.25.22.51.28; Thu, 25 Apr 2019 22:51:44 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727371AbfDZFbh (ORCPT + 99 others); Fri, 26 Apr 2019 01:31:37 -0400 Received: from mx2.suse.de ([195.135.220.15]:42550 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725854AbfDZFbh (ORCPT ); Fri, 26 Apr 2019 01:31:37 -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 DF8F9AD64; Fri, 26 Apr 2019 05:31:35 +0000 (UTC) Date: Fri, 26 Apr 2019 07:31:35 +0200 From: Michal Hocko To: Jann Horn Cc: Matthew Garrett , Linux-MM , kernel list , Matthew Garrett , Linux API Subject: Re: [PATCH V2] mm: Allow userland to request that the kernel clear memory on release Message-ID: <20190426053135.GC12337@dhcp22.suse.cz> References: <20190424211038.204001-1-matthewgarrett@google.com> <20190425121410.GC1144@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 25-04-19 14:42:52, Jann Horn wrote: > On Thu, Apr 25, 2019 at 2:14 PM Michal Hocko wrote: > [...] > > On Wed 24-04-19 14:10:39, Matthew Garrett wrote: > > > From: Matthew Garrett > > > > > > Applications that hold secrets and wish to avoid them leaking can use > > > mlock() to prevent the page from being pushed out to swap and > > > MADV_DONTDUMP to prevent it from being included in core dumps. Applications > > > can also use atexit() handlers to overwrite secrets on application exit. > > > However, if an attacker can reboot the system into another OS, they can > > > dump the contents of RAM and extract secrets. We can avoid this by setting > > > CONFIG_RESET_ATTACK_MITIGATION on UEFI systems in order to request that the > > > firmware wipe the contents of RAM before booting another OS, but this means > > > rebooting takes a *long* time - the expected behaviour is for a clean > > > shutdown to remove the request after scrubbing secrets from RAM in order to > > > avoid this. > > > > > > Unfortunately, if an application exits uncleanly, its secrets may still be > > > present in RAM. This can't be easily fixed in userland (eg, if the OOM > > > killer decides to kill a process holding secrets, we're not going to be able > > > to avoid that), so this patch adds a new flag to madvise() to allow userland > > > to request that the kernel clear the covered pages whenever the page > > > reference count hits zero. Since vm_flags is already full on 32-bit, it > > > will only work on 64-bit systems. > [...] > > > diff --git a/mm/madvise.c b/mm/madvise.c > > > index 21a7881a2db4..989c2fde15cf 100644 > > > --- a/mm/madvise.c > > > +++ b/mm/madvise.c > > > @@ -92,6 +92,22 @@ static long madvise_behavior(struct vm_area_struct *vma, > > > case MADV_KEEPONFORK: > > > new_flags &= ~VM_WIPEONFORK; > > > break; > > > + case MADV_WIPEONRELEASE: > > > + /* MADV_WIPEONRELEASE is only supported on anonymous memory. */ > > > + if (VM_WIPEONRELEASE == 0 || vma->vm_file || > > > + vma->vm_flags & VM_SHARED) { > > > + error = -EINVAL; > > > + goto out; > > > + } > > > + new_flags |= VM_WIPEONRELEASE; > > > + break; > > An interesting effect of this is that it will be possible to set this > on a CoW anon VMA in a fork() child, and then the semantics in the > parent will be subtly different - e.g. if the parent vmsplice()d a > CoWed page into a pipe, then forked an unprivileged child, the child Maybe a stupid question. How do you fork an unprivileged child (without exec)? Child would have to drop priviledges on its own, no? > set MADV_WIPEONRELEASE on its VMA, the parent died somehow, and then > the child died, the page in the pipe would be zeroed out. A child > should not be able to affect its parent like this, I think. If this > was an mmap() flag instead of a madvise() command, that issue could be > avoided. With a VMA flag underneath, I think you can do an early CoW during fork to prevent from that. > Alternatively, if adding more mmap() flags doesn't work, > perhaps you could scan the VMA and ensure that it contains no pages > yet, or something like that? > > > > diff --git a/mm/memory.c b/mm/memory.c > > > index ab650c21bccd..ff78b527660e 100644 > > > --- a/mm/memory.c > > > +++ b/mm/memory.c > > > @@ -1091,6 +1091,9 @@ static unsigned long zap_pte_range(struct mmu_gather *tlb, > > > page_remove_rmap(page, false); > > > if (unlikely(page_mapcount(page) < 0)) > > > print_bad_pte(vma, addr, ptent, page); > > > + if (unlikely(vma->vm_flags & VM_WIPEONRELEASE) && > > > + page_mapcount(page) == 0) > > > + clear_highpage(page); > > > if (unlikely(__tlb_remove_page(tlb, page))) { > > > force_flush = 1; > > > addr += PAGE_SIZE; > > Should something like this perhaps be added in page_remove_rmap() > instead? That's where the mapcount is decremented; and looking at > other callers of page_remove_rmap(), in particular the following ones > look interesting: Well spotted! -- Michal Hocko SUSE Labs