Messages in this thread | | | Date | Sat, 20 Mar 1999 10:53:32 +0100 (CET) | From | Mike Galbraith <> | Subject | Re: [patch] fix for buffer hash leakage |
| |
On Sat, 20 Mar 1999, Simon Kirby wrote:
> On Fri, 19 Mar 1999, Chuck Lever wrote: > > yes, that's exactly what i've found. i have a simple patch that i'm > > testing on the big Dell right now, that is slightly different from yours. > > i thought it would be better to put the forgotten buffers onto the free > > list instead. to wit, here's my bforget(): > > > > [ -3 lines, +2 lines, for those of you keeping track ] > > > > void __bforget(struct buffer_head * buf) > > { > > clear_bit(BH_Protected, &buf->b_state); > > remove_from_queues(buf); > > put_last_free(buf); > > if (!--buf->b_count) > > return; > > printk("VFS: forgot an in-use buffer! (count=%d)\n", > > buf->b_count); > > } > > I tried this change on my dual Celeron at home here and after a few > seconds of booting (truncating utmp and such), I got: > > Kernel Panic: Free list corrupted > > So there's probably something wrong with it somehow. :)
I'm running it now on my UP box with a stress-testers 'kitchen sink'. (pushing it very hard) So far, it is holding up very well.
Lately, heavy load usually results in scsi timeout and bus lockup... is it possible that my inability to kill the box is related to this change?
-Mike
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |