From: Gioh Kim <gi-oh.kim@ionos.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"leon@kernel.org" <leon@kernel.org>,
"dledford@redhat.com" <dledford@redhat.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"haris.iqbal@ionos.com" <haris.iqbal@ionos.com>,
"jinpu.wang@ionos.com" <jinpu.wang@ionos.com>,
"akinobu.mita@gmail.com" <akinobu.mita@gmail.com>,
"corbet@lwn.net" <corbet@lwn.net>
Subject: Re: [PATCH 0/4] Enable Fault Injection for RTRS
Date: Tue, 6 Apr 2021 17:20:07 +0200 [thread overview]
Message-ID: <CAJX1YtYcGJkTH6CyV7uoudVuRamYUVeA6UbmQkEfYq+rxTH=Gw@mail.gmail.com> (raw)
In-Reply-To: <6DBCD231-E108-4F4C-AFBF-688E988DACD7@oracle.com>
On Tue, Apr 6, 2021 at 4:20 PM Chuck Lever III <chuck.lever@oracle.com> wrote:
>
>
>
> > On Apr 6, 2021, at 7:50 AM, Gioh Kim <gi-oh.kim@ionos.com> wrote:
> >
> > My colleagues and I would like to apply the fault injection
> > of the Linux to test error handling of RTRS module. RTRS module
> > consists of client and server modules that are connected via
> > Infiniband network. So it is important for the client to receive
> > the error of the server and handle it smoothly.
>
> I am a fan of fault injection. In fact I added a disconnect fault
> injector for RPC that's in the kernel now, and it uses debugfs
> as its control interface.
>
> But that was years ago. If I were doing this today, I'd consider
> kprobes, since fault injection is generally not something that
> is consumed by users or administrators in a distributed kernel.
>
> Have you considered injection via kprobes or eBPF instead of
> adding permanent code?
I have not considered the eBPF yet.
I will have a discussion with my colleagues about that.
Thank you for the information.
>
>
> > When debugfs is enabled, RTRS is able to export interfaces
> > to fail RTRS client and server.
> > Following fault injection points are enabled:
> > - fail a request processing on RTRS client side
> > - fail a heart-beat transferation on RTRS server side
> >
> > This patch set is just a starting point. We will enable various
> > faults and test as many error cases as possible.
> >
> > Best regards
> >
> > Gioh Kim (4):
> > RDMA/rtrs: Enable the fault-injection
> > RDMA/rtrs-clt: Inject a fault at request processing
> > RDMA/rtrs-srv: Inject a fault at heart-beat sending
> > docs: fault-injection: Add fault-injection manual of RTRS
> >
> > .../fault-injection/rtrs-fault-injection.rst | 83 +++++++++++++++++++
> > drivers/infiniband/ulp/rtrs/Makefile | 2 +
> > drivers/infiniband/ulp/rtrs/rtrs-clt-sysfs.c | 44 ++++++++++
> > drivers/infiniband/ulp/rtrs/rtrs-clt.c | 7 ++
> > drivers/infiniband/ulp/rtrs/rtrs-clt.h | 13 +++
> > drivers/infiniband/ulp/rtrs/rtrs-fault.c | 52 ++++++++++++
> > drivers/infiniband/ulp/rtrs/rtrs-fault.h | 28 +++++++
> > drivers/infiniband/ulp/rtrs/rtrs-srv-sysfs.c | 44 ++++++++++
> > drivers/infiniband/ulp/rtrs/rtrs-srv.c | 5 ++
> > drivers/infiniband/ulp/rtrs/rtrs-srv.h | 13 +++
> > 10 files changed, 291 insertions(+)
> > create mode 100644 Documentation/fault-injection/rtrs-fault-injection.rst
> > create mode 100644 drivers/infiniband/ulp/rtrs/rtrs-fault.c
> > create mode 100644 drivers/infiniband/ulp/rtrs/rtrs-fault.h
> >
> > --
> > 2.25.1
> >
>
> --
> Chuck Lever
>
>
>
next prev parent reply other threads:[~2021-04-06 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 11:50 [PATCH 0/4] Enable Fault Injection for RTRS Gioh Kim
2021-04-06 11:50 ` [PATCH 1/4] RDMA/rtrs: Enable the fault-injection Gioh Kim
2021-04-06 11:50 ` [PATCH 2/4] RDMA/rtrs-clt: Inject a fault at request processing Gioh Kim
2021-04-06 11:50 ` [PATCH 3/4] RDMA/rtrs-srv: Inject a fault at heart-beat sending Gioh Kim
2021-04-06 11:50 ` [PATCH 4/4] docs: fault-injection: Add fault-injection manual of RTRS Gioh Kim
2021-04-06 14:20 ` [PATCH 0/4] Enable Fault Injection for RTRS Chuck Lever III
2021-04-06 15:20 ` Gioh Kim [this message]
2021-04-13 22:53 ` Jason Gunthorpe
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='CAJX1YtYcGJkTH6CyV7uoudVuRamYUVeA6UbmQkEfYq+rxTH=Gw@mail.gmail.com' \
--to=gi-oh.kim@ionos.com \
--cc=akinobu.mita@gmail.com \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).