linux-kernel - Re: [git pull] drm for 6.15-rc1

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: <20250331133137.GA263675@nvidia.com>
Date: Mon, 31 Mar 2025 10:31:37 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Airlie <airlied@...il.com>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.15-rc1

On Mon, Mar 31, 2025 at 01:03:38PM +0200, Simona Vetter wrote:
> Hi Linus,
> 
> On Mon, Mar 31, 2025 at 01:17:28PM +0300, Jani Nikula wrote:
> > On Fri, 28 Mar 2025, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> > > If you want to do that hdrtest thing, do it as part of your *own*
> > > checks. Don't make everybody else see that disgusting thing and have
> > > those turds in their trees.
> > >
> > > I'll just disable it by marking it BROKEN for now. You guys can figure
> > > out what you want to do, but no, forcing others to see those things is
> > > not the answer.
> > 
> > Fair. I hear you.
> 
> Mea culpa also from the drm maintainer side. As Jani explains below, we
> really want to make this and similar things happen in drm, and we thought
> this much more limited version would address your concerns. 

Please don't keep it fully isolated to DRM.. This new stuff did find
an error in the fwctl UAPI headers around uuid_t that had gone unnoticed:

https://lore.kernel.org/all/f6489337-67c7-48c8-b48a-58603ec15328@paulmck-laptop/raw

I think that was a valuable report, you just need to find a way to
make the tests it runs more acceptable..

FWIW, there is a "trick" I like to use for C header files, just ensure
that some C file someplace includes each header file first in the
#include list. It automatically makes the compiler check it is self
contained naturally. You can get pretty far by paying attention to
this detail and it costs nothing at build time.

Jason