{"id":120265,"date":"2024-10-22T13:09:17","date_gmt":"2024-10-22T11:09:17","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/predstavlena-vetka-yadra-linus-next-dlya-testirovaniya-v-rezhime-nepreryvnoj-integraczii"},"modified":"2024-10-22T13:09:17","modified_gmt":"2024-10-22T11:09:17","slug":"predstavlena-vetka-yadra-linus-next-dlya-testirovaniya-v-rezhime-nepreryvnoj-integraczii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/predstavlena-vetka-yadra-linus-next-dlya-testirovaniya-v-rezhime-nepreryvnoj-integraczii","title":{"rendered":"The linus-next kernel branch has been introduced for testing in continuous integration mode.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Sasha Levin from Google, who manages the LTS branches of the Linux kernel and is a member of the advisory board of the Linux Foundation, has announced the creation of a new Linux kernel branch \u2014 'linus-next'. This branch, similar to 'linux-next', is intended for testing changes proposed for inclusion in the main future Linux kernel branch, but it differs in its focus on changes ready for acceptance into the main branch and providing a more stable and testable base. <\/p>\n
The previously used 'linux-next' branch is excellent for checking the integration of changes into the kernel, assessing conflicts between sub-branches from different maintainers, and identifying related build errors and warnings. However, it is problematic to use it for testing the functionality of the changes being introduced. The 'linux-next' branch includes a mix of changes ready for transfer to the main kernel and experimental additions that may take a long time to finalize and might never be accepted into the main kernel branch. <\/p>\n
The presence of unstable experimental code prevents the 'linux-next' kernel from being used for full-fledged working testing, as the experimental code can negatively impact other kernel subsystems. In the new 'linus-next' branch, the criteria for accepting changes will be stricter \u2014 only pull requests addressed to Linus Torvalds that, according to the developers, Linus is expected to accept into the main kernel branch will be included. <\/p>\n
The emergence of the branch «linus-next» will provide an opportunity not only to test the compatibility of proposed changes at the kernel assembly level, but also to directly evaluate their performance, leading to an improved quality of testing changes at the review stage of already submitted but not yet reviewed pull requests by Linus. The new branch will also encourage the submission of pull requests as early as possible, even before the changes acceptance window opens, to allow for testing in real conditions. Furthermore, the «linus-next» branch will develop according to a continuous integration model rather than a daily update with the creation of a new tag, simplifying the analysis of emerging issues and identifying the specific changes that caused failures. <\/p>\n
Additionally, it is worth noting Linus Torvalds' dissatisfaction with the process of blocking hardware vulnerabilities at the kernel level, expressed during discussions about issues and regressions in the code aimed at countering attacks that exploit vulnerabilities in the CPU's speculative execution mechanism. The changes necessary to block hardware vulnerabilities complicate development, lead to regressions, and negatively impact performance, given that most attacks exploiting such vulnerabilities are purely theoretical and never occur in practice outside of laboratory conditions. <\/p>\n
Considering the proposal to modify the kernel to bypass potential issues in countering hardware vulnerabilities, Linus suggested placing the responsibility on hardware manufacturers, as the culprits behind the emergence of hardware vulnerabilities, and making it clear that they should address their own problems. The proposed change was suggested as a precaution, as the uncertainty in CPU behavior could potentially render protection ineffective on some new Intel CPUs. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"