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 6879EC27C53 for ; Wed, 19 Jun 2024 21:53:32 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BE3948D008E; Wed, 19 Jun 2024 17:53:31 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B936F8D0084; Wed, 19 Jun 2024 17:53:31 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A5B238D008E; Wed, 19 Jun 2024 17:53:31 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 86FF18D0084 for ; Wed, 19 Jun 2024 17:53:31 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id C5554814FA for ; Wed, 19 Jun 2024 21:53:30 +0000 (UTC) X-FDA: 82248990180.19.D7F1F1A Received: from sin.source.kernel.org (sin.source.kernel.org [145.40.73.55]) by imf19.hostedemail.com (Postfix) with ESMTP id B377F1A0008 for ; Wed, 19 Jun 2024 21:53:28 +0000 (UTC) Authentication-Results: imf19.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=H1zB9xn9; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf19.hostedemail.com: domain of rppt@kernel.org designates 145.40.73.55 as permitted sender) smtp.mailfrom=rppt@kernel.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1718834002; a=rsa-sha256; cv=none; b=GDwBxnsmLX1+Dvl+0NiG3zc9b36yIWmhwZLzxo1UHi3DF7YGL0bYp+sxFk46wR48AAk79W ZaS4gLfNvrAeSbDaviZjP562+6Dfx8He+ObNLPo6HUkVO+fW2X0lA0oN1qXpCJCC9xzGEt P7JZaKXbZipbAxnmRdm/X67S7Jm8Ggw= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=H1zB9xn9; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf19.hostedemail.com: domain of rppt@kernel.org designates 145.40.73.55 as permitted sender) smtp.mailfrom=rppt@kernel.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1718834002; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=2aYaUH+IO5LUnHpwraCoqb28JupLupmDRGoJDrZB7QA=; b=L1+wXjZ8D+pXSkdtnFnV/OInc+OgdDmcn+PVNNflBbKuYYRy05PxGRECYiSgU3Raxcu6DV qysdtcjvIhaFgFDNhjij2GnAU/Tgf4XpgmYdsNKBaIJb/UuxquDjkRvpyHnifhkCD65Az1 NGdsgf8eqaqowS0M/Ck6k+MpBZmHf08= Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 6C719CE0223; Wed, 19 Jun 2024 21:53:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E6148C2BBFC; Wed, 19 Jun 2024 21:53:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1718834004; bh=ik3/SNXZztDENIS5byMNDl0QRzOh2H6BTGRmfxVgcuE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=H1zB9xn9PvO4oADyyjfHM2Q0NGTOVIJ7z4g57z/oJr6A/oHVAIdEJATJOOuidDa5A 9/N+e8dtHDrb/q5Ohf8ze/yylnIzgJlEGZSz404dN5dpwCl38O59CXMPVKbX5eIf2u ZPH5IV9fzCQS1jW2kOStUX9oKlAVNAQSLoyuAtEY5L0Pn1eQMBBCiTSo4i/n3aSm7R THVBAHm0Bj9xG/7nZzVn4K1U9BvXBdZ/mp3dRQFbmIf3l1OWJiuTRC4Grsl6/F2mIZ 9EGyTR8r8fqS32z3tLIP/PWv8ZaqQRwosXeVqkT1Pv7ypVPBJ4XbYHo5YPN/tjxAor 508Vlya81i+9Q== From: Mike Rapoport To: Andrew Morton , James Gowans Cc: Mike Rapoport , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Alex Graf Subject: Re: [PATCH v2] memblock: Move late alloc warning down to phys alloc Date: Thu, 20 Jun 2024 00:53:06 +0300 Message-ID: <171883398192.3581885.4505580925551979480.b4-ty@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240619095555.85980-1-jgowans@amazon.com> References: <20240619095555.85980-1-jgowans@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: B377F1A0008 X-Rspam-User: X-Rspamd-Server: rspam05 X-Stat-Signature: 7ujkkpp1j1hd1eo61c9x6m6xpmbeyhbx X-HE-Tag: 1718834008-608335 X-HE-Meta: U2FsdGVkX1/Abx3cRp3xi73IqMxJft5/RQBrNZPIMIpwtK68M/WF/QO7rlwqJNaNW3MyDSk29YcPQVupTy1uDD+6X7VBKa9rJC5WZ6/MifTIxWgjGj2pVfeVuN8IVfKPIjXhYcic3V/ftt57IT7cP4MAEn9ohEN3lgCSqzkpNpQImdd1Inwcg/JmMGcKkRoAiJDakiMbsKxMwsF4DFwjspEFZ+iffBH4QAztTVUO1NwGZoBU6hEkecMXs0FIwxDTZkyntjdoVIUUBvmPPuc0agB65xq2LqffMSI3NlzUcX73ekKTLdc5L20ijU447NFFzkWha5O5cCFR4DjEC1XrzjVbwEkHi8PiTYtQf7e9d0C/4tBTY9P37gJq4+6rMn4QkdxYM5AdP35sIatSNxFhnizZn9qUIesytV0xUgiikGjuebAlrFfbwyI2mHJR1uDLLdiqTh45g8pUHlpGOjNN/lrCr5KSxGZsq41Qh+f/Mj83mUkQl2DAk84Xg5v06D9MA4jX3P/95O+UkYcXS7ZGtvRmB7iufxF3stz+iioLm6TtrZSfcFvrUmFeHjWu2OpK2pg6Q7hmWdlstB/rnM59biNo6uX8ktPeqRYKvGXwgdQBsfXtZwGUdCvxO+PxWu7v9U5EyO4JXUK2FN7rwtJdVoqyHn1XVmGA9onQX7xJsN+WqGEAmgZ/iqlQHm5vvrIy6Fwan8fYlrUXfprYdy4WW5gz0INPNU8cRC/KusobHwOlj8U3XVStQdI6fzaHUmzUMPbezaRGdG3RVLVUHe8cMyOV3e9PvvHiEN2q+E7M7BaLpx0xwbc+WvVJr3sqJtMW7RNePS2MfmvtvvnPaLJ98u0/WS+2msNHs8Sbnmrp4uVcR82vXM1ZhBMmkg6LLHjdcxan9BmX1bY+pwvNBdkkgudbzdGOOyCVA8T3Hn+PzNwIMAKQ+vGmBCf19MehG1be3y0sRdaji/m3mNFlAR8 eBaCYujB 4IhCL9Zv4jjxTdUhkHvy7wAe9QmQhfDs4RUdD5Rs3ZED1dWuI7cSp8zBP4rKP1tQTLthoraVZXxProd1V0+YoFyVqYqwWT6GzPK3JMe5KrP3zOArq4ZCnrdkmjbPHivXkt9Kgxds2TeAhMrN2p7mzgWG4OuRQSJNjrGxHm7ao18XmgHV0Bm9sjgrIIis3ELTYl6wX8ERgbbDN0+vz6O7IqQOtZoC14eH28eoTEomoI6Ru1XAzCkTntI/DOg== 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: List-Subscribe: List-Unsubscribe: From: Mike Rapoport (IBM) On Wed, 19 Jun 2024 11:55:55 +0200, James Gowans wrote: > If a driver/subsystem tries to do an allocation after the memblock > allocations have been freed and the memory handed to the buddy > allocator, it will not actually be legal to use that allocation: the > buddy allocator owns the memory. Currently this mis-use is handled by > the memblock function which does allocations and returns virtual > addresses by printing a warning and doing a kmalloc instead. However > the physical allocation function does not to do this check - callers of > the physical alloc function are unprotected against mis-use. > > [...] Applied to for-next branch of memblock.git tree, thanks! [1/1] memblock: Move late alloc warning down to phys alloc commit: 94ff46de4a738e7916b68ab5cc0b0380729f02af tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock branch: for-next -- Sincerely yours, Mike.