Message ID | 20250311104359.1767728-1-shinichiro.kawasaki@wdc.com (mailing list archive) |
---|---|
Headers | show |
Series | block: nvme: fix blktests nvme/039 failure | expand |
On 3/11/25 4:43 AM, Shin'ichiro Kawasaki wrote: > Commit 1f47ed294a2b ("block: cleanup and fix batch completion adding > conditions") in the kernel tag v6.14-rc3 triggered blktests nvme/039 > failure [1]. > > The test case injects errors to the NVMe driver and confirms the errors > are logged. The first half of the test checks it for non-passthrough > requests, and the second half checks for passthrough requests. The > commit made both halves fail. > > This series addresses the test case failure. The first patch covers the > passthrough requests, and the second patch covers the non-passthrough > requests. Looks good to me, and better than the quick fix-up for the problem. Thanks for taking the time to do it right!
On Tue, 11 Mar 2025 19:43:57 +0900, Shin'ichiro Kawasaki wrote: > Commit 1f47ed294a2b ("block: cleanup and fix batch completion adding > conditions") in the kernel tag v6.14-rc3 triggered blktests nvme/039 > failure [1]. > > The test case injects errors to the NVMe driver and confirms the errors > are logged. The first half of the test checks it for non-passthrough > requests, and the second half checks for passthrough requests. The > commit made both halves fail. > > [...] Applied, thanks! [1/2] nvme: move error logging from nvme_end_req() to __nvme_end_req() commit: e5c2bcc0cd47321d78bb4e865d7857304139f95d [2/2] block: change blk_mq_add_to_batch() third argument type to bool commit: f00baf2eac785bba837e5ed79d489f16520e7a6d Best regards,