linux-kernel - Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS

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

Message-ID: <RMIFRuUra0Qgzx9r2eT-GsI-9FdUFjfiNCvpax8I4OwuQidm8sFcaSzoZqHfbA3iXsW-z0z31K5qZ-7w_1ciDF4KSZwz2JbOggtTqHTsHsY=@emersion.fr>
Date:   Wed, 23 Aug 2023 10:58:11 +0000
From:   Simon Ser <contact@...rsion.fr>
To:     James Zhu <jamesz@....com>
Cc:     Christian König <christian.koenig@....com>,
        Michał Winiarski <michal.winiarski@...el.com>,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
        intel-gfx@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Maxime Ripard <mripard@...nel.org>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Matthew Wilcox <willy@...radead.org>,
        Oded Gabbay <ogabbay@...nel.org>,
        James Zhu <James.Zhu@....com>,
        Pekka Paalanen <pekka.paalanen@...labora.com>,
        Emil Velikov <emil.l.velikov@...il.com>
Subject: Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS

On Wednesday, August 23rd, 2023 at 12:53, Simon Ser <contact@...rsion.fr> wrote:

> On Tuesday, August 8th, 2023 at 17:04, James Zhu jamesz@....com wrote:
> 
> > I have a MR for libdrm to support drm nodes type up to 2^MINORBITS
> > nodes which can work with these patches,
> > 
> > https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/305
> 
> FWIW, this MR has been merged, so in theory this kernel patch should
> work fine with latest libdrm.

Hm, we might want to adjust MAX_DRM_NODES still. It's set to 256
currently, which should be enough for 128 DRM devices, but not more.
Not bumping this value will make drmGetDevices2() print a warning and
not return all devices on systems with more than 128 DRM devices.