public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	Nitesh Shetty <nj.shetty@samsung.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH] nvme: add nvme pci timeout testcase
Date: Wed, 10 Jan 2024 07:59:45 -0700	[thread overview]
Message-ID: <d921a213-df5d-45dd-bc37-99f3034a1a03@kernel.dk> (raw)
In-Reply-To: <aa82e427-a599-4cef-80bc-fac5bc517335@nvidia.com>

On 1/10/24 1:12 AM, Chaitanya Kulkarni wrote:
> 
>>>>
>>>> Should this be TEST_DEV instead ?
>>>
>>> why ?
>>>
>> My understanding of blktests is, add device which we want to test in
>> config files under TEST_DEV (except null-blk and nvme-fabrics loopback
>> devices, which are usually populated inside the tests).
>> In this case, if someone do not want to disturb nvme0n1 device,
>> this test doesn't allow it.
>>
>> Regards,
>> Nitesh Shetty
>>
> 
> it is clearly stated in the documentation that blktests are destructive
> to the entire system and including any devices you have, if your
> system has sensitive data then _don't run these tests_ simple, when
> you are running blktests you are bound to disturb system you can't
> prevent that by using TEST_DEV.

It should very much be possible to run blktests on specific devices
ONLY, the intent of a test suite is not to potentially mess up
everything around you. It should ONLY operate on the devices given, not
poke at random devices in the system.

-- 
Jens Axboe


  parent reply	other threads:[~2024-01-10 14:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240110062350epcas5p351f5b4f8e27b3c57545b49509d2a48b6@epcas5p3.samsung.com>
2024-01-10  3:57 ` [PATCH] nvme: add nvme pci timeout testcase Chaitanya Kulkarni
2024-01-10  6:17   ` Nitesh Shetty
2024-01-10  7:40     ` Chaitanya Kulkarni
2024-01-10  7:54       ` Nitesh Shetty
2024-01-10  8:12         ` Chaitanya Kulkarni
2024-01-10  9:13           ` Shinichiro Kawasaki
2024-01-10  9:24           ` Hannes Reinecke
2024-01-10 23:47             ` Chaitanya Kulkarni
2024-01-10 14:59           ` Jens Axboe [this message]
2024-01-10 23:51             ` Chaitanya Kulkarni
2024-01-10 12:23   ` Shinichiro Kawasaki
2024-01-11  0:00     ` Chaitanya Kulkarni
2024-01-11  4:41       ` Shinichiro Kawasaki
2024-01-11  5:01         ` Chaitanya Kulkarni
2024-01-11  1:25   ` Yi Zhang
2024-01-11  3:09     ` Chaitanya Kulkarni

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=d921a213-df5d-45dd-bc37-99f3034a1a03@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nj.shetty@samsung.com \
    --cc=shinichiro.kawasaki@wdc.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