Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1013910ybi; Fri, 31 May 2019 12:18:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvT+vNzfOcnbmHjlicL19pqmsreZm1qlrvTQgHMvIkspu4h+FZm5tJ1qppH/DkZNHCv0XB X-Received: by 2002:a63:2a06:: with SMTP id q6mr11045116pgq.290.1559330321762; Fri, 31 May 2019 12:18:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559330321; cv=none; d=google.com; s=arc-20160816; b=GRW94/UtTwVuD2Mmwli8gVeF6NWhUOwElnJToD+HxsTxVadkpQ2GgdfMq7P0zUzLCQ DfGN2uiJ8BS7nDnuBWV5Cn/dw+UvNHdI1OBteVpj6w2A4irdVq425dLDFzoMO7IIS+kO lidhr7o303KM3qIYCIwaTsud0wvoE5AysRAUx1A9Y2FUgv7c344mb82h38nXjEvqfMB8 ukAtE0s4UlTt1p7EBpQBl3dmkOGuAfwnt+9PLrAkBH+BfOQp7r1OZ9qU0gYXuGM22tPd pmSzEucJnoa8cU8+7poZ+Xn2WHUTn3aZuYY4xXEIk3dbi7OY1Ko4o6ZSsT2TL/rtlBgn +jtg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=DjQwDIi/X61xUHV4KfxSIoA+Qjc34xm4m1RHGFioGsc=; b=xBsutmeRmniJ3cud/qQ7/koDCqg2ODM5vGqYnKrZfcGWQ/YZHmTZQzLHS/wEjujH/n UVis6rnLWFpjm9Bnw9gIfMJKpMeFcKKmTxlghZFppcMGmUbZYGwMOEHIEXNsB4UxL7jM OmthSv4NJFOiplqAlGH3ch9zwFHer1HYj3ZCjpmxF0s3oVwk07vLt8B7Qs4aki9Et5+i YqZJNplVrGtXzqY2iYyXVNUCeFFpfhtFjAA2598/V2UiOulgpLkB6jkH/FhuP4OIKJyD uLsnPy3oojb8YvnfZ4d6i/tzL3RTLtlJYJYZyXj4gEkWTjavZlhx/c8BaSTi2stkyvgc eBAA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lca.pw header.s=google header.b=ZopKFNJc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cg6si7766184plb.350.2019.05.31.12.18.25; Fri, 31 May 2019 12:18:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@lca.pw header.s=google header.b=ZopKFNJc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727194AbfEaTQv (ORCPT + 99 others); Fri, 31 May 2019 15:16:51 -0400 Received: from mail-qk1-f195.google.com ([209.85.222.195]:42182 "EHLO mail-qk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727085AbfEaTQu (ORCPT ); Fri, 31 May 2019 15:16:50 -0400 Received: by mail-qk1-f195.google.com with SMTP id b18so7009420qkc.9 for ; Fri, 31 May 2019 12:16:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lca.pw; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=DjQwDIi/X61xUHV4KfxSIoA+Qjc34xm4m1RHGFioGsc=; b=ZopKFNJcSrYMQh6vJRz0XiFxwmu0mpansaayj5Zy/797bC9u6uwCvaV/kLUFXhh4Pj m0LsqckNjFJ9MsMDJIn/w11kTW/SHyrveVAqJEOdAcUA+Dp6x05Jax7sj/DF70JwiXq5 3a7DqsSZeVqrOnWM5eQM2k8SaJPkv/bqVm5LmDUA4sQEeRd9rv/d8k31ZJKUtoJvv/v0 W40JXHgcIaAdttiEYsvjY02NeA0ODQC1PCUTizEBq1DxCdzYzZTKF9cUh0FDI23o2m/7 KsSeZbZXTX3EROMNlBhLLMaTR2YKXps1Y9ev55CDExQ/13/WEMUVwhNJzZqoIuG6ZbJ+ zgCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=DjQwDIi/X61xUHV4KfxSIoA+Qjc34xm4m1RHGFioGsc=; b=PlCD29XQiInRk3LyZ6XESJ+Kj9nMIZW2HZC1GftFYdwtGKytZf2iHghdsWf4ILbVAI RNiKZ/zzpc1UeQJ1uyyrlOqq+BclfGpfQi4Ynkv/kaceX8Cn0EKBt0rw+9dUc+bi7aN/ w1OpZbhKHZGmEiwwUzdJSKCarFwnMT7yKUtX7VFOx2VrAf/9AbaGVQB+tvXEFJbc73ta K1HWHpyOMVo5TbpNq6sU+Ik1kzBr542ULbI2tyOcgr7FN3KLsVpkFGyXNqo4KAbgE2sy 4/ie0biHs7nVs2QIq0UXWc2GoMBN11MYuGx5Xoeo9AIpE3OF6u01t0QKrMq5T9dCy8N4 7IqA== X-Gm-Message-State: APjAAAXWt8U0E12ckLl2n7hq3Ukim7Y+ajE8w/xMrTzEp8Z/jPAFn8Db 4HI7+aThFMOk370SByRU7eNRYg== X-Received: by 2002:a37:490f:: with SMTP id w15mr10187190qka.165.1559330209566; Fri, 31 May 2019 12:16:49 -0700 (PDT) Received: from dhcp-41-57.bos.redhat.com (nat-pool-bos-t.redhat.com. [66.187.233.206]) by smtp.gmail.com with ESMTPSA id p1sm1905606qti.83.2019.05.31.12.16.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 May 2019 12:16:48 -0700 (PDT) Message-ID: <1559330205.6132.40.camel@lca.pw> Subject: Re: [PATCH -mm] mm, swap: Fix bad swap file entry warning From: Qian Cai To: Dexuan-Linux Cui , Mike Kravetz Cc: "Huang, Ying" , Andrew Morton , linux-mm@kvack.org, Linux Kernel Mailing List , Andrea Parri , "Paul E . McKenney" , Michal Hocko , Minchan Kim , Hugh Dickins , Dexuan Cui , v-lide@microsoft.com, Yury Norov Date: Fri, 31 May 2019 15:16:45 -0400 In-Reply-To: References: <20190531024102.21723-1-ying.huang@intel.com> <2d8e1195-e0f1-4fa8-b0bd-b9ea69032b51@oracle.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-05-31 at 11:27 -0700, Dexuan-Linux Cui wrote: > Hi, > Did you know about the panic reported here: > https://marc.info/?t=155930773000003&r=1&w=2 > > "Kernel panic - not syncing: stack-protector: Kernel stack is > corrupted in: write_irq_affinity.isra" > > This panic is reported on PowerPC and x86. > > In the case of x86, we see a lot of "get_swap_device: Bad swap file entry" > errors before the panic: > > ... > [   24.404693] get_swap_device: Bad swap file entry 5800000000000001 > [   24.408702] get_swap_device: Bad swap file entry 5c00000000000001 > [   24.412510] get_swap_device: Bad swap file entry 6000000000000001 > [   24.416519] get_swap_device: Bad swap file entry 6400000000000001 > [   24.420217] get_swap_device: Bad swap file entry 6800000000000001 > [   24.423921] get_swap_device: Bad swap file entry 6c00000000000001 > [   24.427685] get_swap_device: Bad swap file entry 7000000000000001 > [   24.760678] Kernel panic - not syncing: stack-protector: Kernel > stack is corrupted in: write_irq_affinity.isra.7+0xe5/0xf0 > [   24.760975] CPU: 25 PID: 1773 Comm: irqbalance Not tainted > 5.2.0-rc2-2fefea438dac #1 > [   24.760975] Hardware name: Microsoft Corporation Virtual > Machine/Virtual Machine, BIOS 090007  06/02/2017 > [   24.760975] Call Trace: > [   24.760975]  dump_stack+0x46/0x5b > [   24.760975]  panic+0xf8/0x2d2 > [   24.760975]  ? write_irq_affinity.isra.7+0xe5/0xf0 > [   24.760975]  __stack_chk_fail+0x15/0x20 > [   24.760975]  write_irq_affinity.isra.7+0xe5/0xf0 > [   24.760975]  proc_reg_write+0x40/0x60 > [   24.760975]  vfs_write+0xb3/0x1a0 > [   24.760975]  ? _cond_resched+0x16/0x40 > [   24.760975]  ksys_write+0x5c/0xe0 > [   24.760975]  do_syscall_64+0x4f/0x120 > [   24.760975]  entry_SYSCALL_64_after_hwframe+0x44/0xa9 > [   24.760975] RIP: 0033:0x7f93bcdde187 > [   24.760975] Code: c3 66 90 41 54 55 49 89 d4 53 48 89 f5 89 fb 48 > 83 ec 10 e8 6b 05 02 00 4c 89 e2 41 89 c0 48 89 ee 89 df b8 01 00 00 > 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 a4 05 02 > 00 48 > [   24.760975] RSP: 002b:00007ffc4600d900 EFLAGS: 00000293 ORIG_RAX: > 0000000000000001 > [   24.760975] RAX: ffffffffffffffda RBX: 0000000000000006 RCX: > 00007f93bcdde187 > [   24.760975] RDX: 0000000000000008 RSI: 00005595ad515540 RDI: > 0000000000000006 > [   24.760975] RBP: 00005595ad515540 R08: 0000000000000000 R09: > 00005595ab381820 > [   24.760975] R10: 0000000000000008 R11: 0000000000000293 R12: > 0000000000000008 > [   24.760975] R13: 0000000000000008 R14: 00007f93bd0b62a0 R15: > 00007f93bd0b5760 > [   24.760975] Kernel Offset: 0x3a000000 from 0xffffffff81000000 > (relocation range: 0xffffffff80000000-0xffffffffbfffffff) > [   24.760975] ---[ end Kernel panic - not syncing: stack-protector: > Kernel stack is corrupted in: write_irq_affinity.isra.7+0xe5/0xf0 ]--- Looks familiar, https://lore.kernel.org/lkml/1559242868.6132.35.camel@lca.pw/ I suppose Andrew might be better of reverting the whole series first before Yury came up with a right fix, so that other people who is testing linux-next don't need to waste time for the same problem.