linux-kernel - Re: [RFC PATCH v1 0/1] possibile regression in the mm

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: <a5f8ae02-85f5-b98a-5900-603f189ccb85@nvidia.com>
Date:   Sun, 12 Mar 2023 17:45:11 -0700
From:   John Hubbard <jhubbard@...dia.com>
To:     Vincenzo Palazzo <vincenzopalazzodev@...il.com>,
        linux-kernel@...r.kernel.org
Cc:     jgg@...pe.ca, Liam.Howlett@...cle.com, david@...hat.com,
        willy@...radead.org, akpm@...ux-foundation.org,
        linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [RFC PATCH v1 0/1] possibile regression in the mm_types

On 3/12/23 15:41, Vincenzo Palazzo wrote:
> While I was testing the last rc1 version on my build machine
> I noticed that I was not able to build my nvidia driver and 
> also, the vboxhost/7.0.6_OSE driver while I was building [1].
> 
> So I noticed that this change was introduced in the 6.3-rc1 
> and proposed by [2]. However, I think I can miss important 
> around this change,  there may be some motivation to 
> have the `const` constraint here, 
> and this change needs to be done in the out-of-tree driver 

Yes it does. The out of tree drivers are responsible for keeping
themselves up to date.

Note also that this is an -rc kernel. NVIDIA is generally careful 
to keep its driver building against released kernels, but with -rc
kernels we often just wait until the kernel is released, in order
to avoid too much churn. Most customers don't (and shouldn't) run
an -rc Linux kernel anyway, is why.

Anyway, no, we don't patch the upstream kernel for this kind of 
issue. But thanks for thinking about it. :)

thanks,
-- 
John Hubbard
NVIDIA