[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ccbd7330-b7d7-9048-b49a-80f904353c21@redhat.com>
Date: Thu, 5 Jan 2023 10:04:14 +0100
From: David Hildenbrand <david@...hat.com>
To: Suren Baghdasaryan <surenb@...gle.com>, akpm@...ux-foundation.org
Cc: hughd@...gle.com, hannes@...xchg.org, vincent.whitchurch@...s.com,
seanjc@...gle.com, rppt@...nel.org, shy828301@...il.com,
pasha.tatashin@...een.com, paul.gortmaker@...driver.com,
peterx@...hat.com, vbabka@...e.cz, Liam.Howlett@...cle.com,
ccross@...gle.com, willy@...radead.org, arnd@...db.de,
cgel.zte@...il.com, yuzhao@...gle.com, bagasdotme@...il.com,
suleiman@...gle.com, steven@...uorix.net, heftig@...hlinux.org,
cuigaosheng1@...wei.com, kirill@...temov.name,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org,
syzbot+91edf9178386a07d06a7@...kaller.appspotmail.com
Subject: Re: [PATCH v2 1/1] mm: fix vma->anon_name memory leak for anonymous
shmem VMAs
On 05.01.23 01:02, Suren Baghdasaryan wrote:
> free_anon_vma_name() is missing a check for anonymous shmem VMA which
> leads to a memory leak due to refcount not being dropped. Fix this by
> calling anon_vma_name_put() unconditionally. It will free vma->anon_name
> whenever it's non-NULL.
>
> Fixes: d09e8ca6cb93 ("mm: anonymous shared memory naming")
> Signed-off-by: Suren Baghdasaryan <surenb@...gle.com>
> Suggested-by: David Hildenbrand <david@...hat.com>
> Reported-by: syzbot+91edf9178386a07d06a7@...kaller.appspotmail.com
> Cc: David Hildenbrand <david@...hat.com>
> Cc: Hugh Dickins <hughd@...gle.com>
> Cc: Pasha Tatashin <pasha.tatashin@...een.com>
Reviewed-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists