> Andrew Morton writes: > > > It looks like we died in ext3_xattr_block_get(): > > > > memcpy(buffer, bh->b_data + le16_to_cpu(entry->e_value_offs), > > size); > > > > Perhaps entry->e_value_offs is no good. I wonder if the filesystem is > > corrupted and this snuck through the defenses. > > > > I also wonder if there is enough info in that trace for a ppc person to > > be able to determine whether the faulting address is in the source or > > destination of the memcpy() (please)? > > It appears to have faulted on a load, implicating the source. The > address being referenced (0xc00000003f380000) doesn't look > outlandish. I wonder if this kernel has CONFIG_DEBUG_PAGEALLOC turned > on, and what page size is selected? Hmm, OK. But then I'm not sure how that can happen. Obviously, memcpy somehow got beyond end of the page referenced by bh->b_data. So it means that le16_to_cpu(entry->e_value_offs) + size > page_size. But ext3_xattr_find_entry() calls ext3_xattr_check_entry() which in particular checks whether e_value_offs + e_value_size isn't greater than bh->b_size. So I see no way how memcpy can get beyond end of the page. Sachin, is the problem reproducible? If yes, can you send us contents of the page just before the faulting address (i.e., for current fault it would be 0xc00000003f370000-0xc00000003f37ffff). As far as I can remember powerpc monitor could dump it. BTW, I suppose you use 4KB blocksize on the filesystem, right? Honza -- Jan Kara <jack@xxxxxxx> SuSE CR Labs -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
