Skip to content

P
parallel_fuzzing
Commit 2093d49d by Xu Zhou
Options

add abstract.

parent f8946d29
Showing with 1 additions and 87 deletions
Conference-LaTeX-template_7-9-18/conference_041818.aux deleted 100644 → 0
\relax
\@writefile{toc}{\contentsline {section}{\numberline {I}Introduction}{1}}
\@writefile{toc}{\contentsline {section}{\numberline {II}background}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {II-A}}Parallel computing technology}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {II-B}}The details about AFL}{2}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {II-B}1}Seed}{2}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {II-B}2}Bitmap}{2}}
\newlabel{eq1}{{1}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {II-C}}The discussion of parallel mechanism in fuzzing}{2}}
\@writefile{loa}{\contentsline {algorithm}{\numberline {1}{\ignorespaces 123}}{3}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {II-C}1}A Na\IeC {\"\i }ve approach}{3}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {II-C}2}Previous parallel fuzzing application}{3}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {II-D}}Concurrency and data race}{3}}
\@writefile{toc}{\contentsline {section}{\numberline {III}methodology}{3}}
\newlabel{alogrithm}{{III}{3}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {III-A}}The algorithm of balancing workloads}{3}}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Example of distributing workloads}}{3}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(a)}{\ignorespaces {The example of distributing workloads by previous works }}}{3}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(b)}{\ignorespaces {The example of distributing workloads by p-fuzz}}}{3}}
\newlabel{figcarrybox}{{1}{3}}
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces the framework overview of p-fuzz}}{4}}
\newlabel{figoverview}{{2}{4}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {III-B}}Immediate response to update}{4}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {III-C}}Data race handling}{4}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {III-C}1}Flag:two clients want to access the same seed simultaneously.}{4}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {III-C}2}Service:some clients update bitmap in the database simultaneously}{4}}
\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces race of updating bitmap from different clients}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(a)}{\ignorespaces {the origin bitmap}}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(b)}{\ignorespaces {the bitmap updated from client1}}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(c)}{\ignorespaces {the bitmap updated from client2}}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(d)}{\ignorespaces {the final bitmap}}}{4}}
\newlabel{figbitmap}{{3}{4}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {III-C}3}Time stamp:a client quits fuzzing accidently but doesn\IeC {\textquoteright }t finish a complete fuzzing round}{4}}
\@writefile{toc}{\contentsline {section}{\numberline {IV}implementation}{4}}
\newlabel{implementation}{{IV}{4}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {IV-A}}Workflow}{4}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {IV-B}}Server}{4}}
\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces the two collections of database}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(a)}{\ignorespaces {the seed collection in the database}}}{4}}
\@writefile{lof}{\contentsline {subfigure}{\numberline{(b)}{\ignorespaces {the bitmap collection in the database}}}{4}}
\newlabel{figdatabase}{{4}{4}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {IV-B}1}MongoDB}{5}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {\unhbox \voidb@x \hbox {IV-B}2}Service}{5}}
\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces the workflow of service}}{5}}
\newlabel{figservice}{{5}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {IV-C}}Client}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {V}experiment}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {V-A}}experiment setup}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {V-B}}comparison in crashes and branches}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {V-C}}comparison in speed}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {VI}discussion}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VI-A}}limitation}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VI-B}}future work}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {VII}conclusion}{5}}
\newlabel{eq}{{2}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VII-A}}\LaTeX -Specific Advice}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VII-B}}Some Common Mistakes}{5}}
\newlabel{SCM}{{\unhbox \voidb@x \hbox {VII-B}}{5}}
\citation{b7}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VII-C}}Authors and Affiliations}{6}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VII-D}}Identify the Headings}{6}}
\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb@x \hbox {VII-E}}Figures and Tables}{6}}
\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb@x \hbox {VII-E}0a}Positioning Figures and Tables}{6}}
\@writefile{lot}{\contentsline {table}{\numberline {I}{\ignorespaces Table Type Styles}}{6}}
\newlabel{tab1}{{I}{6}}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Example of a figure caption.}}{6}}
\newlabel{fig}{{6}{6}}
\citation{b1}
\citation{b2}
\citation{b3}
\citation{b3}
\citation{b3}
\citation{b3}
\citation{b4}
\citation{b5}
\citation{b6}
\bibcite{b1}{1}
\bibcite{b2}{2}
\bibcite{b3}{3}
\bibcite{b4}{4}
\bibcite{b5}{5}
\bibcite{b6}{6}
\bibcite{b7}{7}
\@writefile{toc}{\contentsline {section}{References}{7}}
Conference-LaTeX-template_7-9-18/conference_041818.tex
......@@ -63,9 +63,7 @@ email address}
\maketitle
\begin{abstract}
This document is a model and instructions for \LaTeX.
This and the IEEEtran.cls file define the components of your paper [title, text, heads, etc.]. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes,
or Math in Paper Title or Abstract.
Fuzz is an effective technology in software testing and security vulnerability detection. Unfortunately, fuzzing is an extremely compute-intensive job, which may cause thousands of computing hours to find a bug. Current novel works generally improve fuzzing efficiency by developping delicate algorithms. In this paper, we propose another direction of improvement in this filed, i.e., leveraging parallel computing to improve fuzzing effiency. In this way, we develop p-fuzz, a parallel fuzzing system that can utilize massive distributed computing resources to fuzz a single program. p-fuzz uses a no-sql database to share the fuzzing status such as seeds, covered paths, etc. All fuzzing nodes get jobs from the database, and update their fuzzing status to the database. We control the synchronization period to a coarse granularity so that the database will not be a bottleneck. P-fuzz is implemented based on AFL. We compare p-fuzz with AFL and XXX in our experiment. The result shows that we can easily gain a speedup of AFL by simply using 4 nodes, i.e., using 3X more resources.
\end{abstract}
\begin{IEEEkeywords}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment