On Mon, Feb 25, 2013 at 12:21:30PM -0700, Mace Moneta wrote:
> On Mon, Feb 25, 2013 at 2:12 PM, Josef Bacik <jbacik@xxxxxxxxxxxx> wrote:
>
> >
> > Is there any chance you got the line above [ cut here ]? (I hate that stupid [
> > cut here ], it makes us miss all the usefull info.) Thanks,
> >
> > Josef
>
> There was really nothing significant above the 'cut here'. Here it is
> with over an hour of earlier context:
>
Sigh, I don't know why this warn_on(1, printk) isn't doing it's job. Here is a
debug patch, please capture the output from this so I can figure out what is
going on. Thanks,
Josef
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 66f999b..eed5554 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -4715,9 +4715,10 @@ int map_private_extent_buffer(struct extent_buffer *eb, unsigned long start,
}
if (start + min_len > eb->len) {
- WARN(1, KERN_ERR "btrfs bad mapping eb start %llu len %lu, "
+ printk(KERN_ERR "btrfs bad mapping eb start %llu len %lu, "
"wanted %lu %lu\n", (unsigned long long)eb->start,
eb->len, start, min_len);
+ WARN_ON(1);
return -EINVAL;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
