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 12461C433EF for ; Mon, 6 Dec 2021 17:44:09 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9EFAD6B0071; Mon, 6 Dec 2021 12:43:58 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 99F2F6B0072; Mon, 6 Dec 2021 12:43:58 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 866936B007E; Mon, 6 Dec 2021 12:43:58 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0132.hostedemail.com [216.40.44.132]) by kanga.kvack.org (Postfix) with ESMTP id 7945D6B0071 for ; Mon, 6 Dec 2021 12:43:58 -0500 (EST) Received: from smtpin26.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 30D2782FDC for ; Mon, 6 Dec 2021 17:43:48 +0000 (UTC) X-FDA: 78888092136.26.70F7D19 Received: from mail-ot1-f46.google.com (mail-ot1-f46.google.com [209.85.210.46]) by imf03.hostedemail.com (Postfix) with ESMTP id DA4F620002 for ; Mon, 6 Dec 2021 17:43:47 +0000 (UTC) Received: by mail-ot1-f46.google.com with SMTP id n17-20020a9d64d1000000b00579cf677301so14571330otl.8 for ; Mon, 06 Dec 2021 09:43:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HVGknVxk9En34YD7oMS0OxgDesFXXWSJuOEhaMPVhpQ=; b=MpGHgZI9p7ODUr8Ziu1rRD5W2VAFdUdsq5QuMb8JQ1BuEpd1+uqvcjxHMUjZ312Lly Plu9EQIKcZqOmqpshM9Znnj7yClb/SvXKd3Wfrzi7qL1SZbXEZzcyrczj/EwWtGwQod1 08iQT+zhwDbEOYWmBVKR4duWMM1W5/8AL5ol2DOhMqWG0vqSJiyGvZUWG3eANHrhddWw DXUeM+omRfwyCW14gjde2833BcoRsGkqsa99M0ChDdq0H6iyYn2zkINBrHdTnjft19VU nQRYLnUXiEVHQH1xyNrfbpxzXTA/X2Bccypfpy8Jgguh2Gu+R4HJ81Uc4TQAUMToWPBi efGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HVGknVxk9En34YD7oMS0OxgDesFXXWSJuOEhaMPVhpQ=; b=bghdHRTeGkEC9mEY7L2zMR4KdDUThZ+YzX6m5UqrhDiJ9BV5xG4t2WdZGeqbK2YXQn QQ+fWmkr9MCeErLZdwwBmhEmJSmOhnL2leBvW7U35jR4v4tpsxc3q5Ia48PvdbcuT8E8 99qpXT3Eb3Qoo3xgwbCv1sqoJkR1PzhtJqnrbreHkZ5dT/NmWvjZ2MIatPLypq7tMOHU gt8QDKZg+HMmuFzBx0LaBSyVOMa3CJ/gXBCfGclMmCErRI7s4D9WM2yL5dMiWTB6r631 EqTHWSD6K15MAesxQ7NjYKdbQ2vYLxhD8kEvRA4HIMutaLS5oIn4El6QS9Wkz7eImvrq JHjw== X-Gm-Message-State: AOAM530ErsdY7vabHzqyohE0qbwau60nVEkup9AJGQXBqYPFW/467WeR X98J99gh6xNIjaE6o7TJ3ec3vE8Isj2GDhXfHVMltg== X-Google-Smtp-Source: ABdhPJwnJvhriQXJt7rZ6riEAR2EXPbFDLRKJiml6FMJ04J3vUhopqP8qsROsH9l385k2pCLUzX0KjbomLQtJ4BQ3b8= X-Received: by 2002:a9d:77d1:: with SMTP id w17mr30319312otl.329.1638812626987; Mon, 06 Dec 2021 09:43:46 -0800 (PST) MIME-Version: 1.0 References: <202112070117.78ld7W01-lkp@intel.com> In-Reply-To: <202112070117.78ld7W01-lkp@intel.com> From: Marco Elver Date: Mon, 6 Dec 2021 18:43:35 +0100 Message-ID: Subject: Re: [linux-next:master 4752/5235] kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte' To: kernel test robot Cc: kbuild-all@lists.01.org, Linux Memory Management List , "Paul E. McKenney" Content-Type: text/plain; charset="UTF-8" Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=MpGHgZI9; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf03.hostedemail.com: domain of elver@google.com designates 209.85.210.46 as permitted sender) smtp.mailfrom=elver@google.com X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: DA4F620002 X-Stat-Signature: 9c1ic1k6ditywamptcufm33hfuzsfjzc X-HE-Tag: 1638812627-833249 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 Mon, 6 Dec 2021 at 18:40, kernel test robot wrote: [...] > kernel/kcsan/kcsan_test.c: In function 'test_barrier_nothreads': > >> kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte' [-Werror=implicit-function-declaration] > 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > kernel/kcsan/kcsan_test.c:537:17: note: in definition of macro '__KCSAN_EXPECT_BARRIER' > 537 | barrier; \ > | ^~~~~~~ > kernel/kcsan/kcsan_test.c:592:9: note: in expansion of macro 'KCSAN_EXPECT_READ_BARRIER' > 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true); > | ^~~~~~~~~~~~~~~~~~~~~~~~~ > kernel/kcsan/kcsan_test.c: In function 'test_atomic_builtins': > kernel/kcsan/kcsan_test.c:1233:17: warning: 'atomic_thread_fence' is not supported with '-fsanitize=thread' [-Wtsan] > 1233 | __atomic_thread_fence(__ATOMIC_SEQ_CST); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > cc1: some warnings being treated as errors FTR, like the other issue, fixed by same patch: https://lore.kernel.org/all/20211206064151.3337384-2-elver@google.com/ But I'm glad to see the test robot discovered this, too. Thanks, -- Marco