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 13A33C433F5 for ; Tue, 11 Oct 2022 17:23:30 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9CD9B6B0071; Tue, 11 Oct 2022 13:23:29 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 97D2E6B0073; Tue, 11 Oct 2022 13:23:29 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7F7406B0074; Tue, 11 Oct 2022 13:23:29 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 6D2D36B0071 for ; Tue, 11 Oct 2022 13:23:29 -0400 (EDT) Received: from smtpin26.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 4645BA025B for ; Tue, 11 Oct 2022 17:23:29 +0000 (UTC) X-FDA: 80009340138.26.08EAB48 Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) by imf01.hostedemail.com (Postfix) with ESMTP id EF5BE4003B for ; Tue, 11 Oct 2022 17:23:28 +0000 (UTC) Received: by mail-qv1-f45.google.com with SMTP id y10so1808791qvo.11 for ; Tue, 11 Oct 2022 10:23:28 -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:from:date:from:to:cc:subject:date:message-id:reply-to; bh=a5c3GaIFAJ3ThsYjOgMQ5PeBEv2Rk81PZ4kNMxgrIlU=; b=Kyyhsa2weHle/mcPVTK5CBy7ViWi8hcWuFfiu/1wZ0PcwWoe5PwlsAbnemKHmmEBUm LuM4gsL9XFq/0pJdQfqTNkW7urhYhalmt0ueqhuU1Gb4Epm8mmt0ehBu/DqHDxDwxDRu CTPyuam97iJIEd4xenjQ6SHOTbPcolJM9PU9UR+2T0uoSqQq9Qb44qS7oYijkGqlk3Wd 6Wfg3+A9GMffeZb5gLmKogn/ecGQEZTRty9bS1wQOoxK51pYe8Bui41ximTBL5HhWoHQ r8SSFAg6NBBpY3QHlud+2kJToh2VemI0MsMEoEg39zwk/T553WH+v9HkUqiwenWrQmiT VKNQ== 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:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=a5c3GaIFAJ3ThsYjOgMQ5PeBEv2Rk81PZ4kNMxgrIlU=; b=HxshXKC1JBvJSa9Q+k1NnwGBmtxAJg93rt5aseHPW/B4za+/w9Av7USTMM5f17ToDJ CmTcsXHd24h7qHcvC+T+BImGT5j4jjGUcE8dUc3lCp6bDwrjy7VMmEbm5lU3nz52Q81s PZAknY3AR4+2w5bEA8ofe/hWsbijTlvL26+Q5PnSN8VkSUGioB8kTzl2elyVdH1NRTZx pDeqeyl2tfilU9W8z5gJdH5pd3NGzJvFRorUd3ybbVNOq8D4rlimLitimGYRRt8e0pBG 8oo6yeYrOAt1uiv0bTHg7GB3wYHUm5R87bUmmTh87VQA3ODQhaz4uY1Fu2REkf9t1QUP AaCg== X-Gm-Message-State: ACrzQf1kLrCRkGzvBOKMyfZg6QBeyGK1CwbLCmVSJnsUwpf78udqgrTj +uOhrJ11TZVFlJ1S4PgTm08= X-Google-Smtp-Source: AMsMyM4FKyle0DhP/MvxKNqJiW9g+ccx1kXt2IX5Ng7IZkRFEtEGJ/1KGdmL9xPtdXPU9FXJYQEouA== X-Received: by 2002:a0c:a90d:0:b0:4b3:f322:1280 with SMTP id y13-20020a0ca90d000000b004b3f3221280mr11185401qva.83.1665509008068; Tue, 11 Oct 2022 10:23:28 -0700 (PDT) Received: from localhost ([2601:4c1:c100:2270:6051:2739:340:f252]) by smtp.gmail.com with ESMTPSA id fd6-20020a05622a4d0600b00342f8984348sm10495156qtb.87.2022.10.11.10.23.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Oct 2022 10:23:27 -0700 (PDT) Date: Tue, 11 Oct 2022 10:23:27 -0700 From: Yury Norov To: Andrew Jones Cc: Linus Torvalds , lkp@lists.01.org, lkp@intel.com, Linux Memory Management List , linux-kernel@vger.kernel.org Subject: Re: [oliver.sang@intel.com: [cpumask] b9a7ecc71f: WARNING:at_include/linux/cpumask.h:#__is_kernel_percpu_address] Message-ID: References: <20221011170949.upxk3tcfcwnkytwm@kamzik> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1665509009; a=rsa-sha256; cv=none; b=jmEMZGX05jmP5Fs4vrZAy55CFn81ccoEC8FvVDOr77earIJ3l2Kldb2KgupDjB4ZTTVTEb ei/cZ1igyW5PkZIJyrz4mnBF74G8lD33ZQ/uN2ZMxAyovrWi9JY6V76F9CItfJwpbC/BR1 DoqqAH8tLNQz5bj4XsMXn40JQwj+O8k= ARC-Authentication-Results: i=1; imf01.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Kyyhsa2w; spf=pass (imf01.hostedemail.com: domain of yury.norov@gmail.com designates 209.85.219.45 as permitted sender) smtp.mailfrom=yury.norov@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1665509009; 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=a5c3GaIFAJ3ThsYjOgMQ5PeBEv2Rk81PZ4kNMxgrIlU=; b=5ZW7+Cc2ZeQkHvgP1dbCmj0mmSrZM4wkuNskVVR/azB+F+6/Uwumhswa2xr2Tmlc+H0CCn OwMxgOW6eW6gKXt3zHYOQmQs4HVXz3wnd//GTiViCvZZgDULod4+Z4J0DhvDQl86VfHHxF /FINSFA+Gucjg/mYSDqrsRqVABhD8/M= X-Stat-Signature: 7q1efeuetff1wjw8r7r4gtkqz3pd7fsy X-Rspamd-Queue-Id: EF5BE4003B X-Rspam-User: X-Rspamd-Server: rspam08 Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Kyyhsa2w; spf=pass (imf01.hostedemail.com: domain of yury.norov@gmail.com designates 209.85.219.45 as permitted sender) smtp.mailfrom=yury.norov@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-HE-Tag: 1665509008-134315 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, Oct 11, 2022 at 10:16:03AM -0700, Yury Norov wrote: > > Hi Yury, > > > > I just wanted to report that the warning fires when doing > > 'cat /proc/cpuinfo' on at least x86 and riscv. I don't think > > those are false positives. I'm guessing a patch should be > > something like the following diff. If you haven't already > > addressed this and I'm not off in left field, then I guess > > we should integrate it into your series. > > > > Thanks, > > drew > > Hi Andrew, > > Can you please send it as a patch with a description? Also, can you describe why we'd silence the warning this way? If the cpu number greater than nr_cpu_ids comes from upper layer, we quite probably should investigate what happens there... Thanks, Yury