From: Dan Carpenter <dan.carpenter@oracle.com>
To: javier@javigon.com
Cc: linux-block@vger.kernel.org
Subject: [bug report] lightnvm: pblk: return NVM_ error on failed submission
Date: Mon, 11 May 2020 16:50:58 +0300 [thread overview]
Message-ID: <20200511135058.GA216886@mwanda> (raw)
Hello Javier González,
The patch b6730dd4a954: "lightnvm: pblk: return NVM_ error on failed
submission" from Jun 1, 2018, leads to the following static checker
warning:
drivers/lightnvm/pblk-recovery.c:473 pblk_recov_scan_oob()
warn: 'pblk->inflight_io.counter' not decremented on lines: 426.
drivers/lightnvm/pblk-recovery.c
417
418 for (j = 0; j < pblk->min_write_pgs; j++, i++)
419 ppa_list[i] =
420 addr_to_gen_ppa(pblk, paddr + j, line->id);
421 }
422
423 ret = pblk_submit_io_sync(pblk, rqd, data);
424 if (ret) {
425 pblk_err(pblk, "I/O submission failed: %d\n", ret);
426 return ret;
The pblk_submit_io_sync() increments the pblk->inflight_io counter but
doesn't decrement it on all error paths. It looks like something a
little bit subtle is going no but I'm not sure how it works exactly.
427 }
428
429 atomic_dec(&pblk->inflight_io);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
430
431 /* If a read fails, do a best effort by padding the line and retrying */
432 if (rqd->error && rqd->error != NVM_RSP_WARN_HIGHECC) {
433 int pad_distance, ret;
434
435 if (padded) {
436 pblk_log_read_err(pblk, rqd);
437 return -EINTR;
438 }
439
regards,
dan carpenter
next reply other threads:[~2020-05-11 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:50 Dan Carpenter [this message]
2020-05-12 9:03 ` [bug report] lightnvm: pblk: return NVM_ error on failed submission Javier González
2020-05-12 11:29 ` Dan Carpenter
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=20200511135058.GA216886@mwanda \
--to=dan.carpenter@oracle.com \
--cc=javier@javigon.com \
--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;
as well as URLs for NNTP newsgroup(s).