On Thu, 16 Aug 2007 22:42:42 +0200, devzero@web.de said:There's something even scarier - O(1) being taken out and replaced by multiple new things, none of which ever gets fully tested because if one misbehaves, the user says "so what" and tries another one without bothering to file a bug report... Been there, done that - I found a timing hole in the pluggable I/O schedulers that probably nobody had managed to hit because there were 3 or 4 choices available, and they just set a default they liked. Turned out there was a race condition if I/O happened while schedulers were being swapped.
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Trond Myklebust | Re: (NFS) BUG: at page-writeback.c:829 [Was: 2.6.22-rc1-mm1] |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
