diff options
author | Christian Grothoff <christian@grothoff.org> | 2015-05-21 10:07:58 +0000 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2015-05-21 10:07:58 +0000 |
commit | 7fb5550c4dd74db2bc71ec188a645697416ebb11 (patch) | |
tree | 0804b9b14cda73d205e505079116199db7871855 /src/transport/gnunet-transport-wlan-receiver.c | |
parent | 5cc05fe11eba4926c5ec754f7d0ea596a3b87418 (diff) | |
download | gnunet-7fb5550c4dd74db2bc71ec188a645697416ebb11.tar.gz gnunet-7fb5550c4dd74db2bc71ec188a645697416ebb11.zip |
with respect to #3615: we might (theoretically) get a migration stop before we finished the peerstore lookup; in that case, we would do a GSF_push_start() twice (once via revive migration, and once from peerstore lookup succeeding), and then on disconnect only stop once, keeping the migration going for a disconnected peer. That still does not explain the bug report, as the '*cp' in the report doesn't show BADFOOD, and we'd expect a free'd cp in this case to be used for the transmission. Still, this is a possible issue which can be fixed by ignoring migration stop messages until after peerstore lookup succeeded
Diffstat (limited to 'src/transport/gnunet-transport-wlan-receiver.c')
0 files changed, 0 insertions, 0 deletions