From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-arch@vger.kernel.org, hjl.tools@gmail.com, mhocko@suse.com,
rguenther@suse.de, richard@nod.at, gxt@pku.edu.cn,
jdike@addtoit.com, x86@kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
luto@amacapital.net, linux-mm@kvack.org, paulus@samba.org,
yang.shi@linux.alibaba.com, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, vbabka@suse.cz,
anton.ivanov@cambridgegreys.com
Subject: Re: [PATCH] [v2] x86/mpx: fix recursive munmap() corruption
Date: Thu, 9 May 2019 10:31:11 +0200 [thread overview]
Message-ID: <20190509083111.GA75918@gmail.com> (raw)
In-Reply-To: <20190419194747.5E1AD6DC@viggo.jf.intel.com>
* Dave Hansen <dave.hansen@linux.intel.com> wrote:
> Reported-by: Richard Biener <rguenther@suse.de>
> Reported-by: H.J. Lu <hjl.tools@gmail.com>
> Fixes: dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in munmap")
> Cc: Yang Shi <yang.shi@linux.alibaba.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: x86@kernel.org
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: stable@vger.kernel.org
> Cc: linuxppc-dev@lists.ozlabs.org
> Cc: linux-um@lists.infradead.org
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: linux-arch@vger.kernel.org
> Cc: Guan Xuetao <gxt@pku.edu.cn>
> Cc: Jeff Dike <jdike@addtoit.com>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
I've also added your:
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Because I suppose you intended to sign off on it?
Thanks,
Ingo
prev parent reply other threads:[~2019-05-09 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 19:47 [PATCH] [v2] x86/mpx: fix recursive munmap() corruption Dave Hansen
2019-04-20 11:00 ` Michael Ellerman
2019-04-22 17:08 ` Yang Shi
2019-05-09 8:31 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190509083111.GA75918@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=dave.hansen@linux.intel.com \
--cc=gxt@pku.edu.cn \
--cc=hjl.tools@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@amacapital.net \
--cc=mhocko@suse.com \
--cc=paulus@samba.org \
--cc=rguenther@suse.de \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=x86@kernel.org \
--cc=yang.shi@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).