From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org, vbabka@suse.cz,
sfr@canb.auug.org.au, hughd@google.com,
akpm@linux-foundation.org
Subject: + mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch added to -mm tree
Date: Mon, 28 Mar 2022 13:09:36 -0700 [thread overview]
Message-ID: <20220328200937.AE5C2C340ED@smtp.kernel.org> (raw)
The patch titled
Subject: mm/munlock: remove fields to fix htmldocs warnings
has been added to the -mm tree. Its filename is
mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Hugh Dickins <hughd@google.com>
Subject: mm/munlock: remove fields to fix htmldocs warnings
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.
Link: https://lkml.kernel.org/r/d2c8f66d-be8e-7c91-b0c8-b2f7ffb08bec@google.com
Fixes: 07ca76067308 ("mm/munlock: maintain page->mlock_count while unevictable")
Signed-off-by: Hugh Dickins <hughd@google.com>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mm_types.h | 8 +-------
mm/swap.c | 4 ++--
2 files changed, 3 insertions(+), 9 deletions(-)
--- a/include/linux/mm_types.h~mm-munlock-remove-fields-to-fix-htmldocs-warnings
+++ a/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;
--- a/mm/swap.c~mm-munlock-remove-fields-to-fix-htmldocs-warnings
+++ a/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);
}
_
Patches currently in -mm which might be from hughd@google.com are
mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch
next reply other threads:[~2022-03-28 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 20:09 Andrew Morton [this message]
2022-03-28 21:54 ` + mm-munlock-remove-fields-to-fix-htmldocs-warnings.patch added to -mm tree Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220328200937.AE5C2C340ED@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.