linux-kernel - Re: [PATCH] staging: gasket: remove it from the kernel

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: <842fccfa-30a6-d40a-bf9a-8e7dea355666@siemens.com>
Date:   Thu, 25 Mar 2021 15:57:56 +0100
From:   Jan Kiszka <jan.kiszka@...mens.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Rob Springer <rspringer@...gle.com>,
        Todd Poynor <toddpoynor@...gle.com>,
        Ben Chan <benchan@...omium.org>, Richard Yeh <rcy@...gle.com>,
        linux-staging@...ts.linux.dev, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: gasket: remove it from the kernel

On 25.03.21 15:52, Greg KH wrote:
> On Thu, Mar 25, 2021 at 03:46:10PM +0100, Jan Kiszka wrote:
>> On 15.03.21 17:10, Rob Springer wrote:
>>> Acked-by: Rob Springer <rspringer@...gle.com>
>>>
>>>
>>> On Mon, Mar 15, 2021 at 8:44 AM <gregkh@...uxfoundation.org> wrote:
>>>>
>>>> From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>>>>
>>>> As none of the proposed things that need to be changed in the gasket
>>>> drivers have ever been done, and there has not been any forward progress
>>>> to get this out of staging, it seems totally abandonded so remove the
>>>> code entirely so that people do not spend their time doing tiny cleanups
>>>> for code that will never get out of staging.
>>>>
>>>> If this code is actually being used, it can be reverted simply and then
>>>> cleaned up properly, but as it is abandoned, let's just get rid of it.
>>>>
>>>> Cc: Rob Springer <rspringer@...gle.com>
>>>> Cc: Todd Poynor <toddpoynor@...gle.com>
>>>> Cc: Ben Chan <benchan@...omium.org>
>>>> Cc: Richard Yeh <rcy@...gle.com>
>>>> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>>
>> OK, so is there a plan of the HW vendor to improve the user experience
>> for this hardware? Is there a different software architecture in sight
>> which will not need a kernel driver?
> 
> What hardware vendor makes this thing?  What systems require it?  And
> why can't you use UIO instead?
> 
>> Just wondering loudly while fiddling with dkms packages and starring at
>> the code diffs between what was removed here and what I still have to
>> install manually from remote sources.
> 
> Where are the remote sources for this thing and why didn't they ever get
> synced into the kernel tree?
> 

Very good questions, and I'm curious to learn if someone in CC can
answer them.

I was just starting to play with this thing, using Google's binary
Debian repo. But that is not... optimal. Even more when thinking beyond
a try-out stage.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux