Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp5474298iog; Wed, 22 Jun 2022 21:39:58 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uYckfSPqFfNdiuJTAwCYSdfxnZ8QsIJV+GrkJJdHQI7glc8D+aOAn85RxQMoRQLARm+RbN X-Received: by 2002:a17:90a:e013:b0:1ec:7b12:e326 with SMTP id u19-20020a17090ae01300b001ec7b12e326mr2002493pjy.13.1655959198674; Wed, 22 Jun 2022 21:39:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655959198; cv=none; d=google.com; s=arc-20160816; b=mZqAr3UfDrWMBCsErvv7vv1dDZ9zrCpniXkBFSkyBqdnsWTXE7Pt2LDnc4eCc4QB/U Nd4I76N/tp3LRAqgGRVsXJ3l8iztqAfppFPtA2s4EH0jNRxcoetqSkh4stabmY//5V9H z7SUm5JEGBlqjRhmiCtvs+xbyZH4fj9ZK6n+tflsKaNMk2GP3HtjDf5hMsr3C5dPhvmZ 3334Bd7XF3gFQZ60rsNX5Km8wq8HqHmne7YRe4293GgdFgivCK18YfVrq95gDEZHnQ80 1y3MoiJ9xck0hNFknyQ4cgidS/8a0JDzOyxEmrWSMqliOz8MroNrR8h422hteLhrs1XE xNkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=5C+XiHaOAuGr9ITlyPSDvgchDu5ILHwN6mWwq8+shYQ=; b=rVOQQBL1Mr1ULEU8cRaNAiZxl+VHZOPTXujfr6uzD76zq6MgrfDpplmbHYx+dPCGpV ZidqVGmq7aDQjprhaoRzp9ig+lsgDpBXi5D0O/BptarlPdXZfpXidZahzkxDYva4j/qp 06pyuE7nOkTppYIsqX9BuVq/1mBvi/KuhBEv/lCrQZ29PGv03FuozuBrHtTGBnKEDk6Q V9qLvPt7KukQb8H0fmZZWfQUQ/awbXjyYQrG3NlglO+F0WzgZNVT3PIySpe7mc8T+3M9 EHw52h94av3Jiyw6h4O9+Y/7IKaEvjvrUJPWtQasb8bIMxKjbi3mZWD20h8X/t6wuXHX 3U8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=RMUg4hFq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=bytedance.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y12-20020a170903010c00b0016a24d76abasi12016247plc.298.2022.06.22.21.39.09; Wed, 22 Jun 2022 21:39:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=RMUg4hFq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=bytedance.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377348AbiFWCPw (ORCPT + 99 others); Wed, 22 Jun 2022 22:15:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230296AbiFWCPu (ORCPT ); Wed, 22 Jun 2022 22:15:50 -0400 Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0C98133A22 for ; Wed, 22 Jun 2022 19:15:47 -0700 (PDT) Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-3137316bb69so180462937b3.10 for ; Wed, 22 Jun 2022 19:15:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5C+XiHaOAuGr9ITlyPSDvgchDu5ILHwN6mWwq8+shYQ=; b=RMUg4hFqzCPu+TwayaHdoFw1lEbENOR5xl7OVHaaEiPmKSiuW3Kv90JlK7sqZ6l10G l+HgfjYGmez3OLT2bYaEshICznR44QsKw3PKKnmd8QUZJYNxScpifo0BsC5K6dOw9iwA BkpzezUlxh2ElDJoRYqiE4r9vZhA/WX22xWN223+4yKu7xAMTnQtD0d8v4qMtoTPnEze 8ZhCJxsH6zs2HBu2lZ7BLoTq7y/QdEVDrOs6WLZ496MQeB2kHV9ALEEu3SVZfsObKgYW 3o84Af8L9ggU9AQ7/Amd/kLnSEULTzT5zFqxvz1HM+aAuIV/aTvcSAz9pvB9xBrcmuzZ az1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5C+XiHaOAuGr9ITlyPSDvgchDu5ILHwN6mWwq8+shYQ=; b=dWBx0FS5pYJgEoOb5uJqPYNQdHdSUL2kYWKCRth/G4ExxwWvH+2HfIbFBDWhHydfh8 +0O/EVUesd7DuAHkIRpMSWDCLv7gN8+xkWTftR2hgk1bCsFsHZsV8lSL10uiFOa25n6c RSTp9Aw73wxZhMiMKTax7AbAnBg+nZ9ftpbhGWuBeNsfN2tda/gPSl4NZX0WVbOgDx94 zfynHKkLb4hgUEHJBMbjTBhMGQ6tL15s840VgIqGMC8QtSuRwoxudcnEqdr4QHSlBieQ 5R5EYFmeyJs4KnSueHBd5tUTgsMcgYlGqYhleITEuOa1oB+ykuUTRyeQTtsU5JVm2qsr 2cIQ== X-Gm-Message-State: AJIora/x+X/JEKgsC+ZvIss5fnxYNC7HPlsayBcwduBzsde3g7xoZ2GV Ip0NZsUfxw5PcJyQjDi8wxzQYW7A6PFGgHQLQfWynQ== X-Received: by 2002:a81:2fd8:0:b0:314:eaa:bbc1 with SMTP id v207-20020a812fd8000000b003140eaabbc1mr8055504ywv.141.1655950546326; Wed, 22 Jun 2022 19:15:46 -0700 (PDT) MIME-Version: 1.0 References: <20220622153815.6f2e671a@canb.auug.org.au> <20220622115917.5268aeea70b22a566c90be8c@linux-foundation.org> In-Reply-To: <20220622115917.5268aeea70b22a566c90be8c@linux-foundation.org> From: Muchun Song Date: Thu, 23 Jun 2022 10:15:09 +0800 Message-ID: Subject: Re: linux-next: manual merge of the mm tree with the folio tree To: Andrew Morton Cc: Stephen Rothwell , Matthew Wilcox , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 23, 2022 at 2:59 AM Andrew Morton wrote: > > On Wed, 22 Jun 2022 15:22:35 +0800 Muchun Song wrote: > > > > Today's linux-next merge of the mm tree got a conflict in: > > > > > > mm/vmscan.c > > > > > > between commit: > > > > > > 15077be8badc ("vmscan: Add check_move_unevictable_folios()") > > > > Sorry for the conflicts, I didn't see this change in the mm-unstable branch > > yesterday. Based on this commit, I have reworked the following commit > > (see attachment, mainly changes are about check_move_unevictable_folios()). > > Andrew can pick it up if he wants to replace the original patch with > > the new one. > > Your comments in > https://lkml.kernel.org/r/YrM2XCwzu65cb81r@FVFYT0MHHV2J.googleapis.com > make me wonder whether simply dropping cca700a8e695 ("mm: lru: use > lruvec lock to serialize memcg changes") would be best? > Hi Andrew, Well, I think we can drop this now. After memcg reparenting work stabilizes, I will resend this patch again. Thanks.