16 ms·
A regression is the kernel not giving the same result with the same user space
- oinkush 9y agoThat's bonkers. This sounds like a reasonable definition, but quickly it turns out to be completely insane. Lets start somewhere far away from Linux, as far away as possible. Windows XP SP2 blocked access to raw sockets for non-administrators. It also blocked access to \Device\PhysicalMemory to all user-mode code, regardless of the user running it. Linus would say this is a regression. Fine, lets try something else. I wrote some C++ code that violated the strict aliasing rule. It worked for me 15 years ago when compilers weren't optimizing so aggressively. I tried to compile it using the latest GCC and got strange results. Should I file a bug with GCC? Sounds like a bug according to Linus's definition. It used to work and now it doesn't. Who cares that I violated the rules in the first place? "Now, hold on" I head you say. "We were talking about kernel and user, not compiling C++ code. That completely different!" Well, sure, it's different. But it's also similar. I maintain that the point is the same, but lets go back to Windows for a second. Lets say we have a program that used to parse the PEB.Ldr structs for whatever reason. In Windows 8 they went through a major change. This program no longer works. Is this a regression? Raymond Chen has had to deal with this nonsense enough. For example: https://blogs.msdn.microsoft.com/oldnewthing/20031223-00/?p=41373/ https://blogs.msdn.microsoft.com/oldnewthing/20031223-00/?p=... And his blog is full of example of dumb programmers counting on internal, undocumented, subject to change and actually changing structs. If you, the reader, think you're very clever and say it's dissimilar because the LDR structs are user- rather than kernel-owned and -managed structs I give you the same example with EPROCESS. Take a look: http://terminus.rewolf.pl/terminus/structures/ntdll/_EPROCESS_x64.html http://terminus.rewolf.pl/terminus/structures/ntdll/_EPROCES... The point is that "breaking" code that does things it wasn't supposed to to should be - and can reasonably be - considered a regression. The very first example - with raw sockets - may be considered a regression, though I prefer the term "breaking change", since "regression" is a form of a bug, and this is not a bug, even if you think it's a bad policy. The other examples don't even fall under the "Breaking change" the category. Nothing THAT WAS GUARANTEED was changed. If you counted on things that nobody promised you that would remain the same to actually remain the same that's your problem. And back to Windows for a moment. Lets say someone uses the UpdateProcThreadAttribute API to set the mitigation policy on a child process it creates. Instead of only setting the bits he want (like PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON to force ASLR on all modules, PROCESS_CREATION_MITIGATION_POLICY_WIN32K_SYSTEM_CALL_DISABLE_ALWAYS_ON to block win32k calls and PROCESS_CREATION_MITIGATION_POLICY_EXTENSION_POINT_DISABLE_ALWAYS_ON to prevent injection by the system of a couple sorts of plugins) he goes on to pass 0xFFFFFFFFFFFFFFFF. He wants all the possible mitigations! He's that smart! Then comes along Windows 10 with its binary signature policy mitigation and (0x00000003ui64 << 44) is interpreted as PROCESS_CREATION_MITIGATION_POLICY_BLOCK_NON_MICROSOFT_BINARIES_ALLOW_STORE. His child process can't load any of his DLLs. Clearly a regression under the Linus rules. Obviously not a regression. From what I understand the situation is very similar to this. I'm quoting from John Johansen message on the thread: It is entirely possible to use the 4.14 kernel on suse without having to modify policy if the policy version/feature set is pinned. However this is not a feature that suse seems to be using. Instead suse policy is tracking and enforcing all kernel supported features when they become available, regardless of whether the policy has been updated. The clever folks at SUSE decided to enable all the protections/mitigations/features/whatever of AppArmor, including those that didn't even exist when they wrote this stupid policy. It's completely reasonable to think that a program restriction infrastructure's new feature won't restrict programs more. Sure. If it does that's a regression.
- signa11 9y agoand later he clarifies it thusly: ''' People should basically always feel like they can update their kernel and simply not have to worry about it. I refuse to introduce "you can only update the kernel if you also update that other program" kind of limitations. If the kernel used to work for you, the rule is that it continues to work for you. '''
- kalleboo 9y agoHere's a link to that reply for those who don't want to spend a bunch of time browsing the thread to find it: http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html It's a very good summary of the Linux kernel userspace compatibility policy.
- worldsayshi 9y agoFor user experience reasons that seems like a extremely sensible principle. But doesn't this make fixing some security issues impossible?
- dangoor 9y agoLinus calls out the fact that there are some times in which breakage is unavoidable, but that should only be after trying very hard to avoid breakage.
- Bartweiss 9y agoI do think there's an enormous difference between breaking changes of the form "hey, this is important and it's going to break shit, we can't find an alternative, be prepared" and "oops, we broke it, good luck!" Rare, planned breaking changes are a reasonable answer to improving security and usability. Python 2 -> 3 and the Mac PowerPC switch both seem like examples: they caused real inconvenience, but they were very clearly announced and had real benefits. Sporadically screwing over users, though, really is unforgivable. Last time I updated Windows it escalated a minor graphics card issue from "automatically recovers" to "kills your session to collect error data". It's like the patch author comes into my house once a week and unplugs my machine, just for their own amusement.
- mar77i 9y agoIt's uncannily similar to him going nuclear on a guy called Mauro in 2012. https://lkml.org/lkml/2012/12/23/75 https://lkml.org/lkml/2012/12/23/75
- mar77i 9y agoIt seems to be kind of a running gag, and I wonder what else do people imagine is what the kernel is supposed to satisfy than as many other people's expectations as possible?
- jordigh 9y agoMercurial, made by another (in my opinion) much more well-spoken kernel hacker, is what really introduced me to the concept that you do not break interface for downstream users, no matter how wrongly you may think they are using the interface. It’s an attitude that is difficult to convey because software developers always want to have the freedom to “improve” their own software, even at the possible cost of breaking something for some users (and worse, even telling users that they shouldn’t have been doing that in the first place). I keep going back to this blog post which I wish more people agreed with (Steve Losh is another person influenced by Mercurial): http://stevelosh.com/blog/2012/04/volatile-software/ http://stevelosh.com/blog/2012/04/volatile-software/
- _Codemonkeyism 9y agoFor various reasons I would not go back to Java, but that was wonderful, your very old code still worked with newer versions, nothing broke during upgrades (even when behind deprecation one version).
- pjmlp 9y agoWe do enjoy breaking changes every now and then. :) http://www.oracle.com/technetwork/java/javase/jdk-relnotes-index-2162236.html http://www.oracle.com/technetwork/java/javase/jdk-relnotes-i... Of course, they are never at the level of a Python 3 release.
- _Codemonkeyism 9y agoYes, but compared to e.g. Scala breaking changes in Java are heaven, thanks :-)
- cgdub 9y agoThere's a great talk about backwards compatibility in Java by Brian Goetz: https://www.youtube.com/watch?v=2y5Pv4yN0b0 https://www.youtube.com/watch?v=2y5Pv4yN0b0
- 9y ago
- eeks 9y agoAhh, nothing like a good rant with my morning coffee !
- OJFord 9y ago> - we don't cause regressions Clearly false. > and the corollary is that when regressions do occur, we admit to them and fix them, instead of blaming user space. Clearly not a corollary...
- skywhopper 9y agoYour comment is clearly willfully obtuse and clearly serves no purpose.
- bauerd 9y agoThese are normative, not descriptive statements.
- OJFord 9y agoHow is it normative? Although that's a bit of a rabbit hole, since presumably you won't allow me to appeal to the definition of 'normative'. Torvalds lambasts a developer for making a mistake, swears at him, and tells him the first rule of kernel development is that you don't make mistakes. Great.
- bauerd 9y ago>we should not cause regressions >and the corollary is that when regressions do occur, we should admit to them and fix them, instead of blaming user space Clearly he is aware that they did cause a regression as the mailing list post he responds to would not exist otherwise. Reading these two statements descriptively renders him an idiot.
- deleted 9y ago[deleted]
- ptero 9y agoHe lambasts the developer not for making a mistake, but for making a mistake and refusing to admit that this is a mistake. That is very different.
- leemike 9y agoMany good summaries of the Linux kernel userspace compatibility policy are available. Search for them.
- orcdork 9y agoIn any other kind of social/business arrangement he would be politely but firmly escorted out, possibly by security, for this kind of behavior. Being right or wrong is irrelevant.
- granos 9y agoLinus or the contributor? I can see an argument for either.
- grenoire 9y agoYou know what? I'm glad he is doing it this way. Hard to imagine the kernel getting to this point if he did not communicate and scrutinise like this.
- teamhappy 9y ago> Hard to imagine the kernel getting to this point if he did not communicate and scrutinise like this. Not hard to imagine at all. He could exercise the same amount of authority without losing his shit and would get exactly the same result. It's one of his flaws and that's fine, but arguing that this kind of behaviour is somehow helpful is just ridiculous.
- grenoire 9y agoTo me, it's just reminiscent of the movie Whiplash. Sometimes it helps to lash (excuse the pun) out.
- stestagg 9y agoI can tell you, this sort of discussion happens in many Business settings, and doesn’t often end up involving security
- vacri 9y agoYou need to work in a wider variety of workplaces, if you genuinely believe that. Perhaps put another way: were Jobs or Ballmer ever escorted out for their obnoxious behaviours?
- Nokinside 9y agoLinus being salty is like soap opera for HN. Pleasant and good mannered application programmers gasp when real men (aka systems programmers) communicate at each other.
- deleted 9y ago[deleted]
- delroth 9y agoAs much as I think the general principle of "no userspace visible change" is great, I can't make up my mind on whom I agree with the most in this specific instance. My understanding is that some distros (e.g. OpenSUSE) ship with AppArmor in a whitelist mode where things have to be explicitly permitted by policy, otherwise they're denied by default. AppArmor introduced a new class of actions that wasn't there before, and with these restrictive policies it's causing daemons to crash (because it gets auto-denied). The whole point of these policies is to not expose new attack surface if it's not needed by the software. It's going to break whenever AppArmor will start supporting more checks, unless policies get pinned to a specific version of AppArmor. But AppArmor doesn't currently support this (they refer to it as "features ABI" in the thread). WAI?
- bonzini 9y agoIt's not clear to me either. From John's replies it also seemed to be an OpenSUSE bug. On the other hand, if it's bad enough it certainly makes sense to treat it as a kernel bug. The difficulty lies in finding where to draw the line.
- wolfwyrd 9y agoIt's laid out further in the thread [1]. The key quote comes from Thorsten: > All that afaics doesn't matter. If a new kernel breaks things for people > (that especially includes people that do not update their userland) > then it's a kernel regression, even if the root of the problem is in > usersland. Linus (CCed) said that often enough [1] http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html
- __david__ 9y agoLinus's followup post later on in the thread explains his position in more detail and is a pretty good read: http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02487.html
- piker 9y agoInteresting. > Behavioral changes happen, and maybe we don't even support some feature any more. There's a number of fields in /proc/<pid>/stat that are printed out as zeroes, simply because they don't even exist in the kernel any more, or because showing them was a mistake (typically an information leak). But the numbers got replaced by zeroes, so that the code that used to parse the fields still works. The user might not see everything they used to see, and so behavior is clearly different, but things still _work_, even if they might no longer show sensitive (or no longer relevant) information. I'm not sure I prefer the described result. If my application depends on some of those zero'd fields, it seems like that has potential to cause serious debugging problems, as opposed to just causing an error on the parse.
- chii 9y ago> If my application depends on some of those zero'd fields, it seems like that has potential to cause serious debugging problems, as opposed to just causing an error on the parse. if your app didn't used to handle the 'zero' case (assuming zero was a "valid" value for said field), then the app was poorly written and would'be been broken in the first place. However, if the app _did_ handle the 'zero' case, then the app continued to work! The end user would've been none-the-wiser about the change (mostly), and some time later, the app could be upgraded to ignore those known fields. Causing a parse error would mean the app stopped working altogether. Much worse a result for the end user.
- piker 9y agoI guess that depends on whether or not zeros were valid in the first instance. My post assumed they were. I agree with your point if zero would be outside of the valid range in the first instance.
- TempleOS 9y ago#!/bin/bash #This prints random words from the Linux dictionary. echo "$(shuf -n 32 /usr/share/dict/words --random-source=/dev/urandom | tr '\n' ' ')"
- bjourne 9y agoJohn Johansen will survive. Linus has made it incredibly damn clear what "no user space regressions ever" mean. See f.e the similar rant from 2012: https://lkml.org/lkml/2012/12/23/75 https://lkml.org/lkml/2012/12/23/75 And it is his kernel so it is his rules. John Johansen admitted he messed up (http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02539.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02539.html) and promised to handle things better in the future so all is well.
- deleted 9y ago[deleted]
- jancsika 9y agoIt's sad that often the only thing that stops a developer from spinning out more yarns of rationalization is Linus coming in and barking the first rule of kernel development at them. It's like Fight Club, except instead of fighting all the characters keep asking Brad Pitt's character why they can't perform a one-man show on Broadway about fight club.
- leeoniya 9y ago> Linus has made it incredibly damn clear what "no user space regressions ever" mean out of curiosity, how does a policy like this translate to microkernel OSes (e.g. Redox) where most everything runs in userspace?
- olewhalehunter 9y agoshhh just get out the popcorn and enjoy the rantings of an egomaniac who wrote a glorified DOS extender for an outdated time-sharing system
- sctb 9y agoLet's not join in with rantings of our own? https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- 9y ago
- raverbashing 9y agoI'm glad Linus has this attitude and it is unfortunate it's not present in some other places Though it is annoying if you're at the receiving end of it, own up (the opposite of what the patch author was doing)
- Cthulhu_ 9y agoAnnoying and hurtful, yes, but at the same time, he's not wrong - you fucked up, you did bad and you should feel bad. The upside of this rant too is that the author is not "fired", as such, but told to shape up or gtfo. In a lot of companies, mistakes are accepted, fixed, and forgiven without adding a bit of emotion to it. I think adding this kind of emotion will have a bigger impact and will make the receiving end do better.
- sepeth 9y agoHow? Really? Ask that to a child beaten up by their parents in the street. I am sure that child won't make the same mistake again. I am not interested about if Linus is right or wrong, many other people have done that already. I am more interested the way that he speaks. I am gonna go ahead and say it. The way he speaks in this email is ugly, wrong, and should never be encouraged. The language we use is important, even though sometimes it takes more effort, love takes effort, good things take effort, and good communication takes effort too. We should at least try to be nice. Otherwise life would be kak.
- raverbashing 9y ago> The way he speaks in this email is ugly, wrong If that's the way problems get solved, then he's right in using it If you ask nicely and people don't do it, or keep ignoring it then you up the tone
- sepeth 9y agoAnd to the people who actually help you. Not only your users are important, people who help you are also important. > If you ask nicely and people don't do it, or keep ignoring it then you up the tone I am sure it can be done much better with a little effort. Being smart, or being someone who has done something important shouldn't exempt you from being nice to other people.
- jokoon 9y agoEli5, What is kernel regression? Does he mean breaking backward compatibility?
- santoshalper 9y agoA change was made to the kernel that broke some applications - this is called a regression (a bug introduced in an update). The developer who made the change that caused the bug in the downstream application tried to argue that it was the application's fault, not the kernel. Linus then calmly and politely reminded him that the official policy of kernel development is that they never introduce changes that break applications.
- Beltiras 9y agoYou only say "calmly and politely" because Linus is a known pottymouth and frequently "tears people a new one". An email like this might get you demoted or fired in some workplaces.
- fcbrooklyn 9y agoYes, effectively.
- pluma 9y agoregression = "it worked before, it doesn't work anymore"
- how_obnoxious 9y agoHow obnoxious.
- snvzz 9y agoIf the interface was simple, such as seL4's, we wouldn't have to see it become a clusterfuck which, to maintain userspace compatibility, can't be fixed. It will only get worse over time.
- dingo_bat 9y agoI'm always eager to read Linus's rants. I wish more of my coworkers were like him. I hate the environment where nobody reacts strongly to anything! If somebody fucks up hard and refuses to own up, I (or whoever's in charge) should be able to shout at them. It's only natural.
- hatred 9y agoBecause its hard to say the least. This sums it up: https://news.ycombinator.com/item?id=15610108 https://news.ycombinator.com/item?id=15610108
- andyjohnson0 9y agoI disagree. To me he usually comes across as an asshole, albeit an extremely smart and accomplished one. A working environment where the person at the top can be relied upon to react to human failings with an aggressive, sweary [1] rant is not somewhere I ever want to work. [1] I'm aware that use of profanity in everyday speech is common in Finland. I don't mind swearing per se, but I find its over-use a bit tedious.
- JumpCrisscross 9y agoI don’t. He’s effectively using certain emotions to clearly broadcast his point.
- andyjohnson0 9y agoUnderstood. But what happens if everyone in an organisation reacts in the same way? Is it a useful leadership style?
- deleted 9y ago[deleted]
- vidoc 9y ago> [1] I'm aware that use of profanity in everyday speech is common in Finland. I don't mind swearing per se, but I find its over-use a bit tedious. Actually what you are unaware of, might be that the use of profanity in everyday speech is actually very common pretty much anywhere in the world other than in the US&A where mince words and puritanism are still king.
- alkonaut 9y ago> "We simply do not break userspace" Wish this would be a goal for more of the application environment on Linux than just the kernel.
- fauigerzigerk 9y agoIndeed. I upgraded a Ubuntu installation a while ago. The network just stopped working because the developers of NetworkManager had decided that NM should no longer manage wired network connections on some Ubuntu configurations. That is just a crappy attitude and I have to say NetworkManager is generally one of the buggiest and most unreliable pieces of software I have ever used. And I'm actually making a great effort to be polite here.
- danschumann 9y agoWhat does "regression" mean in this sense?
- draw_down 9y agoHe is right. I’m sorry if he says “fuck” too much or whatever.
- thriftwy 9y ago"the first rule of kernel development" is so awesome to have compared to what e.g. distros do with GLIBC. Remember when they changed behavior of memmove, which broke user code including the damn flash player, and then blamed users for that? E.g., Drepper seems to be the person who is an opposite of Linus.
- whack 9y agoI can understand and empathize with both perspectives here. On the margin, is it better to have consistent interfaces, or simpler implementation? This debate reminds me of the worse-is-better design style, which is supposedly at the root of Unix's success. https://www.jwz.org/doc/worse-is-better.html https://www.jwz.org/doc/worse-is-better.html (copy-paste the link in a new tab. Do not click on it) The worse-is-better philosophy is only slightly different: - Simplicity-the design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design. - Correctness-the design must be correct in all observable aspects. It is slightly better to be simple than correct. - Consistency-the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency. - Completeness-the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface. Early Unix and C are examples of the use of this school of design, and I will call the use of this design strategy the ``New Jersey approach.'' I have intentionally caricatured the worse-is-better philosophy to convince you that it is obviously a bad philosophy and that the New Jersey approach is a bad approach. However, I believe that worse-is-better, even in its strawman form, has better survival characteristics than the-right-thing, and that the New Jersey approach when used for software is a better approach than the MIT approach.
- aeorgnoieang 9y agoThat "worse-is-better" link redirects to a rather rude Imgur image. I'm guessing the author dislikes HN. Following the same link from a Google result did not redirect to the Imgur image.
- macinjosh 9y agoLinus is right but his choice of words seems unprofessional bordering on harassment. Almost sounds childish in parts, especially the ALL CAPS screaming he does. Its cool to be passionate but also be civil.
- catpolice 9y agoI think of the line from the Big Lebowski a lot: "You're not wrong, Walter. You're just an asshole."
- arkadiytehgraet 9y agoLinus has addressed so called "professionalism" several times, one of the best discussions is here: https://lkml.org/lkml/2013/7/15/427; https://lkml.org/lkml/2013/7/15/427; Linus's point of view on overall "professionalism": https://lkml.org/lkml/2013/7/15/547 https://lkml.org/lkml/2013/7/15/547
- sameyepatch 9y agoGoddammit, I wanted to go to sleep early tonight.
- bischofs 9y agoSomeone needs to codify this shit for when he leaves. Its surprising that he still needs to scream at people after two decades of kernel work. I don't have a lot of faith that whoever comes after him will be as proud of the kernel as he is given they just inherited most of it. Succession is a weird concept with linux but the fact that it has always been more stable than the other OS' is I think the main reason it is been so successful in the internet age. An example of a failed succession is Tim Cook; the guy is the complete opposite of Jobs. Just take a look at the apple website nowadays. A product guru would not sell three generations of iphones that are all cannibalizing each other and lack any real differences.
- s_dev 9y agoI don't think the Cook/Jobs comparison is fair. It's always been well understood the the same people who are typically good are starting companies aren't typically the best people to run them once they achieve a certain scale.
- deleted 9y ago[deleted]
- Torwald 9y agoHow are "three generations of iphones" "cannibalizing each other and lack any real differences" ? Care to elaborate?
- proginthebox 9y agoWe will hopefully have a new kernel written in Rust by someone new.
- scott_karana 9y agoGod, I hope not. Ground-up rewrites (when they even succeed) typically lose features, performance, and security, since they don't have the benefit of 20+ years of correcting mistakes. Plus you lose all your contributors. However, Rust is linker compatible with C, and can be runtimeless, so rewriting the kernel piecemeal over time instead could be great. ;-)
- lightedman 9y ago"a return to a former or less developed state." See, it's the fact that Linus doesn't even know the real definition of 'regression' that makes me think I cant' trust him or anything he produces. That level of idiocy is simply intolerable.
- phaemon 9y agoIt is a "less developed state". Software that worked, no longer works. That's what a software regression is. The fact that you don't even understand the definition you quoted makes me...etc etc
- lightedman 9y agoNo, a software regression is when you fix a specific problem and re-introduce it later on in a code revision. That's literally the definition of a regression bug. That definition has been around since the 70s and I don't think any of you have the designated rights or privileges to change or modify or append that definition.
- phaemon 9y agoNonsense. You don't have the designated rights or privileges to lock down the meaning of anything. The definition as I gave it was used in the 1975 edition of "The Mythical Man-Month". Is that good enough for you?
- lightedman 9y agoNope. The definition I gave comes from the original hackers from TMRC at MIT. As in, the people who also defined the term 'hack.' Which predates yours by about 20-ish years.
- fernandotakai 9y agouh, what? software regression is a well known term that is widely used to say "something used to work and it doesn't work now" https://en.wikipedia.org/wiki/Software_regression https://en.wikipedia.org/wiki/Software_regression
- butterisgood 9y agoSame view as EVERY kernel regression it seems.
- megaman22 9y agoLinus is such a breath of fresh air. I'll take an honest, emotional, impossible to misconstrue, ass-chewing over the alternatives. Too often there's an avoidance of straightforward, blunt speech that conveys exactly what is meant. I really have better things to do than try to parse nonspecific beating-around-the-bush and deconstruct word-castles.
- 13of40 9y agoI think a good leader could get the point across without resorting to bullying.
- otabdeveloper1 9y agoYour comment deserves a 4chan-style meme arrow: > getting an incompetent bozo fired > "bullying"
- adamnemecek 9y agoThe guy does seem like he was shifting blame around.
- WhitneyLand 9y agoI think most people agree with you, he screwed up more with his handling of the situation. Occasional good faith mistakes shouldn’t get people in trouble, but he was weaseling. The interesting issue is more of leadership. 1) Is it possible to get equally direct and effective results in a different style? 2) Does Linus care about the answer to question (1), or would he act out of emotion even if he knew knew there was a equal or more productive way?
- ams6110 9y agoNothing in TFA is bullying. Impolite, rude, brash yes.
- vorpalhex 9y agoI wouldn't call it bullying. He isn't attacking the committer personally or due to anything outside the issue. He isn't hounding the committer. Bluntly telling someone they really screwed up and need to stop denying it isn't bullying. Someone being mean isn't bullying.
- dis-sys 9y agoglad that Linus is still 100% passionate on _his_ kernel. I will start to worry for the future of Linux when Linus stops doing such rants.
- johnnyRose 9y agoPoor guy. Linus just melted his face off. Makes me scared to even _consider_ contributing...
- justabystander 9y agoPlenty of people claim that they're scared to contribute because Linus might yell at them. That's unfounded for a lot of reasons. TL;DR: Test your code before you submit it. Don't accept or acknowledge patches from others that haven't been reviewed or tested. And if you make a mistake, own up quick and he's not going to yell at you. It's pretty simple. He will occasionally jump in and yell when people aren't accepting responsibility for problems they caused. Especially when they won't accept nicer, less authoritative criticism from their peers. That's what happened in this case. Check the follow-up message in the thread where Linus explains his dissatisfaction (http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02507.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02507.html). The contributor who caused the regression was caught denying that there was even a regression. His patch had already long been identified as the culprit and reverted. But over the course of three weeks he was insisting that it was not a kernel regression. Essentially he dug in for 22 days saying that it wasn't his problem. And he wasted tons of valuable contributor time where people were nicely telling him that, yes, it was indeed a regression. Multiple people were telling him about the "don't break userspace" policy and how it was a regression. And yet that contributor was still deflecting responsibility for the problems caused. But the problem is that this patch would leave the distros in the lurch - scrambling to update their configuration before the kernel breaks behavior. And that's without any ETA on their "long term ... flexible solution" (http://lkml.iu.edu/hypermail/linux/kernel/1710.3/00380.html http://lkml.iu.edu/hypermail/linux/kernel/1710.3/00380.html). Thousands of people with varying levels of technical competency would have had their systems break in unexpected ways. Quite frankly, he earned the dressing down. And plenty of people tried to be nice to him about it. It just didn't take hold in his mind until Linus dropped in to rudely remind him that even "correct" behavior is a regression if it breaks userspace. Also note that Linus said the issue had been escalated to him. Someone explicitly brought this to his attention because there was a distinct lack of progress due to CYA responsibility deflection.
- fareesh 9y agoLinux is what it is because of the passion and principle that fuel rants like this. I hope he continues to be just the way he is, and never gives an inch.
- sunstone 9y agoYikes, Linus on a bad day is not a pretty sight :)
- d0g 9y agoIt's the best sight there is . Got to love the man .
- peterwwillis 9y agoSlow clap
- tuananh 9y agoand here in node.js land, we have this beautiful thing call Code of Conduct /s
- throw2016 9y agoThe only time Linus gets talked about here is in context of conflicts. This creates a fabricated one sided image of a person who has now given us Linux and Git. Its not a corporation, the tradition and history is completely different, the levels of formality are much lower and the context and culture is completely new. There is no traditional hierarchy and the authoritarian structure that most including commentators here work under in the corporate world. No one works for Linus and he has zero power over anyone. Commentators pretend its all roses in their world yet the corporate world is full of people who have power over others and are actually abusive. Linus's emails are tame stuff and those casually comparing this to abusive behavior are simply devaluing actual abusive behavior that becomes possible under non transparent authoritarian structures.
- yeukhon 9y agoI was recludant to agree woth Linus at first. Why should we avoid break hard? I understand we wany to avoid breaking user interface as much as possible - who would want to use an unstable API? But why is it better off to let things fail silently? For example he cited certain obsolete fields in /proc/stats return zeros. Is it because Kernel is used by so many people and projects we can’t afford having some <insert your favorite Linuz utilit> broken after upgrading to a new kernel. Replace Linux kernel with OSX or Android etc Yes of course. But I feel the consequence of never break your interface and never blame userland is to force the users to write tests that can report changed behavior.
- jubalfh 9y agothe orange site truly is a self-perpetuating Stockholm syndrome chamber
- drngdds 9y agoWhat a child. There's a difference between being direct and telling your co-collaborators that their opinions are "fucking idiocy."
- deleted 9y ago[deleted]
- eutropia 9y agoTorvalds gets upset about people messing things up because he cares. He reminds me of Gordon Ramsey, who also gets a bunch of shit for being an asshole to people who ruin food in his kitchen -- but Ramsey has more Michelin stars than anyone else...
- andromaton 9y agoI read Linus' reply and it's not clear to me if he is ok with the regression, is not ok with the regression, or even if he considers it a regression. I wish he'd stop trying to be so diplomatic.