linux-kernel - Re: linux-next: build warning after merge of the scsi 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]

Message-ID: <CAK7LNASpcXLdQXdYErgYu1dCJWpw4qNGxqg8SxP1RzGi-Y5JBQ@mail.gmail.com>
Date:   Fri, 20 Aug 2021 15:30:49 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the scsi tree

On Fri, Aug 20, 2021 at 3:14 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the scsi tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/scsi/Makefile:197: FORCE prerequisite is missing
>
> Exposed by commit
>
>   0fc7db58e2a6 ("kbuild: warn if FORCE is missing for if_changed(_dep,_rule) and filechk")
>
> I don't know why this warning only appeared after the merge of the scsi
> tree, since the offending line has been in this Makefile since 2017

You are doing incremental builds.

Presumably, because include/scsi/scsi_devinfo.h
is touched by the following commit in the scsi tree.

commit f591a2e0548da88130c7b1c79f1f735273adc683
Author: Martin Kepplinger <martink@...teo.de>
Date:   Sun Jul 4 09:54:01 2021 +0200


Kbuild rebuilds scsi_devinfo_tbl.o due to the
timestamp update, then displays the warning.



If the scsi maintainers want to fix this issue,
a patch is already there.

https://lore.kernel.org/patchwork/patch/1478797/

Since this is a bug, it can get in the scsi tree
any time.





-- 
Best Regards
Masahiro Yamada