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 46ED9C433FE for ; Sat, 1 Oct 2022 17:18:50 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 613566B0072; Sat, 1 Oct 2022 13:18:49 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 59C088D0001; Sat, 1 Oct 2022 13:18:49 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 415246B0074; Sat, 1 Oct 2022 13:18:49 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 2F0E36B0072 for ; Sat, 1 Oct 2022 13:18:49 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id E73D18013C for ; Sat, 1 Oct 2022 17:18:48 +0000 (UTC) X-FDA: 79973040336.20.FB334B6 Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) by imf21.hostedemail.com (Postfix) with ESMTP id A01711C000B for ; Sat, 1 Oct 2022 17:18:48 +0000 (UTC) Received: by mail-oi1-f175.google.com with SMTP id j188so7802228oih.0 for ; Sat, 01 Oct 2022 10:18:48 -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; bh=cLZiX1CfDD5wzZRlKNg0VPwntEHdFJ/mrgmQeQb80LI=; b=EiRWLni/58H42zoaCGTwEWGrnFt/bNWBVE5wyVaP06m9KR6FMFjL7Mezf9o6YLyu/Y abVA2gXnc7MLs0DvN3ILTaGsPH6Q4VNMSQLKKv04uUkOT/4UT4dRGVcwtJMTFmlvTKF7 CotWpWcOz0BdhP9FFtLm1ALNCbkmERopFu1GPuMBY34gCeN3/NiqAPAqlgDB38KjgFMM H8hrWXeZWebryZ/y5wE00t1zMIn501iDlAl2QearaRl6mc+08RU8j4/z6SC38Ss1kg5P viNSr+inccRYaR43U5io9Ana17m+sWoDW3+elZ4PCxw4jIpAkL4wJ+Yixbwql73LmdyV a0Yw== 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; bh=cLZiX1CfDD5wzZRlKNg0VPwntEHdFJ/mrgmQeQb80LI=; b=A84Noj4jYi2ct9euEwamB2YdgjyMUA+Va+xMhGyMT0Gylp0L2qeWlQjtgjasyjHU1k tvgu0dgdNxVBQqJMhq9FBfiAZVc5dm4WIkwakD+vu5w3E6509feiLp9nkiunk0Dgx5CN Ilsc44RDT/SCd7Jry9u/awUdwMmwC9wFsqh95p+CKg657qYpOiWFb36vJjNP7onPYQnq zN7fCRjhqlYEqwrrwes72awGhD371G+da506+MBiT5j+YAD3O0/visZb0pMiIVyz46io em5ywJ4A4+ysCbz6Rst/WG+R8VFQKUyTnUgbjrJ6cyrnQxW2JLVMzf2L93Ct6nTu8wRM /+cQ== X-Gm-Message-State: ACrzQf3etTHyRxEprI7FYSvCGPQuQ/AKvF8lPywMv4KRVJSRuo2dFzHQ ub0KrcRzxyIr85b/h6ueoijSlCMrsVY= X-Google-Smtp-Source: AMsMyM6S5fsQk1JAa+ow3vXjxkGR+bZDns6dmDrsWnOfMBy1YIB4yOSCVuOQXU9JvqTvo5rjuKvLNg== X-Received: by 2002:a05:6808:1a14:b0:350:1965:8b5 with SMTP id bk20-20020a0568081a1400b00350196508b5mr1333174oib.85.1664644727738; Sat, 01 Oct 2022 10:18:47 -0700 (PDT) Received: from localhost ([12.97.180.36]) by smtp.gmail.com with ESMTPSA id t15-20020a056870e74f00b0011f00b027bdsm1551169oak.45.2022.10.01.10.18.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 01 Oct 2022 10:18:47 -0700 (PDT) Date: Sat, 1 Oct 2022 10:16:36 -0700 From: Yury Norov To: Linus Torvalds Cc: 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: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664644728; 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=cLZiX1CfDD5wzZRlKNg0VPwntEHdFJ/mrgmQeQb80LI=; b=f2P/HRp9bGOnL5Ax2Qv1g1FeQBkF+jZDFOvzdQqfE+oae88VoaodA85aCTAXrwMMNnLrOf ycgQyF98bMzWxem37qVeuDrtO6JF7eR8WhmWCqALsJW/7lAUGIFLkctfRVWEX6ypznTpWl +vhpd3gdBS0EVe9WYXq3JEbdwXnssJ0= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b="EiRWLni/"; spf=pass (imf21.hostedemail.com: domain of yury.norov@gmail.com designates 209.85.167.175 as permitted sender) smtp.mailfrom=yury.norov@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664644728; a=rsa-sha256; cv=none; b=D1zN649XoVpyq8VPPgwM9dsCrmKhyfYa+O2VHlOk5SNzkxE0ItzaYf0qwJTkgw6FNku5dC gB1gSmeE2qpcTW2NiGbpcwBRv9Y89lmuYMYr1lcxgPmVye1xC9js3CdoGInmvvR3Lv1bpr A8s2wTP3hy//UEmel3u/oc12jt/R7Ck= X-Rspam-User: X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: A01711C000B Authentication-Results: imf21.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b="EiRWLni/"; spf=pass (imf21.hostedemail.com: domain of yury.norov@gmail.com designates 209.85.167.175 as permitted sender) smtp.mailfrom=yury.norov@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Stat-Signature: 4pg1kujxj4b1tyd5s3m58c3p6j6yux4e X-HE-Tag: 1664644728-262000 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 Sat, Oct 01, 2022 at 09:20:53AM -0700, Linus Torvalds wrote: > On Fri, Sep 30, 2022 at 6:51 PM Yury Norov wrote: > > > > The commit b9a7ecc71fe582e ("cpumask: fix checking valid cpu range") > > fixes broken cpumask_check(), which for now doesn't warn user when it > > should. After the fix, I observed many false-positive warnings which > > were addressed in the following patches. > > Are all the false positives fixed? I build-tested on x86_64 and arm64. All fixed except for those generated by cpumask_next_wrap(). And I'm not even sure they are false positives. This is what I'm working on right now. Hope moving it in next merge window. > I suspect that to avoid any automation noise, you should just rebase > so that the fixes come first. Otherwise we'll end up wasting a lot of > time on the noise. > > This is not that different from introducing new buil;d-time warnings: > the things they point out need to be fixed before the warning can be > integrated, or it causes bisection problems. OK, I'll reorder the patches. Thanks for your help.