Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Changming Liu <liu.changm@northeastern.edu>
Cc: "jgg@ziepe.ca" <jgg@ziepe.ca>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	yaohway <yaohway@gmail.com>
Subject: Re: How to fuzz testing infiniband/uverb driver
Date: Tue, 3 Nov 2020 16:40:48 -0800	[thread overview]
Message-ID: <20201104004048.GA1538856@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <BN6PR06MB2532A64BB4D75A9D8D02E310E5100@BN6PR06MB2532.namprd06.prod.outlook.com>

On Mon, Nov 02, 2020 at 10:26:22PM +0000, Changming Liu wrote:
> 
> 
> > -----Original Message-----
> > From: Ira Weiny <ira.weiny@intel.com>
> > Sent: Monday, November 2, 2020 11:16 AM
> > To: Changming Liu <liu.changm@northeastern.edu>
> > Cc: jgg@ziepe.ca; linux-rdma@vger.kernel.org; yaohway
> > <yaohway@gmail.com>
> > Subject: Re: How to fuzz testing infiniband/uverb driver
> > 
> > On Sun, Nov 01, 2020 at 09:00:13PM +0000, Changming Liu wrote:
> > >
> > > there is no 'uverbs0' file created under /sys/class/infiniband or
> > > /dev/infiniband/. So may I ask how to properly set up my testing
> > > environment so that I can fuzzi testing this driver? Is a physical
> > > device required?
> > 
> > A physical device is not required.  Look at one of the software drivers like rxe.
> > 
> 
> Thank you so much for your guidance, 
> now uverb0 has appeared and syzkaller works!

Awesome!  More testing is never a bad thing!  :-D

Ira


      reply	other threads:[~2020-11-04  0:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01 21:00 How to fuzz testing infiniband/uverb driver Changming Liu
2020-11-02 16:16 ` Ira Weiny
2020-11-02 22:26   ` Changming Liu
2020-11-04  0:40     ` Ira Weiny [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=20201104004048.GA1538856@iweiny-DESK2.sc.intel.com \
    --to=ira.weiny@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=liu.changm@northeastern.edu \
    --cc=yaohway@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox