{"cursor":"100","tags":[{"annotation":{"message":"Linux 7.3","oid":"091b06388b117fefdcb63336ac09956a4914b961","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-18T13:14:58.000000-10:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-18T13:14:58.000000-10:00"},"message":"Linux 7.3\n","name":"v7.3","oid":"c03c1a14507dfaf8b856c2608f9ac216021fc222"},{"annotation":{"message":"Clean up assoc_array library\n\nNils Ollrogge reported a bug in the assoc_array library and had a patch\nto fix it too, but that code was too obscure for me to follow, so I did\nwhat I preach: use modern LLM tools to help make sense of it all.\n\nSo this is an LLM-assisted branch which makes the code more readable by\nsplitting up some of the larger and hard-to-read functions. The code\nwas then run through a test harness in user space, which not only\nconfirmed the bug Nils reported, but found three other bugs too - all\ngoing back to the very first commit adding this library back in 2013.\n\nv2: David Howells asked for a fix-up of a couple of comments and rename\nassoc_array_segment_leaves() to assoc_array_fill_segment_cache(), and\nadded his Tested-by: and Reviewed-by:","oid":"6f22cd85d026e54861f8bdb2295dc15639517e35","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-13T10:01:27.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-11T11:44:59.000000-07:00"},"message":"assoc_array: use assoc_array_parent_link() when splitting a shortcut\n\nassoc_array_insert_mid_shortcut() works out by hand which pointer leads\nto the shortcut it splits: the same cases as assoc_array_parent_link(),\nwith a BUG() for a shortcut behind anything but a node. Use the\nfunction, and keep the check as a BUG_ON().\n\nNo functional change.\n\nAssisted-by: LLM\nSigned-off-by: Linus Torvalds \nTested-by: David Howells \nReviewed-by: David Howells \n","name":"assoc-array-fixes-v2","oid":"bbab563c51315a1c6dbf6e801e4237b6d2b8b81e"},{"annotation":{"message":"Linux 7.3-rc7","oid":"ec8bf8280261294a9b9b4520414b42704c7f9f6b","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-11T20:04:55.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-11T20:04:55.000000-07:00"},"message":"Linux 7.3-rc7\n","name":"v7.3-rc7","oid":"24a19b953e2a3d0ea5a8c4951a0ab8f32720c907"},{"annotation":{"message":"Clean up assoc_array library\n\nNils Ollrogge reported a bug in the assoc_array library and had a patch\nto fix it too, but that code was too obscure for me to follow, so I did\nwhat I preach: use modern LLM tools to help make sense of it all.\n\nSo this is an LLM-assisted branch which makes the code more readable by\nsplitting up some of the larger and hard-to-read functions. The code\nwas then run through a test harness in user space, which not only\nconfirmed the bug Nils reported, but found three other bugs too - all\ngoing back to the very first commit adding this library back in 2013.","oid":"d09c91d022a36e6a471db39577f6da81c705e56b","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-11T12:54:56.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-11T11:44:59.000000-07:00"},"message":"assoc_array: use assoc_array_parent_link() when splitting a shortcut\n\nassoc_array_insert_mid_shortcut() works out by hand which pointer leads\nto the shortcut it splits: the same cases as assoc_array_parent_link(),\nwith a BUG() for a shortcut behind anything but a node. Use the\nfunction, and keep the check as a BUG_ON().\n\nNo functional change.\n\nAssisted-by: LLM\nSigned-off-by: Linus Torvalds \n","name":"assoc-array-fixes","oid":"99136562aa5b8599e1e565d8dace29554c84c969"},{"annotation":{"message":"Linux 7.3-rc6","oid":"4eeccbed21e50c19f97be9d325511f3de6343f2d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-04T13:45:25.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-10-04T13:45:25.000000-07:00"},"message":"Linux 7.3-rc6\n","name":"v7.3-rc6","oid":"a90ee4305c4a5df72c11b31dacfdc76e00fcf78a"},{"annotation":{"message":"Linux 7.3-rc5","oid":"5a956dde5526a634dca7ccad27c051ebcc306089","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-27T13:55:01.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-27T13:55:01.000000-07:00"},"message":"Linux 7.3-rc5\n","name":"v7.3-rc5","oid":"72d3fcf802c45d00b300f25b848a93c3a2bd7c7e"},{"annotation":{"message":"Linux 7.3-rc4","oid":"dec005ae90a2946656a090f37bf1cfbd22f08e57","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-20T13:48:15.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-20T13:48:15.000000-07:00"},"message":"Linux 7.3-rc4\n","name":"v7.3-rc4","oid":"93f51579e7df248780214094418f205253383cc5"},{"annotation":{"message":"Linux 7.3-rc3","oid":"c2cd463d6ee7d55a3ec0719d93c49ff99022d58f","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-13T14:38:02.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-13T14:38:02.000000-07:00"},"message":"Linux 7.3-rc3\n","name":"v7.3-rc3","oid":"fd73f4a6659897191fa0d40695fe370925dd3780"},{"annotation":{"message":"Linux 7.3-rc2","oid":"5e036ce12de91c6fd674dad33b169c6150be2a7a","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-06T15:07:20.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-09-06T15:07:20.000000-07:00"},"message":"Linux 7.3-rc2\n","name":"v7.3-rc2","oid":"df2908090cda368b01ff43709f51890076c56157"},{"annotation":{"message":"Linux 7.3-rc1","oid":"e5e04726cdd043e309677071ab1b65a4b18f422b","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-30T13:34:40.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-30T13:34:40.000000-07:00"},"message":"Linux 7.3-rc1\n","name":"v7.3-rc1","oid":"cee9395acd8043be0644b25c34bfa86623f2b935"},{"annotation":{"message":"Linux 7.2","oid":"237a1c39e8dfd3e1c6f1f023eea37a48ec04cc63","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-16T14:32:26.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-16T14:32:26.000000-07:00"},"message":"Linux 7.2\n","name":"v7.2","oid":"8d3ae59288f1e7d58d76558a6ee96d533bc5019f"},{"annotation":{"message":"Linux 7.2-rc7","oid":"2ee859ebf156157609f71060ae472711c8cbc326","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-09T14:54:50.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-09T14:54:50.000000-07:00"},"message":"Linux 7.2-rc7\n","name":"v7.2-rc7","oid":"db2ddb87143519e20a95aa36c60b36107b736a58"},{"annotation":{"message":"Linux 7.2-rc6","oid":"d7dd96eb916519208210bb4a0408fcf4f7fdce5d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-02T16:24:24.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-08-02T16:24:24.000000-07:00"},"message":"Linux 7.2-rc6\n","name":"v7.2-rc6","oid":"075b74841bd0065a3bda3440873c747938e69b68"},{"annotation":{"message":"Linux 7.2-rc5","oid":"a8e429896436e8c2d288181f875f92af8204bc58","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-26T14:45:48.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-26T14:45:48.000000-07:00"},"message":"Linux 7.2-rc5\n","name":"v7.2-rc5","oid":"f5098b6bae761e346ebcd9da7f95622c04733cff"},{"annotation":{"message":"Linux 7.2-rc4","oid":"6946cd5d0aa4dd10a414ddcb7a10844fdb0ad345","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-19T13:54:41.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-19T13:54:41.000000-07:00"},"message":"Linux 7.2-rc4\n","name":"v7.2-rc4","oid":"1590cf0329716306e948a8fc29f1d3ee87d3989f"},{"annotation":{"message":"Linux 7.2-rc3","oid":"1137d8b5df06137fb49513cc923b3b24d94cb809","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-12T14:16:39.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-12T14:16:39.000000-07:00"},"message":"Linux 7.2-rc3\n","name":"v7.2-rc3","oid":"a13c140cc289c0b7b3770bce5b3ad42ab35074aa"},{"annotation":{"message":"Linux 7.2-rc2","oid":"4c45e14df2f4e77982ad70d6d8e3fe750edd4c37","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-05T14:44:06.000000-10:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-07-05T14:44:06.000000-10:00"},"message":"Linux 7.2-rc2\n","name":"v7.2-rc2","oid":"8cdeaa50eae8dad34885515f62559ee83e7e8dda"},{"annotation":{"message":"Linux 7.2-rc1","oid":"728e68a889bcf257b1e67298b12c360e5c3a13e0","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-28T12:01:31.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-28T12:01:31.000000-07:00"},"message":"Linux 7.2-rc1\n","name":"v7.2-rc1","oid":"dc59e4fea9d83f03bad6bddf3fa2e52491777482"},{"annotation":{"message":"Linux 7.1","oid":"b3f94b2b3f3e51ab880a51fc6510e1dafba654ed","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-14T15:58:38.000000+01:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-14T15:58:38.000000+01:00"},"message":"Linux 7.1\n","name":"v7.1","oid":"8cd9520d35a6c38db6567e97dd93b1f11f185dc6"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2026-06-13\n","oid":"31341c445e37d40b48b2dc81fcf8637a38e38a94","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"tglx@kernel.org","name":"Thomas Gleixner","when":"2026-06-13T15:31:03.000000+02:00"},"message":"x86/irq: Add missing 's' back to thermal event printout\n\nThe /proc/interrupt handling rework dropped a 's' in the thermal event\nprintout, which breaks the thermal test in the Intel LKVS suite.\n\nBring the important letter back.\n\nFixes: 2b57c69917ee (\"x86/irq: Make irqstats array based\")\nReported-by: kernel test robot \nSigned-off-by: Thomas Gleixner \nCloses: https://lore.kernel.org/oe-lkp/202606121325.97b29701-lkp@intel.com\n","name":"refs/merge-window/0ff315766685b74ebb0b20bf9eb039ef31509057","oid":"8f727615134abc6382f0ea07b90270d7bdde578f"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-vdso-2026-06-13\n","oid":"e6c8efc9bb5df0989fb16429a8f4315b58d2c5c5","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"thomas.weissschuh@linutronix.de","name":"Thomas Weißschuh","when":"2026-05-21T08:53:23.000000+02:00"},"message":"MIPS: VDSO: Fold MIPS_CLOCK_VSYSCALL into MIPS_GENERIC_GETTIMEOFDAY\n\nThis configuration option exists so \"that we don't provide the symbol\nwhen there's no possibility of there being a usable clocksource\".\nHowever it only covers __vdso_gettimeofday() and none of the other vDSO\nfunctions which should be affected by the same circumstances.slightly slightly.\n\nRemove MIPS_CLOCK_VSYSCALL and fold its usecase into\nMIPS_GENERIC_GETTIMEOFDAY, which works correctly.\n\nSigned-off-by: Thomas Weißschuh \nSigned-off-by: Thomas Gleixner \nCc: Thomas Bogendoerfer \nCc: Daniel Lezcano \nCc: Thomas Gleixner \nCc: Andy Lutomirski \nCc: Vincenzo Frascino \nCc: Arnd Bergmann \nCc: linux-mips@vger.kernel.org\nLink: https://patch.msgid.link/20260521-vdso-mips-kconfig-v1-9-2f79dcd6c78f@linutronix.de\n","name":"refs/merge-window/10665a9025de5dc73a3599a48aa1eaa0134804fc","oid":"8d563bd7904734c05a4f2abf4ecca0e4fe764b50"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-drivers-2026-06-13\n","oid":"621dee2e323dae821fceca313e8df4a73ea02702","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"markus.stockhausen@gmx.de","name":"Markus Stockhausen","when":"2026-06-04T20:25:06.000000+02:00"},"message":"irqchip/irq-realtek-rtl: Add multicore support\n\nThe Realtek interrupt driver currently supports only single core\nsystems. So the higher end devices like RTL839x and RTL930x with\ndual VPEs must be driven with NR_CPU=1. Enhance the driver to\nsupport multicore (dual VPE) systems. For this:\n\n - Extend the register map for multiple cores\n - Search for multiple CPU cores in the devicetree\n - Improve the register helpers to support multiple cores\n - Add an affinity setter\n - Enhance the IRQ handler for multiple cores\n\nSigned-off-by: Markus Stockhausen \nSigned-off-by: Thomas Gleixner \nLink: https://patch.msgid.link/20260604182506.1113440-3-markus.stockhausen@gmx.de\n","name":"refs/merge-window/136e9300e5177580086bece9aaf1dabc9e267b44","oid":"a1a35c09241f0577cc40f65d7372fed01138619d"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-core-2026-06-13\n","oid":"4fafc90258916e76e54155554d239dc2afe09461","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"reinette.chatre@intel.com","name":"Reinette Chatre","when":"2026-06-03T20:38:47.000000-07:00"},"message":"cpu: Add lockdep_is_cpus_held()/lockdep_is_cpus_write_held() stubs for !CONFIG_HOTPLUG_CPU\n\nlockdep_is_cpus_held() and lockdep_is_cpus_write_held() are undefined when\n!CONFIG_HOTPLUG_CPU. This is ok because their few callers protect the calls\nwith a \"if (IS_ENABLED(CONFIG_HOTPLUG_CPU) ...\" check.\n\nIt is error prone to require callers to protect lockdep_is_cpus_held()\nand lockdep_is_cpus_write_held() with an IS_ENABLED(CONFIG_HOTPLUG_CPU)\ncheck while the custom for equivalent functions, for example the more\nprevalent lockdep_is_held(), is to not require similar protection.\nIt is also inconsistent with CPU hotplug lockdep code self since related\ncall lockdep_assert_cpus_held() does not require protection.\n\nCreate stubs for lockdep_is_cpus_held() and lockdep_is_cpus_write_held()\nthat returns 1 (LOCK_STATE_UNKNOWN/LOCK_STATE_HELD) when !CONFIG_HOTPLUG_CPU.\nThis makes the CPU hotplug lockdep checks consistent while following\nexisting lockdep custom. Drop the \"extern\" from the function declaration\nas part of the move to match kernel coding style.\n\nKeep the IS_ENABLED(CONFIG_HOTPLUG_CPU) checks in existing users since\nremoving them would change the logic of these expressions.\n\nReported-by: Sashiko \nSigned-off-by: Reinette Chatre \nSigned-off-by: Thomas Gleixner \nLink: https://patch.msgid.link/7484f0b58fd86153d445819cc4e172adba16cff9.1780543665.git.reinette.chatre@intel.com\nCloses: https://sashiko.dev/#/patchset/cover.1780456704.git.reinette.chatre%40intel.com?part=1\n","name":"refs/merge-window/1f2df8a15dad238c66ff0b664ad65e635ef4d482","oid":"9c91efd1d63e995bb0577fc1c5e909613dfe671d"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rseq-2026-06-13\n","oid":"bacbdc2add3188f3d49f696488367671790b010a","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"broonie@kernel.org","name":"Mark Brown","when":"2026-04-24T13:45:21.000000+01:00"},"message":"selftests/rseq: Add config fragment\n\nCurrently there is no config fragment for the rseq selftests but there are\na couple of configuration options which are required for running them:\n\n - CONFIG_RSEQ is required for obvious reasons, it is enabled by default\n but it doesn't hurt to specify it in case the user is usinsg a\n defconfig that disables it.\n\n - CONFIG_RSEQ_SLICE_EXTENSION is tested by the slice_test test, the\n test will fail without it.\n\nAdd a configuration fragment which enables these options, helping encourage\nCI systems and people doing manual testing to run the tests with all the\nfeatures. This also requires CONFIG_EXPERT since it is a dependency for\nslice extension.\n\nSigned-off-by: Mark Brown \nSigned-off-by: Thomas Gleixner \nLink: https://patch.msgid.link/20260424-selftests-rseq-config-fragment-v2-1-a9475996edcb@kernel.org\n","name":"refs/merge-window/9533eddc702700a11461d3da0a8f49e3d7d52dd2","oid":"5a0daaff6ed9c1177d58b7367451ef9714dac81d"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-nohz-2026-06-13\n","oid":"2f7a88cd58ea60a7dd247bd0290b41761f55fb3d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"frederic@kernel.org","name":"Frederic Weisbecker","when":"2026-05-08T15:16:47.000000+02:00"},"message":"sched/cputime: Handle dyntick-idle steal time correctly\n\nThe dyntick-idle steal time is currently accounted when the tick restarts\nbut the stolen idle time is not subtracted from the idle time that was\nalready accounted. This is to avoid observing the idle time going backward\nas the dyntick-idle cputime accessors can't reliably know in advance the\nstolen idle time.\n\nIn order to maintain a forward progressing idle cputime while subtracting\nidle steal time from it, keep track of the previously accounted idle stolen\ntime and substract it from _later_ idle cputime accounting.\n\nSigned-off-by: Frederic Weisbecker \nSigned-off-by: Thomas Gleixner \nTested-by: Shrikanth Hegde \nLink: https://patch.msgid.link/20260508131647.43868-16-frederic@kernel.org\n","name":"refs/merge-window/a491e1430a4fbfab275a200b4acfa057f0aab44d","oid":"6199f9999a9b62b2b84a1bf5b52a9fd0bb8de5af"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-2026-06-13\n","oid":"80a33b3a68d0993af638aa17176934207afd566d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"vulab@iscas.ac.cn","name":"WenTao Liang","when":"2026-06-12T00:17:38.000000+08:00"},"message":"posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path\n\nIn do_cpu_nanosleep(), posix_cpu_timer_create() takes a pid reference\nvia get_pid() and stores it in timer.it.cpu.pid. If the subsequent\nposix_cpu_timer_set() call fails, the function returns immediately\nwithout calling posix_cpu_timer_del() to release the pid reference,\ncausing a leak.\n\nFix it by calling posix_cpu_timer_del() before the unlock-and-return\non the error path, consistent with the other exit paths in the same\nfunction.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nSigned-off-by: WenTao Liang \nSigned-off-by: Thomas Gleixner \nReviewed-by: Frederic Weisbecker \nCc: stable@vger.kernel.org\nLink: https://patch.msgid.link/20260611161738.97043-1-vulab@iscas.ac.cn\n","name":"refs/merge-window/c00c858bfaf38e9c7aec8391ba34e0a51ccd96a2","oid":"87bd2ad568e15b90d5f7d4bcd70342d05dad649c"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-ptp-2026-06-13\n","oid":"6476a5b76c344a30eaf898aacd4cf60c349430b5","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"dwmw@amazon.co.uk","name":"David Woodhouse","when":"2026-06-04T10:35:18.000000+01:00"},"message":"ptp: vmclock: Use hw_cycles from snapshot for precise TSC pairing\n\nWhen the system clocksource is kvmclock or Hyper-V (not the TSC directly),\nvmclock_get_crosststamp() falls through to a separate get_cycles() call,\nlosing the atomic pairing between the system time snapshot and the TSC\nreading.\n\nNow that ktime_get_snapshot_id() populates hw_cycles with the underlying\nTSC value for derived clocksources, use it when available. This gives a\nperfect (system_time, tsc) pairing for the device time calculation.\n\nThe SUPPORT_KVMCLOCK wrapper is still needed to convert the TSC into\nkvmclock nanoseconds for system_counter->cycles, because otherwise\nget_device_system_crosststamp() can't interpret the result against the\nsystem clock.\n\nSigned-off-by: David Woodhouse \nSigned-off-by: Thomas Gleixner \nAssisted-by: Kiro:claude-opus-4.6-1m\nLink: https://patch.msgid.link/20260604095755.64849-4-dwmw2@infradead.org\n","name":"refs/merge-window/df7610115bad68761e38a34648dfd6f5cd161cd6","oid":"bc484a5096732cd858771cccd3164ec985bdc03d"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-msi-2026-06-13\n","oid":"60074660d9778f74abd4ed8cd3f4235293b5f728","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"mileskrause5200@gmail.com","name":"Miles Krause","when":"2026-05-04T21:46:02.000000-04:00"},"message":"genirq/msi: Fix typos in msi_domain_ops comment\n\nFix spelling and possessive typos in the msi_domain_ops comment.\n\nNo functional change.\n\nSigned-off-by: Miles Krause \nSigned-off-by: Thomas Gleixner \nLink: https://patch.msgid.link/20260505014602.5879-1-mileskrause5200@gmail.com\n","name":"refs/merge-window/e2d852f67fe5bf43458749b71ed8658a03563958","oid":"3661d5f403769b872482b584e658b71bbdb5f55e"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-clocksource-2026-06-13\n","oid":"63a86c92d1d18565def939c959b61463ea001838","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:36:29.000000-07:00"}},"author":{"email":"tglx@kernel.org","name":"Thomas Gleixner","when":"2026-06-13T16:24:29.000000+02:00"},"message":"Merge tag 'timers-v7.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource\n\nPull clocksource/driver updates from Daniel Lezcano:\n\n - Remove the sifive,fine-ctr-bits property bindings because it is a\n redundant information (Nick Hu)\n\n - Remove the TCIU8 interrupt bindings on Renesas because it should not\n be described as the documentation marked reserved and fix the\n conditional reset line for the RZ/{T2H,N2H} (Cosmin Tanislav)\n\n - Add the StarFive JHB100 clint DT bindings compatible string (Ley\n Foon Tan)\n\n - Extend schema condition for interrupts to cover D1 compatible\n variant an add the D1 hstimer support (Michal Piekos)\n\n - Update the ARM architected timer support to handle the ACPI GTDT v3\n format and the EL2 virtual timer, enabling Linux to use the most\n appropriate timer when running with VHE, while also fixing several\n Device Trees to accurately reflect the underlying hardware (Marc\n Zyngier)\n\n - Cleanup and add the clocksource and the clockevent in the TI DM\n timer (Markus Schneider-Pargmann)\n\n - Add the multiple watchdogs support in the tegra186 and\n tegra234. Dedicate one as a kernel watchdog (Kartik Rajput)\n\n - Add the NXP clocksource selection for the scheduler in the Kconfig\n (Enric Balletbo i Serra)\n\nLink: https://lore.kernel.org/all/1e55e8d6-8024-4f17-8620-ab3385465d76@oss.qualcomm.com\n","name":"refs/merge-window/edf9c19adbc39c9eeef99ad12e7feaf3b434c25c","oid":"c66494c79ede1af529dbf67f9ed6fdbf42e05ef3"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.openat2\n","oid":"a8c6a26a6e5e3a04079dafdcedc80cce0ddfe4cb","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"jkoolstra@xs4all.nl","name":"Jori Koolstra","when":"2026-05-28T17:58:47.000000Z"},"message":"vfs: replace ints with enum last_type for LAST_XXX\n\nSeveral functions in namei.c take an \"int *type\" parameter, such as\nfilename_parentat(). To know what values this can take you have to find\nthe anonymous struct that defines the LAST_XXX values. Define an enum\nlast_type to make this type explicit.\n\nSigned-off-by: Jori Koolstra \nLink: https://patch.msgid.link/20260528175854.57626-2-jkoolstra@xs4all.nl\nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/2f310bb0cd7d95b7f29ffbffa8e2846aea58a7e4","oid":"318643721de396012da102723f337f35ba7ec1e9"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.super\n","oid":"6dd790155331031b74204a0e5734b118b3d3e6f5","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-06-03T09:09:57.000000+02:00"},"message":"Merge patch series \"super: retire sget()\"\n\nChristian Brauner says:\n\nCIFS plus the two ext4 KUnit tests (extents-test, mballoc-test) were the\nlast in-tree callers, and all three convert cleanly to sget_fc(). That\nlets sget() and its prototype come out, taking ~60 lines that only\nexisted to be kept in lockstep with sget_fc() on every publish-path\nchange.\n\n* patches from https://patch.msgid.link/20260529-work-sget-v2-0-57bbe08604e4@kernel.org:\n fs: retire sget()\n smb: client: convert cifs_smb3_do_mount() to sget_fc()\n ext4: convert mballoc KUnit test to sget_fc()\n ext4: convert extents KUnit test to sget_fc()\n\nLink: https://patch.msgid.link/20260529-work-sget-v2-0-57bbe08604e4@kernel.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/3e57ed20c0db4bc381e695c33b3235c6a948b4f8","oid":"2c6f0c248a6b49a6fc8c301c84d367860c56ccd8"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/melver/linux.git tags/kcsan-20260612-v7.2-rc1\n","oid":"429e9007a164692cdb60491cef220bbe824bc1cd","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"elver@google.com","name":"Marco Elver","when":"2026-04-22T13:59:45.000000+02:00"},"message":"kcsan: Silence -Wmaybe-uninitialized when calling __kcsan_check_access()\n\nSome subsystems enable -Wmaybe-uninitialized [1], which can trigger\nfalse positives when KCSAN is enabled. Specifically, passing an\nuninitialized variable to functions that instrument accesses (e.g.,\ncopy_from_user()) results in calls to __kcsan_check_access().\n\nBecause __kcsan_check_access() takes a `const volatile void *ptr`, GCC\ninfers that the function may only read the memory location, and thus\nwarns if the passed variable is uninitialized.\n\nHowever, KCSAN is a dynamic analysis tool for data race detection; while\nit does read the memory location to detect concurrent modifications, the\n\"initialized'ness\" of the memory location is irrelevant for its analysis.\n\nUse absolute_pointer() in __kcsan_check_write(), kcsan_check_write(),\nand kcsan_check_atomic_write() to hide the pointer from the compiler,\npreventing it from concluding that the pointer passed points to\nuninitialized memory.\n\nThis fixes warnings like:\n\n| CC fs/ntfs3/file.o\n| In file included from include/asm-generic/rwonce.h:27,\n| from arch/arm64/include/asm/rwonce.h:81,\n| from include/linux/compiler.h:369,\n| from include/linux/array_size.h:5,\n| from include/linux/kernel.h:16,\n| from include/linux/backing-dev.h:12,\n| from fs/ntfs3/file.c:10:\n| In function 'instrument_copy_from_user_before',\n| inlined from '_inline_copy_from_user' at include/linux/uaccess.h:184:2,\n| inlined from 'copy_from_user' at include/linux/uaccess.h:221:9,\n| inlined from 'ntfs_ioctl_fitrim' at fs/ntfs3/file.c:77:6,\n| inlined from 'ntfs_ioctl' at fs/ntfs3/file.c:164:10:\n| include/linux/kcsan-checks.h:220:28: error: 'range' may be used uninitialized [-Werror=maybe-uninitialized]\n| 220 | #define kcsan_check_access __kcsan_check_access\n| | ^\n| include/linux/kcsan-checks.h:311:9: note: in expansion of macro 'kcsan_check_access'\n| 311 | kcsan_check_access(ptr, size, KCSAN_ACCESS_WRITE)\n| | ^~~~~~~~~~~~~~~~~~\n| include/linux/instrumented.h:147:9: note: in expansion of macro 'kcsan_check_write'\n| 147 | kcsan_check_write(to, n);\n| | ^~~~~~~~~~~~~~~~~\n| include/linux/kcsan-checks.h: In function 'ntfs_ioctl':\n| include/linux/kcsan-checks.h:37:6: note: by argument 1 of type 'const volatile void *' to '__kcsan_check_access' declared here\n| 37 | void __kcsan_check_access(const volatile void *ptr, size_t size, int type);\n| | ^~~~~~~~~~~~~~~~~~~~\n| fs/ntfs3/file.c:65:29: note: 'range' declared here\n| 65 | struct fstrim_range range;\n| | ^~~~~\n\nLink: https://lore.kernel.org/all/5da10cca-875b-418d-b54e-6be3ea32c266@app.fastmail.com/ [1]\nReported-by: Arnd Bergmann \nReviewed-by: Arnd Bergmann \nTested-by: Arnd Bergmann \nSigned-off-by: Marco Elver \n","name":"refs/merge-window/434fad0bfd31704048031688b14196f088486f6a","oid":"07a1a6562ce29e2e0c134a57882d6e52e8758492"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git thermal-7.2-rc1\n","oid":"33bf1e191ef56fdcf3f87293ec2c29b1dd8821ed","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"rafael.j.wysocki@intel.com","name":"Rafael J. Wysocki","when":"2026-06-11T18:21:22.000000+02:00"},"message":"Merge branch 'thermal-testing'\n\nMerge thermal control testing facility updates for 7.2:\n\n - Replace sscanf() with kstrtoul() or kstrtoint() in several places in\n the thermal testing code (Ovidiu Panait)\n\n - Make the thermal testing facility reject missing command arguments to\n avoid NULL pointer dereferences (Samuel Moelius)\n\n* thermal-testing:\n thermal: sysfs: Replace sscanf() with kstrtoul()\n thermal: testing: Replace sscanf() with kstrtoint()\n thermal: testing: reject missing command arguments\n","name":"refs/merge-window/488e6dbc39230cf047569f2038b03fa749a4f5ac","oid":"bc1c872ce0ab3984f5fcefeb952541a802b891e7"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.exportfs\n","oid":"a52f3422c49a2feb25edcece5e19d4773323ede4","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-05-11T11:11:55.000000+02:00"},"message":"Merge patch series \"cleanup block-style layouts exports\"\n\nChuck Lever says:\n\nThis series cleanups the exportfs support for block-style layouts that\nprovide direct block device access. This is preparation for supporting\nexportfs of more than a single device per file system.\n\n* patches from https://patch.msgid.link/20260423181854.743150-1-cel@kernel.org:\n exportfs,nfsd: rework checking for layout-based block device access support\n exportfs: don't pass struct iattr to ->commit_blocks\n exportfs: split out the ops for layout-based block device access\n nfsd/blocklayout: always ignore loca_time_modify\n\nLink: https://patch.msgid.link/20260423181854.743150-1-cel@kernel.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/4f3ec96d69ffb78260cd04bd26a65ecfde9de6ff","oid":"79e33ddc62c03cce6c29f0792454e1d618228acf"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.casefold\n","oid":"519f476c7e04f2209666ab7a1eff1ba216e513c9","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-05-15T17:49:29.000000+02:00"},"message":"Merge patch series \"Casefold Fixes\"\n\nBring in a bunch of fixes for the casefold work.\n\n* patches from https://patch.msgid.link/20260515153515.362266-1-cel@kernel.org:\n nfsd: Cap case-folding probe cost across READDIR entries\n nfsd: Map -ESTALE from case probe to NFS3ERR_STALE\n nfsd: Use kernel credentials for case-info probe\n fs: Clarify FS_CASEFOLD_FL semantics in UAPI header\n nfs: Skip pathconf probe when neither field is consumed\n nfs: Avoid transient zeroed case capability bits during probe\n tools headers UAPI: Sync case-sensitivity flags from linux/fs.h\n\nLink: https://patch.msgid.link/20260515153515.362266-1-cel@kernel.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/5d822687f8e7a9ed508bb5b73fd4fa90a6f526e9","oid":"ea3120fd5153c967efb20e6e3330caecbf9d8b0a"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.kfunc\n","oid":"e524b496f72536963ba9b156122b04b2c2c6b9dc","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"mattbobrowski@google.com","name":"Matt Bobrowski","when":"2026-04-30T07:38:36.000000Z"},"message":"bpf: fix crash in bpf_[set|remove]_dentry_xattr for negative dentries\n\nbpf_set_dentry_xattr and bpf_remove_dentry_xattr BPF kfuncs attempt to\nlock the inode of the supplied dentry without checking if it is\nNULL. If a negative dentry is passed (e.g. from\nsecurity_inode_create), d_inode(dentry) returns NULL, and\ninode_lock(inode) will cause a NULL pointer dereference.\n\nTrivially fix this by adding a NULL check for inode before attempting\nto lock it, returning -EINVAL if it is NULL.\n\nAdditionally, drop WARN_ON(!inode) in bpf_xattr_read_permission() and\nbpf_xattr_write_permission(). These warnings could be triggered by\npassing a negative dentry to bpf_get_dentry_xattr() or the _locked\nvariants of the xattr kfuncs, potentially causing a Denial of Service\non systems with panic_on_warn enabled. Instead, simply return -EINVAL.\n\nReported-by: Quan Sun <2022090917019@std.uestc.edu.cn>\nCloses: https://lore.kernel.org/bpf/1587cbf4-1293-4e25-ad24-c970836a1686@std.uestc.edu.cn/\nFixes: 56467292794b (\"bpf: fs/xattr: Add BPF kfuncs to set and remove xattrs\")\nSigned-off-by: Matt Bobrowski \nLink: https://patch.msgid.link/20260430073836.2894001-1-mattbobrowski@google.com\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/69e5cd1262043a6bfdd55693f1950119f50f0f77","oid":"07410646f6ff1d23222f105ccab778957d401bbe"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.inode\n","oid":"ce20e990a4155f904a5a8250a389a542c1317e93","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"mjguzik@gmail.com","name":"Mateusz Guzik","when":"2026-04-23T19:04:31.000000+02:00"},"message":"fs: retire stale lock ordering annotations from inode hash\n\n1. iunique does not take the hash lock as of:\n3f19b2ab97a97b41 (\"vfs, afs, ext4: Make the inode hash table RCU searchable\")\n2. s_inode_list_lock is no longer taken under the hash lock as of:\nc918f15420e336a9 (\"fs: call inode_sb_list_add() outside of inode hash lock\")\n\nSigned-off-by: Mateusz Guzik \nLink: https://patch.msgid.link/20260423170431.1483370-1-mjguzik@gmail.com\nReviewed-by: Jan Kara \nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/78fcd640d0bb2c68b3ce6a3ad583b4428310122b","oid":"5b451b76c85c8309d2e02caa467b38f5999c986f"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-7.2-rc1\n","oid":"3a2b16e87486fb80da42dec57b6de076e5d5f9dc","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"dmitry.torokhov@gmail.com","name":"Dmitry Torokhov","when":"2026-06-06T20:51:29.000000-07:00"},"message":"software node: allow passing reference args to PROPERTY_ENTRY_REF()\n\nWhen dynamically creating software nodes and properties for subsequent\nuse with software_node_register() current implementation of\nPROPERTY_ENTRY_REF() is not suitable because it creates a temporary\ninstance of struct software_node_ref_args on stack which will later\ndisappear, and software_node_register() only does shallow copy of\nproperties.\n\nFix this by allowing to pass address of reference arguments structure\ndirectly into PROPERTY_ENTRY_REF(), so that caller can manage lifetime\nof the object properly.\n\nSigned-off-by: Dmitry Torokhov \nReviewed-by: Andy Shevchenko \nLink: https://patch.msgid.link/aiTo4dvKu8pyimHA@google.com\nSigned-off-by: Danilo Krummrich \n","name":"refs/merge-window/87cffa2fc43294966d89248a021b5cb1fe318000","oid":"fe221742e388bea3f5856b5d9b2cb0a037020ea4"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/kernel-7.2-rc1.misc\n","oid":"313935e7712aae6bad896ff0f5b6a77e6aad243a","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-05-27T14:11:47.000000+02:00"},"message":"Merge patch series \"selftests/clone3: fix cap_checkpoint_restore test\"\n\nEva Kurchatova says:\n\nThis patchset fixes misuse of libcap library interface, and existing\ncompilation warnings due to unused variables.\n\n* patches from https://patch.msgid.link/20260524163840.34247-1-eva.kurchatova@virtuozzo.com:\n selftests/clone3: remove unused variables\n selftests/clone3: fix libcap interface usage\n\nLink: https://patch.msgid.link/20260524163840.34247-1-eva.kurchatova@virtuozzo.com\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/8dabae51c611444836f2bdf517511a316e46d680","oid":"ee8ab98f831226d69d43ccd93f53c50e6f19b389"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.xattr\n","oid":"7851c050d359da51c8d5e0c5722256d10789ba8a","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"daniel@iogearbox.net","name":"Daniel Borkmann","when":"2026-06-02T09:40:12.000000+02:00"},"message":"bpf: Add simple xattr support to bpffs\n\nAdd support for extended attributes on bpffs inodes so that user space\nand BPF LSM programs can attach metadata, for example, a content hash\nor a security label - to a pinned object or directory. BPF LSM or user\nspace tooling can then uniformly look at this (e.g. security.bpf.*) in\nsimilar way to other fs'es. The store is in-memory and non-persistent:\nit lives only for the lifetime of the mount, like everything else in\nbpffs. The modelling is similar to tmpfs.\n\nbpffs serves the trusted.* and security.* namespaces; user.* is left\nunsupported. As bpffs is FS_USERNS_MOUNT, security.* is reachable by\nthe unprivileged mounter in a user namespace, and thus we are using\nthe simple_xattr_set_limited infra there (trusted.* needs global\nCAP_SYS_ADMIN).\n\nbpf_fill_super() is open-coded instead of using simple_fill_super(),\nbecause the root inode must now be allocated through bpf_fs_alloc_inode()\ni.e. carry the bpf_fs_inode wrapper and come from the right cache -\nwhich requires s_op (and s_xattr) to be installed before the first\ninode is created. While at it, also harden s_iflags with SB_I_NOEXEC\nand SB_I_NODEV.\n\nbpf_fs_listxattr() is only reachable through the filesystem via\ni_op->listxattr, so the BPF token inode is left untouched. Name-based\nfsetxattr()/fgetxattr() on a token fd still work since the get/set\nhandlers are installed at the superblock.\n\nFor security.* namespace, we use simple_xattr_set_limited() but\nthere was no simple_xattr_add_limited() API yet which was needed\nin bpf_fs_initxattrs() to avoid underflows in the accounting. The\nsymlink target is freed in bpf_free_inode() rather than in\nbpf_destroy_inode() so that it is released only after an RCU grace\nperiod, as an RCU path walk following the symlink may still\ndereference inode->i_link in security_inode_follow_link(). Lastly,\nthe bpf_symlink() allocated the symlink target is switched to\nGFP_KERNEL_ACCOUNT, so the string is charged to the caller's memcg.\n\nSigned-off-by: Daniel Borkmann \nLink: https://patch.msgid.link/20260602074012.416289-1-daniel@iogearbox.net\nCc: Christian Brauner \nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/90272c66977cd3593c735fe51cb0a52cc0e89077","oid":"9722955b54307e9070994f2382ec06af3d7405e0"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.directory.delegations\n","oid":"ff570ffb8eeb863de6ec6e8fc294c273a91e96bd","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"jlayton@kernel.org","name":"Jeff Layton","when":"2026-05-16T07:11:23.000000-04:00"},"message":"filelock: move LEASE_BREAK_* flags out of #ifdef CONFIG_FILE_LOCKING\n\nThis was causing a build break when CONFIG_FILE_LOCKING was disabled.\nMove the LEASE_BREAK_* flags into the non-#ifdef'ed part of the file.\n\nReported-by: kernel test robot \nCloses: https://lore.kernel.org/oe-kbuild-all/202605161232.1lY6pZoM-lkp@intel.com/\nSigned-off-by: Jeff Layton \nLink: https://patch.msgid.link/20260516-dir-deleg-fix-v1-1-1b68f0aa990a@kernel.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/a7e15565268e294de1ce6b56f6eb3e3b6edc43ab","oid":"246bc86d0fd891273a8502314f158eab23af823c"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-7.2-rc1\n","oid":"5c561244dad54c13a7e7c12e91a3e5974a6d001f","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"rafael.j.wysocki@intel.com","name":"Rafael J. Wysocki","when":"2026-06-11T21:42:36.000000+02:00"},"message":"Merge branches 'pm-sleep', 'pm-powercap' and 'pm-tools'\n\nMerge updates related to system sleep support, two updates of the\nintel_rapl power capping driver, and a pm-graph utility fix for\n7.2-rc1:\n\n - Add sysctl interface for DPM watchdog timeouts (Tzung-Bi Shih)\n\n - Use complete() instead of complete_all() in device_pm_sleep_init() to\n avoid a false-positive warning from lockdep_assert_RT_in_threaded_ctx()\n when CONFIG_PROVE_RAW_LOCK_NESTING is enabled (Jiakai Xu)\n\n - Use a flexible array for CRC uncompressed buffers during hibernation\n image saving (Rosen Penev)\n\n - Make the LZ4 algorithm available for hibernation compression (l1rox3)\n\n - Move the preallocate_image() call during hibernation after the\n \"prepare\" phase of the \"freeze\" transition (Matthew Leach)\n\n - Fix a memory leak in rapl_add_package_cpuslocked() in the intel_rapl\n power capping driver and use sysfs_emit() in cpumask_show() in that\n driver (Sumeet Pawnikar, Yury Norov)\n\n - Fix ValueError when parsing incomplete device properties in the\n pm-graph utility (Gongwei Li)\n\n* pm-sleep:\n PM: dpm_watchdog: Add sysctl interface for DPM watchdog timeouts\n PM: hibernate: Use flexible array for CRC uncompressed buffers\n PM: hibernate: make LZ4 available for hibernation compression\n PM: sleep: Use complete() in device_pm_sleep_init()\n PM: hibernate: call preallocate_image() after freeze prepare\n\n* pm-powercap:\n powercap: intel_rapl: Use sysfs_emit() in cpumask_show()\n powercap: intel_rapl: Fix memory leak in rapl_add_package_cpuslocked()\n\n* pm-tools:\n PM: tools: pm-graph: fix ValueError when parsing incomplete device properties\n","name":"refs/merge-window/b7b9fef85ccd38cebf187688b321fb1bd2429d63","oid":"5ca48f6f2afc0a0c3f0584f95843451042ffc5ca"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.iomap\n","oid":"d5a487a8becf33462461f35248aadad70a1406f9","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"linkinjeon@kernel.org","name":"Namjae Jeon","when":"2026-06-03T23:40:31.000000+09:00"},"message":"iomap: Add IOMAP_F_ZERO_TAIL flag to trace event strings\n\nAdd IOMAP_F_ZERO_TAIL to the flag string mapping in iomap trace\nevents. This allows the new flag to be properly displayed in\nftrace output when iomap operations use it.\n\nSigned-off-by: Namjae Jeon \nLink: https://patch.msgid.link/20260603144031.7370-1-linkinjeon@kernel.org\nReviewed-by: \"Darrick J. Wong\" \nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/b827c43e648e8fb7728896c0eaeb088d89b2cde9","oid":"b7bae6880e8de2a5f693c18d87ad5cc26f157eb2"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.eventpoll\n","oid":"fbdc1d8b0a4582e3211cee46b1e18a231f34f1fe","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"zhanwei919@gmail.com","name":"Zhan Wei","when":"2026-05-29T22:25:33.000000+08:00"},"message":"eventpoll: restore EP_UNACTIVE_PTR sentinel for ctx->tfile_check_list\n\nCommit e09c77d94003 (\"eventpoll: hoist CTL_ADD scratch state into\nstruct ep_ctl_ctx\") moved tfile_check_list from a file-scope global into\nthe stack-allocated struct ep_ctl_ctx, and in doing so replaced the\nEP_UNACTIVE_PTR sentinel with NULL on the grounds that \"NULL is the\nobvious 'empty' value and zero-init handles it for free\", describing the\nchange as \"No functional change\". It is not.\n\nepitems_head->next is overloaded with two roles:\n\n 1. the \"next\" pointer that threads a head onto ctx->tfile_check_list;\n 2. a membership flag: ep_remove_file() uses\n !smp_load_acquire(&v->next) to mean \"this head is not on any\n pending ctx->tfile_check_list and is therefore safe to free\".\n\nBefore that change the EP_UNACTIVE_PTR sentinel kept the two roles\ndisjoint: a head on the list always had a non-NULL ->next (another head,\nor the sentinel at the tail), so ->next == NULL was equivalent to \"never\nlisted\". With the sentinel gone the list is NULL-terminated, so the tail\nhead's ->next is NULL as well. ep_remove_file()'s gate can no longer\ndistinguish \"never listed\" from \"listed at the tail\", and misfires on\nthe tail head.\n\nThe reader (reverse_path_check_proc) holds epnested_mutex +\nrcu_read_lock; the freer (ep_remove_file) holds ep->mtx + file->f_lock.\nThe two sides share no mutex -- the sentinel was the invariant the gate\nrelied on to know it could skip the read side. With it gone,\nep_remove_file() frees the tail head while reverse_path_check_proc() is\nstill walking it, producing the slab-use-after-free read. The syzbot\nreproducer hits this within seconds on a multi-CPU VM.\n\nRestore the sentinel: initialize ctx.tfile_check_list to EP_UNACTIVE_PTR\nin do_epoll_ctl_file(), and terminate the walk on \"!= EP_UNACTIVE_PTR\"\nin reverse_path_check() and clear_tfile_check_list(). The tail head's\n->next becomes the sentinel again rather than NULL, so\nep_remove_file()'s gate regains its exclusivity and stops misfiring on\nthe tail. ep_remove_file() itself is unchanged.\n\nThis restores the invariant the file-scope tfile_check_list relied on\nbefore that change while preserving the ctx packaging it introduced.\n\nReported-by: syzbot+e70e1b6cba8714543f7c@syzkaller.appspotmail.com\nCloses: https://syzkaller.appspot.com/bug?extid=e70e1b6cba8714543f7c\nFixes: e09c77d94003 (\"eventpoll: hoist CTL_ADD scratch state into struct ep_ctl_ctx\")\nSuggested-by: Christian Brauner \nLink: https://lore.kernel.org/all/20260528-rotwild-summt-kuhhandel-7276ef4c33b7@brauner.io/\nSigned-off-by: Zhan Wei \nLink: https://patch.msgid.link/20260529142533.23696-1-zhanwei919@gmail.com\nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/c259ae4b4ae025450466b9dc324e64daec2f75db","oid":"a1e9718b406bc4e6d0c63c7b999d06febbdc4091"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.bh\n","oid":"7b936c817821e50b58fd3639a910c384a8a97d4c","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-06-04T10:28:17.000000+02:00"},"message":"Merge patch series \"Remove b_end_io from struct buffer_head\"\n\nMatthew Wilcox (Oracle) says:\n\nThere are four benefits to this patchset. First, it removes an\nindirect function call from the completion path. Instead of setting\nbio->bi_end_io to end_bio_bh_io_sync() which then calls bh->b_end_io(),\nwe set bio->bi_end_io to the appropriate completion handler, replacing\ntwo indirect function calls with one.\n\nSecond, there is a slight security advantage to this. It is one fewer\nfunction pointer in the middle of a writable data structure that can\nbe corrupted. Third, it shrinks struct buffer_head from 104 bytes to 96\nbytes, allowing for appropriximately 7% reduction in the amount of memory\nused by buffer_heads (or, alternatively, allows 7% more buffer_heads to\nbe cached in the same amount of memory). Fourth, it removes some\natomic operations as the buffer refcount is no longer incremented before\ncalling the end_io handler.\n\nI've run ext4 through its paces, and everything seems OK. I've only\ncompiled ocfs2/gfs2/nilfs/md-bitmap. Hopefully the maintainers can give\nthis series a try. I'm sending the entire series to linux-fsdevel\nand cc'ing the fs-specific mailing lists for the fs-specific patches.\n\n* patches from https://patch.msgid.link/20260528173150.1093780-1-willy@infradead.org: (34 commits)\n buffer: Remove end_buffer_write_sync()\n buffer: Change calling convention for end_buffer_read_sync()\n buffer: Remove b_end_io\n buffer: Remove submit_bh()\n md-bitmap: Convert read_file_page and write_file_page to bh_submit()\n nilfs2: Convert nilfs_mdt_submit_block to bh_submit()\n nilfs2: Convert nilfs_gccache_submit_read_data to bh_submit()\n nilfs2: Convert nilfs_btnode_submit_block to bh_submit()\n buffer: Remove mark_buffer_async_write()\n gfs2: Convert gfs2_aspace_write_folio to bh_submit()\n gfs2: Remove use of b_end_io in gfs2_meta_read_endio()\n gfs2: Convert gfs2_dir_readahead to bh_submit()\n gfs2: Convert gfs2_metapath_ra to bh_submit()\n ocfs2: Convert ocfs2_write_super_or_backup to bh_submit()\n ocfs2: Convert ocfs2_read_blocks to bh_submit()\n ocfs2: Convert ocfs2_read_block to bh_submit()\n ocfs2: Convert ocfs2_write_block to bh_submit()\n jbd2: Convert jbd2_write_superblock() to bh_submit()\n jbd2: Convert journal commit to bh_submit()\n ext4: Convert ext4_commit_super() to bh_submit()\n ...\n\nLink: https://patch.msgid.link/20260528173150.1093780-1-willy@infradead.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/c4231d23938e5c6e3efb8a84e45e9b41ce42c335","oid":"f0d857543e4d37464759c338f46ad6c85a618a2e"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-7.2-rc1\n","oid":"deae96778c6620ca990f72a9643f8fc79c1f352d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"rafael.j.wysocki@intel.com","name":"Rafael J. Wysocki","when":"2026-06-11T15:34:30.000000+02:00"},"message":"Merge branches 'acpi-processor', 'acpi-cppc' and 'acpi-pci'\n\nMerge an ACPI processor driver update, two ACPI CPPC library updates\nand ACPI PCI/CXL support updates for 7.2-rc1:\n\n - Add cpuidle driver check in acpi_processor_register_idle_driver() to\n avoid evaluating _CST unnecessarily (Tony W Wang-oc)\n\n - Suppress UBSAN warning caused by field misuse during PCC-based\n register access in the ACPI CPPC library (Jeremy Linton)\n\n - Add support for CPPC v4 to the ACPI CPPC library (Sumit Gupta)\n\n - Update the ACPI device enumeration code to honor _DEP for ACPI0016\n PCI/CXL host bridges and make the ACPI PCI root driver clear _DEP\n dependencies for PCI roots that have become operational (Chen Pei)\n\n* acpi-processor:\n ACPI: processor: Add cpuidle driver check in acpi_processor_register_idle_driver()\n\n* acpi-cppc:\n ACPI: CPPC: Suppress UBSAN warning caused by field misuse\n ACPI: CPPC: Add support for CPPC v4\n\n* acpi-pci:\n ACPI: scan: Honor _DEP for ACPI0016 PCI/CXL host bridge\n ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach\n","name":"refs/merge-window/c62359836cbaf2b8ba628d60a44af990e7f0992b","oid":"615f90d3b1b7900d591a9162793f616b051f07b8"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git tags/kbuild-7.2-1\n","oid":"22cf6aa7fe6f92e947d217b09e76d9e3fc9f7406","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"enelsonmoore@gmail.com","name":"Ethan Nelson-Moore","when":"2026-06-08T19:17:10.000000-07:00"},"message":"kconfig: tests: fix typo in comment\n\nscripts/kconfig/tests/no_write_if_dep_unmet/__init__.py contains a typo\n\"COFIG_\" for \"CONFIG_\". Fix it.\n\nDiscovered while searching for typos in CONFIG_* variable references.\n\nSigned-off-by: Ethan Nelson-Moore \nLink: https://patch.msgid.link/20260609021712.7965-1-enelsonmoore@gmail.com\nSigned-off-by: Nathan Chancellor \n","name":"refs/merge-window/ce05216f68127d8642f5e042288f65a554f08fd2","oid":"1a1e62a5a48494cdf33e3bfb82fb8f408da7c4cc"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git tags/rcu.release.v7.2\n","oid":"9a75f69e9549dcdc232cf095404098070e6acdf5","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"urezki@gmail.com","name":"Uladzislau Rezki (Sony)","when":"2026-06-02T19:45:08.000000+02:00"},"message":"Merge branches 'rcutorture.2026.05.24' and 'misc.2026.05.24' into rcu-merge.2026.05.24\n\nrcutorture.2026.05.24: Torture-test updates\nmisc.2026.05.24: Miscellaneous RCU updates\n","name":"refs/merge-window/d0426043cbc2fc676d6152b911adbeaf2a2cc1f1","oid":"e853c1b28580ea93fda3cd729e440a3fc16fa647"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-7.2-rc1-tag\n","oid":"6961a9a12e9ca188d5f605218af7365a6ae3b9a8","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"david.laight.linux@gmail.com","name":"David Laight","when":"2026-06-06T21:25:58.000000+01:00"},"message":"xen/xenbus: Replace strcpy() with memcpy()\n\nThe length of the string is calculated in order to allocate the correct\nsized memory block, use the same length to copy the string.\n\nSigned-off-by: David Laight \nReviewed-by: Juergen Gross \nSigned-off-by: Juergen Gross \nMessage-ID: <20260606202633.5018-4-david.laight.linux@gmail.com>\n","name":"refs/merge-window/d125f5c03e2ad0c25ecb026c6c504c1f4f1cbc9a","oid":"a174910917a8e93cb5334e9dce8bac32bff22c47"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/kernel-7.2-rc1.task_exec_state\n","oid":"7923dc7d03fb3c2741012d47a242197facf6c345","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-05-22T16:03:30.000000+02:00"},"message":"exec: free the old mm outside the exec locks\n\nexec_mmap() installs the new mm and then tears the old one down while\nstill holding exec_update_lock for writing -- and with cred_guard_mutex\nheld all the way to setup_new_exec():\n\n\tsetmax_mm_hiwater_rss(&tsk->signal->maxrss, old_mm);\n\tmm_update_next_owner(old_mm);\n\tmmput(old_mm);\n\nNeither lock is needed for this. exec_update_lock only exists to make the\nmm swap atomic with the later commit_creds(), so that permission-checking\nreaders (proc, ptrace, the futex robust list, perf, kcmp, mm_access())\nnever observe the new mm together with the old credentials. Those readers\nall operate on task->mm, i.e. the new mm after the swap; none looks at the\ndetached old mm, its ->owner or signal->maxrss. cred_guard_mutex guards\ncredential calculation and is equally irrelevant here.\n\nThe cost is real: __mmput() runs exit_mmap() over the entire old address\nspace and can block in exit_aio() waiting for in-flight AIO, all while\nholding exec_update_lock for writing and cred_guard_mutex. For execve() of\na large process this blocks ptrace_attach() and every exec_update_lock\nreader for the duration of the teardown.\n\nStash the old mm in bprm->old_mm and release it from setup_new_exec()\nafter both locks are dropped. setup_new_exec() still runs before\nsetup_arg_pages() and the segment mappings, so the old address space is\nfreed before the new one is populated and peak memory is unchanged. The\nordering constraints are kept: old_mm's mmap_lock is still dropped in\nexec_mmap() before mm_update_next_owner() (required since commit\n31a78f23bac0 (\"mm owner: fix race between swapoff and exit\")), and\nmm_update_next_owner() still precedes mmput(); both run in the execing\ntask's context, as mm_update_next_owner() requires.\n\nIf exec swaps the mm but fails before setup_new_exec() runs the old mm\nwould leak, so add a backstop in free_bprm(). The lazy-tlb case\n(old_mm == NULL, e.g. kernel_execve()) has no address space to\nfree and is left in exec_mmap().\n\nLink: https://patch.msgid.link/20260522-work-exit_mm-v1-1-bd32d5a560bb@kernel.org\nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/d72f629726433dd34b82ee31359234a9e00e8c98","oid":"38205ecbe6b6dc47968ad4e9c978e2117720969e"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.writeback\n","oid":"a2339af1d66ff6d192d7b8dfce3eedd9f1c9b7b8","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"brauner@kernel.org","name":"Christian Brauner","when":"2026-06-04T10:18:25.000000+02:00"},"message":"Merge patch series \"mm: improve write performance with RWF_DONTCACHE\"\n\nJeff Layton says:\n\nThis patch series is intended to improve write performance with\nRWF_DONTCACHE. This version fixes additional stat accounting issues\nfound during review: integer promotion on 32-bit, cgroup writeback\ndomain migration, folio split flag preservation, and a UAF that could\noccur in filemap_dontcache_kick_writeback().\n\n* patches from https://patch.msgid.link/20260511-dontcache-v7-0-2848ddce8090@kernel.org:\n mm: kick writeback flusher for IOCB_DONTCACHE with targeted dirty tracking\n mm: track DONTCACHE dirty pages per bdi_writeback\n mm: preserve PG_dropbehind flag during folio split\n\nLink: https://patch.msgid.link/20260511-dontcache-v7-0-2848ddce8090@kernel.org\nSigned-off-by: Christian Brauner \n","name":"refs/merge-window/feb500dc97ab9fa92ee34b32e661d52d15b9b36a","oid":"0275dc184aa007b260374af6d46fb15741c062a8"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.procfs\n","oid":"13d279473d7d8557620373392e7b73599f04f696","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"mjguzik@gmail.com","name":"Mateusz Guzik","when":"2026-06-10T16:39:54.000000+02:00"},"message":"fs: fix ups and tidy ups to /proc/filesystems caching\n\n- add missing unlocks in some corner cases\n- whitespace touch ups\n- s/smp_store_release/rcu_assign_pointer/ [nop, the macro expands to the same thing]\n- mark file_systems_string as __read_mostly\n\nSigned-off-by: Mateusz Guzik \nLink: https://patch.msgid.link/20260610143954.34185-1-mjguzik@gmail.com\nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/fef1ec39862add142fe2078106ab54ee8563a0a7","oid":"cf30ceccfaec3d2549ff60f7c915625f12dd3a93"},{"annotation":{"message":"git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc1.misc\n","oid":"5f5a7bc3c4a2ce71a00a1216d65beef676b6f3fe","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-13T14:15:15.000000-07:00"}},"author":{"email":"liwang@kylinos.cn","name":"Li Wang","when":"2026-05-28T18:42:08.000000+08:00"},"message":"backing-file: fix backing_file_open() kerneldoc parameter\n\nThe kerneldoc for backing_file_open() documented a @user_path argument,\nbut the function takes const struct file *user_file. The user\npath is derived as &user_file->f_path.\n\nUpdate the @-tag to @user_file and adjust the description accordingly.\nAlso fix the \"reuqested\" typo to 'requested' in the old comment.\n\nSigned-off-by: Li Wang \nLink: https://patch.msgid.link/20260528104208.395757-1-liwang@kylinos.cn\nReviewed-by: Amir Goldstein \nSigned-off-by: Christian Brauner (Amutable) \n","name":"refs/merge-window/ff01ee92fd1554bdb7e1df2b9532690e425f3b81","oid":"aa5c4fe3ba0cb2af90bbcfa7a8ef4fefcd5c2370"},{"annotation":{"message":"Linux 7.1-rc7","oid":"b7e5ac83cb16f7ffd11dc23736f84276602100ed","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-07T15:37:58.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-06-07T15:37:58.000000-07:00"},"message":"Linux 7.1-rc7\n","name":"v7.1-rc7","oid":"4549871118cf616eecdd2d939f78e3b9e1dddc48"},{"annotation":{"message":"Linux 7.1-rc6","oid":"3bc831df9ee16fceee851872315161377ca1417d","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-31T15:14:24.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-31T15:14:24.000000-07:00"},"message":"Linux 7.1-rc6\n","name":"v7.1-rc6","oid":"e43ffb69e0438cddd72aaa30898b4dc446f664f8"},{"annotation":{"message":"Linux 7.1-rc5","oid":"9e171fc1d7d7ab847a750c03571c87ac3c17bd84","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-24T13:48:06.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-24T13:48:06.000000-07:00"},"message":"Linux 7.1-rc5\n","name":"v7.1-rc5","oid":"e7ae89a0c97ce2b68b0983cd01eda67cf373517d"},{"annotation":{"message":"Linux 7.1-rc4","oid":"aa61612ab641d7d62b0b6889f2c7c9251489f6e3","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-17T13:59:58.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-17T13:59:58.000000-07:00"},"message":"Linux 7.1-rc4\n","name":"v7.1-rc4","oid":"5200f5f493f79f14bbdc349e402a40dfb32f23c8"},{"annotation":{"message":"Linux 7.1-rc3","oid":"bb1459368dd795c43380057523f571d5eb0ddded","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-10T14:08:09.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-10T14:08:09.000000-07:00"},"message":"Linux 7.1-rc3\n","name":"v7.1-rc3","oid":"5d6919055dec134de3c40167a490f33c74c12581"},{"annotation":{"message":"Linux 7.1-rc2","oid":"9e0898f1c0f134c6bad146ca8578f73c3e40ac0a","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-03T14:21:25.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-05-03T14:21:25.000000-07:00"},"message":"Linux 7.1-rc2\n","name":"v7.1-rc2","oid":"7fd2df204f342fc17d1a0bfcd474b24232fb0f32"},{"annotation":{"message":"Linux 7.1-rc1","oid":"5e9b7d093f3f77cb0af4409559e3d139babfb443","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-26T14:19:00.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-26T14:19:00.000000-07:00"},"message":"Linux 7.1-rc1\n","name":"v7.1-rc1","oid":"254f49634ee16a731174d2ae34bc50bd5f45e731"},{"annotation":{"message":"Linux 7.0","oid":"3131ff5a117498bb4b9db3a238bb311cbf8383ce","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-12T13:48:06.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-12T13:48:06.000000-07:00"},"message":"Linux 7.0\n","name":"v7.0","oid":"028ef9c96e96197026887c0f092424679298aae8"},{"annotation":{"message":"Linux 7.0-rc7","oid":"0e5d0a0b5ca6ea4e391d6786266405c5871e0151","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-05T15:26:23.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-04-05T15:26:23.000000-07:00"},"message":"Linux 7.0-rc7\n","name":"v7.0-rc7","oid":"591cd656a1bf5ea94a222af5ef2ee76df029c1d2"},{"annotation":{"message":"Linux 7.0-rc6","oid":"b6c7d19951061de1be08fb8f5714e630b24bcc1c","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-29T15:40:00.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-29T15:40:00.000000-07:00"},"message":"Linux 7.0-rc6\n","name":"v7.0-rc6","oid":"7aaa8047eafd0bd628065b15757d9b48c5f9c07d"},{"annotation":{"message":"Linux 7.0-rc5","oid":"d1d81e9d1a4dd846aee9ae77ff9ecc2800d72148","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-22T14:42:17.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-22T14:42:17.000000-07:00"},"message":"Linux 7.0-rc5\n","name":"v7.0-rc5","oid":"c369299895a591d96745d6492d4888259b004a9e"},{"annotation":{"message":"Linux 7.0-rc4","oid":"34cb4f916af10153c87fabaf6c34e4cafa170427","tagger":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-15T13:52:05.000000-07:00"}},"author":{"email":"torvalds@linux-foundation.org","name":"Linus Torvalds","when":"2026-03-15T13:52:05.000000-07:00"},"message":"Linux 7.0-rc4\n","name":"v7.0-rc4","oid":"f338e77383789c0cae23ca3d48adcc5e9e137e3c"},{"annotation":{"message":"Lin