mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-10 11:55:49 +00:00
8e72e4cc2f
This patch adjusts tools/fuzzing/ in such a way that the relevant parts can be reused in the JS engine. Changes in detail include: * Various JS_STANDALONE checks to exclude parts that cannot be included in those builds. * Turn LibFuzzerRegistry and LibFuzzerRunner into generic FuzzerRegistry and FuzzerRunner classes and use them for AFL as well. Previously, AFL was piggy-backing on gtests which was kind of an ugly solution anyway (besides that it can't work in JS). Now more code like registry and harness is shared between the two and they follow almost the same call paths and entry points. AFL macros in FuzzingInterface have been rewritten accordingly. This also required name changes in various places. Furthermore, this unifies the way, the fuzzing target is selected, using the FUZZER environment variable rather than LIBFUZZER (using LIBFUZZER in browser builds will give you a deprecation warning because I know some people are using this already and need time to switch). Previously, AFL target had to be selected using GTEST_FILTER, so this is also much better now. * I had to split up FuzzingInterface* such that the STREAM parts are in a separate set of files FuzzingInterfaceStream* because they use nsStringStream which is not allowed to be included into the JS engine even in a full browser build (error: "Using XPCOM strings is limited to code linked into libxul."). I also had to pull FuzzingInterface.cpp (the RAW part only) into the header and make it static because otherwise, would have to make not only separate files but also separate libraries to statically link to the JS engine, which seemed overkill for a single small function. The streaming equivalent of the function is still in a cpp file. * LibFuzzerRegister functions are now unique by appending the module name to avoid redefinition errors. MozReview-Commit-ID: 44zWCdglnHr --HG-- extra : rebase_source : fe07c557032fd33257eb701190becfaf85ab79d0 |
||
---|---|---|
.. | ||
build | ||
fuzztest | ||
ipc | ||
test | ||
third_party | ||
common.build | ||
databuffer.h | ||
dtlsidentity.cpp | ||
dtlsidentity.h | ||
logging.h | ||
m_cpp_utils.h | ||
moz.build | ||
nr_socket_prsock.cpp | ||
nr_socket_prsock.h | ||
nr_timer.cpp | ||
nricectx.cpp | ||
nricectx.h | ||
nricectxhandler.cpp | ||
nricectxhandler.h | ||
nricemediastream.cpp | ||
nricemediastream.h | ||
nriceresolver.cpp | ||
nriceresolver.h | ||
nriceresolverfake.cpp | ||
nriceresolverfake.h | ||
nricestunaddr.cpp | ||
nricestunaddr.h | ||
nrinterfaceprioritizer.cpp | ||
nrinterfaceprioritizer.h | ||
README | ||
rlogconnector.cpp | ||
rlogconnector.h | ||
runnable_utils.h | ||
sigslot.h | ||
simpletokenbucket.cpp | ||
simpletokenbucket.h | ||
stun_socket_filter.cpp | ||
stun_socket_filter.h | ||
test_nr_socket.cpp | ||
test_nr_socket.h | ||
transportflow.cpp | ||
transportflow.h | ||
transportlayer.cpp | ||
transportlayer.h | ||
transportlayerdtls.cpp | ||
transportlayerdtls.h | ||
transportlayerice.cpp | ||
transportlayerice.h | ||
transportlayerlog.cpp | ||
transportlayerlog.h | ||
transportlayerloopback.cpp | ||
transportlayerloopback.h |
This is a generic media transport system for WebRTC. The basic model is that you have a TransportFlow which contains a series of TransportLayers, each of which gets an opportunity to manipulate data up and down the stack (think SysV STREAMS or a standard networking stack). You can also address individual sublayers to manipulate them or to bypass reading and writing at an upper layer; WebRTC uses this to implement DTLS-SRTP. DATAFLOW MODEL Unlike the existing nsSocket I/O system, this is a push rather than a pull system. Clients of the interface do writes downward with SendPacket() and receive notification of incoming packets via callbacks registed via sigslot.h. It is the responsibility of the bottom layer (or any other layer which needs to reference external events) to arrange for that somehow; typically by using nsITimer or the SocketTansportService. This sort of push model is a much better fit for the demands of WebRTC, expecially because ICE contexts span multiple network transports. THREADING MODEL There are no thread locks. It is the responsibility of the caller to arrange that any given TransportLayer/TransportFlow is only manipulated in one thread at once. One good way to do this is to run everything on the STS thread. Many of the existing layer implementations (TransportLayerIce, TransportLayerLoopback) already run on STS so in those cases you must run on STS, though you can do setup on the main thread and then activate them on the STS. EXISTING TRANSPORT LAYERS The following transport layers are currently implemented: * DTLS -- a wrapper around NSS's DTLS [RFC 6347] stack * ICE -- a wrapper around the nICEr ICE [RFC 5245] stack. * Loopback -- a loopback IO mechanism * Logging -- a passthrough that just logs its data The last two are primarily for debugging.