From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754623AbdC1Xi1 (ORCPT ); Tue, 28 Mar 2017 19:38:27 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:51994 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753119AbdC1Xi0 (ORCPT ); Tue, 28 Mar 2017 19:38:26 -0400 Date: Tue, 28 Mar 2017 16:38:23 -0700 From: Andrew Morton To: Dmitry Vyukov Cc: nyc@holomorphy.com, Michal Hocko , Mike Kravetz , "Kirill A. Shutemov" , Andrea Arcangeli , "linux-mm@kvack.org" , LKML , Andrey Ryabinin Subject: Re: mm: BUG in resv_map_release Message-Id: <20170328163823.3a0445a058670be9254e115c@linux-foundation.org> In-Reply-To: References: X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 23 Mar 2017 11:19:38 +0100 Dmitry Vyukov 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?