From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <876a2abe-41ab-5819-4ae8-ad26186d0d1c@kernel.org> <226099bc-9763-3a73-e26a-b292f601494c@kernel.org> <20191011180248.GA24089@rei.lan> <20191014085414.GB31760@rei.lan> <62903a33-8ffc-56b6-de1a-539f10b5de2a@oracle.com> <86bde120-e5fe-4bb1-9b93-769a444500f9@oracle.com> <8a4dbbb1-f8ba-00ba-41d2-d82a35fc0f81@oracle.com> In-Reply-To: From: Palash Oswal Date: Thu, 12 May 2022 14:05:09 -0400 Message-ID: Subject: Re: [Automated-testing] syzkaller reproducers Content-Type: text/plain; charset="UTF-8" List-ID: To: syzkaller , Shuah Khan , kernelci@groups.io, automated-testing@yoctoproject.org, george.kennedy@oracle.com + Shuah, George and mailing lists Google groups did not CC all of the members in the thread for my reply. It would be valuable to get everyone's feedback on this thread. On Sat, May 7, 2022 at 11:34 PM Palash wrote: > > Hello all, > > Reviving this old thread. Do we think there's value in automatically publishing a C reproducer(if it exists) whenever syzkaller determines a reported bug is patched and fixed? > This allows us to track these reproducers more diligently and we only have reproducers for the bugs that have been patched. > If this is valuable, then we could think about answering these questions - > 1. Is there a particular way we want to format the reproducers? (Example : SKIP/OK/FAIL/TIMEOUT (if output is possible)) > 2. Where do we want to submit the reproducers to be added to the testing project and what is the process we want to use? > 3. Is it valuable to record the crash report information for the original fuzzer crash when the c reproducer is filed to add context to it; in case developers want to troubleshoot? This could save valuable debugging time. > > Happy to contribute on this change to the upstream fuzzing system. > > Thanks, > Palash > On Friday, March 13, 2020 at 11:59:31 AM UTC-4 shuah wrote: >> >> On 3/3/20 1:45 AM, Dmitry Vyukov wrote: >> > Shauh, >> > >> > We've added more reproducers to: >> > https://github.com/dvyukov/syzkaller-repros/tree/master/linux >> > >> > It makes sense to pull in them to the kernel-arts repo. Not sure >> > what's the most convenient way for you since it's not exactly a >> > traditional "patch"? Perhaps you just copy linux/*.c files and commit? >> > >> >> Thanks Dmitry. I will pull these in. I will pull these in. >> >> thanks, >> -- Shuah > > -- > You received this message because you are subscribed to a topic in the Google Groups "syzkaller" group. > To unsubscribe from this topic, visit https://groups.google.com/d/topic/syzkaller/RQFLqAvdsEc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to syzkaller+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/cd301033-f152-4eeb-bce3-2d95f39a05fbn%40googlegroups.com.