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 X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 885ABC07E9B for ; Fri, 9 Jul 2021 22:33:19 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 21668613BF for ; Fri, 9 Jul 2021 22:33:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 21668613BF Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1AC9E6B0073; Fri, 9 Jul 2021 18:33:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1377F6B0078; Fri, 9 Jul 2021 18:33:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id F183E6B007B; Fri, 9 Jul 2021 18:33:18 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0096.hostedemail.com [216.40.44.96]) by kanga.kvack.org (Postfix) with ESMTP id C998B6B0073 for ; Fri, 9 Jul 2021 18:33:18 -0400 (EDT) Received: from smtpin40.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 0F13818547 for ; Fri, 9 Jul 2021 22:33:18 +0000 (UTC) X-FDA: 78344501676.40.802CD8A Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf23.hostedemail.com (Postfix) with ESMTP id B549490000B7 for ; Fri, 9 Jul 2021 22:33:17 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id BFCA4613B0; Fri, 9 Jul 2021 22:33:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1625869996; bh=vB6UUDCayTxmA7o4zqOKFTp2vJ9b5CMA+bhTA3+T6UY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=oIhUGKASaH0OdOwF/jv5ekgOeIjfDYZ4SnnN43ojN2s7HF2+TkRCDxTG4tSwWzwN1 PidrWQdd+CRTVHnLi5TAImaovQJ6KRAnnbzDyhb80y/hQARBuWd6cfAjx/np8C6S0F o9lKhO5RnWM5z6oC6UQ0Y2BtROjGmca7lB+3lKVQ= Date: Fri, 9 Jul 2021 15:33:16 -0700 From: Andrew Morton To: Yang Huan Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, kernel@vivo.com, syzbot+b07d8440edb5f8988eea@syzkaller.appspotmail.com, Wang Qing Subject: Re: [PATCH] mm/page_alloc: fix alloc_pages_bulk/set_page_owner panic on irq disabled Message-Id: <20210709153316.a81214a453920dbcc2714ae6@linux-foundation.org> In-Reply-To: <20210709090600.9804-1-link@vivo.com> References: <20210709090600.9804-1-link@vivo.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=oIhUGKAS; spf=pass (imf23.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-Stat-Signature: 4jda1eqedmorqjkhqf3awrm4zp3t79ib X-Rspamd-Queue-Id: B549490000B7 X-Rspamd-Server: rspam01 X-HE-Tag: 1625869997-836193 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 Fri, 9 Jul 2021 17:05:59 +0800 Yang Huan wrote: > The problem is caused by set_page_owner alloc memory to save stack with > GFP_KERNEL in local_riq disabled. > So, we just can't assume that alloc flags should be same with new page, > let's split it. But in most situation, same is ok, in alloc_pages_bulk, > input GFP_ATOMIC when prep_new_pages Please more fully describe the bug which is being fixed. A link to the sysbot report would be helpful. I assume there was a stack backtrace available? Seeing the will help others to understand the bug. And if you are able to identify the patch which introduced the bug, a Fixes: tag would be helpful as well. Thanks.