linux-kernel - Re: kernel/trace/blktrace.c:347:12: sparse: sparse: incorrect type in assignment (different address spaces)

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] [day] [month] [year] [list]

Date:   Thu, 4 Jun 2020 07:17:18 +0000
From:   Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
To:     Jens Axboe <axboe@...nel.dk>
CC:     kernel test robot <lkp@...el.com>, "Jan, Kara," <jack@...e.cz>,
        "kbuild-all@...ts.01.org" <kbuild-all@...ts.01.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Ming Lei <ming.lei@...hat.com>,
        Bart Van Assche <bvanassche@....org>
Subject: Re: kernel/trace/blktrace.c:347:12: sparse: sparse: incorrect type in
 assignment (different address spaces)

On 6/3/20 7:30 PM, Jens Axboe wrote:
>> Can you please let me know how can we proceed with the series so that
>> we can stop these emails ?
> Which patch from Jan? I saw one, and it had issues. Then there's a second
> one, which is ordered behind a series that's not in my tree and wasn't
> queued for 5.8. And finally, there's your series, which seemed to be a
> subset of Jan's patch for patch 1.
> 
> So it's really not very clear. Maybe if folks got together and actually
> put together a series to fix this it would be easier to get this done.
> 
> -- Jens Axboe

I sent an updated series on the linux-block/for-next which removes the
duplicate patch (Jan's rcu warning fix). In case you happened to apply
other series before mine (with V2) which has Jan's patch I'll resend
this one with V3.