Aneesh Kumar K.V wrote:
> This helps in better debugging of the problem reported.
ext4_error happens potentially often in some scenarios, and if I chose
errors=continue I'm not sure I'd want to dump this much.
Would it be worth limiting how often this goes off (maybe just once per fs?)
-Eric
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
> ---
> fs/ext4/super.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index cd7cac0..93f4820 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -238,6 +238,7 @@ void ext4_error (struct super_block * sb, const char * function,
> vprintk(fmt, args);
> printk("\n");
> va_end(args);
> + dump_stack();
>
> ext4_handle_error(sb);
> }
> @@ -320,6 +321,7 @@ void ext4_abort (struct super_block * sb, const char * function,
> vprintk(fmt, args);
> printk("\n");
> va_end(args);
> + dump_stack();
>
> if (test_opt(sb, ERRORS_PANIC))
> panic("EXT4-fs panic from previous error\n");
> @@ -345,6 +347,7 @@ void ext4_warning (struct super_block * sb, const char * function,
> vprintk(fmt, args);
> printk("\n");
> va_end(args);
> + dump_stack();
> }
>
> void ext4_update_dynamic_rev(struct super_block *sb)
--
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
