From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29277C433FE for ; Thu, 6 Oct 2022 15:35:56 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BCEC96B0072; Thu, 6 Oct 2022 11:35:55 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B7FD58E0002; Thu, 6 Oct 2022 11:35:55 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A46B18E0001; Thu, 6 Oct 2022 11:35:55 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 905C56B0072 for ; Thu, 6 Oct 2022 11:35:55 -0400 (EDT) Received: from smtpin14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 6B04AA02F3 for ; Thu, 6 Oct 2022 15:35:55 +0000 (UTC) X-FDA: 79990925070.14.5E39261 Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) by imf28.hostedemail.com (Postfix) with ESMTP id D1656C001A for ; Thu, 6 Oct 2022 15:35:54 +0000 (UTC) Received: by mail-lj1-f180.google.com with SMTP id by36so2666591ljb.4 for ; Thu, 06 Oct 2022 08:35:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:date:from:from:to:cc:subject:date:message-id:reply-to; bh=6CuEgzY/EsQIVYA7F7bbwn+/BSxzEsOn8OyorR31d+4=; b=HRnOx16IgwIuDntVMbjSo9+7lRRVgMz63uXeAlZO8kZrAT5mEOfNWGcc6iwrAWNMlo ysRnB8V64/BxKU/Ome4OwiDkljXhbOZKVavhGxRJkTRhIb7uwja66NQKsgqCzPkCpTsd KRQt2hhPzHFEfSaEaYORECV7wRqjqfFAao/ZtvBqbUrweoV+w3+XJaTv47z8a07BiKDR nuzTuNdW41gVAwmiVb4HmQCvHeyj+vQb7KEe8NLHUoSqmlED0BGSb5Ut00UPoAfH72jx Of4JmcZZU4gOHYhBdq8YrZxeqiU+tsEFvbDKol6N1wj1rDcHKxu2Hqal/h2KrW6Iizh4 LMrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:date:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=6CuEgzY/EsQIVYA7F7bbwn+/BSxzEsOn8OyorR31d+4=; b=SrHuvWw6VOD18ZxFxYmoDP3/qJGZmQAuLW3TAq1CP7qFxob8EAl+18oM9cOEWhyE0J Dg83dYfeuQ7oYZraNjAr4mRDxFQTt+ywj8mUaIVOzJlUWRr4LGSDiPQAnSkJJ+9n23Rh qxFldcIHaFJWQm67Ak1V6D0sUEUoJosyuUYDnYIkGOXO1uc/RWN8F1SkW1+JqTUgb2eL vAq4rUu2GP7FQwnt7a80wLmqUnRtBd6H2dPHWiwFXinD6reuGTRxWvKuSDdMqg5fI3yd QSBCDrT4bl4fJ7xlI7aLOs3n/AzIuv9i3B2RXbWe5komsCZ/up0Hi5QpFarZWVS408Wt 2gaw== X-Gm-Message-State: ACrzQf0MH9HcDZ095vOGCx0/bU173T4Culzw2nwFt7DGxFhbfekTtuxn vg2A676R42G1jzs7SIoGmI8= X-Google-Smtp-Source: AMsMyM6q4HfJP+PvF2XwQM1hAF9r7D41giXjEevmtMvTuP39/zbMs61ism3wOi0gzhxZz57xzTE27w== X-Received: by 2002:a05:651c:17a1:b0:26c:87c:c104 with SMTP id bn33-20020a05651c17a100b0026c087cc104mr74977ljb.419.1665070553064; Thu, 06 Oct 2022 08:35:53 -0700 (PDT) Received: from pc636 (host-90-235-28-254.mobileonline.telia.com. [90.235.28.254]) by smtp.gmail.com with ESMTPSA id o20-20020a056512231400b004979ec19380sm2717433lfu.285.2022.10.06.08.35.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Oct 2022 08:35:52 -0700 (PDT) From: Uladzislau Rezki X-Google-Original-From: Uladzislau Rezki Date: Thu, 6 Oct 2022 17:35:49 +0200 To: David Hildenbrand Cc: Alexander Potapenko , "Uladzislau Rezki (Sony)" , Andrey Konovalov , "linux-mm@kvack.org" , Andrey Ryabinin , Dmitry Vyukov , Vincenzo Frascino , kasan-dev@googlegroups.com Subject: Re: KASAN-related VMAP allocation errors in debug kernels with many logical CPUS Message-ID: References: <8aaaeec8-14a1-cdc4-4c77-4878f4979f3e@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8aaaeec8-14a1-cdc4-4c77-4878f4979f3e@redhat.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1665070554; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=6CuEgzY/EsQIVYA7F7bbwn+/BSxzEsOn8OyorR31d+4=; b=pSUV/TMcpG58EH61EaTVmzw1w1UBUK77FV9RcV+v3aoiAAxn5ZRuFT18hvlk45FTqVR7Iu eGgZ4/XDWRxuTOzoB1GOqnctsaiW2pdf5a6EPoYKm/yBICWP2Sp2LzaC5uXymWIoZSKn87 Y70nRjMqSR2OqNJfUtnw1vF0wtmRjpo= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=HRnOx16I; spf=pass (imf28.hostedemail.com: domain of urezki@gmail.com designates 209.85.208.180 as permitted sender) smtp.mailfrom=urezki@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1665070555; a=rsa-sha256; cv=none; b=mBBTcHlFnAh5+4ILt7/YaBYCxjTW3hSafy3NDZQwR3W080xohyg5dxWv1df2JPaeEy/PJf VJuxvBm3vJXRFU76xx2wdz+5qR3H08263xkssRoFlSGHkWbQ8fGfqziuBumjDCNTbTgBuk U+ygPlrpyGzSjZW+N36r13cRHMOfF4U= X-Rspam-User: Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=HRnOx16I; spf=pass (imf28.hostedemail.com: domain of urezki@gmail.com designates 209.85.208.180 as permitted sender) smtp.mailfrom=urezki@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Stat-Signature: 9mitqg4b8uu5twqigdeg5d83t7986weh X-Rspamd-Queue-Id: D1656C001A X-Rspamd-Server: rspam02 X-HE-Tag: 1665070554-960936 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: > Hi, > > we're currently hitting a weird vmap issue in debug kernels with KASAN enabled > on fairly large VMs. I reproduced it on v5.19 (did not get the chance to > try 6.0 yet because I don't have access to the machine right now, but > I suspect it persists). > > It seems to trigger when udev probes a massive amount of devices in parallel > while the system is booting up. Once the system booted, I no longer see any > such issues. > > > [ 165.818200] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.836622] vmap allocation for size 315392 failed: use vmalloc= to increase size > [ 165.837461] vmap allocation for size 315392 failed: use vmalloc= to increase size > [ 165.840573] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.841059] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.841428] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.841819] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.842123] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.843359] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.844894] vmap allocation for size 2498560 failed: use vmalloc= to increase size > [ 165.847028] CPU: 253 PID: 4995 Comm: systemd-udevd Not tainted 5.19.0 #2 > [ 165.935689] Hardware name: Lenovo ThinkSystem SR950 -[7X12ABC1WW]-/-[7X12ABC1WW]-, BIOS -[PSE130O-1.81]- 05/20/2020 > [ 165.947343] Call Trace: > [ 165.950075] > [ 165.952425] dump_stack_lvl+0x57/0x81 > [ 165.956532] warn_alloc.cold+0x95/0x18a > [ 165.960836] ? zone_watermark_ok_safe+0x240/0x240 > [ 165.966100] ? slab_free_freelist_hook+0x11d/0x1d0 > [ 165.971461] ? __get_vm_area_node+0x2af/0x360 > [ 165.976341] ? __get_vm_area_node+0x2af/0x360 > [ 165.981219] __vmalloc_node_range+0x291/0x560 > [ 165.986087] ? __mutex_unlock_slowpath+0x161/0x5e0 > [ 165.991447] ? move_module+0x4c/0x630 > [ 165.995547] ? vfree_atomic+0xa0/0xa0 > [ 165.999647] ? move_module+0x4c/0x630 > [ 166.003741] module_alloc+0xe7/0x170 > [ 166.007747] ? move_module+0x4c/0x630 > [ 166.011840] move_module+0x4c/0x630 > [ 166.015751] layout_and_allocate+0x32c/0x560 > [ 166.020519] load_module+0x8e0/0x25c0 > Can it be that we do not have enough "module section" size? I mean the section size, which is MODULES_END - MODULES_VADDR is rather small so some modules are not loaded due to no space. CONFIG_RANDOMIZE_BASE also creates some offset overhead if enabled on your box. But it looks it is rather negligible. Maybe try to increase the module-section size to see if it solves the problem. -- Uladzislau Rezki