linux-kernel - Re: [PATCH] dma-buf: add option text so it can be enabled by users

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]

Date:   Thu, 5 May 2022 14:03:15 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Oleksandr Tymoshenko <ovt@...gle.com>
Cc:     "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dma-buf: add option text so it can be enabled by users

On Thu, May 05, 2022 at 04:50:01AM +0000, Oleksandr Tymoshenko wrote:
> This reverts commit 3b32a592ea6e4 ("dma-buf: drop option text so users
> don't select it.") to allow users select DMA_SHARED_BUFFER option
> explicitly. This is required for out-of-tree modules that depend on
> dma-buf functionality, for instance drivers that rely on Google's Gasket
> framework.

We do not add code to the kernel for out of tree code, sorry.  To do so
would be a total nightmare and maintance impossiblity, and not something
you would want us to do as Linux overall would suffer.

As you well know, the correct solution is to get your code merged
upstream.  I have asked many times to get the gasket code upstream
properly, please do so to resolve problems like this.

thanks,

greg k-h