Badari Pulavarty wrote: > This is exactly the solution I proposed earlier (to check > buffer_mapped() before calling submit_bh()). > But at that time, Jan pointed out that the whole handling is wrong. > > But if this is the only case we need to handle, I am okay with this band > aid :) Doh! And we come full circle... ok let me go reread that thread, it got long enough I had to swap out... :) -Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- References:
- Re: 2.6.18 ext3 panic.
- From: Dave Jones <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Andrew Morton <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- Prev by Date: Re: kdump/kexec/crash on vmcore file
- Next by Date: Re: [patch 1/5] oom: don't kill unkillable children or siblings
- Previous by thread: Re: 2.6.18 ext3 panic.
- Next by thread: Re: 2.6.18 ext3 panic.
- Index(es):
 |