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: <BYAPR04MB496578B5C8F42E1639F56D8A86880@BYAPR04MB4965.namprd04.prod.outlook.com>
Date:   Wed, 3 Jun 2020 22:34:34 +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)

Jens,

On 6/3/20 4:32 AM, kernel test robot wrote:
> tree:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git  master
> head:   d6f9469a03d832dcd17041ed67774ffb5f3e73b3
> commit: c780e86dd48ef6467a1146cf7d0fe1e05a635039 blktrace: Protect q->blk_trace with RCU
> date:   3 months ago
> config: arc-randconfig-s031-20200603 (attached as .config)
> compiler: arc-elf-gcc (GCC) 9.3.0
> reproduce:
>          # apt-get install sparse
>          # sparse version: v0.6.1-244-g0ee050a8-dirty
>          git checkout c780e86dd48ef6467a1146cf7d0fe1e05a635039
>          # save the attached .config to linux build tree
>          make W=1 C=1 ARCH=arc CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot<lkp@...el.com>

I think Jan has sent the patch to fix the rcu and I've sent out the 
series to fix the rest of the issues.

Can you please let me know how can we proceed with the series so that
we can stop these emails ?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ