 Hello everyone, this is Piyush Mishra, currently pursuing my Bachelor of Technology in Professor of Science and Engineering from Bundelkhand University, Jhasi. And these are the slides that I have maintained from mentorship showcase 2023. I came from, I basically belong from Android Development and I have worked on open source development too. And I started working with the Linux environment a year ago for continuing my Android development. Linux kernel bug fixing project was my project under Linux foundation Fall and Paid 2022 that I was enrolled in and the topics I am going to cover will be virtualization, sending patches kernel maintenance. So entire debugging program, entire debugging profile was completely new for me. I maintained my Linux build environment from sites like Linux from scratch.org. But debugging was really a typical matter. So kernel bug fixing the messenger and fixing the issues in the procedure. As we all know that kernel acts like the messenger between the software and hardware level interfaces. And why do we have bugs? We have bugs to make sure that to bugs tell us that there is something that needs to be improved. So as of effective operating system, as of an effective operating system, simple and powerful Linux was the operating system that I chose to work upon. And compatible with Android 2 as Android is based upon Linux architecture, Linux kernel, how it starts. So I started with the open source development and working with the Linux environment. Then I go on through Linux from scratch.org. So half build or working procedure. I built up a build environment and I completely built a Linux kernel, completely built a bootable kernel, which could be booted using Kim. So these are the development environment that I have gone through. The major challenges in these mentorship was understanding the tasks was a major deal as you have to get what you have to do. Then you have to search what you have to do or you have to ask what you have to do. Starting with the mainline source, working with mainline, compiling and booting it. And then working with the syscaller, working with the sysbot dashboard for actively looking into the bugs and how they could be improved was a major task for me. Understanding the kernel.org logs, building the key foundation resources for debugging the kernel. Finding resources is also a major task in this mentorship as you have to actively look upon the web for resources that you could collect or you cannot further proceed in that procedure. Virtualization, the life and time saver as if you don't want to spoil your machine, main cold boot machine, then you can build the kernel upon the key move. Using virtual boss or GTP techniques, booting the compiled kernel with Kim and using GTP and build route. So there was a task of mine that I have to define fuzzing. Fuzzing is simply executing a program over a point with different inputs to break the program in order to fix it in order to detect bugs. Stacktrace was there. We have to use decode the stacktrace.sh script for finding the PIDs and for finding the processes that go upon while the kernel is booting. Syscaller and sysbot are debuggers too. While working with the syscaller tools, syscaller is actually maintained by Google and sysbot is the dashboard where you get about the bugs online that gives you about a critical level of bugs that are listed upon sysbot dashboard. So in all the procedures, the most effective tools were Kim. As I have told before, it prevents you from using your main machine as the code you are entering or debugging procedures you are going through and break the machine and counter the chances of exploiting the machine. Sending patches. Email sending was the major task enrolled in this program as sending emails is the way of sharing what you have done upon the kernel with the other developers being the biggest development environment. This is the most active form of communication between the developers. My work that I did in this mentorship program was to create patches and generate patches and actively look for what other bugs that could be resolved as it was completely new for me. I created patches and submitted as of my task to my mentor and I get used to with checkpatch.pl script and various other scripts too. In the meantime, I came in knowledge. Actually, this was a bug case in that case in reported in September. In September, that was reserve SFA size. So rearranging the flow action size or there was just a bit manipulation with the code that fixed the bug. So it was a minor change that saved the day. And I learned about that. It was not fixed by me, but I learned about how we can get into debugging while we are working with the kernel. The kernel mailing list is actually an important task as the kernel mailing list keeps you updated about what active bugs are being found or what active bugs need to be resolved. So I also came up with other bugs that I founded. I also came up with other bugs. Please wait a second. Yeah. So these are the four bugs that were resolved earlier. And I came up with the reference that what these bugs were capable of and actually these bugs were fixed. These were evos-stopping bugs that were used for active communication reaching in Android and fixed in October 2021 patch. Later, these bugs were also fixed in updates about Android 12 and are confirmed to be fixed in Android 13 updates as well. So these bugs were fixed and learning about how bugs work, learning about what impact that they can make, or this was my mentorship experience with Linux Foundation. So thank you everyone. So thank you everyone. Again, as we all have bugs and we all fixed them. So thanks again to Linux Foundation, my peers, my mentors and everyone. Thank you.