linux-kernel - Re: linux-next: build warning after merge of the device-mapper tree

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, 9 Jul 2020 12:38:30 +0800
From:   yangerkun <yangerkun@...wei.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Alasdair G Kergon <agk@...hat.com>,
        Mike Snitzer <snitzer@...hat.com>
CC:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
        Bryan Gurney <bgurney@...hat.com>
Subject: Re: linux-next: build warning after merge of the device-mapper tree

在 2020/7/9 11:26, Stephen Rothwell 写道:
> Hi all,
> 
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> In file included from drivers/md/dm-dust.c:11:
> drivers/md/dm-dust.c: In function 'dust_list_badblocks':
> drivers/md/dm-dust.c:307:10: warning: zero-length gnu_printf format string [-Wformat-zero-length]
>    307 |   DMEMIT("");
Mike and Bryan,

Should we just use "DMEMIT("\n")"? Maybe it's bad since this lead a
blank line...


>        |          ^~
> include/linux/device-mapper.h:555:46: note: in definition of macro 'DMEMIT'
>    555 |      0 : scnprintf(result + sz, maxlen - sz, x))
>        |                                              ^
> 
> Introduced by commit
> 
>    20f93ea74f9c ("dm dust: add interface to list all badblocks")
>