[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201005125216.GV816047@nvidia.com>
Date: Mon, 5 Oct 2020 09:52:16 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Jann Horn <jannh@...gle.com>
CC: Michel Lespinasse <walken@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
"Eric W . Biederman" <ebiederm@...ssion.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Jeff Dike <jdike@...toit.com>,
"Richard Weinberger" <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
<linux-um@...ts.infradead.org>, John Hubbard <jhubbard@...dia.com>
Subject: Re: [PATCH 1/2] mmap locking API: Order lock of nascent mm outside
lock of live mm
On Mon, Oct 05, 2020 at 03:30:43AM +0200, Jann Horn wrote:
> But another place where lockdep asserts should be added is find_vma();
> there are currently several architectures that sometimes improperly
> call that with no lock held:
Yes, I've seen several cases of this mis-use in drivers too
Jason
Powered by blists - more mailing lists