From: Jens Axboe <axboe@kernel.dk>
To: "Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
Bart Van Assche <bvanassche@acm.org>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
Damien Le Moal <damien.lemoal@wdc.com>
Subject: Re: Zoned block device regression test 11
Date: Wed, 22 Aug 2018 11:05:44 -0600 [thread overview]
Message-ID: <8b834df5-0e58-d012-d9c3-b040ea6c4925@kernel.dk> (raw)
In-Reply-To: <CY4PR21MB0773D0F69E91EA2BD4B34FAFDC300@CY4PR21MB0773.namprd21.prod.outlook.com>
On 8/22/18 10:54 AM, Michael Kelley (EOSG) wrote:
> From: Jens Axboe <axboe@kernel.dk> Sent: Wednesday, August 22, 2018 8:49 AM
>>
>> On 8/22/18 9:47 AM, Michael Kelley (EOSG) wrote:
>>> Any special configuration needed to run this test? Any options needs on
>>> command line? I figured out to enable CONFIG_BLK_DEV_ZONED, but
>>> now I get the following on my 4.18.3 kernel:
>>>
>>> root@MHKfio2:~# ./fio/t/zbd/run-tests-against-zoned-nullb
>>> ./fio/t/zbd/run-tests-against-zoned-nullb: line 27: ./fio/t/zbd/test-zbd-support: No such file or
>> directory
>>>
>>> /sys/kernel/config/nullb/nullb0/* and /dev/nullb0 are present as expected.
>>
>> You need current -git from Linus, the zoned null_blk support was added
>> after 4.18.
>
> So grab the linux-next tree, or are you referring to something else? In my
> 4.18.3 tree, the source file drivers/block/null_blk_zoned.c is there and builds.
Just grab Linus's tree, for instance. 4.18.3 does definitely not have support
for zoned null_blk, and null_blk_zoned.c should not exist. It was introduced
by this commit:
commit ca4b2a011948fae4e4d31490107db4926385a983
Author: Matias Bjørling <matias.bjorling@wdc.com>
Date: Fri Jul 6 19:38:39 2018 +0200
null_blk: add zone support
which is not in 4.18. So either your sources are messed up, or something else
funky is going on at your end.
--
Jens Axboe
prev parent reply other threads:[~2018-08-22 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 0:10 Zoned block device regression test 11 Bart Van Assche
2018-08-22 4:32 ` Michael Kelley (EOSG)
2018-08-22 15:47 ` Michael Kelley (EOSG)
2018-08-22 15:48 ` Jens Axboe
2018-08-22 16:54 ` Michael Kelley (EOSG)
2018-08-22 17:04 ` Bart Van Assche
2018-08-22 19:04 ` Michael Kelley (EOSG)
2018-08-22 19:54 ` Bart Van Assche
2018-08-23 0:38 ` Michael Kelley (EOSG)
2018-08-22 19:55 ` Damien Le Moal
2018-08-22 17:05 ` Jens Axboe [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=8b834df5-0e58-d012-d9c3-b040ea6c4925@kernel.dk \
--to=axboe@kernel.dk \
--cc=Michael.H.Kelley@microsoft.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@wdc.com \
--cc=fio@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