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 E2E0EC433F5 for ; Tue, 12 Apr 2022 17:31:02 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6078B6B0072; Tue, 12 Apr 2022 13:31:02 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5B6156B0073; Tue, 12 Apr 2022 13:31:02 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4A5306B0074; Tue, 12 Apr 2022 13:31:02 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 3B4AB6B0072 for ; Tue, 12 Apr 2022 13:31:02 -0400 (EDT) Received: from smtpin13.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 19A526222D for ; Tue, 12 Apr 2022 17:31:02 +0000 (UTC) X-FDA: 79348917564.13.22AA7E3 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf29.hostedemail.com (Postfix) with ESMTP id 9868D120007 for ; Tue, 12 Apr 2022 17:31:01 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D24ED619F1; Tue, 12 Apr 2022 17:31:00 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BB52EC385A5; Tue, 12 Apr 2022 17:30:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1649784660; bh=Mvmfe8DoFFgIAg2F5ziwb8TSiIedoMypZAvScsFewFU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wjIp8//vAM3sAUmdS8O5w/1W6BzyxGis2Mgp9rXhiCSZeDUHH3FYM3Yn2h3V4carz CFE8iOt4p1OG/sEF9DL/J1m4Lca2uzd5uBcyiGMqVGtky3iHduK2kdoSoHrCHzpk0/ HyqgLKU1UuwlVEeMsYW5ToATB6PO1Y1EFqhCmz5U= Date: Tue, 12 Apr 2022 19:30:57 +0200 From: Greg Kroah-Hartman To: Naresh Kamboju Cc: Marco Elver , linux-kernel@vger.kernel.org, stable@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, slade@sladewatkins.com, Alexander Potapenko , Dmitry Vyukov , kasan-dev , linux-mm Subject: Re: [PATCH 5.15 000/277] 5.15.34-rc1 review Message-ID: References: <20220412062942.022903016@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: nt1grjqisy3gn1kazhtwrxnbdc3msbuo Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=linuxfoundation.org header.s=korg header.b="wjIp8//v"; dmarc=pass (policy=none) header.from=linuxfoundation.org; spf=pass (imf29.hostedemail.com: domain of gregkh@linuxfoundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: 9868D120007 X-HE-Tag: 1649784661-622326 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: On Tue, Apr 12, 2022 at 07:23:10PM +0200, Greg Kroah-Hartman wrote: > On Tue, Apr 12, 2022 at 06:43:15PM +0200, Greg Kroah-Hartman wrote: > > On Tue, Apr 12, 2022 at 09:13:59PM +0530, Naresh Kamboju wrote: > > > Hi Marco > > > > > > On Tue, 12 Apr 2022 at 20:32, Marco Elver wrote: > > > > > > > > On Tue, 12 Apr 2022 at 16:16, Naresh Kamboju wrote: > > > > > > > > > > On Tue, 12 Apr 2022 at 12:11, Greg Kroah-Hartman > > > > > wrote: > > > > > > > > > > > > This is the start of the stable review cycle for the 5.15.34 release. > > > > > > There are 277 patches in this series, all will be posted as a response > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > let me know. > > > > > > > > > > > > Responses should be made by Thu, 14 Apr 2022 06:28:59 +0000. > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > The whole patch series can be found in one patch at: > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.34-rc1.gz > > > > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y > > > > > > and the diffstat can be found below. > > > > > > > > > > > > thanks, > > > > > > > > > > > > greg k-h > > > > > > > > > > > > > > > On linux stable-rc 5.15 x86 and i386 builds failed due to below error [1] > > > > > with config [2]. > > > > > > > > > > The finding is when kunit config is enabled the builds pass. > > > > > CONFIG_KUNIT=y > > > > > > > > > > But with CONFIG_KUNIT not set the builds failed. > > > > > > > > > > x86_64-linux-gnu-ld: mm/kfence/core.o: in function `__kfence_alloc': > > > > > core.c:(.text+0x901): undefined reference to `filter_irq_stacks' > > > > > make[1]: *** [/builds/linux/Makefile:1183: vmlinux] Error 1 > > > > > > > > > > Reported-by: Linux Kernel Functional Testing > > > > > > > > > > I see these three commits, I will bisect and get back to you > > > > > > > > > > 2f222c87ceb4 kfence: limit currently covered allocations when pool nearly full > > > > > e25487912879 kfence: move saving stack trace of allocations into > > > > > __kfence_alloc() > > > > > d99355395380 kfence: count unexpectedly skipped allocations > > > > > > > > My guess is that this commit is missing: > > > > > > This patch is missing Fixes: tag. > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f39f21b3ddc7fc0f87eb6dc75ddc81b5bbfb7672 > > > > > > For your information, I have reverted the below commit and build pass. > > > > > > kfence: limit currently covered allocations when pool nearly full > > > > > > [ Upstream commit 08f6b10630f284755087f58aa393402e15b92977 ] > > > > I've added the above commit, does that fix the issue? > > > > Hm, I can test that here, let me try it... > > I can't duplicate the failure here with my config, let me try yours... Yes, with your config before it fails, after I added the commit it works. I'll push out a -rc2 soon with that added. thanks, greg k-h