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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 7BA73C433ED for ; Mon, 10 May 2021 13:51:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4928860FE5 for ; Mon, 10 May 2021 13:51:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231344AbhEJNwf (ORCPT ); Mon, 10 May 2021 09:52:35 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:39573 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241661AbhEJNpU (ORCPT ); Mon, 10 May 2021 09:45:20 -0400 Received: from mail-ot1-f46.google.com ([209.85.210.46]) by mrelayeu.kundenserver.de (mreue010 [213.165.67.97]) with ESMTPSA (Nemesis) id 1N0nzR-1lL7To0U9l-00wlLR; Mon, 10 May 2021 15:44:09 +0200 Received: by mail-ot1-f46.google.com with SMTP id t4-20020a05683014c4b02902ed26dd7a60so4284961otq.7; Mon, 10 May 2021 06:44:08 -0700 (PDT) X-Gm-Message-State: AOAM5328FdHEOHaAUuEIq1f7rSVESUcQlT58FuYhYbZHsUfaWvF9wtxY 7ViGpo9ADRI5VV/9HOdJzNIScTORXPXWtZM/Iog= X-Google-Smtp-Source: ABdhPJyf4ohtmioZ4kBKNKLfyswa7BdPHuxKlk9MsZP//sYaokfeX3BZsjL/Fq6RIqRnBVeec+JlEiMV654qEXfujKI= X-Received: by 2002:a9d:222a:: with SMTP id o39mr20683875ota.246.1620654241959; Mon, 10 May 2021 06:44:01 -0700 (PDT) MIME-Version: 1.0 References: <20210510085339.1857696-4-schnelle@linux.ibm.com> <202105102111.SyGVczHt-lkp@intel.com> In-Reply-To: <202105102111.SyGVczHt-lkp@intel.com> From: Arnd Bergmann Date: Mon, 10 May 2021 15:43:08 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v5 3/3] asm-generic/io.h: warn in inb() and friends with undefined PCI_IOBASE To: kernel test robot Cc: Niklas Schnelle , Vineet Gupta , "David S. Miller" , kbuild-all@lists.01.org, Networking , Nathan Chancellor , Nick Desaulniers , clang-built-linux , linux-arch , Linux Kernel Mailing List , linux-s390 Content-Type: text/plain; charset="UTF-8" X-Provags-ID: V03:K1:nVQFemXOPYeLeABTrJITdRG/VMGJSTepcBPBcH+ZAK5l8KOhUK5 cjjIHddG4heP3Nv4sCg9gA+VDn9dEEoJnlK0zPVMmZeuBUIX3A0rmcbNZjeFu4reZIDmJ4O g+S/75EwrMaCZxUbKgpGjZXOxs+AEZnOzvRVx5LQEIDHxJtwsNAbb2JKWGLUFIHKj80rAMY T/it7stYcME7laYJ1NQvQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:Prnpub61Edo=:IwPSuMdgZzzmzWl0boyLEI p0hy5Y8FrUj7Y7fBTgG+PSI2N5MLBF3YIN/8ozLLXRpgeekf5XnJNNiEp2Q9dh6R5iE6KaTwz Ogurhx8aqyPxHAmyY8QaOdL5CoOA6W8jOB8yXZXSiCSC3NY4/hVdK3F4/VE/oz+8QxYPcvVvb 9iKWMXGhVHsFiQc/dSMtNVx+LmDzARz7VrVgkBCF7ur9R39JhwKS6BkkLCeeh1Zm6sJMEQ1Tp g50GtGpUqWFh31MasSFjJ5VipUBv9ubYFFJg0tE2bPa+9xKxmh0dYtVCdrfohpBz+5SxwzLiu EiaMkXQTW/m/0gWJIZ1vqCZD0y9GB0/yGGmTlhHsj80/ICrvlKrrG1/AEXVV2OKB5kvKPSS3N dhoCQakHsz7+1iTWH7L7zXkVTxYZMLNP7tO+btpMSwPhMsj+BkTeFkz4aVfjLuhBGAt1wg0sE CtDoDPWm6VvBgJTvYh0QWcedN7s07q159Mg6ToNZpMSUs8RAbonv6hHSrMRWpzgsEVC82p6Pa qLhfNbzTvZTRHJPoQcthc0= Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Mon, May 10, 2021 at 3:30 PM kernel test robot wrote: > All warnings (new ones prefixed by >>): > > In file included from include/linux/kernel.h:10, > from include/linux/list.h:9, > from include/linux/module.h:12, > from drivers/net/arcnet/com20020.c:31: > drivers/net/arcnet/com20020.c: In function 'com20020_reset': > >> include/linux/compiler.h:70:32: warning: 'inbyte' is used uninitialized in this function [-Wuninitialized] > 70 | (__if_trace.miss_hit[1]++,1) : \ > | ^ > drivers/net/arcnet/com20020.c:286:9: note: 'inbyte' was declared here > 286 | u_char inbyte; > | ^~~~~~ This looks like a real problem with the patch: the insb()/insw()/insl() helpers should memset(buffer, 0xff, size) to avoid using random stack data. Arnd