The problem is that no testing is done. I found 3 bugs in fcntl/dup2/dup3 in the latest kernel release, things which were easily found when I ran the gnulib test suite, but had been bugs in the kernel for at least 2 months:
http://www.spinics.net/lists/linux-fsdevel/msg58725.html
Re:How Linux 3.6 Nearly Broke PostgreSQL
by chris_wot on Friday October 12, 2012 @07:41AM
(#4644576)
Does the Linux kernel have test suites?
It has autotest.
It has gnulib (not a test suite, but a very comprehensive POSIX API test).
It has the poor saps who have to use it.
However none of these things gate commits to the kernel.
Re:How Linux 3.6 Nearly Broke PostgreSQL
by Florin_Andrei on Thursday October 11, 2012 @01:04PM
(#4641691)
Well, living creatures are like that, too.
You just arched an eyebrow. Simple, isn't it? Well, when you know a bit about biology...
What a tease.
Re:How Linux 3.6 Nearly Broke PostgreSQL
by Someone on Thursday October 11, 2012 @04:30PM
(#4642617)
Nice, but I think "I, pencil" (http://en.wikisource.org/wiki/I,_Pencil) is better.
Every time I read or hear about unintended-consequence incidents like this one, I'm reminded me of Jean-Baptiste Queru's essay, "Dizzying but Invisible Depth" -- highly recommended if you haven't read it.[1]
--
[1] https://plus.google.com/u/0/112218872649456413744/posts/dfyd...