All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Heming Zhao <heming.zhao@suse.com>, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v2 5/5] ocfs2: rewrite error handling of ocfs2_fill_super
Date: Thu, 14 Apr 2022 09:47:42 +0800	[thread overview]
Message-ID: <72ee0290-4140-f3d1-170f-3b5b883133f7@linux.alibaba.com> (raw)
In-Reply-To: <20220413131105.7k7xpmlzemwgw44x@c73>



On 4/13/22 9:11 PM, Heming Zhao wrote:
> On Wed, Apr 13, 2022 at 07:37:59PM +0800, Joseph Qi wrote:
>> It mostly looks good to me.
>> Have you done error injection test after this patchset applied?
>> I'm afraid ocfs2-test can't cover this as of now.
>>
> 
> I plan to write a debugfs api for error injection test.
> The code only for these patches test
> 
> My idea:
> echo N > /sys/kernel/debug/ocfs2/xxx/error
> N: 1,2,3,4,...
> 
> "echo N" will make ocfs2 trigger Nth error point become true:
> 
> ```
>  	status = ocfs2_initialize_super(sb, bh, sector_size, &stats);
>  	brelse(bh);
>  	bh = NULL;
> -	if (status < 0)
> +	if (error_inject(n)) //eg. "echo 1 > xx" will trigger there "if()" becomes true.
>  		goto out;
> ```
> 
> What's your opinion about my idea?
> Or do you have other method to test?

Good idea, actually we did it in this way before since existing
fault-injection can only inject common failures such as slab allocation.

Thanks,
Joseph

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

      reply	other threads:[~2022-04-14  3:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  8:29 [Ocfs2-devel] [PATCH v2 0/5] rewrite error handling during mounting stage Heming Zhao via Ocfs2-devel
2022-04-13  8:29 ` [Ocfs2-devel] [PATCH v2 1/5] ocfs2: fix mounting crash if journal is not alloced Heming Zhao via Ocfs2-devel
2022-04-13 10:54   ` Joseph Qi via Ocfs2-devel
2022-04-13 13:18     ` heming.zhao--- via Ocfs2-devel
2022-04-13  8:29 ` [Ocfs2-devel] [PATCH v2 2/5] ocfs2: change return type of ocfs2_resmap_init Heming Zhao via Ocfs2-devel
2022-04-13 10:56   ` Joseph Qi via Ocfs2-devel
2022-04-13  8:29 ` [Ocfs2-devel] [PATCH v2 3/5] ocfs2: ocfs2_initialize_super does cleanup job before return error Heming Zhao via Ocfs2-devel
2022-04-13 11:02   ` Joseph Qi via Ocfs2-devel
2022-04-13  8:29 ` [Ocfs2-devel] [PATCH v2 4/5] ocfs2: ocfs2_mount_volume " Heming Zhao via Ocfs2-devel
2022-04-13 11:25   ` Joseph Qi via Ocfs2-devel
2022-04-14  9:14     ` heming.zhao--- via Ocfs2-devel
2022-04-13  8:29 ` [Ocfs2-devel] [PATCH v2 5/5] ocfs2: rewrite error handling of ocfs2_fill_super Heming Zhao via Ocfs2-devel
2022-04-13 11:37   ` Joseph Qi via Ocfs2-devel
2022-04-13 13:11     ` Heming Zhao via Ocfs2-devel
2022-04-14  1:47       ` Joseph Qi via Ocfs2-devel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72ee0290-4140-f3d1-170f-3b5b883133f7@linux.alibaba.com \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=heming.zhao@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.