{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":122839397,"defaultBranch":"base-6.6","name":"linux","ownerLogin":"kakra","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2018-02-25T13:39:28.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/17684?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1700977098.0","currentOid":""},"activityList":{"items":[{"before":"76e1b3eeb9a99149bf171453f2f7ced1040e3c41","after":"186029a410e9bf8df21f6d7af3d8d6ce6ff01c84","ref":"refs/heads/rebase-6.6/btrfs-patches","pushedAt":"2024-09-09T19:33:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: add allocator_hint for no allocation preferred\n\nThis is useful where you want to prevent new allocations of chunks on a\ndisk which is going to removed from the pool anyways, e.g. due to bad\nblocks or because it's slow.\n\nSigned-off-by: Kai Krakow ","shortMessageHtmlLink":"btrfs: add allocator_hint for no allocation preferred"}},{"before":"9d24eaa21731132873c7a88955a4a61ef4e6491c","after":"ad07a29023cebd40848fce81e6732d671ede5fe6","ref":"refs/heads/base-6.6","pushedAt":"2024-09-09T19:28:08.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.6.50\n\nLink: https://lore.kernel.org/r/20240905093722.230767298@linuxfoundation.org\nTested-by: Shuah Khan \nLink: https://lore.kernel.org/r/20240905163540.863769972@linuxfoundation.org\nTested-by: Florian Fainelli \nTested-by: Mark Brown \nTested-by: Linux Kernel Functional Testing \nTested-by: Jon Hunter \nTested-by: Harshit Mogalapalli \nTested-by: Peter Schneider \nTested-by: Takeshi Ogasawara \nTested-by: Ron Economos \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.6.50"}},{"before":"7213910600667c51c978e577bf5454d3f7b313b7","after":"9d24eaa21731132873c7a88955a4a61ef4e6491c","ref":"refs/heads/base-6.6","pushedAt":"2024-09-09T19:26:48.000Z","pushType":"push","commitsCount":949,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"i2c: Use IS_REACHABLE() for substituting empty ACPI functions\n\ncommit 71833e79a42178d8a50b5081c98c78ace9325628 upstream.\n\nReplace IS_ENABLED() with IS_REACHABLE() to substitute empty stubs for:\n i2c_acpi_get_i2c_resource()\n i2c_acpi_client_count()\n i2c_acpi_find_bus_speed()\n i2c_acpi_new_device_by_fwnode()\n i2c_adapter *i2c_acpi_find_adapter_by_handle()\n i2c_acpi_waive_d0_probe()\n\ncommit f17c06c6608a (\"i2c: Fix conditional for substituting empty ACPI\nfunctions\") partially fixed this conditional to depend on CONFIG_I2C,\nbut used IS_ENABLED(), which is wrong since CONFIG_I2C is tristate.\n\nCONFIG_ACPI is boolean but let's also change it to use IS_REACHABLE()\nto future-proof it against becoming tristate.\n\nSomehow despite testing various combinations of CONFIG_I2C and CONFIG_ACPI\nwe missed the combination CONFIG_I2C=m, CONFIG_ACPI=y.\n\nSigned-off-by: Richard Fitzgerald \nFixes: f17c06c6608a (\"i2c: Fix conditional for substituting empty ACPI functions\")\nReported-by: kernel test robot \nCloses: https://lore.kernel.org/oe-kbuild-all/202408141333.gYnaitcV-lkp@intel.com/\nReviewed-by: Takashi Iwai \nSigned-off-by: Wolfram Sang \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"i2c: Use IS_REACHABLE() for substituting empty ACPI functions"}},{"before":"a5781ef7ac408018a2127ce37e8de6232253f60b","after":"d29edf912f5a2bb2bcb8b0c8e19eb2efb017f5dc","ref":"refs/heads/rebase-6.6/steam-patches","pushedAt":"2024-08-04T11:52:20.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"ZEN: Input: evdev - use call_rcu when detaching client\n\nSignificant time was spent on synchronize_rcu in evdev_detach_client\nwhen applications closed evdev devices. Switching VT away from a\ngraphical environment commonly leads to mass input device closures,\nwhich could lead to noticable delays on systems with many input devices.\n\nReplace synchronize_rcu with call_rcu, deferring reclaim of the evdev\nclient struct till after the RCU grace period instead of blocking the\ncalling application.\n\nWhile this does not solve all slow evdev fd closures, it takes care of a\ngood portion of them, including this simple test:\n\n\t#include \n\t#include \n\n\tint main(int argc, char *argv[])\n\t{\n\t\tint idx, fd;\n\t\tconst char *path = \"/dev/input/event0\";\n\t\tfor (idx = 0; idx < 1000; idx++) {\n\t\t\tif ((fd = open(path, O_RDWR)) == -1) {\n\t\t\t\treturn -1;\n\t\t\t}\n\t\t\tclose(fd);\n\t\t}\n\t\treturn 0;\n\t}\n\nTime to completion of above test when run locally:\n\n\tBefore: 0m27.111s\n\tAfter: 0m0.018s\n\nSigned-off-by: Kenny Levinsen ","shortMessageHtmlLink":"ZEN: Input: evdev - use call_rcu when detaching client"}},{"before":"2eaf5c0d81911ba05bace3a722cbcd708fdbbcba","after":"7213910600667c51c978e577bf5454d3f7b313b7","ref":"refs/heads/base-6.6","pushedAt":"2024-08-04T11:43:56.000Z","pushType":"push","commitsCount":719,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.6.44\n\nLink: https://lore.kernel.org/r/20240730151639.792277039@linuxfoundation.org\nTested-by: Florian Fainelli \nTested-by: Shuah Khan \nTested-by: Mark Brown \nTested-by: Linux Kernel Functional Testing \nTested-by: Takeshi Ogasawara \nTested-by: Jon Hunter \nTested-by: Peter Schneider \nTested-by: Allen Pais \nTested-by: SeongJae Park \nTested-by: Ron Economos \nTested-by: kernelci.org bot \nTested-by: Conor Dooley \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.6.44"}},{"before":"cffc5a25dcfeaa72a62db168f0c64c2550376117","after":"76e1b3eeb9a99149bf171453f2f7ced1040e3c41","ref":"refs/heads/rebase-6.6/btrfs-patches","pushedAt":"2024-07-19T09:16:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: tree-checker: validate dref root and objectid\n\nNot yet upstreamed.\n\n[CORRUPTION]\nThere is a bug report that btrfs flips RO due to a corruption in the\nextent tree, the involved dumps looks like this:\n\n \titem 188 key (402811572224 168 4096) itemoff 14598 itemsize 79\n \t\textent refs 3 gen 3678544 flags 1\n \t\tref#0: extent data backref root 13835058055282163977 objectid 281473384125923 offset 81432576 count 1\n \t\tref#1: shared data backref parent 1947073626112 count 1\n \t\tref#2: shared data backref parent 1156030103552 count 1\n BTRFS critical (device vdc1: state EA): unable to find ref byte nr 402811572224 parent 0 root 265 owner 28703026 offset 81432576 slot 189\n BTRFS error (device vdc1: state EA): failed to run delayed ref for logical 402811572224 num_bytes 4096 type 178 action 2 ref_mod 1: -2\n\n[CAUSE]\nThe corrupted entry is ref#0 of item 188.\nThe root number 13835058055282163977 is beyond the upper limit for root\nitems (the current limit is 1 << 48), and the objectid also looks\nsuspicious.\n\nOnly the offset and count is correct.\n\n[ENHANCEMENT]\nAlthough it's still unknown why we have such many bytes corrupted\nrandomly, we can still enhance the tree-checker for data backrefs by:\n\n- Validate the root value\n For now there should only be 3 types of roots can have data backref:\n * subvolume trees\n * data reloc trees\n * root tree\n Only for v1 space cache\n\n- validate the objectid value\n The objectid should be a valid inode number.\n\nHopefully we can catch such problem in the future with the new checkers.\n\nReported-by: Kai Krakow \nLink: https://lore.kernel.org/linux-btrfs/CAMthOuPjg5RDT-G_LXeBBUUtzt3cq=JywF+D1_h+JYxe=WKp-Q@mail.gmail.com/#t\nReviewed-by: Filipe Manana \nSigned-off-by: Qu Wenruo ","shortMessageHtmlLink":"btrfs: tree-checker: validate dref root and objectid"}},{"before":"ffc253263a1375a65fa6c9f62a893e9767fbebfa","after":"2eaf5c0d81911ba05bace3a722cbcd708fdbbcba","ref":"refs/heads/base-6.6","pushedAt":"2024-07-19T09:16:17.000Z","pushType":"push","commitsCount":8565,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.6.41\n\nLink: https://lore.kernel.org/r/20240716152751.312512071@linuxfoundation.org\nTested-by: SeongJae Park \nTested-by: Florian Fainelli \nTested-by: Shuah Khan \nTested-by: Allen Pais \nLink: https://lore.kernel.org/r/20240717063802.663310305@linuxfoundation.org\nTested-by: Peter Schneider \nTested-by: Takeshi Ogasawara \nTested-by: Ron Economos \nTested-by: Linux Kernel Functional Testing \nTested-by: Kelsey Steele \nTested-by: Mark Brown \nTested-by: Florian Fainelli \nTested-by: Jon Hunter \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.6.41"}},{"before":"2b554bdebe49d0a673d858acdae673051cf735e1","after":"cffc5a25dcfeaa72a62db168f0c64c2550376117","ref":"refs/heads/rebase-6.6/btrfs-patches","pushedAt":"2024-07-16T09:57:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: tree-checker: validate dref root and objectid\n\nNot yet upstreamed.\n\n[CORRUPTION]\nThere is a bug report that btrfs flips RO due to a corruption in the\nextent tree, the involved dumps looks like this:\n\n \titem 188 key (402811572224 168 4096) itemoff 14598 itemsize 79\n \t\textent refs 3 gen 3678544 flags 1\n \t\tref#0: extent data backref root 13835058055282163977 objectid 281473384125923 offset 81432576 count 1\n \t\tref#1: shared data backref parent 1947073626112 count 1\n \t\tref#2: shared data backref parent 1156030103552 count 1\n BTRFS critical (device vdc1: state EA): unable to find ref byte nr 402811572224 parent 0 root 265 owner 28703026 offset 81432576 slot 189\n BTRFS error (device vdc1: state EA): failed to run delayed ref for logical 402811572224 num_bytes 4096 type 178 action 2 ref_mod 1: -2\n\n[CAUSE]\nThe corrupted entry is ref#0 of item 188.\nThe root number 13835058055282163977 is beyond the upper limit for root\nitems (the current limit is 1 << 48), and the objectid also looks\nsuspicious.\n\nOnly the offset and count is correct.\n\n[ENHANCEMENT]\nAlthough it's still unknown why we have such many bytes corrupted\nrandomly, we can still enhance the tree-checker for data backrefs by:\n\n- Validate the root value\n For now there should only be 3 types of roots can have data backref:\n * subvolume trees\n * data reloc trees\n * root tree\n Only for v1 space cache\n\n- validate the objectid value\n The objectid should be a valid inode number.\n\nHopefully we can catch such problem in the future with the new checkers.\n\nReported-by: Kai Krakow \nLink: https://lore.kernel.org/linux-btrfs/CAMthOuPjg5RDT-G_LXeBBUUtzt3cq=JywF+D1_h+JYxe=WKp-Q@mail.gmail.com/#t\nReviewed-by: Filipe Manana \nSigned-off-by: Qu Wenruo ","shortMessageHtmlLink":"btrfs: tree-checker: validate dref root and objectid"}},{"before":"01a6de57d05bf598d426b737ae0c08917cd4f677","after":"2b554bdebe49d0a673d858acdae673051cf735e1","ref":"refs/heads/rebase-6.6/btrfs-patches","pushedAt":"2024-06-27T21:38:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: add allocator_hint for no allocation preferred\n\nThis is useful where you want to prevent new allocations of chunks on a\ndisk which is going to removed from the pool anyways, e.g. due to bad\nblocks or because it's slow.","shortMessageHtmlLink":"btrfs: add allocator_hint for no allocation preferred"}},{"before":"fd4eb87d6c072b55372e28e7a5971627a7356e9c","after":"a5781ef7ac408018a2127ce37e8de6232253f60b","ref":"refs/heads/rebase-6.6/steam-patches","pushedAt":"2024-01-11T17:51:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"ZEN: Input: evdev - use call_rcu when detaching client\n\nSignificant time was spent on synchronize_rcu in evdev_detach_client\nwhen applications closed evdev devices. Switching VT away from a\ngraphical environment commonly leads to mass input device closures,\nwhich could lead to noticable delays on systems with many input devices.\n\nReplace synchronize_rcu with call_rcu, deferring reclaim of the evdev\nclient struct till after the RCU grace period instead of blocking the\ncalling application.\n\nWhile this does not solve all slow evdev fd closures, it takes care of a\ngood portion of them, including this simple test:\n\n\t#include \n\t#include \n\n\tint main(int argc, char *argv[])\n\t{\n\t\tint idx, fd;\n\t\tconst char *path = \"/dev/input/event0\";\n\t\tfor (idx = 0; idx < 1000; idx++) {\n\t\t\tif ((fd = open(path, O_RDWR)) == -1) {\n\t\t\t\treturn -1;\n\t\t\t}\n\t\t\tclose(fd);\n\t\t}\n\t\treturn 0;\n\t}\n\nTime to completion of above test when run locally:\n\n\tBefore: 0m27.111s\n\tAfter: 0m0.018s\n\nSigned-off-by: Kenny Levinsen ","shortMessageHtmlLink":"ZEN: Input: evdev - use call_rcu when detaching client"}},{"before":null,"after":"a689a088dcf5d118aa3fb0ad489a0b73d5621909","ref":"refs/heads/rebase-6.6/bcache-updates","pushedAt":"2023-11-26T05:38:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"bcache: Only skip data request in io_prio bypass mode\n\nEven if ioprio_bypass hints bypassing the request, we still allow it\nfor REQ_META|REQ_PRIO bio.\n\nCc: Eric Wheeler \nSigned-off-by: Kai Krakow ","shortMessageHtmlLink":"bcache: Only skip data request in io_prio bypass mode"}},{"before":null,"after":"01a6de57d05bf598d426b737ae0c08917cd4f677","ref":"refs/heads/rebase-6.6/btrfs-patches","pushedAt":"2023-11-26T05:38:05.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: add allocator_hint mode\n\nWhen this mode is enabled, the chunk allocation policy is modified as\nfollow.\n\nEach disk may have a different tag:\n- BTRFS_DEV_ALLOCATION_PREFERRED_METADATA\n- BTRFS_DEV_ALLOCATION_METADATA_ONLY\n- BTRFS_DEV_ALLOCATION_DATA_ONLY\n- BTRFS_DEV_ALLOCATION_PREFERRED_DATA (default)\n\nWhere:\n- ALLOCATION_PREFERRED_X means that it is preferred to use this disk for\nthe X chunk type (the other type may be allowed when the space is low)\n- ALLOCATION_X_ONLY means that it is used *only* for the X chunk type.\nThis means also that it is a preferred choice.\n\nEach time the allocator allocates a chunk of type X , first it takes the\ndisks tagged as ALLOCATION_X_ONLY or ALLOCATION_PREFERRED_X; if the space\nis not enough, it uses also the disks tagged as ALLOCATION_METADATA_ONLY;\nif the space is not enough, it uses also the other disks, with the\nexception of the one marked as ALLOCATION_PREFERRED_Y, where Y the other\ntype of chunk (i.e. not X).\n\nSigned-off-by: Goffredo Baroncelli ","shortMessageHtmlLink":"btrfs: add allocator_hint mode"}},{"before":null,"after":"d7c6cf799abaa15b7202a4237c311b1ac46e870a","ref":"refs/heads/rebase-6.6/pf-ksm","pushedAt":"2023-11-26T05:37:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"mm: expose per-process KSM control via syscalls\n\nd7597f59d1d3 added a new API to enable per-process KSM control. It\nhowever uses prctl, which doesn't allow controlling KSM from outside of\nthe current process.\n\nHence, expose this API via 3 syscalls: process_ksm_enable,\nprocess_ksm_disable and process_ksm_status. Given sufficient privileges,\nauto-KSM can be enable by another process.\n\nSince these syscalls are not in the upstream kernel, also expose their\nnumbers under /sys/kernel/process_ksm so that userspace tooling like\nuksmd knows how to use them.\n\nSigned-off-by: Oleksandr Natalenko ","shortMessageHtmlLink":"mm: expose per-process KSM control via syscalls"}},{"before":null,"after":"5edc2983c6717da74e2a289245cb54c085ea792f","ref":"refs/heads/rebase-6.6/clearlinux-tweaks","pushedAt":"2023-11-26T05:37:38.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"sched/fair: remove upper limit on cpu number\n\nSigned-off-by: Colin Ian King ","shortMessageHtmlLink":"sched/fair: remove upper limit on cpu number"}},{"before":null,"after":"72c00d18a65a8d17f670cbe593a76809a0e50b88","ref":"refs/heads/rebase-6.6/xpadneo","pushedAt":"2023-11-26T05:37:26.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"xpadneo: Merge upstream changes\n\nSigned-off-by: Kai Krakow ","shortMessageHtmlLink":"xpadneo: Merge upstream changes"}},{"before":null,"after":"fd4eb87d6c072b55372e28e7a5971627a7356e9c","ref":"refs/heads/rebase-6.6/steam-patches","pushedAt":"2023-11-26T05:37:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"ZEN: Input: evdev - use call_rcu when detaching client\n\nSignificant time was spent on synchronize_rcu in evdev_detach_client\nwhen applications closed evdev devices. Switching VT away from a\ngraphical environment commonly leads to mass input device closures,\nwhich could lead to noticable delays on systems with many input devices.\n\nReplace synchronize_rcu with call_rcu, deferring reclaim of the evdev\nclient struct till after the RCU grace period instead of blocking the\ncalling application.\n\nWhile this does not solve all slow evdev fd closures, it takes care of a\ngood portion of them, including this simple test:\n\n\t#include \n\t#include \n\n\tint main(int argc, char *argv[])\n\t{\n\t\tint idx, fd;\n\t\tconst char *path = \"/dev/input/event0\";\n\t\tfor (idx = 0; idx < 1000; idx++) {\n\t\t\tif ((fd = open(path, O_RDWR)) == -1) {\n\t\t\t\treturn -1;\n\t\t\t}\n\t\t\tclose(fd);\n\t\t}\n\t\treturn 0;\n\t}\n\nTime to completion of above test when run locally:\n\n\tBefore: 0m27.111s\n\tAfter: 0m0.018s\n\nSigned-off-by: Kenny Levinsen ","shortMessageHtmlLink":"ZEN: Input: evdev - use call_rcu when detaching client"}},{"before":null,"after":"ffc253263a1375a65fa6c9f62a893e9767fbebfa","ref":"refs/heads/base-6.6","pushedAt":"2023-11-26T04:46:48.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.6","shortMessageHtmlLink":"Linux 6.6"}},{"before":"9c8331b43261b55937082b2983df0c232a60367f","after":"5bc7728c20790bf602f1706f96ab1ec9a03f0c50","ref":"refs/heads/rebase-6.1/steam-patches","pushedAt":"2023-10-11T21:42:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"ZEN: sched/fair: Multi-LLC select_idle_sibling()\n\nTejun reported that when he targets workqueues towards a specific LLC\non his Zen2 machine with 3 cores / LLC and 4 LLCs in total, he gets\nsignificant idle time.\n\nThis is, of course, because of how select_idle_sibling() will not\nconsider anything outside of the local LLC, and since all these tasks\nare short running the periodic idle load balancer is ineffective.\n\nAnd while it is good to keep work cache local, it is better to not\nhave significant idle time. Therefore, have select_idle_sibling() try\nother LLCs inside the same node when the local one comes up empty.\n\nReported-by: Tejun Heo \nSigned-off-by: Peter Zijlstra (Intel) ","shortMessageHtmlLink":"ZEN: sched/fair: Multi-LLC select_idle_sibling()"}},{"before":"1cc3fcf63192dfbf5ac13bc6134ae9120ebdcba6","after":"082280fe94a09462c727fb6e7b0c982efb36dede","ref":"refs/heads/base-6.1","pushedAt":"2023-10-11T20:36:24.000Z","pushType":"push","commitsCount":6484,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.1.57\n\nLink: https://lore.kernel.org/r/20231009130122.946357448@linuxfoundation.org\nTested-by: SeongJae Park \nTested-by: Shuah Khan \nTested-by: Florian Fainelli \nTested-by: Bagas Sanjaya \nTested-by: Jon Hunter \nTested-by: Takeshi Ogasawara \nTested-by: Guenter Roeck \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.1.57"}},{"before":"be074ebc4aaaebe079099f337e186fe24d55697f","after":"9c8331b43261b55937082b2983df0c232a60367f","ref":"refs/heads/rebase-6.1/steam-patches","pushedAt":"2023-05-09T09:36:05.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"mm: bump DEFAULT_MAX_MAP_COUNT\n\nSome games such as Detroit: Become Human tend to be very crash prone with\nlower values.","shortMessageHtmlLink":"mm: bump DEFAULT_MAX_MAP_COUNT"}},{"before":"2512f848b4f027224a0ac025b1852f4fb0e2fdfa","after":"be074ebc4aaaebe079099f337e186fe24d55697f","ref":"refs/heads/rebase-6.1/steam-patches","pushedAt":"2023-03-12T11:46:20.655Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"futex: Add entry point for FUTEX_WAIT_MULTIPLE (opcode 31)\n\nAdd an option to wait on multiple futexes using the old interface, that\nuses opcode 31 through futex() syscall. Do that by just translation the\nold interface to use the new code. This allows old and stable versions\nof Proton to still use fsync in new kernel releases.\n\nSigned-off-by: André Almeida ","shortMessageHtmlLink":"futex: Add entry point for FUTEX_WAIT_MULTIPLE (opcode 31)"}},{"before":"2cb8e624295ffa0c4d659fcec7d9e7a6c48de156","after":"1cc3fcf63192dfbf5ac13bc6134ae9120ebdcba6","ref":"refs/heads/base-6.1","pushedAt":"2023-03-12T11:46:09.084Z","pushType":"push","commitsCount":2506,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.1.18\n\nLink: https://lore.kernel.org/r/20230310133717.050159289@linuxfoundation.org\nTested-by: Markus Reichelt \nTested-by: Jon Hunter \nTested-by: Salvatore Bonaccorso \nTested-by: Shuah Khan \nTested-by: Guenter Roeck \nTested-by: Bagas Sanjaya \nTested-by: Linux Kernel Functional Testing \nTested-by: Conor Dooley \nTested-by: Sudip Mukherjee \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.1.18"}},{"before":null,"after":"abe642f2c7474244773cc18f23db0379e896565e","ref":"refs/heads/rebase-6.1/xpadneo","pushedAt":"2023-03-11T15:48:42.204Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"xpadneo: Merge upstream changes\n\nSigned-off-by: Kai Krakow ","shortMessageHtmlLink":"xpadneo: Merge upstream changes"}},{"before":null,"after":"2512f848b4f027224a0ac025b1852f4fb0e2fdfa","ref":"refs/heads/rebase-6.1/steam-patches","pushedAt":"2023-03-11T15:48:31.182Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"futex: Add entry point for FUTEX_WAIT_MULTIPLE (opcode 31)\n\nAdd an option to wait on multiple futexes using the old interface, that\nuses opcode 31 through futex() syscall. Do that by just translation the\nold interface to use the new code. This allows old and stable versions\nof Proton to still use fsync in new kernel releases.\n\nSigned-off-by: André Almeida ","shortMessageHtmlLink":"futex: Add entry point for FUTEX_WAIT_MULTIPLE (opcode 31)"}},{"before":null,"after":"7ee30f8d6c51aba3effe98184b32f18aae300f56","ref":"refs/heads/rebase-6.1/clearlinux-tweaks","pushedAt":"2023-03-11T15:48:12.266Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"futex bump","shortMessageHtmlLink":"futex bump"}},{"before":null,"after":"dd595aa539b01ef0399f44dfd7906083989cd897","ref":"refs/heads/rebase-6.1/pf-ksm","pushedAt":"2023-03-11T15:47:58.317Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"mm: add sysfs entry for pmadv_ksm syscall number\n\nAs `pmadv_ksm()` syscall is out-of-tree, maintain a separate\n`/sys/kernel/pmadv/ksm` file with a syscall number so that userspace\ntools can always know what to use in runtime even if the syscall number\nshifts after adding another in-tree syscall.\n\nThe idea is borrowed from futex2 submission.\n\nSigned-off-by: Oleksandr Natalenko ","shortMessageHtmlLink":"mm: add sysfs entry for pmadv_ksm syscall number"}},{"before":null,"after":"3eb2fd087d6a0f0e51058bcd397222ee6c8466e6","ref":"refs/heads/rebase-6.1/btrfs-patches","pushedAt":"2023-03-11T15:47:22.920Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"btrfs: add allocator_hint mode\n\nWhen this mode is enabled, the chunk allocation policy is modified as\nfollow.\n\nEach disk may have a different tag:\n- BTRFS_DEV_ALLOCATION_PREFERRED_METADATA\n- BTRFS_DEV_ALLOCATION_METADATA_ONLY\n- BTRFS_DEV_ALLOCATION_DATA_ONLY\n- BTRFS_DEV_ALLOCATION_PREFERRED_DATA (default)\n\nWhere:\n- ALLOCATION_PREFERRED_X means that it is preferred to use this disk for\nthe X chunk type (the other type may be allowed when the space is low)\n- ALLOCATION_X_ONLY means that it is used *only* for the X chunk type.\nThis means also that it is a preferred choice.\n\nEach time the allocator allocates a chunk of type X , first it takes the\ndisks tagged as ALLOCATION_X_ONLY or ALLOCATION_PREFERRED_X; if the space\nis not enough, it uses also the disks tagged as ALLOCATION_METADATA_ONLY;\nif the space is not enough, it uses also the other disks, with the\nexception of the one marked as ALLOCATION_PREFERRED_Y, where Y the other\ntype of chunk (i.e. not X).\n\nSigned-off-by: Goffredo Baroncelli ","shortMessageHtmlLink":"btrfs: add allocator_hint mode"}},{"before":null,"after":"2cb8e624295ffa0c4d659fcec7d9e7a6c48de156","ref":"refs/heads/base-6.1","pushedAt":"2023-03-11T15:44:04.885Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kakra","name":"Kai Krakow","path":"/kakra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17684?s=80&v=4"},"commit":{"message":"Linux 6.1.4\n\nLink: https://lore.kernel.org/r/20230104160511.905925875@linuxfoundation.org\nTested-by: Ronald Warsow \nTested-by: Allen Pais \nTested-by: Florian Fainelli \nTested-by: Shuah Khan \nTested-by: Guenter Roeck \nTested-by: Jon Hunter \nTested-by: Bagas Sanjaya \nTested-by: Fenil Jain \nTested-by: Linux Kernel Functional Testing \nTested-by: Sudip Mukherjee \nTested-by: Ron Economos \nTested-by: Justin M. Forbes \nTested-by: Salvatore Bonaccorso \nTested-by: Rudi Heitbaum \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"Linux 6.1.4"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wOVQxOTozMzo1OC4wMDAwMDBazwAAAASxST2m","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wOVQxOTozMzo1OC4wMDAwMDBazwAAAASxST2m","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0xMVQxNTo0NDowNC44ODU4MjNazwAAAAMBU_8J"}},"title":"Activity · kakra/linux"}