]> git.ipfire.org Git - thirdparty/sqlite.git/commit
When rolling back a journal that contains a super-journal pointer, only attempt to...
authordrh <>
Wed, 24 Jun 2026 20:28:31 +0000 (20:28 +0000)
committerdrh <>
Wed, 24 Jun 2026 20:28:31 +0000 (20:28 +0000)
commita2d0dcb1a09548f1fb8db345d700151715e6bdf5
treee80ab9f30264c59dbf1fd8d955682bc2e3b49eab
parent160a2c26d2fd265fac572b004d35a1dc00f356f1
When rolling back a journal that contains a super-journal pointer, only attempt to unlink the super-journal if (a) the filename looks like one that SQLite might have generated, and (b) the super-journal contains the name of the journal being rolled back. This is to limit the extent to which SQLite can be caused to delete arbitrary files by supplying it with a crafted hot-journal.

FossilOrigin-Name: 9471fa2c9ce03713b875b3350d65b5ed6e38e501585126bb3b90694800edfb25
manifest
manifest.uuid
src/pager.c
test/mjournal.test
test/tester.tcl