Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: alan.adamson@oracle.com
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"chaitanyak@nvidia.com" <chaitanyak@nvidia.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH blktests V2 1/1] nvme: Add passthru error logging tests to nvme/039
Date: Wed, 21 Feb 2024 08:42:46 -0800	[thread overview]
Message-ID: <634dcc24-d02e-431b-afe4-277f06bb57c4@oracle.com> (raw)
In-Reply-To: <emp34ucgyak4r7ajed3nrk4npbwgv5hyfovlv7mo434m2e7cq7@m4itoplxugis>


On 2/21/24 2:41 AM, Shinichiro Kawasaki wrote:
> Thanks for this v2. I confirmed nvme/039 passes with this patch on my test
> system. Good.
>
> On Feb 20, 2024 / 15:30, Alan Adamson wrote:
>> Tests the ability to enable and disable error logging for passthru admin commands issued to
>> the controller and passthru IO commands issued to a namespace.
>>
>> These tests will only run on 6.8.0 and greater kernels.
> This v2 uses the kernel version as the condition to run passthru tests. But I
> think sysfs file check is much simpler and more accurate. Please see my comment
> below.
>
> [...]
>
>> diff --git a/tests/nvme/039 b/tests/nvme/039
>> index 73b53d0b949c..38a866417db9 100755
>> --- a/tests/nvme/039
>> +++ b/tests/nvme/039
> [...]
>
>> @@ -155,6 +197,26 @@ test_device() {
>>   	inject_invalid_status_on_read "${ns_dev}"
>>   	inject_write_fault_on_write "${ns_dev}"
>>   
>> +	if [ $RUN_PASSTHRU_TESTS -ne 0 ]; then
> The line above can be:
>
>         if [ -e "$TEST_DEV_SYSFS/passthru_err_log_enabled" ]; then
>
> Then RUN_PASSTHRU_TESTS and check_kver680_for_passthru_tests() are not required.

That makes sense.  I'll make this change.


Thanks,

Alan



      reply	other threads:[~2024-02-21 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 23:30 [PATCH blktests V2 0/1] nvme: Add passthru error logging tests to nvme/039 Alan Adamson
2024-02-20 23:30 ` [PATCH blktests V2 1/1] " Alan Adamson
2024-02-21  7:12   ` Chaitanya Kulkarni
2024-02-21 10:41   ` Shinichiro Kawasaki
2024-02-21 16:42     ` alan.adamson [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=634dcc24-d02e-431b-afe4-277f06bb57c4@oracle.com \
    --to=alan.adamson@oracle.com \
    --cc=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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