linux-kernel - Re: kismet: WARNING: unmet direct dependencies detected for SM_GCC_8550 when selected by SM_CAMCC

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: <20231108155711.tulvsq5ajpyhwyzk@work.work.opentheblackbox.net>
Date:   Wed, 8 Nov 2023 10:57:11 -0500
From:   Paul Gazzillo <paul@...zz.com>
To:     Yujie Liu <yujie.liu@...el.com>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Philip Li <philip.li@...el.com>,
        kernel test robot <lkp@...el.com>,
        Jagadeesh Kona <quic_jkona@...cinc.com>,
        Necip Fazil Yildiran <fazilyildiran@...il.com>,
        oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
        Bjorn Andersson <andersson@...nel.org>,
        Taniya Das <quic_tdas@...cinc.com>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for
 SM_GCC_8550 when selected by SM_CAMCC_8550

On 11/08/2023, Yujie Liu wrote:
> On Tue, Nov 07, 2023 at 08:00:33AM -0800, Randy Dunlap wrote:
> > Hi Philip,
> > 
> > On 11/7/23 04:45, Philip Li wrote:
> > > On Tue, Nov 07, 2023 at 11:11:54AM +0100, Geert Uytterhoeven wrote:
> > >> Hi Robot,
> > >>
> > >> On Mon, Nov 6, 2023 at 4:06 PM kernel test robot <lkp@...el.com> wrote:
> > >>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > >>> head:   d2f51b3516dade79269ff45eae2a7668ae711b25
> > >>> commit: ccc4e6a061a21d75b96d82fc4b084a8d96df6eb4 clk: qcom: camcc-sm8550: Add camera clock controller driver for SM8550
> > >>> date:   7 weeks ago
> > >>> config: arm-kismet-CONFIG_SM_GCC_8550-CONFIG_SM_CAMCC_8550-0-0 (https://download.01.org/0day-ci/archive/20231106/202311062309.XugQH7AH-lkp@intel.com/config)
> > >>> reproduce: (https://download.01.org/0day-ci/archive/20231106/202311062309.XugQH7AH-lkp@intel.com/reproduce)
> > >>>
> > >>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > >>> the same patch/commit), kindly add following tags
> > >>> | Reported-by: kernel test robot <lkp@...el.com>
> > >>> | Closes: https://lore.kernel.org/oe-kbuild-all/202311062309.XugQH7AH-lkp@intel.com/
> > >>>
> > >>> kismet warnings: (new ones prefixed by >>)
> > >>>>> kismet: WARNING: unmet direct dependencies detected for SM_GCC_8550 when selected by SM_CAMCC_8550
> > >>>    .config:7280:warning: symbol value 'ONFIG_ARCH_MMAP_RND_BITS_MI' invalid for ARCH_MMAP_RND_BITS
> > >>                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >> Where is this coming from? I have seen this warning in several build
> > >> reports (earliest 2023-01-31), but cannot reproduce it with the provided
> > >> commit and config.
> > > 
> > 
> > I'm pretty sure that what Geert is asking about here is the warning (".config:7280:...") with
> > the truncated kconfig symbol 'ONFIG_ARCH_MMAP_RND_BITS_MI'.  I have also seen several of these.
> > Is this a bug in kismet or a bug in the robot or something else?
> 
> Hi Randy, Hi Geert,
> 
> We looked into this case and found that it is likely to be a kismet bug.
> We have created an issue ticket at [1].
> 
> [1] https://github.com/paulgazz/kmax/issues/239
> 
> Hi Paul, could you please help take a look?
> 
> Thanks,
> Yujie

Hi Yujie, Randy, and Geert,

Thanks for reporting this.  It was indeed a bug in how some
non-Boolean config options get set when kismet generates .config files
for bug validation.  kismet v4.5.1 now includes the fix, and the
symbol value warning no longer appears when I replicate with Philip
and Yujie's steps.

The unmet dependency bug for SM_GCC_8550, however, still appears and
looks to be to be genuine.  Jagadeesh's patch seems to fix that.

Best,
Paul