this post was submitted on 30 Aug 2023
104 points (100.0% liked)

Linux

7943 readers
346 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] baggins@lemmy.ca 16 points 1 year ago (4 children)

Hmm I don't really understand any of this. Wish this one came with an ELI5

[–] LPThinker@lemmy.world 25 points 1 year ago (1 children)

I can't claim full understanding, but what I took away from it was that NVIDIA somehow ended up using GPL-licensed code in their proprietary drivers, possibly in a way that could incriminate the Linux kernel if not handled properly. My best guess (as someone with no kernel programming experience) is that NVIDIA sometimes contributes code directly to the Linux kernel that exists solely to support their proprietary drivers (the shims mentioned in the article). Apparently, these shims were exporting GPL-licensed code for use inside the proprietary drivers, which would be a violation of the GPL (unless NVIDIA made the source code for their proprietary drivers freely available in compliance with the GPL).

TLDR: (I think?) NVIDIA essentially infected the linux kernel with license violations to support their proprietary drivers, and the linux kernel devs are working to excise the violations and prevent anything like that going forward.

[–] superminerJG@lemmy.world 10 points 1 year ago (1 children)

well, if that's true I should be allowed to email NVIDIA and ask for their driver code

[–] ggppjj@lemmy.world 6 points 1 year ago (1 children)

You're allowed to email anyone you want.

[–] Ajen@sh.itjust.works 2 points 1 year ago (1 children)

That's not what the restraining order says

[–] ggppjj@lemmy.world 1 points 1 year ago

And you're gonna listen to that silly 'ol piece of paper over me, a complete stranger online?

[–] IHeartBadCode@kbin.social 20 points 1 year ago

Tainted kernels are not supported. Kernel devs aren't spending time to fix bugs that come from a taint (uses blobs of code that are not open sourced) driver. Because the closed drivers can wreck all kinds of havoc and the kernel devs are helpless to fix the actual "source" of the problem.

There's been all kinds of ways for the kernel to detect tainted binaries. nVidia is notorious for trying to circumvent that detection so that engineers can sit there and blame the kernel for failures.

nVidia has been a massively shit company to the open source community. If I had a list of most anti FOSS companies to ever exist, nVidia would be right behind SCO, with like TiVo behind nVidia. I know it's hard but people who enjoy open source projects shouldn't do business with the company. But if you got to have a nVidia card so be it, but I cannot NOT recommend nVidia enough.

[–] dan_linder@lemmy.world 20 points 1 year ago (1 children)

I'm not an expert but this is what I understand from a podcast l listened to (https://twit.tv/shows/untitled-linux-show):

There's a subset of Linux users who desire or need GPL compliant environments for they purposes (personal or work related).

There's a kernel flag that is set to track if the drivers or gas loaded are also 100% GPL.

NVidia wrote their own video driver which is NOT GPL compliant, so as soon as they are loaded the kennel flag is set to "not GPL". To get around the simple checks for GPL compliant drivers, NVidia wrote a wrapper (a "condom") to lie that it was GPL-compliant when it was violating the GPL flag meaning.

The Linux 6.6 release apparently has more protections to keep NVidia from working around the GPL check. (For now...)

[–] baggins@lemmy.ca 4 points 1 year ago (1 children)

Interesting. I wonder why Nvidia cares.

[–] d3Xt3r@lemmy.world 9 points 1 year ago (1 children)

nVidia doesn't, but lawyers do. License violations are not cool, regardless of who does it.

[–] baggins@lemmy.ca 1 points 1 year ago

They must care otherwise why would they bother to hack the GPL flag. 🤷

[–] ono@lemmy.ca 12 points 1 year ago

Disclaimer: I haven't looked at the code.

It looks like Nvidia's proprietary driver was caught circumventing measures that keep proprietary code from mixing with GPL code in the kernel, deliberately violating the kernel's license. The kernel maintainers are responding by adding more restrictions.