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? Paul. -- 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
