Slashdot Mirror


IP Theft in the Linux Kernel

Søren Schmidt was browsing through the 2.4.10 linux kernel source when he saw something that looked a bit familiar. Too familiar in fact. Søren is the principle developer of FreeBSD's ATA drivers, including FreeBSD's support for ATA RAID cards, and as he looked through the linux/drivers/ide/ files the sense of deja vu was overwhelming. Read on for more.

"They just took my code and filed off the copyright" said Søren. "This is clearest with the two header files hptraid.h and pdcraid.h. Compare these with FreeBSD's ata-raid.h, and just look at the similarities." And it's true that these two header files certainly look like a chopped up copy of the FreeBSD header, after a quick search-and-replace. "The reading of the RAID config from the disks is their own code, but is clearly "inspired" from our code," said Søren, "but that's encouraged by the license. It's the verbatim use of the other code without retaining the copyright that's the problem."

ata-raid.h, and the other files, are copyright Søren, and released under the three clause BSD license, which includes the restriction "Redistributions of source code must retain the above copyright notice". So using these files, or significant portions of them, in your own code, without retaining the copyright information, as has happened here, is prohibited.

You may be thinking "This is only a couple of header files, what's the big deal?". As Søren says "The problem here is that the structures in the headers is the whole story. That info tells how you read the proprietary struct off the disks, and was reverse engineered and documented by me after a lot of effort." Søren's intellectual property is tied up in those files.

Right now, Søren is in discussions with the authors of the Linux ATA drivers (employed by RedHat) to ensure that his copyright notice is returned to these and other files, and to ensure that this situation does not recur. And it is hoped that an amicable solution can be reached.

14 of 1,000 comments (clear)

  1. Licensing Problems? by Ted+V · · Score: 1, Flamebait

    I'm pretty sure BSD and Linux use different "copyleft" variants-- what impact will this have on the source code? Is Linux even allowed to use the BSD code without changing their License to match BSD's? I seem to remember the BSD license being slightly fascist...

    -Ted

  2. Say it ain't so! by TTop · · Score: 0, Flamebait

    OMG, Free software stolen from other Free software!! Everybody get ready to write your representatives about this terrible problem!

  3. MicroRedHat? by Valgar · · Score: 0, Flamebait
    My my Redhat is just acting more like microsoft every day....

    Makes me feel warm and fuzzy to see more and more people snatching code from FreeBSD though...It may not be in the limelight, but it must be good enough to inspire others to snag bits of it...

    Scuze me whilst I don my flame resistant gear...

  4. Jumping to conclusions.. by defile · · Score: 0, Flamebait

    Let's anticipate some comments:

    CLEARLY THIS SHOWS THAT LINUX IS INFERIOR AND HAS ALWAYS LEECHED OFF OF FREEBSD.

    ..and..

    RED HAT IS EVIL THEY'RE THE NEW MICROSOFT

    Never attribute to malice that which can be explained by stupidity.

    I'd bet 10:1 that the developers did this unintentionally rather than thought "HEE HEE WE'LL RIP OFF OPEN SOURCE CODE AND PUT IT IN ANOTHER OPEN SOURCE PRODUCT AND NO ONE WILL EVER KNOW!" *slobber*slobber*

    Wait until you hear both stories

  5. Well, who's the code pirate now? by Anonymous Coward · · Score: 1, Flamebait

    So much for respecting IP laws and copyrights, eh fellas?

    I mean, come on, keeping a copyright notice with a piece of code is infinitely easier than complying with the convoluted GPL, and the kernel hackers couldn't even do that?

    Shame on the hackers who filed off the copyright notice. I can't quite put blame on Linus, since he probably accepted the patch whole and assumed it was original code, but the people who did this have tarnished the entire Linux project.

    I'll giggle if MS is ever caught using GPL'd Linux code, seeing as the kernel maintainers no longer have a moral leg to stand on.

  6. Pretty sad, indeed. by dinotrac · · Score: 2, Flamebait

    First GNOME steals from khtml without attribution and now this.
    Oh -- and steals is the right term.
    This is one of the few ways you can steal BSD'd code. The license lets you do pretty much whatever you want.

    Proper attribution is not a big thing to ask, especially as meager compensation to a job well done. If the code's worth taking, it's certainly worth attributing.

    The worst part is that it allows the Microsofts of this world to say that free developers really aren't that different from themselves.
    Phooey.

  7. Re:Slashdot License Enforcement Bureau by MikeBabcock · · Score: 2, Flamebait

    A long time ago, Slashdot became the place for all news nerds might enjoy ... including Star Wars and the like. Feel free to edit your preferences to not include these stories.

    --
    - Michael T. Babcock (Yes, I blog)
  8. Why was he reading the Linux kernel? by mocm · · Score: 0, Flamebait

    Another question is why BSD people read the Linux kernel sources? The 2.4.10 kernel is pretty knew and I haven't even compiled it yet, so why are they so quick to read it. I haven't looked at BSD for a long time, except when we heard that they had a driver for bt848 cards and we found that some parts were very similar to ours, but maybe they used the same data sheets.

    Marcus

    --
    ***Quis custodiet ipsos custodes***
  9. Should't assume malicious intent by Xylantiel · · Score: 1, Flamebait

    License details are complicated, and certainly the last thing you want to worry with when you're trying to get code working. One would figure, BSD, linux, they're both open source, should be ok, just stick it in and work out the license thing later. And then you never get around to working out the license thing. (Which I assume means contacting the original author and saying "can you make this GPL for us Pleeeese?") I think I may have even done this once because I was unsure of the original program's license (this dual-licensing and related license stuff can really confuse things), I should check.

    I admit, though, that removing the copyright all together isn't the smartest temporary solution to the BSD-GPL conflict, but I can see how it might have seemed reasonable at the time (after too much coffee and 24hrs of banging your head against an undocumented interface, as this apparently is.)

  10. But isn't it.... by filmcritic · · Score: 0, Flamebait

    Waaa waaa, my FREE code was copied.....a FREE operating system stole another OS's FREE code. Does anyone else see that word? If you want to contribute to a project that will be given away, please don't expect your work to stay within it. Maybe a proper legal copyright of property should be investigated before charging out of the gates.

  11. Yeah, that's right. by Inoshiro · · Score: 4, Flamebait

    Just post anything at all about the situation as an AC and get modded really high.

    Where are the backups to your statements?

    This reminds me of when there was the large Exodus outage, and in the explanaion story an AC claimed to be some chick who was abuse my Taco (funny since Taco is in Michigan, Exodus cage is very not in Michigan, etc).

    Moderators: don't mod up stuff unless there is PROOF or this person has put a real name behind their statements. Posts like this are just trolls meant no spread disinformation.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  12. Re:This issue was resolved already by phkamp · · Score: 1, Flamebait

    Wouldn't it carry a lot more weight if Søren said that it was resolved ?

    Poul-Henning Kamp
    The other Danish FreeBSD viking

    --
    Poul-Henning Kamp -- FreeBSD since before it was called that...
  13. Mr Kettle, meet Mr Pot! by thorpej · · Score: 4, Flamebait

    Check out the very first revisions of the Linux compatibility module in FreeBSD. It looks quite a lot like the NetBSD Linux compatibility module of the same vintage, which was written by Frank van der Linden and committed to the NetBSD source tree (which was the first public release of that code) -- yet all the files say Soren Schmidt at the top.. Amazing!

    --
    -- Jason R. Thorpe, NetBSD and FreSSH developer
  14. Why was this important? by LinuxATA · · Score: 2, Flamebait

    Congrats Nik, Nice job on hurting FreeBSD. We will see where the so called IP borrowing leads to in the near future. Specifically things like 48-bit LBA, MMIO VirtualDMA under taskfile rules, Mt Rainier GAA decoding and DeIcing, and the new Ultra133. The real kicker will be when I publish the correct and legal headers w/ Linux ATA Development and Promise Copyrights and GPL and require that usage of the information carry the copyrights and terms of usage. This will also include a set of headers for HighPoint, and Silicon Image (formerly CMD). Since I know for a fact that FreeBSD can not do CMD RAID, nor has it heard about it. I am only here to validate your child-like response, as a future reference point to enjoy you choking down the crow you are spreading. I have no issues with Soren (mispelled sorry), but your mistakes will have a price. I hope you feel really good about yourself, because you are a big man. Only because you wanted to thumb us, the Linux Community, in the eye, is the reason you thought it would be useful to paint the world a bloody gaping pie-hole. I really hope you enjoy your time of glory and fame, because you have failed to address my request to clear my name from the issues. A price that would have been cheap pay earlier but, not affordable now. For now it is time to take FreeBSD and all the other variations of BSD to school, watch learn and I will require that my work and my IP be acknowledged in all of these from now on out. I understand that this may prevent you from ever having support and access to some really cool stuff coming down the pipes, because of the License you will be require to acknowledge where and who you are borrowing IP. Please have a good day. Respectfully, Andre Hedrick Linux ATA Development