From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-174.mta1.migadu.com (out-174.mta1.migadu.com [95.215.58.174]) (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 8C8693DCDA9 for ; Wed, 1 Apr 2026 11:51:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775044313; cv=none; b=pmQgbUVdiCkN3Q9NNprSyVD6VR4mQyIUZVcZG3vxKJishXPavoBx+uny0GBpd3ydAkiBUS1ymFN4MLvYrI+QG+sUljdDFXh3xhBU00R0n4MVaJVNOM6KMo/+zEsJo+2UGBM/BNgpgqDxw8xg8iiMTOrBNEnleqgAlSUfGjtp9B0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775044313; c=relaxed/simple; bh=X89KGNZ0v0OFgTMhoZTT5Lei8+uFZGneqbE8y0O7ecQ=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=VRF9cIyMe8MbswmV9CpGq0umhEZ+iTonEIRA2PUtSfX+2z0d5mJ5IpJz13xyVBQSWUQP6jPlFpDoT05SUX/jmqTD4dgLrswr1auZSlnV97V5Zft2+6dZQcrItykuo+7pubhDSNtiROTciyO5jlf6z5b+iAMQs19QXlxUrEL8/Xo= 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=aQQFE9SZ; arc=none smtp.client-ip=95.215.58.174 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="aQQFE9SZ" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1775044309; 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=uLlhZc+mP4ePWpjvv4aWNtQSAr/NOqK11GS/RTSR+bY=; b=aQQFE9SZOw0V8amtAysnp2bzjbgDyyNUV8od9WfM/XRPSxBEnk5xFUK9/Hak+lMwYUtLnf YQf1njE76/9Dl+/mFihl/8m+qXKvr42uEpKPZHrKaL7uyzf/f5ajHKHYgvUlyXVKNh07e0 TdE3TY0OD+0PO1l1PC7r+DWOBIEQT3Y= Date: Wed, 1 Apr 2026 19:51:38 +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 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> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Lance Yang In-Reply-To: <70576b00-6210-4eec-aeb8-69a74cca27d1@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT 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 ;)