Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp5613589pxb; Mon, 28 Mar 2022 14:59:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwD6OZBNyeiXyAIVKTzzORU4e7ojbtUMPzp7edcraycYMYdbWVZoafH5va5RQ4MGivg7Q80 X-Received: by 2002:a63:5c53:0:b0:381:309e:e72c with SMTP id n19-20020a635c53000000b00381309ee72cmr12050184pgm.40.1648504779764; Mon, 28 Mar 2022 14:59:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648504779; cv=none; d=google.com; s=arc-20160816; b=KBr+bGJjtFZB30KothBCeC6yrN80k4KafyRzD4k5TcsHeLgVfaVH2HmZgS6uajU/6k /urYJVa0ZUWq221ORu22ejTJUIXuua1Pn60d5r/w3+t4GhrVrobsWZyzibPQ+GNlIzgP kceJlTH056qMOhpcGifjOnBqD8OxMIc5OAoNg52bunqp5Sg7/v5pF39hHBPue2s8UnKC 3l4ZGXQQUZW9SKb6WlgRrkIHjWNHmjFueuRCMawg9LvbrFli9SNBAmdySsDvm/kZfY7j p3hoz8P6dAX1+Ib1L+OdWoFBUxh0MTSLwq6H2jN2LNqYl7MfoJIzQXgVwp0v9yj3+zmz 7xHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:subject:cc:to:from:date :dkim-signature; bh=NGspnAFOzJSoDZcuTuDayNTMlf+9yY8D8Ve789Ll0sM=; b=mLMN74S2V9ujftB1KGqE2I8h6VEnsNyoR34rZTkOwFUa0Med92PF4bwvVq5J7XRAUB oEsURHpeicHNFZ0LmvmYd4wLc2cPLyuVLjtSFYy2ueyOK1VspLaZxFgU2LWw1xqORGAO ulb0wZL7eSbfvfAwBbvVEf5y8f8+2SNN5gNdLZtgdL8H/fn5q79H5Lhle0JqXhCDmFic S1bSdp2OtTar2NsaM1JdIHRJgvIMxqaTmfU8OyUFvIxZrCdUTWDfXpFXN/sWaBuC/qep tcvlDp/bC4D/EzEDnQWFDUDc9ShxVOeO/KNCZ30/wU0yQuOGBu0wRHLhfBD6v8PKq+nr fDlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=jkm+7pi2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id k65-20020a633d44000000b003982828d932si11496080pga.628.2022.03.28.14.59.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Mar 2022 14:59:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=jkm+7pi2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CCA458230E; Mon, 28 Mar 2022 14:25:27 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235913AbiC1T7O (ORCPT + 99 others); Mon, 28 Mar 2022 15:59:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48266 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245592AbiC1T7F (ORCPT ); Mon, 28 Mar 2022 15:59:05 -0400 Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 339C5673FC for ; Mon, 28 Mar 2022 12:57:24 -0700 (PDT) Received: by mail-qt1-x829.google.com with SMTP id d15so13386766qty.8 for ; Mon, 28 Mar 2022 12:57:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:mime-version; bh=NGspnAFOzJSoDZcuTuDayNTMlf+9yY8D8Ve789Ll0sM=; b=jkm+7pi2evYjUioD24kEJ4jw5PSVqdjUsYal52RTsLOFxeM/JoTW0tmGWK/fsDGF9b dW5MW3VY0ParUG+jUCsp9i2mofXCCMhyHbESxtxK+Tf/4iKI91/RWDhdDQu8Ec4i5DGW G9B+Re0ozD0/P1U02GKOGXSrp/SL59FyJ+Q7vwpVp1Nb4BgnW/I6wwdgXUTOXwVD8UoJ GFlAJXjk5bip6TuZEryLoRVUdgTkXFWPW4aD4OzJ7uqRbqMu7DLajDrviY7g1A4jHOPJ eHfdaH5pc/CghBjQz7k3tG0+PNd5ee/u/TQ0rmubKYYsGZeUNexxJx5gz2rZPzf3Unli 0Aaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version; bh=NGspnAFOzJSoDZcuTuDayNTMlf+9yY8D8Ve789Ll0sM=; b=VxQ4AcfpLvQhlSLtGY7c0uaNcL+gIEMJJlLQbC4LfUUYEMYpzz5XH+zkpRn6CKed4A uUJdLZCvgI8zA+FPhbz8dZKe5hrREiJWKQX8u95NpbPLKszeFBoLc1Ne7eAqIyt+CePC POSkEthoxoIRCly0ZDLmSW+XglyEuyY4Gc5dP6hMkE+LDjqv1wFVv4eVQ4/ViBSEVodX 38Vhq+ZGoYkLKSbLnD+NnYVlyfZcS32csEMQCHLj0b91T48IiocVSKuOHjwaldGKTdea rkYOrOKCNCv6C/IYMp8c6MZYld+DMeSLKkME0BpX1ejwnr1ETfkM1kLcLT99+zpS+y1m ac2Q== X-Gm-Message-State: AOAM533zCd18LiZXRe1sSmVePQv9VUncTUJr5g4qCd0ACXJbqUP1dMM9 bviLuutonPBXdidjFCEwxKLmpg== X-Received: by 2002:a05:622a:552:b0:2e2:72c:a05b with SMTP id m18-20020a05622a055200b002e2072ca05bmr23563976qtx.409.1648497443168; Mon, 28 Mar 2022 12:57:23 -0700 (PDT) Received: from ripple.attlocal.net (172-10-233-147.lightspeed.sntcca.sbcglobal.net. [172.10.233.147]) by smtp.gmail.com with ESMTPSA id q8-20020a05622a030800b002e1c9304db8sm13082619qtw.38.2022.03.28.12.57.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Mar 2022 12:57:22 -0700 (PDT) Date: Mon, 28 Mar 2022 12:57:20 -0700 (PDT) From: Hugh Dickins X-X-Sender: hugh@ripple.anvils To: Andrew Morton cc: Stephen Rothwell , Matthew Wilcox , Vlastimil Babka , Hugh Dickins , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH] mm/munlock: remove fields to fix htmldocs warnings Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-9.5 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE, USER_IN_DEF_DKIM_WL autolearn=no 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 Stephen reports that 'make htmldocs' currently issues two warnings: include/linux/mm_types.h:275: warning: Function parameter or member '__filler' not described in 'folio' include/linux/mm_types.h:275: warning: Function parameter or member 'mlock_count' not described in 'folio' Certainly __filler doesn't want documenting there, and all but one use of mlock_count is through page->mlock_count at present: so I think it's best just to remove them both from struct folio for now, and sort out the right way to document folio->mlock_count once that is the one true way. Reported-by: Stephen Rothwell Fixes: 07ca76067308 ("mm/munlock: maintain page->mlock_count while unevictable") Signed-off-by: Hugh Dickins --- include/linux/mm_types.h | 8 +------- mm/swap.c | 4 ++-- 2 files changed, 3 insertions(+), 9 deletions(-) --- 5.18-pre/include/linux/mm_types.h +++ linux/include/linux/mm_types.h @@ -253,13 +253,7 @@ struct folio { struct { /* public: */ unsigned long flags; - union { - struct list_head lru; - struct { - void *__filler; - unsigned int mlock_count; - }; - }; + struct list_head lru; struct address_space *mapping; pgoff_t index; void *private; --- 5.18-pre/mm/swap.c +++ linux/mm/swap.c @@ -1026,13 +1026,13 @@ static void __pagevec_lru_add_fn(struct folio_clear_active(folio); folio_set_unevictable(folio); /* - * folio->mlock_count = !!folio_test_mlocked(folio)? + * page->mlock_count = !!PageMlocked(page)? * But that leaves __mlock_page() in doubt whether another * actor has already counted the mlock or not. Err on the * safe side, underestimate, let page reclaim fix it, rather * than leaving a page on the unevictable LRU indefinitely. */ - folio->mlock_count = 0; + folio_page(folio, 0)->mlock_count = 0; if (!was_unevictable) __count_vm_events(UNEVICTABLE_PGCULLED, nr_pages); }