> I see you queued this for 2.6.26 -- I'd have thought that this would go > to 2.6.25 as it is a bug fix. What do you think? I didn't think it was serious enough to go in at the rc5/rc6 stage. It's borderline even to call it a bug, and the workaround is pretty trivial -- "don't do that then." - R.