From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=1.0 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.6 Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by gnuweeb.org (Postfix) with ESMTPS id 6C2937E3B9 for ; Sun, 17 Jul 2022 14:50:49 +0000 (UTC) Received: by mail-pj1-f44.google.com with SMTP id o3-20020a17090a744300b001ef8f7f3dddso10371611pjk.3 for ; Sun, 17 Jul 2022 07:50:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=/1vkZ9JABW2K7ica4Ajy0tyKCPUYY75FNBemI4lsUBg=; b=AmSYnyHyEwHQ4QdH4+DGFYGBQFP3nADjuSZzaMZyrRVzMq6/tBSL4UOdxq3kX+/ij6 DMWmZi+AfDpn39wGvG+hurzUoSraGQYRojw+a6yEDgiX/0q3A526jVywH2lAhW218jJ3 2SR0hLjqtr9Jey6aKdGxoWFqEsDUD+IUeYn59jY67GhfJbGlskh54WBHSBQrJ4UlAFa2 7ytV0x7ZQ9af7UBAPLYb1vVytiHNaS85zNrx/LaMUD8yiwFkH7b9h05OdNB0SBiPRIzZ ot1zSBP739FL/rO4KwaZW4hCFuQPZucVkug89pR0D0rOrY6JXxd5eRud2mbpXG5y/POc WX3A== X-Gm-Message-State: AJIora+Vhgq1lQ06QEvKohhwaLU4XqolyO9GmdV6UwH4XLyIIvFNvpIX wG0lN0Gj4f6tddyml9/bCQs= X-Google-Smtp-Source: AGRyM1sDh/unRqWobDUPacv2jQl5xlct+ynv29q8MAGFRuaKNvf+drhrZse3wRx5B3UCFSRgmbxj1Q== X-Received: by 2002:a17:90b:33c4:b0:1f0:3d9d:39ac with SMTP id lk4-20020a17090b33c400b001f03d9d39acmr26700881pjb.56.1658069448793; Sun, 17 Jul 2022 07:50:48 -0700 (PDT) Received: from ?IPV6:2601:647:4000:d7:feaa:14ff:fe9d:6dbd? ([2601:647:4000:d7:feaa:14ff:fe9d:6dbd]) by smtp.gmail.com with ESMTPSA id 11-20020a17090a0f8b00b001efc839ac97sm9532346pjz.3.2022.07.17.07.50.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 17 Jul 2022 07:50:47 -0700 (PDT) Message-ID: <4dc9a4eb-403f-951e-16e3-6fae5ed322be@acm.org> Date: Sun, 17 Jul 2022 07:50:46 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [ammarfaizi2-block:axboe/linux-block/for-next 91/112] include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t Content-Language: en-US To: kernel test robot Cc: kbuild-all@lists.01.org, Ammar Faizi , GNU/Weeb Mailing List , linux-kernel@vger.kernel.org, Jens Axboe , Ryusuke Konishi References: <202207162314.Jz305X9h-lkp@intel.com> From: Bart Van Assche In-Reply-To: <202207162314.Jz305X9h-lkp@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 7/16/22 08:40, kernel test robot wrote: > sparse warnings: (new ones prefixed by >>) > fs/nilfs2/segment.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/nilfs2.h): >>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t >>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t >>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer >>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer I think the root cause of this and similar reports is in the tracing core core. I will post a patch. Thanks, Bart.