Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp923112imi; Thu, 21 Jul 2022 13:41:13 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tIhfixE2CjhKqTm67DfDGla/+Rx0pPcwF5Wha3+xLcjSBWYai8chIbgy2eBfVGlPU9hCtH X-Received: by 2002:a17:903:2343:b0:16c:1efe:1fe0 with SMTP id c3-20020a170903234300b0016c1efe1fe0mr113107plh.106.1658436072811; Thu, 21 Jul 2022 13:41:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658436072; cv=none; d=google.com; s=arc-20160816; b=KKBnlB6t4In1+GgA+pAsP3PUQxh2Z+pps0u/9QjDZULRjT/5YsHkIJFXLDu5aIH5Cb OVGMh5N52+QQuy5erXTzV7EG+z502R8WnDWVP/6KLaCekljYNbFrUGQMvyFvvMehCoDD bwcvZPu8Yox6rzrVA+Mgtsz5MSHlarw87srQghNMBXT11RwES5KA9MWdi5d9QCnWhJrz GwDTGvCX4Lsng3v+xdB9zYO3ny7hHs6HtbURc0WJq398LF6h6gwngMhA9N2J9DH7xBtP nTjYMy4BAPZ5q9O7nTYJRvT5rAOY9DuXbf1P4Bpdoci8g0VteE0wLyh8zKSjPYW6vYFn a7ZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=zccUArvHbZkwSLlopBVJYUUMkElLghD6qyHZAjaPBgs=; b=Sceok7VflVBsajb3iN76pmY2UsMsUl+tDsn/Mx+5ZVh0ANblW2I6vPw3m+9+imb78M 0WJ0TB5dztMSsqLmgkh1eaFGdseu6eDouPk9hCjEeLvyxzCbvzXxfFg7Pm2s5DijN6zD xb+U3/B/E3cY0NqK12x5jKWq24gRQHZxSuoD7sGDhUk3fDx7CgzfB+baUQvsdkCSVamf Mzb/cTVVxdEyyPhpmMSPvwy2gj476OjvElYOIp8Oye113kNGOuQHOFpBeNPFPkD57bI1 1+IqV6N9OorTw4NmtHk/KDR7dgGu/LRc79ViaWQngPLuhqBP66KouWA4RRzL2nFZwLTb HhHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=NFaShSkq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 6-20020a631046000000b00415bfaddcddsi3451398pgq.471.2022.07.21.13.40.32; Thu, 21 Jul 2022 13:41:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=NFaShSkq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232170AbiGUUcW (ORCPT + 99 others); Thu, 21 Jul 2022 16:32:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229961AbiGUUcU (ORCPT ); Thu, 21 Jul 2022 16:32:20 -0400 Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4926787368 for ; Thu, 21 Jul 2022 13:32:19 -0700 (PDT) Received: by mail-ej1-x634.google.com with SMTP id tk8so5117282ejc.7 for ; Thu, 21 Jul 2022 13:32:19 -0700 (PDT) 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=zccUArvHbZkwSLlopBVJYUUMkElLghD6qyHZAjaPBgs=; b=NFaShSkqPcwWe0I+zdT08zjLl533SqHJSZMCnmrymqmk4kjxbEiMj1gB+9m9KkqG7L dTg9IOB4dnPKkcRkYGmYvzzXlf0B83BKWotFKSZAx57vDpeJ4Qgfe+ihjM36eO717Yy0 9Fv2ZOi8mbDTHegwxc7Vtpf+ATsjJLllPJookEK7zZJMRVvOatBpCrqkcf1rmrxgwBSl 2LE29TlLfDA9j3RVQHvM7ulDp7BOLhbSmbkmD8vRZwCR2TjhSgpMRJbIDt5Oh7UvlWjj XQKXYil5HWSvMMYpbf4d9Z7WCDOnqOfJuBI3iFZLdX2KeWf+tZASuEHVkIjfQRZEd7fT IYJw== 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=zccUArvHbZkwSLlopBVJYUUMkElLghD6qyHZAjaPBgs=; b=V9P8uOMaruFMBJEl6zPOA6KimTqu75kQouw76AtRp7gXifPGaTYv7ES7mBluPyjqmb PpwoCFZRfOMkJWvBwgPBXjBboHXovQdCezjkYAU4TysZhhq7vU4BYc4hQYLhqOzs5LlG v6wtp9Puo6JPP2vnFQcZJiYpAmH7Mfe4fPVePkKfTln60Rhj2oo04kCU1ZZHPZTT28cG cZllQXuMxRKHEfkKYtnbmoY6yfISgQKrYOp7zr+cB+Q67KlV9wCboP4R4a5n4RpDp8lI OscL89bXeMoafwk4UNPy8SGZQ17G8quGjmH8uOJLTG+UdAgEBDpBCwXyj3S3uUeMS/qQ Yp1w== X-Gm-Message-State: AJIora+8lci1nsT5HHyZqPdqysprgUP1pcxHYDyYorYrZDPcVqBZA7kQ 82EXhPBf5Z9Tsoy8LnLEF3MlzX6+vezuzySZIpUznA== X-Received: by 2002:a17:906:cc5a:b0:72b:1459:6faa with SMTP id mm26-20020a170906cc5a00b0072b14596faamr285506ejb.221.1658435537581; Thu, 21 Jul 2022 13:32:17 -0700 (PDT) MIME-Version: 1.0 References: <20220720232332.2720091-1-justinstitt@google.com> In-Reply-To: From: Justin Stitt Date: Thu, 21 Jul 2022 13:32:06 -0700 Message-ID: Subject: Re: [PATCH] Makefile.extrawarn: re-enable -Wformat for clang To: Nathan Chancellor Cc: Nick Desaulniers , Masahiro Yamada , Tom Rix , Michal Marek , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 21, 2022 at 12:37 PM Nathan Chancellor wrote: > > On Thu, Jul 21, 2022 at 08:10:27AM -0700, Nathan Chancellor wrote: > > On Thu, Jul 21, 2022 at 07:27:34AM -0700, Nick Desaulniers wrote: > > > On Wed, Jul 20, 2022 at 4:23 PM Justin Stitt wrote: > > > > > > > > There's been an ongoing mission to re-enable the -Wformat warning for > > > > Clang. A previous attempt at enabling the warning showed that there were > > > > many instances of this warning throughout the codebase. The sheer amount > > > > of these warnings really polluted builds and thus -Wno-format was added > > > > to _temporarily_ toggle them off. > > > > > > > > After many patches the warning has largely been eradicated for x86, > > > > x86_64, arm, and arm64 on a variety of configs. The time to enable the > > > > warning has never been better as it seems for the first time we are > > > > ahead of them and can now solve them as they appear rather than tackling > > > > from a backlog. > > > > > > > > As to the root cause of this large backlog of warnings, Clang seems to > > > > pickup on some more nuanced cases of format warnings caused by implicit > > > > integer conversion as well as default argument promotions from > > > > printf-like functions. > > > > > > > > > > > > Link: https://github.com/ClangBuiltLinux/linux/issues/378 > > > > Suggested-by: Nick Desaulniers > > > > Signed-off-by: Justin Stitt > > > > --- > > > > Previous attempt: (https://patchwork.kernel.org/project/linux-kbuild/patch/20190201210853.244043-1-jflat@chromium.org/) > > > > > > > > Note: > > > > For this patch to land on its feet, the plethora of supporting patches that > > > > fixed various -Wformat warnings need to be picked up. Thanfully, a lot > > > > of them have! > > > > > > > > Here are the patches still waiting to be picked up: > > > > * https://lore.kernel.org/all/20220718230626.1029318-1-justinstitt@google.com/ > > > > * https://lore.kernel.org/all/20220711222919.2043613-1-justinstitt@google.com/ > > > > > > Hi Masahiro, Nathan, and Tom, > > > What are your thoughts for _when_ in the release cycle this should be > > > picked up? I worry that if we don't remove this soon, we will > > > backslide, and more -Wformat issues will crop up making removing this > > > in the future like digging in sand. Justin has chased down many > > > instances of this warning, and I'm happy to help clean up fallout from > > > landing this. > > > > Let me do a series of builds with the two patches above against > > next-20220721 to see if there are any instances of this warning across > > the less frequently tested architectures then I will review/ack this. > > Alright, against next-20220721, I applied: > > * https://lore.kernel.org/20220712204900.660569-1-justinstitt@google.com/ (applied to net-next, just not in this -next release) > * https://lore.kernel.org/20220718230626.1029318-1-justinstitt@google.com/ (not picked up) > * https://lore.kernel.org/20220711222919.2043613-1-justinstitt@google.com/ (not picked up) > > I still see the following warnings. I have suggested fixes, which I am happy to > send unless Justin wants to. I can tackle these by EOD. > > ======================================================================== > > ARCH=arm allmodconfig: > > ../drivers/iommu/msm_iommu.c:603:6: error: format specifies type 'unsigned short' but the argument has type 'int' [-Werror,-Wformat] > sid); > ^~~ > ../include/linux/dev_printk.h:146:70: note: expanded from macro 'dev_warn' > dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev, dev_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap' > _p_func(dev, fmt, ##__VA_ARGS__); \ > ~~~ ^~~~~~~~~~~ > 1 error generated. > > Introduced by commit f78ebca8ff3d ("iommu/msm: Add support for generic master > bindings"). > > diff --git a/drivers/iommu/msm_iommu.c b/drivers/iommu/msm_iommu.c > index 428919a474c1..6a24aa804ea3 100644 > --- a/drivers/iommu/msm_iommu.c > +++ b/drivers/iommu/msm_iommu.c > @@ -599,7 +599,7 @@ static int insert_iommu_master(struct device *dev, > > for (sid = 0; sid < master->num_mids; sid++) > if (master->mids[sid] == spec->args[0]) { > - dev_warn(dev, "Stream ID 0x%hx repeated; ignoring\n", > + dev_warn(dev, "Stream ID 0x%x repeated; ignoring\n", > sid); > return 0; > } > > ======================================================================== > > ARCH=hexagon allmodconfig + CONFIG_FRAME_WARN=0: > > ../drivers/misc/lkdtm/bugs.c:107:3: error: format specifies type 'unsigned long' but the argument has type 'int' [-Werror,-Wformat] > REC_STACK_SIZE, recur_count); > ^~~~~~~~~~~~~~ > ../include/linux/printk.h:537:34: note: expanded from macro 'pr_info' > printk(KERN_INFO pr_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/printk.h:464:60: note: expanded from macro 'printk' > #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/printk.h:436:19: note: expanded from macro 'printk_index_wrap' > _p_func(_fmt, ##__VA_ARGS__); \ > ~~~~ ^~~~~~~~~~~ > ../drivers/misc/lkdtm/bugs.c:32:24: note: expanded from macro 'REC_STACK_SIZE' > #define REC_STACK_SIZE (THREAD_SIZE / 8) > ^~~~~~~~~~~~~~~~~ > 1 error generated. > > Introduced by commit 24cccab42c41 ("lkdtm/bugs: Adjust recursion test to avoid > elision"). > > diff --git a/drivers/misc/lkdtm/bugs.c b/drivers/misc/lkdtm/bugs.c > index 009239ad1d8a..6381255aaecc 100644 > --- a/drivers/misc/lkdtm/bugs.c > +++ b/drivers/misc/lkdtm/bugs.c > @@ -29,7 +29,7 @@ struct lkdtm_list { > #if defined(CONFIG_FRAME_WARN) && (CONFIG_FRAME_WARN > 0) > #define REC_STACK_SIZE (_AC(CONFIG_FRAME_WARN, UL) / 2) > #else > -#define REC_STACK_SIZE (THREAD_SIZE / 8) > +#define REC_STACK_SIZE ((unsigned long)(THREAD_SIZE / 8)) > #endif > #define REC_NUM_DEFAULT ((THREAD_SIZE / REC_STACK_SIZE) * 2) > > > ======================================================================== > > ARCH=arm allmodconfig: > > ../drivers/nvme/target/auth.c:492:18: error: format specifies type 'unsigned long' but the argument has type 'size_t' (aka 'unsigned int') [-Werror,-Wformat] > ctrl->cntlid, ctrl->dh_keysize, buf_size); > ^~~~~~~~~~~~~~~~ > ../include/linux/printk.h:517:37: note: expanded from macro 'pr_warn' > printk(KERN_WARNING pr_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/printk.h:464:60: note: expanded from macro 'printk' > #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/printk.h:436:19: note: expanded from macro 'printk_index_wrap' > _p_func(_fmt, ##__VA_ARGS__); \ > ~~~~ ^~~~~~~~~~~ > 1 error generated. > > Introduced by commit 71ebe3842ebe ("nvmet-auth: Diffie-Hellman key exchange > support"). > > This one is not clang specific and already has a fix pending: > > https://lore.kernel.org/20220718050356.227647-1-hch@lst.de/ > > ======================================================================== > > Pretty much every allmodconfig: > > ../sound/soc/sof/ipc3-topology.c:2343:4: error: format specifies type 'unsigned char' but the argument has type 'int' [-Werror,-Wformat] > SOF_ABI_MAJOR, SOF_ABI_MINOR, SOF_ABI_PATCH); > ^~~~~~~~~~~~~ > ../include/linux/dev_printk.h:150:67: note: expanded from macro 'dev_info' > dev_printk_index_wrap(_dev_info, KERN_INFO, dev, dev_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap' > _p_func(dev, fmt, ##__VA_ARGS__); \ > ~~~ ^~~~~~~~~~~ > ../include/uapi/sound/sof/abi.h:30:23: note: expanded from macro 'SOF_ABI_MAJOR' > #define SOF_ABI_MAJOR 3 > ^ > ../sound/soc/sof/ipc3-topology.c:2343:19: error: format specifies type 'unsigned char' but the argument has type 'int' [-Werror,-Wformat] > SOF_ABI_MAJOR, SOF_ABI_MINOR, SOF_ABI_PATCH); > ^~~~~~~~~~~~~ > ../include/linux/dev_printk.h:150:67: note: expanded from macro 'dev_info' > dev_printk_index_wrap(_dev_info, KERN_INFO, dev, dev_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap' > _p_func(dev, fmt, ##__VA_ARGS__); \ > ~~~ ^~~~~~~~~~~ > ../include/uapi/sound/sof/abi.h:31:23: note: expanded from macro 'SOF_ABI_MINOR' > #define SOF_ABI_MINOR 22 > ^~ > ../sound/soc/sof/ipc3-topology.c:2343:34: error: format specifies type 'unsigned char' but the argument has type 'int' [-Werror,-Wformat] > SOF_ABI_MAJOR, SOF_ABI_MINOR, SOF_ABI_PATCH); > ^~~~~~~~~~~~~ > ../include/linux/dev_printk.h:150:67: note: expanded from macro 'dev_info' > dev_printk_index_wrap(_dev_info, KERN_INFO, dev, dev_fmt(fmt), ##__VA_ARGS__) > ~~~ ^~~~~~~~~~~ > ../include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap' > _p_func(dev, fmt, ##__VA_ARGS__); \ > ~~~ ^~~~~~~~~~~ > ../include/uapi/sound/sof/abi.h:32:23: note: expanded from macro 'SOF_ABI_PATCH' > #define SOF_ABI_PATCH 0 > ^ > 3 errors generated. > > Introduced by commit 323aa1f093e6 ("ASoC: SOF: Add a new IPC op for parsing > topology manifest") for little reason it seems? > > diff --git a/sound/soc/sof/ipc3-topology.c b/sound/soc/sof/ipc3-topology.c > index b2cc046b9f60..65923e7a5976 100644 > --- a/sound/soc/sof/ipc3-topology.c > +++ b/sound/soc/sof/ipc3-topology.c > @@ -2338,7 +2338,7 @@ static int sof_ipc3_parse_manifest(struct snd_soc_component *scomp, int index, > } > > dev_info(scomp->dev, > - "Topology: ABI %d:%d:%d Kernel ABI %hhu:%hhu:%hhu\n", > + "Topology: ABI %d:%d:%d Kernel ABI %d:%d:%d\n", > man->priv.data[0], man->priv.data[1], man->priv.data[2], > SOF_ABI_MAJOR, SOF_ABI_MINOR, SOF_ABI_PATCH); > > > ======================================================================== > > I would really like to see patches in flight for these before this patch > is accepted but it is really awesome to see how close we are :) > > Cheers, > Nathan -Justin