![]() ![]() Last week, in response to these "Hypocrite Commits," senior Linux kernel dev Greg Kroah-Hartman reverted 68 patches submitted by folks with umn.edu email addresses. Lu, Wu, and Pakki published their findings in February at the 42nd IEEE Symposium on Security and Privacy. Once the maintainers responded to the submitted patch, the UMN researchers pointed out the bug introduced by their patch and offered a "proper" patch-one that did not introduce a newly exploitable condition-in its place. The three researchers would then email their Trojan-horse patches to Linux kernel maintainers to see if the maintainers detected the more serious problem the researchers had introduced in the course of fixing a minor bug. These minor patches however introduce the missing conditions of the "immature vulnerabilities." The "immature vulnerabilities" are not real vulnerabilities because one condition (such as a use of a freed object) is still missing We construct three incorrect or incomplete minor patches to fix the three bugs. We employ a static-analysis tool to identify three "immature vulnerabilities" in Linux, and correspondingly detect three real minor bugs that are supposed to be fixed. The trio's scheme involved first finding three easy-to-fix, low-priority bugs in the Linux kernel and then fixing them-but fixing them in such a way as to complete what the UMN researchers called an "immature vulnerability": This policy change came as a result of three University of Minnesota researchers-Qiushi Wu, Kangjie Lu, and Aditya Pakki-embarking on a program to test the Linux kernel dev community's resistance to what the group called "Hypocrite Commits." Testing the Linux kernel community Last week, senior Linux kernel developer Greg Kroah-Hartman announced that all Linux patches coming from the University of Minnesota would be summarily rejected by default. After that, if you still have any questions, ask on the kernelnewbies mailing list or in the #kernelnewbies IRC channel.DJRPhoto36 / Flickr reader comments 561 with To learn more, read the KernelNewbies First Kernel Patch tutorial. The Eudyptula challenge is a great way to learn kernel basics.(All questions were answered, and this way saves reading time.) (Notice that the last question was unintentionally left unanswered in the reply.) Do you want to schedule the meeting tomorrow? Yes let’s schedule the meeting tomorrow, on the second floor. Note: Do not top-post to communicate with the reviewer of your patch! Here's an example:.Go through the linux.git log to see commits by previous authors for inspiration.Coccinelle is a helpful tool for pattern matching.You could complete TODOs left incomplete by developers:.Perl scripts/ -f drivers/staging/android/* | less The script detects coding style errors for you.To learn more, read the Linux kernel coding style documentation. You also could start with correcting coding style issues in the code.When you get familiar with the patch-sending process, you could send subsystem-specific patches with increased complexity. Greg Kroah-Hartman's staging tree is a good place to submit your first patch as he accepts easy patches from new contributors.What to know before submitting your first patch To know the list of maintainers to whom to send the patch, use the get_ script. Free online course: RHEL Technical Overview.Step 7: Commit your changes and create a patch. Recompile using make command to ensure that your change does not produce errors. Git rebase origin/staging-testing Step 6: Make a change to the code base. git checkout -b first-patch Step 5: Update your kernel to point to the latest code base. ![]() Sudo make modules_install install Step 4: Make a branch and switch to it. config Step 3: Build/install your kernel. Git:///pub/scm/linux/kernel/git/gregkh/staging.git Copy your current config: cp /boot/config-`uname -r`*. Step 2: Download the Linux kernel code repository : git clone -b staging-testing Steps in this article assume you have the following tools on your system: Contributing to the kernel Step 1: Prepare your system. For a more in-depth look at the submission process for contributing your first patch, read the KernelNewbies First Kernel Patch tutorial. In this article, I'll provide a quick checklist of steps involved with making your first kernel contribution, and look at what you should know before submitting a patch. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |