[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190516162946.zwzhxkft342b25pd@atomlin.usersys.com>
Date: Thu, 16 May 2019 17:29:46 +0100
From: Aaron Tomlin <atomlin@...hat.com>
To: Jann Horn <jannh@...gle.com>
Cc: Oleksandr Natalenko <oleksandr@...hat.com>,
kernel list <linux-kernel@...r.kernel.org>,
Kirill Tkhai <ktkhai@...tuozzo.com>,
Hugh Dickins <hughd@...gle.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...e.com>,
Matthew Wilcox <willy@...radead.org>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Greg KH <greg@...ah.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Timofey Titovets <nefelim4ag@...il.com>,
Grzegorz Halat <ghalat@...hat.com>,
Linux-MM <linux-mm@...ck.org>,
Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH RFC 4/5] mm/ksm, proc: introduce remote merge
On Thu 2019-05-16 12:00 +0200, Jann Horn wrote:
> On Thu, May 16, 2019 at 11:43 AM Oleksandr Natalenko
> <oleksandr@...hat.com> wrote:
[ ... ]
> > + }
> > +
> > + down_write(&mm->mmap_sem);
>
> Should a check for mmget_still_valid(mm) be inserted here? See commit
> 04f5866e41fb70690e28397487d8bd8eea7d712a.
Yes - I'd say this is required here.
Thanks,
--
Aaron Tomlin
Powered by blists - more mailing lists