From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Nitesh Shetty <nj.shetty@samsung.com>
Cc: gost.dev@samsung.com, nitheshshetty@gmail.com
Subject: Re: [PATCH liburing 0/3] test/fixed-seg: Add data verification and
Date: Wed, 23 Apr 2025 14:04:22 -0600 [thread overview]
Message-ID: <174543866212.541287.8947014567777273902.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250423132752.15622-1-nj.shetty@samsung.com>
On Wed, 23 Apr 2025 18:57:49 +0530, Nitesh Shetty wrote:
> Write data before issuing read and verify the data once read is
> completed. This makes sure we are failing if nr_seg is passed wrong,
> incase of offset is present.
>
> At present test fails for block devices formatted with non 512 bytes.
> This allows to test 4k block devices. Some of the corner cases such as
> 3584 offset test are not valid for 4k, hence skipped.
>
> [...]
Applied, thanks!
[1/3] test/fixed-seg: Prep patch, rename the vec to rvec.
commit: f9f133fd9edbdd8e47b06739e0a2e4fa8da9c721
[2/3] test/fixed-seg: verify the data read
commit: fcf273bbae7082fb6413c87c21f1d982ee6b9140
[3/3] test/fixed-seg: Support non 512 LBA format devices.
commit: be5f31287825eb1f81813a15a28989b27627ac10
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-04-23 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250423133628epcas5p2b4752a672a64bd2f1392f663a284f9f2@epcas5p2.samsung.com>
2025-04-23 13:27 ` [PATCH liburing 0/3] test/fixed-seg: Add data verification and Nitesh Shetty
[not found] ` <CGME20250423133638epcas5p34a9cf20f13387f7f604d9c2e2bf6976a@epcas5p3.samsung.com>
2025-04-23 13:27 ` [PATCH liburing 1/3] test/fixed-seg: Prep patch, rename the vec to rvec Nitesh Shetty
[not found] ` <CGME20250423133642epcas5p1bef7e3af23bd8561f359ccc16fdaf980@epcas5p1.samsung.com>
2025-04-23 13:27 ` [PATCH liburing 2/3] test/fixed-seg: verify the data read Nitesh Shetty
[not found] ` <CGME20250423133646epcas5p2e67808b13c6c85444b8a9f28995fe70b@epcas5p2.samsung.com>
2025-04-23 13:27 ` [PATCH liburing 3/3] test/fixed-seg: Support non 512 LBA format devices Nitesh Shetty
2025-04-23 19:05 ` Anuj gupta
2025-04-23 20:02 ` Jens Axboe
2025-04-23 20:04 ` 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=174543866212.541287.8947014567777273902.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=gost.dev@samsung.com \
--cc=io-uring@vger.kernel.org \
--cc=nitheshshetty@gmail.com \
--cc=nj.shetty@samsung.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