From: Philippe Mathieu-Daudé <phi...@redhat.com> Instead of displaying warning on stderr, use warn_report() which also displays it on the monitor.
Reviewed-by: Eric Auger <eric.au...@redhat.com> Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com> Tested-by: Eric Auger <eric.au...@redhat.com> Signed-off-by: Philippe Mathieu-Daudé <phi...@redhat.com> Message-id: 20201029093306.1063879-4-phi...@redhat.com Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> Tested-by: Eric Auger <eric.au...@redhat.com> --- block/nvme.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/block/nvme.c b/block/nvme.c index 739a0a700c..6f1d7f9b2a 100644 --- a/block/nvme.c +++ b/block/nvme.c @@ -399,8 +399,8 @@ static bool nvme_process_completion(NVMeQueuePair *q) } cid = le16_to_cpu(c->cid); if (cid == 0 || cid > NVME_QUEUE_SIZE) { - fprintf(stderr, "Unexpected CID in completion queue: %" PRIu32 "\n", - cid); + warn_report("NVMe: Unexpected CID in completion queue: %"PRIu32", " + "queue size: %u", cid, NVME_QUEUE_SIZE); continue; } trace_nvme_complete_command(s, q->index, cid); -- 2.28.0