From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Johannes Thumshirn <jth@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: fs/zonefs/./trace.h:22:1: sparse: sparse: cast to restricted blk_opf_t
Date: Wed, 10 Aug 2022 11:08:11 -0700 [thread overview]
Message-ID: <8aa0e7a4-265c-21f4-bdb4-57641d15b7b9@acm.org> (raw)
In-Reply-To: <24b7e027-e098-269b-ccf7-b14deb499c33@opensource.wdc.com>
On 8/10/22 07:36, Damien Le Moal wrote:
> On 2022/08/08 8:37, Bart Van Assche wrote:
>> Thanks for having taken a look. Please help with verifying whether the
>> following patch is sufficient to fix the reported warning: "[PATCH]
>> tracing: Suppress sparse warnings triggered by is_signed_type()"
>> (https://lore.kernel.org/all/20220717151047.19220-1-bvanassche@acm.org/).
>
> With the current Linus tree, I do not see this sparse warning. However, applying
> the above patch, "make M=fs/zonefs C=1" generates a lot of warnings:
That doesn't make sense to me. My patch reduces the number of sparse
warnings that are reported.
> make -j64 M=fs/zonefs C=1
> CC [M] fs/zonefs/super.o
> CC [M] fs/zonefs/sysfs.o
> CHECK fs/zonefs/sysfs.c
> CHECK fs/zonefs/super.c
> fs/zonefs/sysfs.c: note: in included file (through include/linux/bitops.h,
> include/linux/kernel.h, arch/x86/include/asm/percpu.h,
> arch/x86/include/asm/preempt.h, include/linux/preempt.h,
> include/linux/spinlock.h, ...):
> ./arch/x86/include/asm/bitops.h:66:1: warning: unreplaced symbol 'return'
I think that you are hitting a bug in sparse. See also
https://lore.kernel.org/all/e91d351c-3c16-e48d-7e9d-9f096c4acbc9@debian.org/T/.
I also see the above warnings if I use the sparse binary from Debian
testing. I do not see these sparse warnings if I download the sparse
source code and compile that source code myself.
Bart.
next prev parent reply other threads:[~2022-08-10 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 8:00 fs/zonefs/./trace.h:22:1: sparse: sparse: cast to restricted blk_opf_t kernel test robot
2022-08-08 14:48 ` Damien Le Moal
2022-08-08 15:37 ` Bart Van Assche
2022-08-10 14:36 ` Damien Le Moal
2022-08-10 18:08 ` Bart Van Assche [this message]
2022-08-10 19:14 ` Damien Le Moal
2022-08-10 22:21 ` Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8aa0e7a4-265c-21f4-bdb4-57641d15b7b9@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jth@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.