lkml.org 
[lkml]   [2006]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Slab corruption in 2.6.16-rc5-mm2
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> > Often I'll check that a patch reverts successfully from the upstream tree
> > before dropping it, but for an obvious one like that I guess I didn't
> > bother, and assumed that James had taken it. Only he hadn't - instead he'd
> > gone and merged something else, hence the rejects. Oh well.
> >
>
> You do a great job, but "push the work out to the end nodes", right?
> That's how we get this network to scale. It is trivial for people to
> verify their important patches have propogated as the release approaches.
>
> (A little harder for part-timers who aren't in the loop about exactly
> when the release will happen, thanks to our -ridiculous-count release
> system, but still easy compared with your having to double check
> everything).

Well yes, Lee sent the fix to the guy who he got the kernel release from in
the reasonable expectation that I'd take care of getting it to where it
needed to be.

Problem is, a) I screwed up, b) James screwed up and c) someone just
happened to change those few lines of code in that place within a few-day
window.

That triple-combo doesn't happen very often.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-03-08 10:18    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site