From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org
Cc: blktests-ci-bot@kernel.org
Subject: Re: [RFC 0/4] fs: support dma-buf backed direct I/O
Date: Sun, 18 Oct 2026 22:32:11 +0900 [thread overview]
Message-ID: <atTJy6MLgDXV80Bq@shinmob> (raw)
In-Reply-To: <25bc51e2bde7437dc692cd60dad9acb68a6522e6796b9e79d9b73c89eb1607b4@mailrelay.wdc.com>
On Oct 17, 2026 / 15:54, shinichiro.kawasaki@wdc.com wrote:
> Dear patch submitter,
>
> Blktests CI has tested the following submission:
> Status: FAILURE
> Name: [RFC,0/4] fs: support dma-buf backed direct I/O
> Patchwork: https://patchwork.kernel.org/series/1187147/&state=*
> Run record: https://github.com/linux-blktests/linux-block/actions/runs/38999893251
>
>
> Failed test cases: md/001
Please ignore this failure report. I believe the failure cause of the md/001
failure is in a different patch for nvme-tcp driver [*].
[*] https://lore.kernel.org/linux-nvme/atSzF3URmcpP2_i2@shinmob/
next prev parent reply other threads:[~2026-10-18 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:19 [RFC 0/4] fs: support dma-buf backed direct I/O Anuj Gupta
2026-10-16 9:19 ` [RFC 1/4] block: factor out bdev_init_dma_buf_io_ctx() Anuj Gupta
2026-10-16 9:23 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 2/4] block: refuse a dma-buf bio for a disk the buffer was not registered on Anuj Gupta
2026-10-16 9:24 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 3/4] iomap: add dma-buf direct I/O guards and registration helper Anuj Gupta
2026-10-16 9:26 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 4/4] xfs: support dma-buf registered buffers for direct I/O Anuj Gupta
2026-10-16 9:28 ` Christoph Hellwig
2026-10-17 18:19 ` Kanchan Joshi
2026-10-18 22:28 ` Pavel Begunkov
2026-10-19 10:29 ` Anuj gupta
2026-10-17 22:54 ` [RFC 0/4] fs: support dma-buf backed " shinichiro.kawasaki
2026-10-18 13:32 ` Shin'ichiro Kawasaki [this message]
2026-10-18 22:18 ` Pavel Begunkov
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=atTJy6MLgDXV80Bq@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=blktests-ci-bot@kernel.org \
--cc=linux-block@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