On Wed, Mar 29 2006, Peter Palfrader wrote:
> On Wed, 29 Mar 2006, Nathan Scott wrote:
>
> > You'll be better off trying the bio_clone fix discussed in the
> > other (ext3-bio_clone-panic) thread than go down this route
> > (there is a fix in 2.6.16.1 apparently - start there). Certainly
> > try that before attempting to revert these changes anyway.
>
> The problem persists on 2.6.16.1.
The original oops showed the path into bio_clone() originating from
crypt_alloc_buffer() in dm-crypt.c - and blk_recount_segments() is
oopsinig in page_to_pfn(), meaning that the most likely cause of this is
dm-crypt passing in a bio with invalid ->bi_idx and/or ->bi_vcnt. At
least they are not matching what ->bi_io_vec[] holds.
--
Jens Axboe
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
