SYS-OSS/FRET-LibAFL
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix Typo. (#330)

Browse Source
This commit is contained in:
intrigus-lgtm 2021-10-14 18:57:39 +02:00 committed by GitHub
parent a782e8faaa
commit 0a1e8be256
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/message_passing/message_passing.md
View File

@ -27,7 +27,7 @@ Throughout LibAFL, we use a wrapper around different operating system's shared m
Shared maps are the backbone of `LLMP`. Shared maps are the backbone of `LLMP`.
Each client, usually a fuzzer trying to share stats and new testcases, maps an outgoing `ShMem` map. Each client, usually a fuzzer trying to share stats and new testcases, maps an outgoing `ShMem` map.
With very few exceptions, only this client writes to this map, therefore, we do not run in race conditions and can live without locks. With very few exceptions, only this client writes to this map, therefore, we do not run in race conditions and can live without locks.
The broker reas from all client's `ShMem` maps. The broker reads from all client's `ShMem` maps.
It checks all incoming client maps periodically, and then forwards new messages to its outgoing broadcast-`ShMem`, mapped by all connected clients. It checks all incoming client maps periodically, and then forwards new messages to its outgoing broadcast-`ShMem`, mapped by all connected clients.
To send new messages, a client places a new message at the end of their map, and then updates a static field to notify the broker. To send new messages, a client places a new message at the end of their map, and then updates a static field to notify the broker.