linux-kernel - drivers/gpu/drm/bridge/samsung-dsim.c link error

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-next>] [day] [month] [year] [list]

Date:   Thu,  3 Aug 2023 16:42:27 +0200
From:   Aleksandr Nogikh <nogikh@...gle.com>
To:     aford173@...il.com, l.stach@...gutronix.de, inki.dae@...sung.com,
        jagan@...rulasolutions.com, m.szyprowski@...sung.com,
        airlied@...il.com, daniel@...ll.ch,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Cc:     syzkaller@...glegroups.com, dvyukov@...gle.com
Subject: drivers/gpu/drm/bridge/samsung-dsim.c link error

Hello,

We've been seing the following linker error on arm64 syzbot instances:

ld.lld: error: undefined symbol: phy_mipi_dphy_get_default_config_for_hsclk
>>> referenced by samsung-dsim.c:731 (drivers/gpu/drm/bridge/samsung-dsim.c:731)
>>>               drivers/gpu/drm/bridge/samsung-dsim.o:(samsung_dsim_init) in archive vmlinux.a

Steps to reproduce on the latest linux-next:

$ git checkout next-20230803
$ wget -O '.config' 'https://raw.githubusercontent.com/google/syzkaller/master/dashboard/config/linux/upstream-arm64-kasan.config'
$ make CC=clang ARCH=arm64 LD=ld.lld CROSS_COMPILE=aarch64-linux-gnu- olddefconfig

This also prints:

WARNING: unmet direct dependencies detected for GENERIC_PHY_MIPI_DPHY
  Depends on [n]: GENERIC_PHY [=n]
  Selected by [y]:
  - DRM_NWL_MIPI_DSI [=y] && DRM_BRIDGE [=y] && DRM [=y] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
  - DRM_SAMSUNG_DSIM [=y] && DRM [=y] && DRM_BRIDGE [=y] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]

$ make CC=clang ARCH=arm64 LD=ld.lld CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc)

The kernel should have still compiled fine even despite the message above, right?

Could you please take a look?

-- 
Thank you!
Aleksandr