summaryrefslogtreecommitdiffstats
path: root/sql/recovery.cc
diff options
context:
space:
mode:
authorshess <shess@chromium.org>2016-02-01 21:15:06 -0800
committerCommit bot <commit-bot@chromium.org>2016-02-02 05:16:20 +0000
commit874ea1bd6ec404bc536c45098910694dea5adb34 (patch)
tree7e4c2c84e9667d38ce7043b698775d231375075b /sql/recovery.cc
parent461ea3688962358c56aef129f01a3de51f41123f (diff)
downloadchromium_src-874ea1bd6ec404bc536c45098910694dea5adb34.zip
chromium_src-874ea1bd6ec404bc536c45098910694dea5adb34.tar.gz
chromium_src-874ea1bd6ec404bc536c45098910694dea5adb34.tar.bz2
[sql] Prevent recovery against a closed database.
The referenced bug is a crash which appears to happen when recovery is attempted against a poisoned (or closed) database. Modify sql::Recovery::Begin() to explicitly short-circuit recovery if the passed connection handle is not open. Otherwise the recovery code will work until the recovered data is restored over the original, and then fail. Also modify the sql::Connection::ReportDiagnosticInfo() to clear the error callback while doing any integrity check. This is a bit of a hack in the interests of not rooting out the crazy error-callback assumptions at this time. BUG=583106 Review URL: https://codereview.chromium.org/1657593005 Cr-Commit-Position: refs/heads/master@{#372896}
Diffstat (limited to 'sql/recovery.cc')
-rw-r--r--sql/recovery.cc10
1 files changed, 10 insertions, 0 deletions
diff --git a/sql/recovery.cc b/sql/recovery.cc
index 377aafb..5e101b1 100644
--- a/sql/recovery.cc
+++ b/sql/recovery.cc
@@ -108,6 +108,16 @@ bool Recovery::FullRecoverySupported() {
scoped_ptr<Recovery> Recovery::Begin(
Connection* connection,
const base::FilePath& db_path) {
+ // Recovery is likely to be used in error handling. Since recovery changes
+ // the state of the handle, protect against multiple layers attempting the
+ // same recovery.
+ if (!connection->is_open()) {
+ // Warn about API mis-use.
+ DLOG_IF(FATAL, !connection->poisoned_)
+ << "Illegal to recover with closed database";
+ return scoped_ptr<Recovery>();
+ }
+
scoped_ptr<Recovery> r(new Recovery(connection));
if (!r->Init(db_path)) {
// TODO(shess): Should Init() failure result in Raze()?