From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752462AbeENJJ5 (ORCPT ); Mon, 14 May 2018 05:09:57 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:37624 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752375AbeENJJw (ORCPT ); Mon, 14 May 2018 05:09:52 -0400 Subject: Re: [PATCH v2] mm/ksm: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm To: Jia He , Andrew Morton Cc: Andrea Arcangeli , Minchan Kim , Claudio Imbrenda , Arvind Yadav , Mike Rapoport , linux-mm@kvack.org, linux-kernel@vger.kernel.org, jia.he@hxt-semitech.com, Hugh Dickins , Marc Zyngier References: <20180503124415.3f9d38aa@p-imbrenda.boeblingen.de.ibm.com> <1525403506-6750-1-git-send-email-hejianet@gmail.com> <20180509163101.02f23de1842a822c61fc68ff@linux-foundation.org> <80070c0b-aecf-0dcf-2b36-fa6110ed8ad5@gmail.com> From: Suzuki K Poulose Message-ID: Date: Mon, 14 May 2018 10:09:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <80070c0b-aecf-0dcf-2b36-fa6110ed8ad5@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/05/18 02:26, Jia He wrote: > Hi Andrew > > > On 5/10/2018 7:31 AM, Andrew Morton Wrote: >> On Fri,  4 May 2018 11:11:46 +0800 Jia He wrote: >> >>> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE >>> unaligned for rmap_item->address under memory pressure tests(start 20 guests >>> and run memhog in the host). >>> >>> ... >>> >>> In rmap_walk_ksm, the rmap_item->address might still have the STABLE_FLAG, >>> then the start and end in handle_hva_to_gpa might not be PAGE_SIZE aligned. >>> Thus it will cause exceptions in handle_hva_to_gpa on arm64. >>> >>> This patch fixes it by ignoring(not removing) the low bits of address when >>> doing rmap_walk_ksm. >>> >>> Signed-off-by: jia.he@hxt-semitech.com >> I assumed you wanted this patch to be committed as >> From:jia.he@hxt-semitech.com rather than From:hejianet@gmail.com, so I >> made that change.  Please let me know if this was inappropriate. > Thanks, because there is still some issues in our company's mail server. > I have to use my gmail mailbox. >> >> You can do this yourself by adding an explicit From: line to the very >> start of the patch's email text. >> >> Also, a storm of WARN_ONs is pretty poor behaviour.  Is that the only >> misbehaviour which this bug causes?  Do you think the fix should be >> backported into earlier kernels? > IMO, it should be backported to stable tree, seems that I missed CC to stable tree ;-) > the stom of WARN_ONs is very easy for me to reproduce. > More than that, I watched a panic (not reproducible) as follows: > [35380.805825] page:ffff7fe003742d80 count:-4871 mapcount:-2126053375 mapping:          (null) index:0x0 > [35380.815024] flags: 0x1fffc00000000000() > [35380.818845] raw: 1fffc00000000000 0000000000000000 0000000000000000 ffffecf981470000 > [35380.826569] raw: dead000000000100 dead000000000200 ffff8017c001c000 0000000000000000 > [35380.834294] page dumped because: nonzero _refcount > [35380.908341] CPU: 29 PID: 18323 Comm: qemu-kvm Tainted: G W 4.14.15-5.hxt.aarch64 #1 > [35380.917107] Hardware name: > [35380.930909] Call trace: > [35380.933345] [] dump_backtrace+0x0/0x22c > [35380.938723] [] show_stack+0x24/0x2c > [35380.943759] [] dump_stack+0x8c/0xb0 > [35380.948794] [] bad_page+0xf4/0x154 > [35380.953740] [] free_pages_check_bad+0x90/0x9c > [35380.959642] [] free_pcppages_bulk+0x464/0x518 > [35380.965545] [] free_hot_cold_page+0x22c/0x300 > [35380.971448] [] __put_page+0x54/0x60 > [35380.976484] [] unmap_stage2_range+0x170/0x2b4 > [35380.982385] [] kvm_unmap_hva_handler+0x30/0x40 > [35380.988375] [] handle_hva_to_gpa+0xb0/0xec > [35380.994016] [] kvm_unmap_hva_range+0x5c/0xd0 > [35380.999833] [] kvm_mmu_notifier_invalidate_range_start+0x60/0xb0 > [35381.007387] [] __mmu_notifier_invalidate_range_start+0x64/0x8c > [35381.014765] [] try_to_unmap_one+0x78c/0x7a4 > [35381.020493] [] rmap_walk_ksm+0x124/0x1a0 > [35381.025961] [] rmap_walk+0x94/0x98 > [35381.030909] [] try_to_unmap+0x100/0x124 > [35381.036293] [] unmap_and_move+0x480/0x6fc > [35381.041847] [] migrate_pages+0x10c/0x288 > [35381.047318] [] compact_zone+0x238/0x954 > [35381.052697] [] compact_zone_order+0xc4/0xe8 > [35381.058427] [] try_to_compact_pages+0x160/0x294 > [35381.064503] [] __alloc_pages_direct_compact+0x68/0x194 > [35381.071187] [] __alloc_pages_nodemask+0xc20/0xf7c > [35381.077437] [] alloc_pages_vma+0x1a4/0x1c0 > [35381.083080] [] do_huge_pmd_anonymous_page+0x128/0x324 > [35381.089677] [] __handle_mm_fault+0x71c/0x7e8 > [35381.095492] [] handle_mm_fault+0xf8/0x194 > [35381.101049] [] __get_user_pages+0x124/0x34c > [35381.106777] [] populate_vma_page_range+0x90/0x9c > [35381.112941] [] __mm_populate+0xc4/0x15c > [35381.118322] [] SyS_mlockall+0x100/0x164 > [35381.123705] Exception stack(0xffff800dce5f3ec0 to 0xffff800dce5f4000) > [35381.130128] 3ec0: 0000000000000003 d6e6024cc9b87e00 0000aaaabe94f000 0000000000000000 > [35381.137940] 3ee0: 0000000000000002 0000000000000000 0000000000000000 0000aaaacf6fc3c0 > [35381.145753] 3f00: 00000000000000e6 0000aaaacf6fc490 0000ffffeeeab0f0 d6e6024cc9b87e00 > [35381.153565] 3f20: 0000000000000000 0000aaaabe81b3c0 0000000000000020 00009e53eff806b5 > [35381.161379] 3f40: 0000aaaabe94de48 0000ffffa7c269b0 0000000000000011 0000ffffeeeabf68 > [35381.169190] 3f60: 0000aaaaceacfe60 0000aaaabe94f000 0000aaaabe9ba358 0000aaaabe7ffb80 > [35381.177003] 3f80: 0000aaaabe9ba000 0000aaaabe959f64 0000000000000000 0000aaaabe94f000 > [35381.184815] 3fa0: 0000000000000000 0000ffffeeeabdb0 0000aaaabe5f3bf8 0000ffffeeeabdb0 > [35381.192628] 3fc0: 0000ffffa7c269b8 0000000060000000 0000000000000003 00000000000000e6 > [35381.200440] 3fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > [35381.208254] [] __sys_trace_return+0x0/0x4 > [35381.213809] Disabling lock debugging due to kernel taint > > I ever injected a fault on purpose in kvm_unmap_hva_range by set size=size-0x200, the call trace is similar > as above. Thus, I thought the panic is similarly caused by the root cause of WARN_ON Please could you share your "changes" (that injected the fault) that triggered this Panic and the steps that triggered this ? The only reason we should get there is by trying to put a page that is not owned by the KVM Stage 2 page table either: 1) It was free'd already ? - We has some race conditions there which were fixed. 2) The code tries to access something that doesn't belong there. - If this happens that doesn't look good for a simple change you mentioned. So we would like to know better about the situation to see if there is something we need to address. Suzuki From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f197.google.com (mail-ot0-f197.google.com [74.125.82.197]) by kanga.kvack.org (Postfix) with ESMTP id BB2586B000A for ; Mon, 14 May 2018 05:09:53 -0400 (EDT) Received: by mail-ot0-f197.google.com with SMTP id w10-v6so14837359otj.14 for ; Mon, 14 May 2018 02:09:53 -0700 (PDT) Received: from foss.arm.com (foss.arm.com. [217.140.101.70]) by mx.google.com with ESMTP id i205-v6si2846818oia.460.2018.05.14.02.09.52 for ; Mon, 14 May 2018 02:09:52 -0700 (PDT) Subject: Re: [PATCH v2] mm/ksm: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm References: <20180503124415.3f9d38aa@p-imbrenda.boeblingen.de.ibm.com> <1525403506-6750-1-git-send-email-hejianet@gmail.com> <20180509163101.02f23de1842a822c61fc68ff@linux-foundation.org> <80070c0b-aecf-0dcf-2b36-fa6110ed8ad5@gmail.com> From: Suzuki K Poulose Message-ID: Date: Mon, 14 May 2018 10:09:47 +0100 MIME-Version: 1.0 In-Reply-To: <80070c0b-aecf-0dcf-2b36-fa6110ed8ad5@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Jia He , Andrew Morton Cc: Andrea Arcangeli , Minchan Kim , Claudio Imbrenda , Arvind Yadav , Mike Rapoport , linux-mm@kvack.org, linux-kernel@vger.kernel.org, jia.he@hxt-semitech.com, Hugh Dickins , Marc Zyngier On 10/05/18 02:26, Jia He wrote: > Hi Andrew > > > On 5/10/2018 7:31 AM, Andrew Morton Wrote: >> On Fri,A 4 May 2018 11:11:46 +0800 Jia He wrote: >> >>> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE >>> unaligned for rmap_item->address under memory pressure tests(start 20 guests >>> and run memhog in the host). >>> >>> ... >>> >>> In rmap_walk_ksm, the rmap_item->address might still have the STABLE_FLAG, >>> then the start and end in handle_hva_to_gpa might not be PAGE_SIZE aligned. >>> Thus it will cause exceptions in handle_hva_to_gpa on arm64. >>> >>> This patch fixes it by ignoring(not removing) the low bits of address when >>> doing rmap_walk_ksm. >>> >>> Signed-off-by: jia.he@hxt-semitech.com >> I assumed you wanted this patch to be committed as >> From:jia.he@hxt-semitech.com rather than From:hejianet@gmail.com, so I >> made that change.A Please let me know if this was inappropriate. > Thanks, because there is still some issues in our company's mail server. > I have to use my gmail mailbox. >> >> You can do this yourself by adding an explicit From: line to the very >> start of the patch's email text. >> >> Also, a storm of WARN_ONs is pretty poor behaviour.A Is that the only >> misbehaviour which this bug causes?A Do you think the fix should be >> backported into earlier kernels? > IMO, it should be backported to stable tree, seems that I missed CC to stable tree ;-) > the stom of WARN_ONs is very easy for me to reproduce. > More than that, I watched a panic (not reproducible) as follows: > [35380.805825] page:ffff7fe003742d80 count:-4871 mapcount:-2126053375 mapping:A A A A A A A A A (null) index:0x0 > [35380.815024] flags: 0x1fffc00000000000() > [35380.818845] raw: 1fffc00000000000 0000000000000000 0000000000000000 ffffecf981470000 > [35380.826569] raw: dead000000000100 dead000000000200 ffff8017c001c000 0000000000000000 > [35380.834294] page dumped because: nonzero _refcount > [35380.908341] CPU: 29 PID: 18323 Comm: qemu-kvm Tainted: G W 4.14.15-5.hxt.aarch64 #1 > [35380.917107] Hardware name: > [35380.930909] Call trace: > [35380.933345] [] dump_backtrace+0x0/0x22c > [35380.938723] [] show_stack+0x24/0x2c > [35380.943759] [] dump_stack+0x8c/0xb0 > [35380.948794] [] bad_page+0xf4/0x154 > [35380.953740] [] free_pages_check_bad+0x90/0x9c > [35380.959642] [] free_pcppages_bulk+0x464/0x518 > [35380.965545] [] free_hot_cold_page+0x22c/0x300 > [35380.971448] [] __put_page+0x54/0x60 > [35380.976484] [] unmap_stage2_range+0x170/0x2b4 > [35380.982385] [] kvm_unmap_hva_handler+0x30/0x40 > [35380.988375] [] handle_hva_to_gpa+0xb0/0xec > [35380.994016] [] kvm_unmap_hva_range+0x5c/0xd0 > [35380.999833] [] kvm_mmu_notifier_invalidate_range_start+0x60/0xb0 > [35381.007387] [] __mmu_notifier_invalidate_range_start+0x64/0x8c > [35381.014765] [] try_to_unmap_one+0x78c/0x7a4 > [35381.020493] [] rmap_walk_ksm+0x124/0x1a0 > [35381.025961] [] rmap_walk+0x94/0x98 > [35381.030909] [] try_to_unmap+0x100/0x124 > [35381.036293] [] unmap_and_move+0x480/0x6fc > [35381.041847] [] migrate_pages+0x10c/0x288 > [35381.047318] [] compact_zone+0x238/0x954 > [35381.052697] [] compact_zone_order+0xc4/0xe8 > [35381.058427] [] try_to_compact_pages+0x160/0x294 > [35381.064503] [] __alloc_pages_direct_compact+0x68/0x194 > [35381.071187] [] __alloc_pages_nodemask+0xc20/0xf7c > [35381.077437] [] alloc_pages_vma+0x1a4/0x1c0 > [35381.083080] [] do_huge_pmd_anonymous_page+0x128/0x324 > [35381.089677] [] __handle_mm_fault+0x71c/0x7e8 > [35381.095492] [] handle_mm_fault+0xf8/0x194 > [35381.101049] [] __get_user_pages+0x124/0x34c > [35381.106777] [] populate_vma_page_range+0x90/0x9c > [35381.112941] [] __mm_populate+0xc4/0x15c > [35381.118322] [] SyS_mlockall+0x100/0x164 > [35381.123705] Exception stack(0xffff800dce5f3ec0 to 0xffff800dce5f4000) > [35381.130128] 3ec0: 0000000000000003 d6e6024cc9b87e00 0000aaaabe94f000 0000000000000000 > [35381.137940] 3ee0: 0000000000000002 0000000000000000 0000000000000000 0000aaaacf6fc3c0 > [35381.145753] 3f00: 00000000000000e6 0000aaaacf6fc490 0000ffffeeeab0f0 d6e6024cc9b87e00 > [35381.153565] 3f20: 0000000000000000 0000aaaabe81b3c0 0000000000000020 00009e53eff806b5 > [35381.161379] 3f40: 0000aaaabe94de48 0000ffffa7c269b0 0000000000000011 0000ffffeeeabf68 > [35381.169190] 3f60: 0000aaaaceacfe60 0000aaaabe94f000 0000aaaabe9ba358 0000aaaabe7ffb80 > [35381.177003] 3f80: 0000aaaabe9ba000 0000aaaabe959f64 0000000000000000 0000aaaabe94f000 > [35381.184815] 3fa0: 0000000000000000 0000ffffeeeabdb0 0000aaaabe5f3bf8 0000ffffeeeabdb0 > [35381.192628] 3fc0: 0000ffffa7c269b8 0000000060000000 0000000000000003 00000000000000e6 > [35381.200440] 3fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > [35381.208254] [] __sys_trace_return+0x0/0x4 > [35381.213809] Disabling lock debugging due to kernel taint > > I ever injected a fault on purpose in kvm_unmap_hva_range by set size=size-0x200, the call trace is similar > as above. Thus, I thought the panic is similarly caused by the root cause of WARN_ON Please could you share your "changes" (that injected the fault) that triggered this Panic and the steps that triggered this ? The only reason we should get there is by trying to put a page that is not owned by the KVM Stage 2 page table either: 1) It was free'd already ? - We has some race conditions there which were fixed. 2) The code tries to access something that doesn't belong there. - If this happens that doesn't look good for a simple change you mentioned. So we would like to know better about the situation to see if there is something we need to address. Suzuki