Originally posted by pdffs
View Post
Announcement
Collapse
No announcement yet.
ZFS On Linux Runs Into A Snag With Linux 5.0
Collapse
X
-
Originally posted by Zan Lynx View PostIf some kernel developers want to be silly about this then I'll be glad to dig out my grep, xargs, sed script that makes everything into ordinary EXPORT.
I had to use it some time in 2007 for the Nvidia binary.
Comment
-
Originally posted by garegin View PostJust shows how weak the corporate support for Linux is.
Originally posted by garegin View PostYou have a dozen multi billion companies fawning over Linux and making money off it, but they can't get their asses in gear to finish a filesystem in 10 years.
on the other hand there is bunch of crying idiots fallen to propaganda of obsolete by design zfs
btw, why useless zfs imbeciles didn't finish upstreaming their filesystem?
Comment
-
Originally posted by GrayShade View Postkernel_fpu_begin and kernel_fpu_end were switched to GPL exports in this commit from 2015.
2015 look at the Linux kernel mailing list where is a ZoL developer saying hey I need this GPL exported function as normal exported? There is not one.
Swaped to GPL exported symbols are from exported with a name starting with __ is in fact more permissive. GPL means this is for modules that are out of tree that are planning to merge ie GPL compatible license modules. __ at the start of name was prototype only not for out of tree modules at all. Using a __ starting function in Linux is the same as using a totally undocumented function with windows.
If you read the 2003 description __kernel_fpu_begin and __kernel_fpu_end are not for out of tree kernel modules at all. Yet ZoL is using these. This is path to trouble. Yes in 2003 developer ask about third party modules and is told no by Linus. Every time Linus is asked that question about __kernel_fpu_begin and __kernel_fpu_end the answer stays the same.
2 to 3 years is quite common migration allowance by the Linux kernel for kernel API. Something else to be clearly aware of with Linux kernel two exports in kernel space module API doing the same thing one is normally always deprecated this is the oldest one. If ZoL were watching the functions they were using they could have raise the issue to get this address with tones of time to spare.
There are api rules with the Linux kernel. Do remember the request to remove __kernel_fpu_begin and __kernel_fpu_end goes though because all the internal usage are gone and due to starting with __ they don't have to ask third party modules if they are using it.
Its one thing to be using a GPL exported symbol with the Linux kernel. Its a far deeper in the pits of hell to be using functions starting with __.
- Likes 3
Comment
-
Originally posted by kobblestown View PostWell, first of all, I get the impression that they did the extra work to make it not work.
Originally posted by kobblestown View PostIn my opinion ZFS provides the best solution for people who value their data above everything else, like I do.
Comment
-
Originally posted by aht0 View PostI think it as a case of upstream breaking the internal API's yet again
Originally posted by aht0 View Post, not caring in the least how it would affect downstream.
Originally posted by aht0 View PostNot that I actually particularly care, more power to FreeBSD.
Originally posted by aht0 View PostWhat particular efforts you would like to see already?
Originally posted by aht0 View PostThe problem has just been found..
Originally posted by aht0 View PostZoL's been developed constantly AFAIK.Last edited by pal666; 12 January 2019, 08:53 AM.
Comment
-
Originally posted by ferry View PostEven if ZFS code would be suddenly re-licensed, more is needed to get it upstream.Last edited by pal666; 12 January 2019, 06:04 AM.
Comment
-
Originally posted by GruenSein View PostThis issue is so representative of the weird attitude that seems to cloud the Linux development community.
Originally posted by GruenSein View PostIt is because many people have wanted to use ZFS for a long time
Originally posted by GruenSein View Postand it is one of the most advanced FSs for its purpose.
Originally posted by GruenSein View PostThey can choose to support a piece of software which would significantly extend the kernels capabilities.
Originally posted by GruenSein View PostAlso, I don't get why they don't simply restore the symbols that ZOL uses and mark them "deprecated" or whatever until the software depending on it can adapt (assuming there is an actual reason to remove them at all).
Comment
Comment