From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta0.migadu.com (out-173.mta0.migadu.com [91.218.175.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E962E3E1213 for ; Wed, 1 Apr 2026 11:54:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775044466; cv=none; b=EpQResNAWHKLDDXSIOlSyosf0XUbcp3NqDCb75BPhO6KhrZLxWe7VSn0TiJBQ1wLxZopYxuB5oIf5+RShVvfunWBbOZrwoAnE1SqMGYx0Zd+Q+TYe7Z0z4jX2m4vUj+0mgz0fo2Shqgg+dxx7TGASPZnyzqOHL1xegWNrHRciR0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775044466; c=relaxed/simple; bh=MPpGat1JrjLAfrTYVFuLaONl0VfI/rxkrkzOvJYSD2Q=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=tyA5wudCON9zyn7OyQLyHr6sJW43p2C5Ls2d0ju3uAp9pcqVwN3mdn84ECf/ZRHUMgLM/oIZoRkESXqySpntRUyebrCmuDFPfhxnxbRmyUvL70jbGWQnmpsq4IKxDc36T6LZUDn8gjP3+3jU6HDVrMq62QaQ/IGHWwsH9X8sCzc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=FA3xorRu; arc=none smtp.client-ip=91.218.175.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="FA3xorRu" Message-ID: <87a48c70-b6fd-48f6-9ec0-7eb2dc6cc3d1@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1775044463; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Od0KGdAt79Hlpl+RQqHGd+sZXqx3QxXuL8MZO01WLhE=; b=FA3xorRuCN1CkX5XsCTYNerU5KwqOVywN0vQvF43TelYLJ3CQvxT0s//W7+9bD9Tk6yhib jJxP3b7CR5X6ngcP1kG4DVpYnqzurWCl+gOykGo72rU+ahThqH07aH8XlkzXU9wXKon0BI auoqb25HQUO00BzqhhzT+QklpElPf9U= Date: Wed, 1 Apr 2026 19:54:14 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [syzbot] [mm?] WARNING in deferred_split_folio Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Lance Yang To: "David Hildenbrand (Arm)" Cc: kartikey406@gmail.com, usama.arif@linux.dev, Liam.Howlett@oracle.com, ziy@nvidia.com, syzbot+a7067a757858ac8eb085@syzkaller.appspotmail.com, akpm@linux-foundation.org, baohua@kernel.org, baolin.wang@linux.alibaba.com, dev.jain@arm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, npache@redhat.com, ryan.roberts@arm.com, syzkaller-bugs@googlegroups.com References: <38a347dc-8a1c-4d04-926d-7a6318e93ca2@kernel.org> <20260401113434.29369-1-lance.yang@linux.dev> <7176f8a2-8830-4fe9-b00e-fae67e2ac81d@linux.dev> <70576b00-6210-4eec-aeb8-69a74cca27d1@kernel.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 2026/4/1 19:51, Lance Yang wrote: > > > On 2026/4/1 19:44, David Hildenbrand (Arm) wrote: >> On 4/1/26 13:41, Lance Yang wrote: >>> >>> >>> On 2026/4/1 19:38, David Hildenbrand (Arm) wrote: >>>> On 4/1/26 13:34, Lance Yang wrote: >>>>> >>>>> >>>>> ACK. >>>>> >>>>> >>>>> certainly, will do! But commit[1] ("mm: migrate: requeue destination >>>>> folio on deferred split queue") is only in mm-stable now, not yet >>>>> upstream/stable ... >>>> >>>> It's tricky. The original commit will be backported to stable kernels, >>>> so we want also the fix to be backported to the same stable kernels. >>>> >>>> The commit id in mm-stable is "stable" now. >>> >>> Emm... Not a big deal, I guess. We can always submit a stable backport >>> once that fix gets merged into stable :D >> >> What's the problem with tagging the commit right way as Cc: stable? > > Sure, that makes sense. I'll add "Cc: stable" to the fix as well, so > it can follow 8a8ca142a488 into stable ;) 8a8ca142a488 refers to commit "mm: migrate: requeue destination folio on deferred split queue".