Mauro, SHUT THE FUCK UP!
闭上你的嘴
It's a bug alright - in the kernel. How long have you been a
maintainer? And you *still* haven't learnt the first rule of kernel
maintenance?
这是已经是一个内核的bug。你做maintainer多久了，难道你不知道内核maintenance的首要原则吗
If a change results in user programs breaking, it's a bug in the
kernel. We never EVER blame the user programs. How hard can this be to
understand?
如果一个内核的改变导致用户程序崩溃，那么这就是内核的bug。我们从来不会将此归罪于用户程序，
这点理解起来很难吗
To make matters worse, commit f0ed2ce840b3 is clearly total and utter
CRAP even if it didn't break applications. ENOENT is not a valid error
return from an ioctl. Never has been, never will be. ENOENT means "No
such file and directory", and is for path operations. ioctl's are done
on files that have already been opened, there's no way in hell that
ENOENT would ever be valid.
更糟糕的是，第f0ed2ce840b3号提交已经明显表示这是一个错误，即使它不会使程序终止。
但是，ENOENT不是ioctl返回的有效结果，以前不是，将来也不会是。ENOENT的意思
是“没有这个文件或者目录”，而且是关于路径操作的。ioctl是在已打开文件上的操作，所以ENOENT
绝对不可能在这个时候出现
> So, on a first glance, this doesn't sound like a regression,
> but, instead, it looks tha pulseaudio/tumbleweed has some serious
> bugs and/or regressions.
Shut up, Mauro. And I don't _ever_ want to hear that kind of obvious
garbage and idiocy from a kernel maintainer again. Seriously.
闭嘴哥们。我不想再一次的听到这种由内核maintainer（维护者）造成显而易见的垃圾和白痴事情。
注意！！！！
I'd wait for Rafael's patch to go through you, but I have another
error report in my mailbox of all KDE media applications being broken
by v3.8-rc1, and I bet it's the same kernel bug. And you've shown
yourself to not be competent in this issue, so I'll apply it directly
and immediately myself.
我在等待Rafael为你而补的补丁，但是我的邮箱里还有另一份关于KDE的多媒体程序在3.8-rc1内核上
跑崩的错误报告，我敢打赌这是同一个内核bug。在这种事情上你显示了你的不专业和不胜任，所以我要亲自
立即的直接的处理这个事情
WE DO NOT BREAK USERSPACE!
我们从来不会干涉用户空间的事情！！！！！
Seriously. How hard is this rule to understand? We particularly don't
break user space with TOTAL CRAP. I'm angry, because your whole email
was so _horribly_ wrong, and the patch that broke things was so
obviously crap. The whole patch is incredibly broken shit. It adds an
insane error code (ENOENT), and then because it's so insane, it adds a
few places to fix it up ("ret == -ENOENT ? -EINVAL : ret").
你可长点心吧！这点很难理解吗！！！我们尤其是不会干涉用户空间的！！！！我很生气，因为你
的邮件充斥着这种可怕的错误而且这个错误干的坏事如此的显而易见，从而导致整个补丁难以置信的
崩了。这个错误多了个傻逼的ENOENT，然后因为它这么傻逼，又加了个简单的修复方法，就那句C
语言"ret==-ENOENT?-EINVAL:ret"
("ret == -ENOENT ? -EINVAL : ret").
The fact that you then try to make *excuses* for breaking user space, and blaming some external program that *used* to work, is just shameful. It's not how we work.
然后就干涉了用户空间，让用户程序崩了，然后你怪罪某些外部应用程序，耻辱啊！这不是我们的
工作方式 Fix your f*cking "compliance tool", because it is obviously broken. And fix your approach to kernel programming.
不要再说你那该死的“不兼容”，因为那实际是显而易见的东西。改正你在kernel组的工作方式
Linus
