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: <g6tcsjmc27jafnfwbyltlq7lhbldcdlfbf4qiqwrnp6iyndk3o@lrcnxz5ud27b>
Date: Tue, 20 Jan 2026 01:09:34 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Mark Brown <broonie@...nel.org>
Cc: Simona Vetter <simona.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Maxime Ripard <mripard@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the drm-misc tree

On Mon, Jan 19, 2026 at 05:37:48PM +0000, Mark Brown wrote:
> Hi all,
> 
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> /tmp/next/build/drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c: In function 'drm_test_check_reject_hdr_infoframe_bpc_10':
> /tmp/next/build/drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c:2926:49: error: passing argument 6 of 'drm_property_replace_blob_from_id' makes integer from pointer without a cast [-Wint-conversion]
>  2926 |                                                 &replaced);
>       |                                                 ^~~~~~~~~
>       |                                                 |
>       |                                                 bool * {aka _Bool *}
> In file included from /tmp/next/build/include/drm/drm_connector.h:33,
>                  from /tmp/next/build/include/drm/drm_modes.h:33,
>                  from /tmp/next/build/include/drm/drm_crtc.h:32,
>                  from /tmp/next/build/include/drm/drm_atomic.h:31,
>                  from /tmp/next/build/drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c:7:
> /tmp/next/build/include/drm/drm_property.h:287:47: note: expected 'ssize_t' {aka 'long int'} but argument is of type 'bool *' {aka '_Bool *'}
>   287 |                                       ssize_t max_size,
>       |                                       ~~~~~~~~^~~~~~~~
> /tmp/next/build/drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c:2922:15: error: too few arguments to function 'drm_property_replace_blob_from_id'
>  2922 |         ret = drm_property_replace_blob_from_id(drm,
>       |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /tmp/next/build/include/drm/drm_property.h:282:5: note: declared here
>   282 | int drm_property_replace_blob_from_id(struct drm_device *dev,
>       |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>    7436a87db99d5 (drm/tests: hdmi: check the infoframes behaviour)
> 
> interacting with
> 
>    ca59e33f5a1f6 (drm/atomic: add max_size check to drm_property_replace_blob_from_id())
> 
> I have applied a fixup:

This fixup is correct. I've sent a formal patch,

https://lore.kernel.org/all/20260119-fix-kunit-infoframe-v1-1-5f2f9b066594@oss.qualcomm.com/

> 

-- 
With best wishes
Dmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ