[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230104173855.48e8734a25c08d7d7587d508@linux-foundation.org>
Date: Wed, 4 Jan 2023 17:38:55 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: hughd@...gle.com, hannes@...xchg.org, david@...hat.com,
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 Wed, 4 Jan 2023 16:02:40 -0800 Suren Baghdasaryan <surenb@...gle.com> 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")
A cc:stable is appropriate here, yes?
Powered by blists - more mailing lists