diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-04-11 14:25:03 -0700 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2016-05-31 10:16:13 -0700 |
commit | 25829721211d8e9295cd3539b3ef05ee49a968e0 (patch) | |
tree | aa306c8894fd0652f1af0c9b221c0b632c338970 /Documentation | |
parent | 8acbeed55584c21931238f9b4738e337919029b9 (diff) | |
download | subsurface-25829721211d8e9295cd3539b3ef05ee49a968e0.tar.gz |
Make 'clear_dive()' free the primary dive computer data properly
Our primary dive computer really is special, not just because it's the
first one: it's directly embedded in the "struct dive", and so if you
just walk the divecomputer list, you'll miss it, because it's not _on_
the list, it is the very head _of_ the list.
We had that bug in copy_dive(), and it turns out we have it in
clear_dive() too: clear_dive() would free all the dive computers on the
list, but not the actual primary one.
This is a minor memory leak, no more, so it's not exactly critial, but
let's just do it right.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions