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 7911CC32771 for ; Wed, 28 Sep 2022 07:21:59 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 063258E012C; Wed, 28 Sep 2022 03:21:59 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id F2E2D8E0120; Wed, 28 Sep 2022 03:21:58 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DCEAF8E012C; Wed, 28 Sep 2022 03:21:58 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id C76428E0120 for ; Wed, 28 Sep 2022 03:21:58 -0400 (EDT) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 9000C140294 for ; Wed, 28 Sep 2022 07:21:58 +0000 (UTC) X-FDA: 79960649916.10.5E94E6F Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by imf15.hostedemail.com (Postfix) with ESMTP id 1A7F6A000F for ; Wed, 28 Sep 2022 07:21:54 +0000 (UTC) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1odROD-0004Rq-FL; Wed, 28 Sep 2022 09:21:53 +0200 Message-ID: Date: Wed, 28 Sep 2022 09:21:52 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: [sparc64] fails to boot, (was: Re: [PATCH memcg v6] net: set proper memcg for net_init hooks allocations) #forregzbot Content-Language: en-US, de-DE To: "regressions@lists.linux.dev" Cc: kernel@openvz.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, sparclinux@vger.kernel.org References: <6b362c6e-9c80-4344-9430-b831f9871a3c@openvz.org> <20220918092849.GA10314@u164.east.ru> From: Thorsten Leemhuis In-Reply-To: <20220918092849.GA10314@u164.east.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1664349715;a338ba5b; X-HE-SMSGID: 1odROD-0004Rq-FL ARC-Authentication-Results: i=1; imf15.hostedemail.com; dkim=none; spf=pass (imf15.hostedemail.com: domain of regressions@leemhuis.info designates 80.237.130.52 as permitted sender) smtp.mailfrom=regressions@leemhuis.info; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664349718; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9OcEGjMlcl1EwVCKdIDEc5Jd8SEXXw4QW/LgP55b/bQ=; b=1SnFIIInSOOt0A6UDHMB2Uxewa65fFeGcvs44ZWmlDu/koiAc4YKMbGfhxmjkfOxtSHxQ6 zxTMyyDODSXvheHQ7FQWtx9V5Jsrf5nI3YXLp0CVMrRi3hlPWmiIk9YrojJ37z8jlOcXiH iyZ2MWGZ8WX9jffZAd8asrketmC4H20= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664349718; a=rsa-sha256; cv=none; b=yd+y1xnsyLX80m3ab1f34PyZ1KYH2QwF8P/pByBBPVgZ+vBratUY7oaJq0U/pUP7yz6DQa neIKqESbtA/SRgzKilpX30cDoaLsxdfjvZ5vvq1BMX4RrfMO+9gDWqhaLI36GYBESCSfO2 SJA5FcezIaOANUrHqvj2Pl1kFvYG9FY= X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 1A7F6A000F X-Stat-Signature: e53gxbscp5367rnzq3s9yh16fhtjyy1h Authentication-Results: imf15.hostedemail.com; dkim=none; spf=pass (imf15.hostedemail.com: domain of regressions@leemhuis.info designates 80.237.130.52 as permitted sender) smtp.mailfrom=regressions@leemhuis.info; dmarc=none X-Rspam-User: X-HE-Tag: 1664349714-186118 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: TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. [TLDR: I'm adding this regression report to the list of tracked regressions; all text from me you find below is based on a few templates paragraphs you might have encountered already already in similar form.] Hi, this is your Linux kernel regression tracker. On 18.09.22 11:28, Anatoly Pugachev wrote: > On Fri, Jun 03, 2022 at 07:19:43AM +0300, Vasily Averin wrote: >> __register_pernet_operations() executes init hook of registered >> pernet_operation structure in all existing net namespaces. >> >> Typically, these hooks are called by a process associated with >> the specified net namespace, and all __GFP_ACCOUNT marked >> allocation are accounted for corresponding container/memcg. >> >> However __register_pernet_operations() calls the hooks in the same >> context, and as a result all marked allocations are accounted >> to one memcg for all processed net namespaces. >> >> This patch adjusts active memcg for each net namespace and helps >> to account memory allocated inside ops_init() into the proper memcg. >> >> Signed-off-by: Vasily Averin >> Acked-by: Roman Gushchin >> Acked-by: Shakeel Butt >> --- >> v6: re-based to current upstream (v5.18-11267-gb00ed48bb0a7) > > > Hello! > > I'm unable to boot my sparc64 VM anymore (5.19 still boots, 6.0-rc1 does not), > bisected up to this patch, > > mator@ttip:~/linux-2.6$ git bisect bad > 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 is the first bad commit > commit 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 > Author: Vasily Averin > Date: Fri Jun 3 07:19:43 2022 +0300 Thanks for the report. To be sure below issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot: #regzbot ^introduced 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 #regzbot title cgroups/sparc64: sparc64 fails to boot #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply -- ideally with also telling regzbot about it, as explained here: https://linux-regtracking.leemhuis.info/tracked-regression/ Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report (the mail this one replies to), as explained for in the Linux kernel's documentation; above webpage explains why this is important for tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.