[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <c3195d8a-2931-0749-973a-1d04e4baec94@suse.cz>
Date: Wed, 20 Apr 2022 11:12:16 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
david@...hat.com, akpm@...ux-foundation.org
Subject: Re: + mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix.patch
added to -mm tree
On 4/13/22 23:33, Andrew Morton wrote:
> The patch titled
> Subject: mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix
> has been added to the -mm tree. Its filename is
> mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix.patch
>
> This patch should soon appear at
> https://ozlabs.org/~akpm/mmots/broken-out/mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix.patch
> and later at
> https://ozlabs.org/~akpm/mmotm/broken-out/mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix.patch
It seems to have disappeared? Also doesn't appear to be squashed in the
original 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: David Hildenbrand <david@...hat.com>
> Subject: mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix
>
> Link: https://lkml.kernel.org/r/ac725bcb-313a-4fff-250a-68ba9a8f85fb@redhat.com
>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> ---
>
>
> --- a/mm/memory.c~mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix
> +++ a/mm/memory.c
> @@ -3747,7 +3747,7 @@ vm_fault_t do_swap_page(struct vm_fault
> */
> exclusive = true;
> } else if (exclusive && PageWriteback(page) &&
> - !(swp_swap_info(entry)->flags & SWP_STABLE_WRITES)) {
> + (swp_swap_info(entry)->flags & SWP_STABLE_WRITES)) {
> /*
> * This is tricky: not all swap backends support
> * concurrent page modifications while under writeback.
> _
>
> Patches currently in -mm which might be from david@...hat.com are
>
> mm-rmap-fix-missing-swap_free-in-try_to_unmap-after-arch_unmap_one-failed.patch
> mm-hugetlb-take-src_mm-write_protect_seq-in-copy_hugetlb_page_range.patch
> mm-memory-slightly-simplify-copy_present_pte.patch
> mm-rmap-split-page_dup_rmap-into-page_dup_file_rmap-and-page_try_dup_anon_rmap.patch
> mm-rmap-convert-rmap-flags-to-a-proper-distinct-rmap_t-type.patch
> mm-rmap-remove-do_page_add_anon_rmap.patch
> mm-rmap-pass-rmap-flags-to-hugepage_add_anon_rmap.patch
> mm-rmap-drop-compound-parameter-from-page_add_new_anon_rmap.patch
> mm-rmap-use-page_move_anon_rmap-when-reusing-a-mapped-pageanon-page-exclusively.patch
> mm-huge_memory-remove-outdated-vm_warn_on_once_page-from-unmap_page.patch
> mm-page-flags-reuse-pg_mappedtodisk-as-pg_anon_exclusive-for-pageanon-pages.patch
> mm-remember-exclusively-mapped-anonymous-pages-with-pg_anon_exclusive.patch
> mm-gup-disallow-follow_pagefoll_pin.patch
> mm-support-gup-triggered-unsharing-of-anonymous-pages.patch
> mm-gup-trigger-fault_flag_unshare-when-r-o-pinning-a-possibly-shared-anonymous-page.patch
> mm-gup-sanity-check-with-config_debug_vm-that-anonymous-pages-are-exclusive-when-unpinning.patch
> mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit.patch
> mm-swap-remember-pg_anon_exclusive-via-a-swp-pte-bit-fix.patch
> mm-debug_vm_pgtable-add-tests-for-__have_arch_pte_swp_exclusive.patch
> x86-pgtable-support-__have_arch_pte_swp_exclusive.patch
> arm64-pgtable-support-__have_arch_pte_swp_exclusive.patch
> s390-pgtable-cleanup-description-of-swp-pte-layout.patch
> s390-pgtable-support-__have_arch_pte_swp_exclusive.patch
> powerpc-pgtable-remove-_page_bit_swap_type-for-book3s.patch
> powerpc-pgtable-support-__have_arch_pte_swp_exclusive-for-book3s.patch
>
Powered by blists - more mailing lists