Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4479253pxf; Tue, 23 Mar 2021 11:34:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzGIL2zeTN1AuQ9cfCcVIm+69sMzvUKakIX9Nzi233DcN3jdr6z/l/KEvrAdLdbMUigbxSR X-Received: by 2002:a17:907:7799:: with SMTP id ky25mr6176890ejc.217.1616524463563; Tue, 23 Mar 2021 11:34:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616524463; cv=none; d=google.com; s=arc-20160816; b=Btqew4WM/njjgaWEfam05VtDkhYx16jYUxOAzFsMpfPAgQ7kuWHHKlH0g5VroWhuiH D1h5CKe88JN4n5g0o9GCKCYNLqh6wm4oZJOkwA+W1qfFeZ4koZ7ZJ0Trh9rcKHe7y4Nt rAgX9cQb9vKokuT01jzWAaHBbVbAJV7TfbpofuQ+UISG3PnuIS7RgoY2+itc54wIk7Rh L/sFpiIhVjYvLHv5DFp0i0bo5elmD6wYoksesJuLAqeRCaKVTzLCrh0wMnA2KVZGTfBQ f3g9LaxS4NEIISqjSxjBnJ2geJEIZaQuLC3OeJB2XHPJ0W9UH2cUMCiREDSVBRed6EQI rrlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=jXChBXIXxhdUvzGFzzddaguDuBIoVDhURbdQGeFrnY4=; b=Er25h2iGYLJtTp5WlXOXi0B97Lc4s3RYU2uStNFJNDpn2cwPFZiNNwavVUA6iLFeXt xbqEIevqfWbWCFOC1UTIRflCuz/KpjpEB1u3t3WiivNayM1WpJhVLy5u/Qjqxh/vplu1 Cp4Rg3GLbXxrfYjvEabojog4TYfbA4SfWb+mrqzyYxfB7D8D8hUJZ5MYp2lU5OSOK3XO U/xSXjbyoBYd0aEtLAD0y4Zbbp92pAFTh9N6ng91rQw3VaLNnr04KaL45HpHZr6rXftp sJTErh8rPL1nO3/Ssqc4ZnFSjOUOfSdzydyi9teIYWv/4GrdRQN9yoi+J5rE0KUI/KQC zrAA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=MVgYvmj5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h16si14535461ede.206.2021.03.23.11.33.59; Tue, 23 Mar 2021 11:34:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=MVgYvmj5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232117AbhCWSdI (ORCPT + 99 others); Tue, 23 Mar 2021 14:33:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45576 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231751AbhCWScv (ORCPT ); Tue, 23 Mar 2021 14:32:51 -0400 Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E868CC061763 for ; Tue, 23 Mar 2021 11:32:49 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id a198so28105931lfd.7 for ; Tue, 23 Mar 2021 11:32:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shutemov-name.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=jXChBXIXxhdUvzGFzzddaguDuBIoVDhURbdQGeFrnY4=; b=MVgYvmj5QuP1gcNyUCyzsgLD/berF3yLFWC97uNHs6plKdE2srVEWxqLne65VIK6Zm sAhq18UNEMv8ne10BNARm9B5UOj9DIdmbI0Sa3DI1XKgyQNGlqcyz6dT7KsSX6P7cFdD YrpwE4JGfbMhIFIj9KBLVbvcMCYiTUglld8+knnKM811WJENeKXEt92dv+vRPvKlaRgM vFrVtJ/3BAgHd3YGpaQZxT7zfZ319DjCm/rTcRXyg0uD8WR+cAnf7lGHLZYcmWV97eUz /ByZm+55qPfBFyi/qr8uOU62ljSoK+KYfivT1Nvj6VNFayEoQoKVrd3RPZwsP9pqfhjB 10oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=jXChBXIXxhdUvzGFzzddaguDuBIoVDhURbdQGeFrnY4=; b=m+N/NMJl2xigsL7ml4/5ds9jrAFrm99SQhaf9tyQHFt8RTKLPs3fR5UOaMVG413Re7 S/veZ/fnd6Jw8UTJrLJoPFwmNIJWXnPZTrwslusmQdcS4RNWgpZ6YDm6lUa6wApSODVx lUETaI34RZvnf0k44hq0TF3Evhfz7ufB4ea6/a5iR8YoniajMGNVeLIhNQQU4Qj33CTO ftZ9bUU+PZqN6FgoSON8MBbFDkSReO7FFGLH2EEtrdjpruTcTtWYiUsn/0/vMdprsnGf VK6p3OHH0sd4XLp9DUOR1jHKRzelH0UOJjsB44rhpX86V+e70V7QN40GY+MMY+lMqu5M R7YA== X-Gm-Message-State: AOAM5300PU6cFiKWeUSfI63X5ZN+dsQR04d5PZ6WRE+H4bYxzBDeyTfI G+QhN9aZpfKdqvR/8efX6CGvmw== X-Received: by 2002:ac2:546b:: with SMTP id e11mr3209103lfn.48.1616524368240; Tue, 23 Mar 2021 11:32:48 -0700 (PDT) Received: from box.localdomain ([86.57.175.117]) by smtp.gmail.com with ESMTPSA id t13sm2431566ljk.47.2021.03.23.11.32.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Mar 2021 11:32:47 -0700 (PDT) Received: by box.localdomain (Postfix, from userid 1000) id 703DD101DEB; Tue, 23 Mar 2021 21:32:55 +0300 (+03) Date: Tue, 23 Mar 2021 21:32:55 +0300 From: "Kirill A. Shutemov" To: "Rafael J. Wysocki" Cc: "Kaneda, Erik" , Vegard Nossum , Vlastimil Babka , "Rafael J. Wysocki" , "Moore, Robert" , Kees Cook , Christoph Lameter , Andrew Morton , Marco Elver , Waiman Long , LKML , Linux MM , ACPI Devel Maling List , Len Brown , Steven Rostedt , Jan Kiszka Subject: Re: slub freelist issue / BUG: unable to handle page fault for address: 000000003ffe0018 Message-ID: <20210323183255.vot2rady3jjjl57f@box> References: <202006041054.874AA564@keescook> <34455dce-6675-1fc2-8d61-45bf56f3f554@suse.cz> <6b2b149e-c2bc-f87a-ea2c-3046c5e39bf9@oracle.com> <894e8cee-33df-1f63-fb12-72dceb024ea7@oracle.com> <874c4ec0-5c2a-da39-c4c0-83f781cba41d@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874c4ec0-5c2a-da39-c4c0-83f781cba41d@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 12, 2020 at 02:26:58PM +0200, Rafael J. Wysocki wrote: > On 6/11/2020 3:40 AM, Kaneda, Erik wrote: > > > > > -----Original Message----- > > > From: Vegard Nossum > > > Sent: Friday, June 5, 2020 7:45 AM > > > To: Vlastimil Babka ; Rafael J. Wysocki > > > ; Moore, Robert ; Kaneda, > > > Erik > > > Cc: Kees Cook ; Wysocki, Rafael J > > > ; Christoph Lameter ; Andrew > > > Morton ; Marco Elver ; > > > Waiman Long ; LKML > > kernel@vger.kernel.org>; Linux MM ; ACPI Devel > > > Maling List ; Len Brown ; > > > Steven Rostedt > > > Subject: Re: slub freelist issue / BUG: unable to handle page fault for > > > address: 000000003ffe0018 > > > > > > On 2020-06-05 16:08, Vlastimil Babka wrote: > > > > On 6/5/20 3:12 PM, Rafael J. Wysocki wrote: > > > > > On Fri, Jun 5, 2020 at 2:48 PM Vegard Nossum > > > wrote: > > > > > > On 2020-06-05 11:36, Vegard Nossum wrote: > > > > > > > On 2020-06-05 11:11, Vlastimil Babka wrote: > > > > > > > > On 6/4/20 8:46 PM, Vlastimil Babka wrote: > > > > > > > > > On 6/4/20 7:57 PM, Kees Cook wrote: > > > > > > > > > > On Thu, Jun 04, 2020 at 07:20:18PM +0200, Vegard Nossum wrote: > > > > > > > > > > > On 2020-06-04 19:18, Vlastimil Babka wrote: > > > > > > > > > > > > On 6/4/20 7:14 PM, Vegard Nossum wrote: > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > > > > > > > > > I ran into a boot problem with latest linus/master > > > > > > > > > > > > > (6929f71e46bdddbf1c4d67c2728648176c67c555) that manifests > > > like this: > > > > > > > > > > > > Hi, what's the .config you use? > > > > > > > > > > > Pretty much x86_64 defconfig minus a few options (PCI, USB, > > > > > > > > > > > ...) > > > > > > > > > > Oh yes indeed. I immediately crash in the same way with this config. > > > > > > > > > > I'll > > > > > > > > > > start digging... > > > > > > > > > > > > > > > > > > > > (defconfig finishes boot) > > > > > > > > > This is funny, booting with slub_debug=F results in: > > > > > > > > > I'm not sure if it's ACPI or ftrace wrong here, but looks like > > > > > > > > > the changed free pointer offset merely exposes a bug in something > > > > > > > > > else. > > > > > > > > So, with Kees' patch reverted, booting with slub_debug=F (or even > > > > > > > > more specific slub_debug=F,ftrace_event_field) also hits this bug > > > > > > > > below. I wanted to bisect it, but v5.7 was also bad, and also > > > > > > > > v5.6. Didn't try further in history. So it's not new at all, and > > > > > > > > likely very specific to your config+QEMU? (and related to the ACPI > > > > > > > > error messages that precede it?). > > > > > > > I see it too, but not on v5.0. I can bisect it. > > > > > > commit 67a72420a326b45514deb3f212085fb2cd1595b5 > > > > > > Author: Bob Moore > > > > > > Date: Fri Aug 16 14:43:21 2019 -0700 > > > > > > > > > > > > ACPICA: Increase total number of possible Owner IDs > > > > > > > > > > > > ACPICA commit 1f1652dad88b9d767767bc1f7eb4f7d99e6b5324 > > > > > > > > > > > > From 255 to 4095 possible IDs. > > > > > > > > > > > > Link: https://github.com/acpica/acpica/commit/1f1652da > > > > > > Reported-by: Hedi Berriche > > > > > > Signed-off-by: Bob Moore > > > > > > Signed-off-by: Erik Schmauss > > > > > > Signed-off-by: Rafael J. Wysocki > > > > > Bob, Erik, did we miss something in that patch? > > > > Maybe the patch just changes layout in a way that exposes the bug. > > > > > > > > Anyway the "ftrace_event_field" cache is not really involved, this is > > > > just because of slab merging. After adding "slub_nomerge" to > > > > "slub_debug=F", it starts making more sense, as the cache becomes > > > > Acpi-Namespace > > > > > > > > [ 0.140408] ------------[ cut here ]------------ > > > > [ 0.140837] cache_from_obj: Wrong slab cache. Acpi-Namespace but > > > object is from kmalloc-64 > > > > [ 0.141406] WARNING: CPU: 0 PID: 1 at mm/slab.h:524 > > > kmem_cache_free+0x1d3/0x250 > > > > [ 0.142105] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.7.0+ #45 > > > > [ 0.142393] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), > > > BIOS rel-1.13.0-0-gf21b5a4-rebuilt.opensuse.org 04/01/2014 > > > > [ 0.142393] RIP: 0010:kmem_cache_free+0x1d3/0x250 > > > > [ 0.142393] Code: 18 4d 85 ed 0f 84 10 ff ff ff 4c 39 ed 74 2f 49 8b 4d 58 48 > > > 8b 55 58 48 c7 c6 10 47 a1 ac 48 c7 c7 00 c2 b0 ac e8 b1 cc eb ff <0f> 0b 48 89 de > > > 4c 89 ef e8 10 d7 ff ff 48 8b 15 59 36 9b 00 4c 89 > > > > [ 0.142393] RSP: 0018:ffffb39cc0013dc0 EFLAGS: 00010282 > > > > [ 0.142393] RAX: 0000000000000000 RBX: ffff937287409e00 RCX: > > > 0000000000000000 > > > > [ 0.142393] RDX: 0000000000000001 RSI: 0000000000000092 RDI: > > > ffffffffacfdd32c > > > > [ 0.142393] RBP: ffff93728742ef00 R08: ffffb39cc0013c7d R09: > > > 00000000000000fc > > > > [ 0.142393] R10: ffffb39cc0013c78 R11: ffffb39cc0013c7d R12: > > > ffff937307409e00 > > > > [ 0.142393] R13: ffff937287401d00 R14: 0000000000000000 R15: > > > 0000000000000000 > > > > [ 0.142393] FS: 0000000000000000(0000) GS:ffff937287a00000(0000) > > > knlGS:0000000000000000 > > > > [ 0.142393] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > > > [ 0.142393] CR2: 0000000000000000 CR3: 0000000003a0a000 CR4: > > > 00000000003406f0 > > > > [ 0.142393] Call Trace: > > > > [ 0.142393] acpi_os_release_object+0x5/0x10 > > > > [ 0.142393] acpi_ns_delete_children+0x46/0x59 > > > > [ 0.142393] acpi_ns_delete_namespace_subtree+0x5c/0x79 > > > > [ 0.142393] ? acpi_sleep_proc_init+0x1f/0x1f > > > > [ 0.142393] acpi_ns_terminate+0xc/0x31 > > > > [ 0.142393] acpi_ut_subsystem_shutdown+0x45/0xa3 > > > > [ 0.142393] ? acpi_sleep_proc_init+0x1f/0x1f > > > > [ 0.142393] acpi_terminate+0x5/0xf > > > > [ 0.142393] acpi_init+0x27b/0x308 > > > > [ 0.142393] ? video_setup+0x79/0x79 > > > > [ 0.142393] do_one_initcall+0x7b/0x160 > > > > [ 0.142393] kernel_init_freeable+0x190/0x1f2 > > > > [ 0.142393] ? rest_init+0x9a/0x9a > > > > [ 0.142393] kernel_init+0x5/0xf6 > > > > [ 0.142393] ret_from_fork+0x22/0x30 > > > > [ 0.142393] ---[ end trace 3539f236ef812ba1 ]--- > > > > [ 0.142396] ------------[ cut here ]------------ > > > > > > > > I've also changed the warning so it's not printed just once, and also > > > > prints tracking info (see the hunk at the end of my mail, I'll turn this to a > > > proper patch later). > > > > With "slub_debug=FU slub_nomerge" there are now multiple warnings, > > > but they all look the same: > > > > [ 0.143815] ------------[ cut here ]------------ > > > > [ 0.144131] cache_from_obj: Wrong slab cache. Acpi-Namespace but > > > object is from kmalloc-64 > > > > [ 0.144929] WARNING: CPU: 0 PID: 1 at mm/slab.h:524 > > > kmem_cache_free+0x1d3/0x250 > > > > [ 0.145129] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.7.0+ #45 > > > > [ 0.145129] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), > > > BIOS rel-1.13.0-0-gf21b5a4-rebuilt.opensuse.org 04/01/2014 > > > > [ 0.145129] RIP: 0010:kmem_cache_free+0x1d3/0x250 > > > > [ 0.145129] Code: 18 4d 85 ed 0f 84 10 ff ff ff 4c 39 ed 74 2f 49 8b 4d 58 48 > > > 8b 55 58 48 c7 c6 10 47 c1 8d 48 c7 c7 00 c2 d0 8d e8 b1 cc eb ff <0f> 0b 48 89 de > > > 4c 89 ef e8 10 d7 ff ff 48 8b 15 59 36 9b 00 4c 89 > > > > [ 0.145129] RSP: 0018:ffff990b80013dc0 EFLAGS: 00010282 > > > > [ 0.145129] RAX: 0000000000000000 RBX: ffff972d474ada80 RCX: > > > 0000000000000000 > > > > [ 0.145129] RDX: 0000000000000001 RSI: 0000000000000092 RDI: > > > ffffffff8e1dd32c > > > > [ 0.145129] RBP: ffff972d47425680 R08: ffff990b80013c7d R09: > > > 00000000000000fc > > > > [ 0.145129] R10: ffff990b80013c78 R11: ffff990b80013c7d R12: > > > ffff972dc74ada80 > > > > [ 0.145129] R13: ffff972d474038c0 R14: 0000000000000000 R15: > > > 0000000000000000 > > > > [ 0.145129] FS: 0000000000000000(0000) GS:ffff972d47a00000(0000) > > > knlGS:0000000000000000 > > > > [ 0.145129] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > > > [ 0.145129] CR2: 0000000000000000 CR3: 000000000660a000 CR4: > > > 00000000003406f0 > > > > [ 0.145129] Call Trace: > > > > [ 0.145129] acpi_os_release_object+0x5/0x10 > > > > [ 0.145129] acpi_ns_delete_children+0x46/0x59 > > > > [ 0.145129] acpi_ns_delete_namespace_subtree+0x5c/0x79 > > > > [ 0.145129] ? acpi_sleep_proc_init+0x1f/0x1f > > > > [ 0.145129] acpi_ns_terminate+0xc/0x31 > > > > [ 0.145129] acpi_ut_subsystem_shutdown+0x45/0xa3 > > > > [ 0.145129] ? acpi_sleep_proc_init+0x1f/0x1f > > > > [ 0.145129] acpi_terminate+0x5/0xf > > > > [ 0.145129] acpi_init+0x27b/0x308 > > > > [ 0.145129] ? video_setup+0x79/0x79 > > > > [ 0.145129] do_one_initcall+0x7b/0x160 > > > > [ 0.145129] kernel_init_freeable+0x190/0x1f2 > > > > [ 0.145129] ? rest_init+0x9a/0x9a > > > > [ 0.145129] kernel_init+0x5/0xf6 > > > > [ 0.145129] ret_from_fork+0x22/0x30 > > > > [ 0.145129] ---[ end trace 574554fca7bd06bb ]--- > > > > [ 0.145133] INFO: Allocated in acpi_ns_root_initialize+0xb6/0x2d1 age=58 > > > cpu=0 pid=0 > > > > [ 0.145881] kmem_cache_alloc_trace+0x1a9/0x1c0 > > > > [ 0.146132] acpi_ns_root_initialize+0xb6/0x2d1 > > > > [ 0.146578] acpi_initialize_subsystem+0x65/0xa8 > > > > [ 0.147024] acpi_early_init+0x5d/0xd1 > > > > [ 0.147132] start_kernel+0x45b/0x518 > > > > [ 0.147491] secondary_startup_64+0xb6/0xc0 > > > > [ 0.147897] ------------[ cut here ]------------ > > > > > > > > And it seems ACPI is allocating an object via kmalloc() and then > > > > freeing it via kmem_cache_free(<"Acpi-Namespace" kmem_cache>) which > > > is wrong. > > > > > ./scripts/faddr2line vmlinux 'acpi_ns_root_initialize+0xb6' > > > > acpi_ns_root_initialize+0xb6/0x2d1: > > > > kmalloc at include/linux/slab.h:555 > > > > (inlined by) kzalloc at include/linux/slab.h:669 (inlined by) > > > > acpi_os_allocate_zeroed at include/acpi/platform/aclinuxex.h:57 > > > > (inlined by) acpi_ns_root_initialize at > > > > drivers/acpi/acpica/nsaccess.c:102 > > > > > > Hi Vegard, > > > > > That's it :-) This fixes it for me: > > We'll take this patch for ACPICA and it will be in the next release. > > > > Rafael, do you want to take this as a part of the next rc? > > Yes, I do. Folks, what happened to the patch? I don't see it in current upstream. Looks like it got reported again: https://lore.kernel.org/r/a1461e21-c744-767d-6dfc-6641fd3e3ce2@siemens.com -- Kirill A. Shutemov