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 X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E176EC432C0 for ; Mon, 2 Dec 2019 16:20:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B80AF2053B for ; Mon, 2 Dec 2019 16:20:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="BBqymoM+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727511AbfLBQUp (ORCPT ); Mon, 2 Dec 2019 11:20:45 -0500 Received: from mail-oi1-f196.google.com ([209.85.167.196]:38267 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727484AbfLBQUp (ORCPT ); Mon, 2 Dec 2019 11:20:45 -0500 Received: by mail-oi1-f196.google.com with SMTP id b8so147913oiy.5 for ; Mon, 02 Dec 2019 08:20:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9BkVxiLv+pBEYtD5UOWEWCQuzcENfBq8d61a5ql7UVI=; b=BBqymoM+p7uOQ5qvkO5cICX7OJOz+9/tpF5VI96m+7u7GQrDTCEIToFN1vqzgNUjCY 5edEc4BtViGkn8BwD1lm9WB804ozxCDkXtWAjfxY5rKCifjBVhkmfV615FK/z57B0t8b YHdizSdbqUcV4V3KNbFowjDEm8RUtmTByzk9d4KdWtY2W/5zeHkOZTXUGkz8pmFKlFrU fZPdzp7rx4+hP6LZsDMzvFqGAQluZDFK94ba5AAQVgaY9xBA1HEHDRtLzut5NyNrkcd3 p/1T+DpZf8lxIPQQsr5zYtvIVXawszGSwJhzC5y5PqlQCO0FOGf8e5mCXkOF8B3jAjxs bIJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9BkVxiLv+pBEYtD5UOWEWCQuzcENfBq8d61a5ql7UVI=; b=k/ykMz6CrIUg2m0gLY33ZgBJuCE+yR/4bVnH6u93WWs1Vh9Jg6IXBIftuIosQ+jI3W xHffh3T8V36cNXEBrJapn1TWWhkkel4GTVTPolnSa6HOTsjjeV5lvbw/vN9k15Mh/Zdg +wkAOoRGb9bNauLfcMf0ChqlqDJlhb+JnFaxgoYfXT96HhLLUcoWc21bzr61plwC4Utd N878SqtFZahb2BGyD1wyRbBYBuK8Mn3Z9ecIcMEgb9MU7IC38ID/TI662bpCkBEweHk8 9OpLb2QCB5YKqUqw4GiKc2oCMTSTAnvJuHcqzjlCjMeL3x2vKTD5rXjwGPObPkJi8PQY Uq5Q== X-Gm-Message-State: APjAAAVCGlKuuEXWEl86dQyzXViDx4jbBy4AR/sE0JeFckxbbjbcIve1 8mGE+iRpfzTNO1MxPnGcPW8yaW1CMig7rSoNaB6f2w== X-Google-Smtp-Source: APXvYqxcjg2wFW+xR4e69BDFbQU5tYUhWFK+NbehjEsS9aW0D3qarZhcvroGXlhhlrXwyUJbAMgw1skovNDuz305KXc= X-Received: by 2002:a05:6808:8d5:: with SMTP id k21mr24359oij.121.1575303643663; Mon, 02 Dec 2019 08:20:43 -0800 (PST) MIME-Version: 1.0 References: <20191202135918.566dd377@canb.auug.org.au> <5231d2c0-41d9-6721-e15f-a7eedf3ce69e@infradead.org> In-Reply-To: <5231d2c0-41d9-6721-e15f-a7eedf3ce69e@infradead.org> From: Marco Elver Date: Mon, 2 Dec 2019 17:20:32 +0100 Message-ID: Subject: Re: linux-next: Tree for Dec 2 (drivers/crypto/hisilicon/sec2/sec_crypto.o +kcsan??) To: Randy Dunlap Cc: Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List , linux-crypto@vger.kernel.org, Zaibo Xu , Dmitry Vyukov Content-Type: text/plain; charset="UTF-8" Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, 2 Dec 2019 at 16:56, Randy Dunlap wrote: > > On 12/1/19 6:59 PM, Stephen Rothwell wrote: > > Hi all, > > > > Please do not add any material for v5.6 to your linux-next included > > trees until after v5.5-rc1 has been released. > > > > Changes since 20191129: > > > > on x86_64: > > ld: drivers/crypto/hisilicon/sec2/sec_crypto.o: in function `sec_bd_send': > sec_crypto.c:(.text+0xae9): undefined reference to `__tsan_atomic64_fetch_add' > ld: drivers/crypto/hisilicon/sec2/sec_crypto.o: in function `sec_req_cb': > sec_crypto.c:(.text+0xbf3): undefined reference to `__tsan_atomic64_fetch_add' > ld: drivers/crypto/hisilicon/sec2/sec_crypto.o: in function `sec_skcipher_callback': > sec_crypto.c:(.text+0x12d3): undefined reference to `__tsan_atomic32_compare_exchange_strong' > > > Full randconfig file is attached. Thanks, Randy. I think uses of __sync compiler builtins are banned in the kernel, so here compiling with KCSAN is actually acting as a linter showing us places where they are used in new code. The hisilicon/sec2 code in question was only recently added. hisilicon/sec2 maintainers: please use atomic64_t and atomic64_inc() for send_cnt and recv_cnt. Thanks, -- Marco