linux-kernel - Re: arch/parisc/math-emu/driver.c:88:17: sparse: sparse: Using plain integer as NULL pointer

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: <YtOwNiF1JJK544bN@chrisdown.name>
Date:   Sun, 17 Jul 2022 07:46:14 +0100
From:   Chris Down <chris@...isdown.name>
To:     kernel test robot <lkp@...el.com>
Cc:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        Petr Mladek <pmladek@...e.com>
Subject: Re: arch/parisc/math-emu/driver.c:88:17: sparse: sparse: Using plain
 integer as NULL pointer

The real issue is this:

     ../arch/parisc/math-emu/decode_exc.c: In function 'decode_fpu':
     ../arch/parisc/math-emu/decode_exc.c:49:25: error: expected identifier before numeric constant
        49 | #define fmt             11      /* bits 19 & 20 */
           |                         ^~
     ../include/linux/printk.h:391:34: note: in expansion of macro 'fmt'
       391 |                                 .fmt = __builtin_constant_p(_fmt) ? (_fmt) : NULL, \

And that's why you don't define such shortly named, ambiguous macros. The 
simplest fix is probably just to have this file and others like it use _printk.

I'll send a patch and cc linux-parisc.