{"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\/hu\/blog\/news\/predstavlena-vetka-yadra-linus-next-dlya-testirovaniya-v-rezhime-nepreryvnoj-integraczii","title":{"rendered":"A linus-next kernel branch has been introduced for continuous integration testing.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Sasha Levin a Google v\u00e1llalat munkat\u00e1rsa, aki a Linux kernel LTS \u00e1g\u00e1nak karbantart\u00e1s\u00e1val foglalkozik, \u00e9s tagja a Linux Foundation tan\u00e1csad\u00f3 test\u00fclet\u00e9nek, bejelentette egy \u00faj Linux kernel \u00e1g, a \u201elinus-next\u201d l\u00e9trehoz\u00e1s\u00e1t. Ez az \u00e1g a \u201elinux-next\u201d \u00e1g mint\u00e1j\u00e1ra k\u00e9sz\u00fclt, amely az alap kernel \u00e1gba j\u00f6v\u0151 v\u00e1ltoztat\u00e1sok tesztel\u00e9s\u00e9re szolg\u00e1l, de a stabilabb \u00e9s tesztel\u00e9sre alkalmasabb b\u00e1zisra \u00f6sszpontos\u00edt. <\/p>\n
A kor\u00e1bban haszn\u00e1lt \u201elinux-next\u201d \u00e1g remek\u00fcl alkalmas a kernelbe t\u00f6rt\u00e9n\u0151 v\u00e1ltoztat\u00e1sok integr\u00e1ci\u00f3j\u00e1nak ellen\u0151rz\u00e9s\u00e9re, a k\u00fcl\u00f6nb\u00f6z\u0151 karbantart\u00f3k al\u00e1gai k\u00f6z\u00f6tti konfliktusok \u00e9rt\u00e9kel\u00e9s\u00e9re, valamint a ford\u00edt\u00e1s sor\u00e1n fell\u00e9p\u0151 hib\u00e1k \u00e9s figyelmeztet\u00e9sek azonos\u00edt\u00e1s\u00e1ra, de a bevezetett v\u00e1ltoztat\u00e1sok tesztel\u00e9s\u00e9re probl\u00e9m\u00e1s. A \u201elinux-next\u201d \u00e1g tartalmaz egy kever\u00e9ket a f\u0151 kernel \u00e1gba \u00e1tvihet\u0151 v\u00e1ltoztat\u00e1sokb\u00f3l, valamint k\u00eds\u00e9rleti b\u0151v\u00edtm\u00e9nyekb\u0151l, amelyek m\u00e9g sok\u00e1ig finom\u00edt\u00e1s alatt \u00e1llhatnak, \u00e9s lehet, hogy sohasem ker\u00fclnek a f\u0151 kernel \u00e1gba. <\/p>\n
A nem stabil k\u00eds\u00e9rleti k\u00f3dok jelenl\u00e9te nem teszi lehet\u0151v\u00e9 a \u201elinux-next\u201d kernel teljes k\u00f6r\u0171 munkatesztel\u00e9s\u00e9t, mivel a k\u00eds\u00e9rleti k\u00f3dok negat\u00edvan befoly\u00e1solhatj\u00e1k a kernel egy\u00e9b alrendszereit. Az \u00faj \u201elinus-next\u201d \u00e1gban a v\u00e1ltoztat\u00e1sok elfogad\u00e1s\u00e1nak krit\u00e9riumai szigor\u00fabbak lesznek \u2013 olyan pull-reqeustok fognak beker\u00fclni, amelyeket Linus Torvaldsnak c\u00edmeztek, \u00e9s amelyek felt\u00e9telez\u00e9sek szerint Linus a f\u0151 kernel \u00e1gba fogad el. <\/p>\n
A \"linus-next\" branch will allow not only testing the compatibility of proposed changes at the kernel assembly level but also evaluating the work directly, which will lead to improved quality of testing changes at the stage of reviewing pull requests that have already been submitted but not yet reviewed by Linus. The new branch will also encourage the submission of pull requests as early as possible, even before the window for accepting changes opens, to allow for their testing in operation. Furthermore, the \"linus-next\" branch will develop according to a continuous integration model rather than daily updates with the creation of new tags, which will simplify the analysis of emerging issues and the identification of specific changes that caused failures. <\/p>\n
Tov\u00e1bbiakban \u00e9rdemes megeml\u00edteni Linus Torvalds el\u00e9gedetlens\u00e9g\u00e9t a hardware sebezhet\u0151s\u00e9gek kernel szint\u0171 blokkol\u00e1si folyamat\u00e1val kapcsolatban, amelyet a CPU spekulat\u00edv utas\u00edt\u00e1sv\u00e9grehajt\u00e1s\u00e1nak sebezhet\u0151s\u00e9geivel kapcsolatos probl\u00e9m\u00e1k \u00e9s regresszi\u00f3k megvitat\u00e1sa sor\u00e1n fejtett ki. A hardware sebezhet\u0151s\u00e9gek blokkol\u00e1s\u00e1hoz sz\u00fcks\u00e9ges v\u00e1ltoztat\u00e1sok bonyol\u00edtj\u00e1k a fejleszt\u00e9st, regresszi\u00f3kat id\u00e9znek el\u0151, \u00e9s negat\u00edvan befoly\u00e1solj\u00e1k a teljes\u00edtm\u00e9nyt, mik\u00f6zben a hasonl\u00f3 sebezhet\u0151s\u00e9geken alapul\u00f3 t\u00e1mad\u00e1sok t\u00f6bbs\u00e9ge csup\u00e1n elm\u00e9leti, \u00e9s soha nem val\u00f3sul meg a gyakorlatban, laborat\u00f3riumi k\u00f6r\u00fclm\u00e9nyek n\u00e9lk\u00fcl. <\/p>\n
A hardware sebezhet\u0151s\u00e9gekkel kapcsolatos potenci\u00e1lis probl\u00e9m\u00e1k kezel\u00e9se \u00e9rdek\u00e9ben Linus javasolta, hogy a felel\u0151ss\u00e9get a hardvergy\u00e1rt\u00f3kra h\u00e1r\u00edts\u00e1k, mint a hardware sebezhet\u0151s\u00e9gek kialakul\u00e1s\u00e1nak okoz\u00f3ir\u00f3l, \u00e9s jelezze, hogy nekik kell \u00f6n\u00e1ll\u00f3an megoldaniuk saj\u00e1t probl\u00e9m\u00e1ikat. A javasolt m\u00f3dos\u00edt\u00e1st biztos\u00edt\u00e1si int\u00e9zked\u00e9sk\u00e9nt indokolt\u00e1k, mivel a CPU viselked\u00e9s\u00e9nek bizonytalans\u00e1ga miatt a v\u00e9delem potenci\u00e1lisan nem m\u0171k\u00f6dhet n\u00e9h\u00e1ny \u00faj Intel CPU-n. \n Forr\u00e1s: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"