[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170516091535.04e3d188@lwn.net>
Date: Tue, 16 May 2017 09:15:35 -0600
From: Jonathan Corbet <corbet@....net>
To: Trond Myklebust <trondmy@...marydata.com>
Cc: "mhocko@...nel.org" <mhocko@...nel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"n.borisov.lkml@...il.com" <n.borisov.lkml@...il.com>
Subject: Re: [GIT PULL] Please pull NFS client fixes for 4.12
On Thu, 11 May 2017 13:10:03 +0000
Trond Myklebust <trondmy@...marydata.com> wrote:
> If we suspect the existence of a load of potential time bombs in the
> kernel due to missing checks, then the status quo is not good enough.
> We should be working on tools to identify these code paths.
>
> Quite frankly, I'd love to see a fuzzer-like tool that can randomly
> fail allocations.
The fault injection framework at least used to work quite nicely for this;
I used it to test out the failure paths in the OLPC drivers years ago.
Documentation/fault-injection/fault-injection.txt.
jon
Powered by blists - more mailing lists