[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170328163823.3a0445a058670be9254e115c@linux-foundation.org>
Date: Tue, 28 Mar 2017 16:38:23 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: nyc@...omorphy.com, Michal Hocko <mhocko@...e.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>
Subject: Re: mm: BUG in resv_map_release
On Thu, 23 Mar 2017 11:19:38 +0100 Dmitry Vyukov <dvyukov@...gle.com> wrote:
> Hello,
>
> I've got the following BUG while running syzkaller fuzzer.
> Note the injected kmalloc failure, most likely it's the root cause.
>
Yes, probably the logic(?) in region_chg() leaked a
resv->adds_in_progress++, although I'm not sure how. And afaict that
code can leak the memory at *nrg if the `trg' allocation attempt failed
on the second or later pass around the retry loop.
Blah. Does someone want to take a look at it?
Powered by blists - more mailing lists