]> git.pond.sub.org Git - empserver/commit
Really fix setsector and setres not to wipe out concurrent updates
authorMarkus Armbruster <armbru@pond.sub.org>
Tue, 8 Jan 2013 16:38:42 +0000 (17:38 +0100)
committerMarkus Armbruster <armbru@pond.sub.org>
Sat, 12 Jan 2013 16:56:34 +0000 (17:56 +0100)
commitbfea79a72d53566745a2310c96c34de1d6ebf45f
tree92e115d07da2c39103652e8e73979947d62d90e9
parentc4c4413ea5fb5a1e9a89c85bc82761ba62fb4800
Really fix setsector and setres not to wipe out concurrent updates

setsector() and setres() continue after check_sect_ok() fails.
Clobbers the updates that made check_sect_ok() fail, triggering a
seqno mismatch oops.

Commit 04a332a8 (v4.3.27) claimed to fix this, but actually only
suppressed the generation oops.
src/lib/commands/setres.c
src/lib/commands/setsect.c