From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id D60EAC433F5 for ; Wed, 13 Apr 2022 02:48:09 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 233FD6B0072; Tue, 12 Apr 2022 22:48:09 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1E20F6B0073; Tue, 12 Apr 2022 22:48:09 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0D24A6B0074; Tue, 12 Apr 2022 22:48:09 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.27]) by kanga.kvack.org (Postfix) with ESMTP id F21036B0072 for ; Tue, 12 Apr 2022 22:48:08 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id B48D3250F9 for ; Wed, 13 Apr 2022 02:48:08 +0000 (UTC) X-FDA: 79350321456.19.7E7D313 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf13.hostedemail.com (Postfix) with ESMTP id 42B9F20002 for ; Wed, 13 Apr 2022 02:48:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649818087; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HL4I/kbAi4EMYznQst2SX99qMFId0RHWKlLCdi0UXhg=; b=hQmpae8YKT1bet4dG2ouQ7I/MDaltvq2WCaWwYu8sSJCjuq1HjKy60uLWsF6h/Fizn1vJn 1d7M64i4Pb9w399jtQtnWzuonwR4yFJlS7Tk0XPnjdI8vQFdKH5dEglQ/ZTPBqbfoLewK2 56NP5cNz0SEDvfCXJiTr9lf7UiVWQA8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-562-QIkJcyNEMZaTlr0_V49QTQ-1; Tue, 12 Apr 2022 22:48:00 -0400 X-MC-Unique: QIkJcyNEMZaTlr0_V49QTQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C77D3101AA44; Wed, 13 Apr 2022 02:47:59 +0000 (UTC) Received: from localhost (ovpn-12-51.pek2.redhat.com [10.72.12.51]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C8B0A2024CBC; Wed, 13 Apr 2022 02:47:52 +0000 (UTC) Date: Wed, 13 Apr 2022 10:47:49 +0800 From: Baoquan He To: Andrew Morton Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, dyoung@redhat.com, linux-mm@kvack.org Subject: Re: [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer Message-ID: References: <20220223113225.63106-1-bhe@redhat.com> <20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=hQmpae8Y; spf=none (imf13.hostedemail.com: domain of bhe@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=bhe@redhat.com; dmarc=pass (policy=none) header.from=redhat.com X-Stat-Signature: cea7d663krh97eijt8kmyzim8pu1p4ch X-Rspam-User: X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: 42B9F20002 X-HE-Tag: 1649818088-2770 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 04/12/22 at 07:27pm, Andrew Morton wrote: > On Thu, 31 Mar 2022 19:32:17 +0800 Baoquan He wrote: > > > Hi Andrew, > > > > On 02/23/22 at 07:32pm, Baoquan He wrote: > > > The memory leak is reported by kmemleak detector, has been existing > > > for very long time. It casue much memory loss on large machine > > > with huge memory hotplug which will trigger kdump kernel reloading > > > many times, with kexec_file_load interface. > > > > Could you merge these two patches? Or should I ping x86 maintainers to > > take them? > > Ah, sorry, I tend to fall asleep if there's "x86" in the subject. > Poking a sleeping Andrew is always the right thing to do. Shall look > at them. Thanks, Andrew. Since it's also MM related, so ping you and x86 maintainers to see who can help pick them.