From: coverity-bot <keescook@chromium.org>
To: Kent Overstreet <koverstreet@google.com>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org
Subject: Coverity: bch_cached_dev_run(): Memory - illegal accesses
Date: Mon, 11 Nov 2019 17:35:10 -0800 [thread overview]
Message-ID: <201911111735.F5BA37CD@keescook> (raw)
Hello!
This is an experimental automated report about issues detected by Coverity
from a scan of next-20191108 as part of the linux-next weekly scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by recent commits:
ee66850642ef ("bcache: Use bd_link_disk_holder()")
Coverity reported the following:
*** CID 1487848: Memory - illegal accesses (USE_AFTER_FREE)
/drivers/md/bcache/super.c: 961 in bch_cached_dev_run()
955 SET_BDEV_STATE(&dc->sb, BDEV_STATE_STALE);
956 bch_write_bdev_super(dc, &cl);
957 closure_sync(&cl);
958 }
959
960 add_disk(d->disk);
vvv CID 1487848: Memory - illegal accesses (USE_AFTER_FREE)
vvv Dereferencing freed pointer "dc".
961 bd_link_disk_holder(dc->bdev, dc->disk.disk);
962 /*
963 * won't show up in the uevent file, use udevadm monitor -e instead
964 * only class / kset properties are persistent
965 */
966 kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1487848 ("Memory - illegal accesses")
Fixes: ee66850642ef ("bcache: Use bd_link_disk_holder()")
Thanks for your attention!
--
Coverity-bot
reply other threads:[~2019-11-12 1:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201911111735.F5BA37CD@keescook \
--to=keescook@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=koverstreet@google.com \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.