linux-kernel - Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dc0dbf3d-d524-7edc-6fbf-0067c75c3d03@acm.org>
Date:   Sat, 6 Aug 2022 08:21:56 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     kernel test robot <lkp@...el.com>
Cc:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        Jens Axboe <axboe@...nel.dk>
Subject: Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in
 argument 5 (different base types)

On 8/5/22 21:44, kernel test robot wrote:
>     drivers/md/raid10.c:1139:30: sparse: sparse: incorrect type in initializer (different base types) @@     expected int const op @@     got restricted blk_opf_t enum req_op @@
>     drivers/md/raid10.c:1139:30: sparse:     expected int const op
>     drivers/md/raid10.c:1139:30: sparse:     got restricted blk_opf_t enum req_op
>     drivers/md/raid10.c:1140:52: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned long const do_sync @@     got restricted blk_opf_t @@
>     drivers/md/raid10.c:1140:52: sparse:     expected unsigned long const do_sync
>     drivers/md/raid10.c:1140:52: sparse:     got restricted blk_opf_t

I can't reproduce this with Linus' master branch. It seems like the 
kernel test robot picked a commit somewhere halfway my patch series?

Bart.