linux-kernel - Re: mm/memcontrol.c:600:9: sparse: sparse: incorrect type in argument 1 (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:   Tue, 11 Oct 2022 08:39:41 +0200
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     kernel test robot <lkp@...el.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, kbuild-all@...ts.01.org,
        linux-kernel@...r.kernel.org,
        Muchun Song <songmuchun@...edance.com>
Subject: Re: mm/memcontrol.c:600:9: sparse: sparse: incorrect type in
 argument 1 (different address spaces)

On 2022-10-11 14:35:04 [+0800], kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   60bb8154d1d77042a5d43d335a68fdb202302cbe
> commit: e575d401583273a7ac5dfb27520e41c821e81816 mm/memcontrol: Replace the PREEMPT_RT conditionals
> date:   3 weeks ago
> config: loongarch-randconfig-s032-20221010
> compiler: loongarch64-linux-gcc (GCC) 12.1.0
> reproduce:

Did this change with the commit change or was it the case before? IMHO
the whole file isn't sparse clean.

Sebastian