There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Linux 6.6 To Better Protect Against The Illicit Behavior Of NVIDIA's Proprietary Driver

Luis Chamberlain sent out the modules changes today for the Linux 6.6 merge window. Most notable with the modules update is a change that better builds up the defenses against NVIDIA’s proprietary kernel driver from using GPL-only symbols. Or in other words, bits that only true open-source drivers should be utilizing and not proprietary kernel drivers like NVIDIA’s default Linux driver in respecting the original kernel code author’s intent.

Back in 2020 when the original defense was added, NVIDIA recommended avoiding the Linux 5.9 for the time being. They ended up having a supported driver several weeks later. It will be interesting to see this time how long Linux 6.6+ thwarts their kernel driver.

BURN ,

I’d rather have working proprietary drivers than broken open source ones, which seem to be our only options. I find it real hard to side with Linux here as they’re going to make performance worse for a platform that already struggles.

And people wonder why Linux will never take off on the desktop. Stuff as basic as this will make sure anyone semi-casual about pc use will have issues with Linux.

anon5621 ,

Or maybe to keep doing social pressure on nvidia and make them feel guilty ,that they finally realse and did support of open version drivers not only for gtx 1650+ and fot more old cards.Because their source codes was published when hackers hacked their infrastructure and leaked source code.

SSUPII ,

Just the existence of CUDA means Linux must remain a target for Nvidia.

Also, this can be quite easily compared to Windows changing their driver’s structure and functionality. And Microsoft did it many times in the past.

SkyeStarfall ,

Or maybe we shouldn’t just accept trillion dollar companies doing whatever the fuck they want?

Nvidia is clearly on the wrong here, and infringing on copyright. Do you want to set the precedent that companies can just ignore copyright? Meanwhile when we certainly can’t ignore theirs?

Maybe we should hold the companies to a higher standard. And not roll over and give in basically as soon as they do something we don’t like, compromising the foundation and good parts of what we already have, in this case Linux. Open source and GPL is the lifeblood of Linux, it’s what makes it as good and useful as it is.

rmstyle ,

That’s just such a great image!

hlqxz ,

Made me lol

TimeSquirrel , (edited )
@TimeSquirrel@kbin.social avatar

Yeah they'd do that with a card that looks like it's from 2003 with those classic dual DVI ports. Stole it right out of some kid's Quake 3 box. Try that with a 4090.

agressivelyPassive ,

Give the gigantic heatsink, that might actually work just fine. The PCI brackets are just stamped aluminium after all.

TenTypekMatus ,
@TenTypekMatus@lemmy.world avatar

What cards are supported because GF 1660s is PITA without proprietary drivers.

MDKAOD ,

TAINT_PROPRIETARY_MODULE & GPL Condom has to be intentional double entendre right?

argv_minus_one ,

Lousy criminals. NVIDIA, I mean. If I wrote code like that, I’d be dragged in front of a judge and made to answer for breaking the DMCA. But if you’re a big, rich company, the government won’t touch you.

Rayspekt ,

Can someone ELI5 what this is about? Why does Nvidia wants to access parts if the Linux kernel and why are linux kernel maintainers against it? Wouldn't it be good if Nvidia uses more open-source stuff?

SSUPII ,

Open source software is given with specific licenses. The Linux kernel is made of many smaller open-source components that each can have their own license. Some of the licenses used disallow the partial or full usage of the licensed software or components in proprietary settings, or in general given usage for specific cases only (in this case, the Nvidia driver using components they are not licensed to use.).

autotldr Bot ,

This is the best summary I could come up with:

The Linux 6.6 modules infrastructure is changing to better protect against the illicit behavior of NVIDIA’s proprietary kernel driver.

Most notable with the modules update is a change that better builds up the defenses against NVIDIA’s proprietary kernel driver from using GPL-only symbols.

Given that symbol_get was only ever intended for tightly cooperating modules using very internal symbols it is logical to restrict it to being used on EXPORY_SYMBOL_GPL and prevent nvidia from costly DMCA circumvention of access controls lawsuits.

Luis Chamberlain further added in today’s pull request: “Christoph Hellwig’s symbol_get() fix to Nvidia’s efforts to circumvent the protection he put in place in year 2020 to prevent proprietary modules from using GPL only symbols, and also ensuring proprietary modules which export symbols grandfather their taint.

The circumvention tactic used by Nvidia was to use symbol_get() to purposely swift through proprietary module symbols and completley bypass our traditional EXPORT_SYMBOL*() annotations and community agreed upon restrictions.”

Back in 2020 when the original defense was added, NVIDIA recommended avoiding the Linux 5.9 for the time being.

The original article contains 476 words, the summary contains 174 words. Saved 63%. I’m a bot and I’m open source!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •