[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201009150420.450833e3830b9d39a2385dd9@linux-foundation.org>
Date: Fri, 9 Oct 2020 15:04:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: =?ISO-8859-1?Q? "Christian_K=F6nig" ?=
<ckoenig.leichtzumerken@...il.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linaro-mm-sig@...ts.linaro.org, dri-devel@...ts.freedesktop.org,
linux-media@...r.kernel.org, chris@...is-wilson.co.uk,
airlied@...hat.com, daniel@...ll.ch, sumit.semwal@...aro.org,
willy@...radead.org, jhubbard@...dia.com, jgg@...pe.ca,
Miaohe Lin <linmiaohe@...wei.com>
Subject: Re: [PATCH 1/6] mm: mmap: fix fput in error path
On Fri, 9 Oct 2020 17:03:37 +0200 "Christian König" <ckoenig.leichtzumerken@...il.com> wrote:
> Patch "495c10cc1c0c CHROMIUM: dma-buf: restore args..."
> adds a workaround for a bug in mmap_region.
>
> As the comment states ->mmap() callback can change
> vma->vm_file and so we might call fput() on the wrong file.
>
> Revert the workaround and proper fix this in mmap_region.
>
Doesn't this patch series address the same thing as
https://lkml.kernel.org/r/20200916090733.31427-1-linmiaohe@huawei.com?
Powered by blists - more mailing lists