)]}' { "log": [ { "commit": "ffc253263a1375a65fa6c9f62a893e9767fbebfa", "tree": "4caeea940e653b2c49a95640aaf2dedb31521c51", "parents": [ "2af9b20dbb39f6ebf9b9b6c090271594627d818e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 29 16:31:08 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 29 16:31:08 2023 -1000" }, "message": "Linux 6.6\n" }, { "commit": "2af9b20dbb39f6ebf9b9b6c090271594627d818e", "tree": "c97722a9de1eea92afe620b3ff50682e22e9200b", "parents": [ "e663ab6bb56fa8f048cf8725aba577e56f7b2644", "bd94d86f490b70c58b3fc5739328a53ad4b18d86" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:15:07 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:15:07 2023 -1000" }, "message": "Merge tag \u0027x86-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull misc x86 fixes from Ingo Molnar:\n\n - Fix a possible CPU hotplug deadlock bug caused by the new TSC\n synchronization code\n\n - Fix a legacy PIC discovery bug that results in device troubles on\n affected systems, such as non-working keybards, etc\n\n - Add a new Intel CPU model number to \u003casm/intel-family.h\u003e\n\n* tag \u0027x86-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n x86/tsc: Defer marking TSC unstable to a worker\n x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility\n x86/cpu: Add model number for Intel Arrow Lake mobile processor\n" }, { "commit": "e663ab6bb56fa8f048cf8725aba577e56f7b2644", "tree": "6b21c9f7341ff2e8c6b9d20f5ee1f94d19ad8dc4", "parents": [ "4714de03329810b9ac57762b6bfdb73b123fedd5", "f199bf5bf84c19a4f488a39d7d694ab10787de35" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:12:34 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:12:34 2023 -1000" }, "message": "Merge tag \u0027irq-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull irq fix from Ingo Molnar:\n \"Restore unintentionally lost quirk settings in the GIC irqchip driver,\n which broke certain devices\"\n\n* tag \u0027irq-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n irqchip/gic-v3-its: Don\u0027t override quirk settings with default values\n" }, { "commit": "4714de03329810b9ac57762b6bfdb73b123fedd5", "tree": "03894e3e4de87311d6da92ac78d351da81c3e91d", "parents": [ "51a7691038c334db81b736faa6b4cc4778e751fc", "a71ef31485bb51b846e8db8b3a35e432cc15afb5" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:10:47 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:10:47 2023 -1000" }, "message": "Merge tag \u0027perf-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull perf event fix from Ingo Molnar:\n \"Fix a potential NULL dereference bug\"\n\n* tag \u0027perf-urgent-2023-10-28\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n perf/core: Fix potential NULL deref\n" }, { "commit": "51a7691038c334db81b736faa6b4cc4778e751fc", "tree": "a3a099d0c1a0db22bb6c4a33a6748baeff9d9861", "parents": [ "bd80d2ef59bb6436effa6b7f77746b1418cf0a15", "926fe783c8a64b33997fec405cf1af3e61aed441" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:04:56 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:04:56 2023 -1000" }, "message": "Merge tag \u0027probes-fixes-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace\n\nPull probes fixes from Masami Hiramatsu:\n\n - tracing/kprobes: Fix kernel-doc warnings for the variable length\n arguments\n\n - tracing/kprobes: Fix to count the symbols in modules even if the\n module name is not specified so that user can probe the symbols in\n the modules without module name\n\n* tag \u0027probes-fixes-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:\n tracing/kprobes: Fix symbol counting logic by looking at modules as well\n tracing/kprobes: Fix the description of variable length arguments\n" }, { "commit": "bd80d2ef59bb6436effa6b7f77746b1418cf0a15", "tree": "694b490e7cb0d8a75eff7992425f33626d7dd9f9", "parents": [ "db5cda7fd46881f88eee52f3960b7856ddf051fb", "d5090484b021794271280ab64d20253883b7f6fd" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:01:31 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 08:01:31 2023 -1000" }, "message": "Merge tag \u0027dma-mapping-6.6-2023-10-28\u0027 of git://git.infradead.org/users/hch/dma-mapping\n\nPull dma-mapping fix from Christoph Hellwig:\n\n - reduce the initialy dynamic swiotlb size to remove an annoying but\n harmless warning from the page allocator (Petr Tesarik)\n\n* tag \u0027dma-mapping-6.6-2023-10-28\u0027 of git://git.infradead.org/users/hch/dma-mapping:\n swiotlb: do not try to allocate a TLB bigger than MAX_ORDER pages\n" }, { "commit": "db5cda7fd46881f88eee52f3960b7856ddf051fb", "tree": "9073c85f9e75a384f6e300859c99244766d66e18", "parents": [ "8907bfd2b11ab0d09f2c408f82bff09e55d53a9a", "28926daf731f72d0537767fdbab2a3e06e31190a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 07:51:27 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 07:51:27 2023 -1000" }, "message": "Merge tag \u0027char-misc-6.6-final\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc\n\nPull char/misc driver fixes from Greg KH:\n \"Here are some very small driver fixes for 6.6-final that have shown up\n in the past two weeks. Included in here are:\n\n - tiny fastrpc bugfixes for reported errors\n\n - nvmem register fixes\n\n - iio driver fixes for some reported problems\n\n - fpga test fix\n\n - MAINTAINERS file update for fpga\n\n All of these have been in linux-next this week with no reported\n problems\"\n\n* tag \u0027char-misc-6.6-final\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:\n fpga: Fix memory leak for fpga_region_test_class_find()\n fpga: m10bmc-sec: Change contact for secure update driver\n fpga: disable KUnit test suites when module support is enabled\n iio: afe: rescale: Accept only offset channels\n nvmem: imx: correct nregs for i.MX6ULL\n nvmem: imx: correct nregs for i.MX6UL\n nvmem: imx: correct nregs for i.MX6SLL\n misc: fastrpc: Unmap only if buffer is unmapped from DSP\n misc: fastrpc: Clean buffers on remote invocation failures\n misc: fastrpc: Free DMA handles for RPC calls with no arguments\n misc: fastrpc: Reset metadata buffer to avoid incorrect free\n iio: exynos-adc: request second interupt only when touchscreen mode is used\n iio: adc: xilinx-xadc: Correct temperature offset/scale for UltraScale\n iio: adc: xilinx-xadc: Don\u0027t clobber preset voltage/temperature thresholds\n dt-bindings: iio: add missing reset-gpios constrain\n" }, { "commit": "8907bfd2b11ab0d09f2c408f82bff09e55d53a9a", "tree": "3e2ac18a335a22f7239badda999c7fbbd3e7c488", "parents": [ "67d4c87945b2d9678347eaa4567d62dd56dc9713", "c896ff2dd8f30a6b0a922c83a96f6d43f05f0e92" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 07:48:37 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 28 07:48:37 2023 -1000" }, "message": "Merge tag \u0027i2c-for-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux\n\nPull i2c fixes from Wolfram Sang:\n \"Bugfixes for Axxia when it is a target and for PEC handling of\n stm32f7.\n\n Plus, fix an OF node leak pattern in the mux subsystem\"\n\n* tag \u0027i2c-for-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:\n i2c: stm32f7: Fix PEC handling in case of SMBUS transfers\n i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node()\n i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node()\n i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()\n i2c: aspeed: Fix i2c bus hang in slave read\n" }, { "commit": "67d4c87945b2d9678347eaa4567d62dd56dc9713", "tree": "53c282767027694f2246e6fc2e28a2cf318baeca", "parents": [ "d1b0949f23a343d3153d5c681fb1866538534227", "790437bbe0ef7e5cb5d091dd711c0d61d03945a5" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 16:52:51 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 16:52:51 2023 -1000" }, "message": "Merge tag \u0027clk-fixes-for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux\n\nPull clk fixes from Stephen Boyd:\n \"Three fixes, one for the clk framework and two for clk drivers:\n\n - Avoid an oops in possible_parent_show() by checking for no parent\n properly when a DT index based lookup is used\n\n - Handle errors returned from divider_ro_round_rate() in\n clk_stm32_composite_determine_rate()\n\n - Fix clk_ops::determine_rate() implementation of socfpga\u0027s\n gateclk_ops that was ruining uart output because the divider\n was forgotten about\"\n\n* tag \u0027clk-fixes-for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux:\n clk: stm32: Fix a signedness issue in clk_stm32_composite_determine_rate()\n clk: Sanitize possible_parent_show to Handle Return Value of of_clk_get_parent_name\n clk: socfpga: gate: Account for the divider in determine_rate\n" }, { "commit": "d1b0949f23a343d3153d5c681fb1866538534227", "tree": "5bd6d0eb56ede3c80d5b525722f115a7765590c6", "parents": [ "56567a20b22bdbf85c3e55eee3bf2bd23fa2f108", "dc32464a5fe4946fe1a4d8f8e29961dc411933c5" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 16:44:58 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 16:44:58 2023 -1000" }, "message": "Merge tag \u0027pull-fixes\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs\n\nPull misc filesystem fixes from Al Viro:\n \"Assorted fixes all over the place: literally nothing in common, could\n have been three separate pull requests.\n\n All are simple regression fixes, but not for anything from this cycle\"\n\n* tag \u0027pull-fixes\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:\n ceph_wait_on_conflict_unlink(): grab reference before dropping -\u003ed_lock\n io_uring: kiocb_done() should *not* trust -\u003eki_pos if -\u003e{read,write}_iter() failed\n sparc32: fix a braino in fault handling in csum_and_copy_..._user()\n" }, { "commit": "926fe783c8a64b33997fec405cf1af3e61aed441", "tree": "8e7b9b273ec98a18ef1ba27b485a7f357c44a3b5", "parents": [ "e0f831836cead677fb07d54bd6bf499df35640c2" ], "author": { "name": "Andrii Nakryiko", "email": "andrii@kernel.org", "time": "Fri Oct 27 16:31:26 2023 -0700" }, "committer": { "name": "Masami Hiramatsu (Google)", "email": "mhiramat@kernel.org", "time": "Sat Oct 28 09:50:42 2023 +0900" }, "message": "tracing/kprobes: Fix symbol counting logic by looking at modules as well\n\nRecent changes to count number of matching symbols when creating\na kprobe event failed to take into account kernel modules. As such, it\nbreaks kprobes on kernel module symbols, by assuming there is no match.\n\nFix this my calling module_kallsyms_on_each_symbol() in addition to\nkallsyms_on_each_match_symbol() to perform a proper counting.\n\nLink: https://lore.kernel.org/all/20231027233126.2073148-1-andrii@kernel.org/\n\nCc: Francis Laniel \u003cflaniel@linux.microsoft.com\u003e\nCc: stable@vger.kernel.org\nCc: Masami Hiramatsu \u003cmhiramat@kernel.org\u003e\nCc: Steven Rostedt \u003crostedt@goodmis.org\u003e\nFixes: b022f0c7e404 (\"tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols\")\nSigned-off-by: Andrii Nakryiko \u003candrii@kernel.org\u003e\nAcked-by: Song Liu \u003csong@kernel.org\u003e\nSigned-off-by: Masami Hiramatsu (Google) \u003cmhiramat@kernel.org\u003e\n" }, { "commit": "dc32464a5fe4946fe1a4d8f8e29961dc411933c5", "tree": "987f42313d23e5a39c4b60ed5d7a31537e901bc0", "parents": [ "1939316bf988f3e49a07d9c4dd6f660bf4daa53d" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Sep 14 21:55:29 2023 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Oct 27 20:14:38 2023 -0400" }, "message": "ceph_wait_on_conflict_unlink(): grab reference before dropping -\u003ed_lock\n\nUse of dget() after we\u0027d dropped -\u003ed_lock is too late - dentry might\nbe gone by that point.\n\nReviewed-by: Jeff Layton \u003cjlayton@kernel.org\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "1939316bf988f3e49a07d9c4dd6f660bf4daa53d", "tree": "41ba99310df374f9125e15ee15f2a8e08dec6dd0", "parents": [ "1f36cd05e0081f2c75769a551d584c4ffb2a5660" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Aug 28 18:47:31 2023 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Oct 27 20:14:11 2023 -0400" }, "message": "io_uring: kiocb_done() should *not* trust -\u003eki_pos if -\u003e{read,write}_iter() failed\n\n-\u003eki_pos value is unreliable in such cases. For an obvious example,\nconsider O_DSYNC write - we feed the data to page cache and start IO,\nthen we make sure it\u0027s completed. Update of -\u003eki_pos is dealt with\nby the first part; failure in the second ends up with negative value\nreturned _and_ -\u003eki_pos left advanced as if sync had been successful.\nIn the same situation write(2) does not advance the file position\nat all.\n\nReviewed-by: Christian Brauner \u003cbrauner@kernel.org\u003e\nReviewed-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "56567a20b22bdbf85c3e55eee3bf2bd23fa2f108", "tree": "4399adee6ec6ba2a43b1a57cf573cac5c231e6ee", "parents": [ "2dc4e0f45593abc53d58d0073b3b314f864c522b", "838b35bb6a89c36da07ca39520ec071d9250334d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 14:10:32 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 14:10:32 2023 -1000" }, "message": "Merge tag \u0027io_uring-6.6-2023-10-27\u0027 of git://git.kernel.dk/linux\n\nPull io_uring fixes from Jens Axboe:\n \"Fix for an issue reported where reading fdinfo could find a NULL\n thread as we didn\u0027t properly synchronize, and then a disable for the\n IOCB_DIO_CALLER_COMP optimization as a recent reported highlighted how\n that could lead to deadlocks if the task issued async O_DIRECT writes\n and then proceeded to do sync fallocate() calls\"\n\n* tag \u0027io_uring-6.6-2023-10-27\u0027 of git://git.kernel.dk/linux:\n io_uring/rw: disable IOCB_DIO_CALLER_COMP\n io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid\n" }, { "commit": "1f36cd05e0081f2c75769a551d584c4ffb2a5660", "tree": "92302bfb013c0edbb0e67ac9954303d3440b4007", "parents": [ "94f6f0550c625fab1f373bb86a6669b45e9748b3" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Sun Oct 22 19:34:28 2023 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Oct 27 20:06:06 2023 -0400" }, "message": "sparc32: fix a braino in fault handling in csum_and_copy_..._user()\n\nFault handler used to make non-trivial calls, so it needed\nto set a stack frame up. Used to be\n\tsave ... - grab a stack frame, old %o... become %i...\n\t....\n\tret\t- go back to address originally in %o7, currently %i7\n\t restore - switch to previous stack frame, in delay slot\nNon-trivial calls had been gone since ab5e8b331244 and that code should\nhave become\n\tretl\t- go back to address in %o7\n\t clr %o0 - have return value set to 0\nWhat it had become instead was\n\tret\t- go back to address in %i7 - return address of *caller*\n\t clr %o0 - have return value set to 0\nwhich is not good, to put it mildly - we forcibly return 0 from\ncsum_and_copy_{from,to}_iter() (which is what the call of that\nthing had been inlined into) and do that without dropping the\nstack frame of said csum_and_copy_..._iter(). Confuses the\nhell out of the caller of csum_and_copy_..._iter(), obviously...\n\nReviewed-by: Sam Ravnborg \u003csam@ravnborg.org\u003e\nFixes: ab5e8b331244 \"sparc32: propagate the calling conventions change down to __csum_partial_copy_sparc_generic()\"\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "2dc4e0f45593abc53d58d0073b3b314f864c522b", "tree": "98ae9b3133303a5c9ee48c655f8947ec269b33ae", "parents": [ "832328c9f8aa4b41423f29a53ba7080eb7214976", "2dd710d476f2f1f6eaca884f625f69ef4389ed40" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 14:01:59 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 14:01:59 2023 -1000" }, "message": "Merge tag \u0027block-6.6-2023-10-27\u0027 of git://git.kernel.dk/linux\n\nPull block fix from Jens Axboe:\n \"Just a single fix for a potential divide-by-zero, introduced in this\n cycle\"\n\n* tag \u0027block-6.6-2023-10-27\u0027 of git://git.kernel.dk/linux:\n blk-throttle: check for overflow in calculate_bytes_allowed\n" }, { "commit": "832328c9f8aa4b41423f29a53ba7080eb7214976", "tree": "ccdd094d53ff1bbb103ad8b3a6eed62e9e7d85eb", "parents": [ "a78a67f3019c687d06dee8cebfb7b7cee7bf0216", "24eca2dce0f8d19db808c972b0281298d0bafe99" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 13:38:59 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 13:38:59 2023 -1000" }, "message": "Merge tag \u0027ata-6.6-final\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata\n\nPull ATA fix from Damien Le Moal:\n \"A single patch to fix a regression introduced by the recent\n suspend/resume fixes.\n\n The regression is that ATA disks are not stopped on system shutdown,\n which is not recommended and increases the disks SMART counters for\n unclean power off events.\n\n This patch fixes this by refining the recent rework of the scsi device\n manage_xxx flags\"\n\n* tag \u0027ata-6.6-final\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:\n scsi: sd: Introduce manage_shutdown device flag\n" }, { "commit": "a78a67f3019c687d06dee8cebfb7b7cee7bf0216", "tree": "7702e4a2aa353cb822e68f3e5037a42630df9d03", "parents": [ "888cf78c29e223fd808682f477c18cf8f61ad995", "3bde7ec13c971445faade32172cb0b4370b841d9" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 13:32:48 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 13:32:48 2023 -1000" }, "message": "Merge tag \u0027platform-drivers-x86-v6.6-6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86\n\nPull x86 platform driver fix from Hans de Goede:\n \"A single patch to extend the AMD PMC driver DMI quirk list\n for laptops which need special handling to avoid NVME s2idle\n suspend/resume errors\"\n\n* tag \u0027platform-drivers-x86-v6.6-6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:\n platform/x86: Add s2idle quirk for more Lenovo laptops\n" }, { "commit": "bd94d86f490b70c58b3fc5739328a53ad4b18d86", "tree": "9ebf57c85a9ea6347bc9fe8e3ff269f3115c5844", "parents": [ "128b0c9781c9f2651bea163cb85e52a6c7be0f9e" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Oct 25 23:31:35 2023 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Oct 27 20:36:57 2023 +0200" }, "message": "x86/tsc: Defer marking TSC unstable to a worker\n\nTetsuo reported the following lockdep splat when the TSC synchronization\nfails during CPU hotplug:\n\n tsc: Marking TSC unstable due to check_tsc_sync_source failed\n \n WARNING: inconsistent lock state\n inconsistent {IN-HARDIRQ-W} -\u003e {HARDIRQ-ON-W} usage.\n ffffffff8cfa1c78 (watchdog_lock){?.-.}-{2:2}, at: clocksource_watchdog+0x23/0x5a0\n {IN-HARDIRQ-W} state was registered at:\n _raw_spin_lock_irqsave+0x3f/0x60\n clocksource_mark_unstable+0x1b/0x90\n mark_tsc_unstable+0x41/0x50\n check_tsc_sync_source+0x14f/0x180\n sysvec_call_function_single+0x69/0x90\n\n Possible unsafe locking scenario:\n lock(watchdog_lock);\n \u003cInterrupt\u003e\n lock(watchdog_lock);\n\n stack backtrace:\n _raw_spin_lock+0x30/0x40\n clocksource_watchdog+0x23/0x5a0\n run_timer_softirq+0x2a/0x50\n sysvec_apic_timer_interrupt+0x6e/0x90\n\nThe reason is the recent conversion of the TSC synchronization function\nduring CPU hotplug on the control CPU to a SMP function call. In case\nthat the synchronization with the upcoming CPU fails, the TSC has to be\nmarked unstable via clocksource_mark_unstable().\n\nclocksource_mark_unstable() acquires \u0027watchdog_lock\u0027, but that lock is\ntaken with interrupts enabled in the watchdog timer callback to minimize\ninterrupt disabled time. That\u0027s obviously a possible deadlock scenario,\n\nBefore that change the synchronization function was invoked in thread\ncontext so this could not happen.\n\nAs it is not crucical whether the unstable marking happens slightly\ndelayed, defer the call to a worker thread which avoids the lock context\nproblem.\n\nFixes: 9d349d47f0e3 (\"x86/smpboot: Make TSC synchronization function call based\")\nReported-by: Tetsuo Handa \u003cpenguin-kernel@i-love.sakura.ne.jp\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nTested-by: Tetsuo Handa \u003cpenguin-kernel@i-love.sakura.ne.jp\u003e\nCc: stable@vger.kernel.org\nLink: https://lore.kernel.org/r/87zg064ceg.ffs@tglx\n" }, { "commit": "128b0c9781c9f2651bea163cb85e52a6c7be0f9e", "tree": "7112ae78f11fc11aeb133d7262a128391fe2c60f", "parents": [ "b99d70c0d1380f1368fd4a82271280c4fd28558b" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Oct 25 23:04:15 2023 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Oct 27 20:36:49 2023 +0200" }, "message": "x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility\n\nDavid and a few others reported that on certain newer systems some legacy\ninterrupts fail to work correctly.\n\nDebugging revealed that the BIOS of these systems leaves the legacy PIC in\nuninitialized state which makes the PIC detection fail and the kernel\nswitches to a dummy implementation.\n\nUnfortunately this fallback causes quite some code to fail as it depends on\nchecks for the number of legacy PIC interrupts or the availability of the\nreal PIC.\n\nIn theory there is no reason to use the PIC on any modern system when\nIO/APIC is available, but the dependencies on the related checks cannot be\nresolved trivially and on short notice. This needs lots of analysis and\nrework.\n\nThe PIC detection has been added to avoid quirky checks and force selection\nof the dummy implementation all over the place, especially in VM guest\nscenarios. So it\u0027s not an option to revert the relevant commit as that\nwould break a lot of other scenarios.\n\nOne solution would be to try to initialize the PIC on detection fail and\nretry the detection, but that puts the burden on everything which does not\nhave a PIC.\n\nFortunately the ACPI/MADT table header has a flag field, which advertises\nin bit 0 that the system is PCAT compatible, which means it has a legacy\n8259 PIC.\n\nEvaluate that bit and if set avoid the detection routine and keep the real\nPIC installed, which then gets initialized (for nothing) and makes the rest\nof the code with all the dependencies work again.\n\nFixes: e179f6914152 (\"x86, irq, pic: Probe for legacy PIC and set legacy_pic appropriately\")\nReported-by: David Lazar \u003cdlazar@gmail.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nTested-by: David Lazar \u003cdlazar@gmail.com\u003e\nReviewed-by: Hans de Goede \u003chdegoede@redhat.com\u003e\nReviewed-by: Mario Limonciello \u003cmario.limonciello@amd.com\u003e\nCc: stable@vger.kernel.org\nCloses: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218003\nLink: https://lore.kernel.org/r/875y2u5s8g.ffs@tglx\n\n" }, { "commit": "b99d70c0d1380f1368fd4a82271280c4fd28558b", "tree": "df356b66bfad11b3834c7355803856e18d40d84d", "parents": [ "ce55c22ec8b223a90ff3e084d842f73cfba35588" ], "author": { "name": "Tony Luck", "email": "tony.luck@intel.com", "time": "Wed Oct 25 13:25:13 2023 -0700" }, "committer": { "name": "Dave Hansen", "email": "dave.hansen@linux.intel.com", "time": "Fri Oct 27 10:19:26 2023 -0700" }, "message": "x86/cpu: Add model number for Intel Arrow Lake mobile processor\n\nFor \"reasons\" Intel has code-named this CPU with a \"_H\" suffix.\n\n[ dhansen: As usual, apply this and send it upstream quickly to\n\t make it easier for anyone who is doing work that\n\t consumes this. ]\n\nSigned-off-by: Tony Luck \u003ctony.luck@intel.com\u003e\nSigned-off-by: Dave Hansen \u003cdave.hansen@linux.intel.com\u003e\nLink: https://lore.kernel.org/all/20231025202513.12358-1-tony.luck%40intel.com\n" }, { "commit": "888cf78c29e223fd808682f477c18cf8f61ad995", "tree": "92e6d5c2fbca4d389474dff130b4a8333057ce62", "parents": [ "09a4a03c073bab5b375b71769f708d6932b370f7", "6e6c6d6bc6c96c2477ddfea24a121eb5ee12b7a3" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 05:43:05 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 05:43:05 2023 -1000" }, "message": "Merge tag \u0027iommu-fix-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu\n\nPull iommu fix from Joerg Roedel:\n\n - Fix boot regression for Sapphire Rapids with Intel VT-d driver\n\n* tag \u0027iommu-fix-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:\n iommu: Avoid unnecessary cache invalidations\n" }, { "commit": "09a4a03c073bab5b375b71769f708d6932b370f7", "tree": "e1aa6039e61f3c0ac28b90409c6da0ad7b8ff505", "parents": [ "750b95887e567848ac2c851dae47922cac6db946", "47b8def9358c5eb888e78b24b7e5b7f2e2e97b8e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 05:40:42 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 27 05:40:42 2023 -1000" }, "message": "Merge tag \u0027powerpc-6.6-6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux\n\nPull powerpc fixes from Michael Ellerman:\n\n - Fix boot crash with FLATMEM since set_ptes() introduction\n\n - Avoid calling arch_enter/leave_lazy_mmu() in set_ptes()\n\nThanks to Aneesh Kumar K.V and Erhard Furtner.\n\n* tag \u0027powerpc-6.6-6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:\n powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes\n powerpc/mm: Fix boot crash with FLATMEM\n" }, { "commit": "3bde7ec13c971445faade32172cb0b4370b841d9", "tree": "a1976cb5e2d25a55cbe3c2b691fce3132669f9e1", "parents": [ "99c09c985e5973c8f0ad976ebae069548dd86f12" ], "author": { "name": "David Lazar", "email": "dlazar@gmail.com", "time": "Wed Oct 25 21:30:16 2023 +0200" }, "committer": { "name": "Hans de Goede", "email": "hdegoede@redhat.com", "time": "Fri Oct 27 16:42:12 2023 +0200" }, "message": "platform/x86: Add s2idle quirk for more Lenovo laptops\n\nWhen suspending to idle and resuming on some Lenovo laptops using the\nMendocino APU, multiple NVME IOMMU page faults occur, showing up in\ndmesg as repeated errors:\n\nnvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain\u003d0x000b\naddress\u003d0xb6674000 flags\u003d0x0000]\n\nThe system is unstable afterwards.\n\nApplying the s2idle quirk introduced by commit 455cd867b85b (\"platform/x86:\nthinkpad_acpi: Add a s2idle resume quirk for a number of laptops\")\nallows these systems to work with the IOMMU enabled and s2idle\nresume to work.\n\nCloses: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218024\nSuggested-by: Mario Limonciello \u003cmario.limonciello@amd.com\u003e\nSuggested-by: Mark Pearson \u003cmpearson-lenovo@squebb.ca\u003e\nSigned-off-by: David Lazar \u003cdlazar@gmail.com\u003e\nReviewed-by: Mario Limonciello \u003cmario.limonciello@amd.com\u003e\nReviewed-by: Mark Pearson \u003cmpearson-lenovo@squebb.ca\u003e\nLink: https://lore.kernel.org/r/ZTlsyOaFucF2pWrL@localhost\nSigned-off-by: Hans de Goede \u003chdegoede@redhat.com\u003e\n" }, { "commit": "e0f831836cead677fb07d54bd6bf499df35640c2", "tree": "706e3beef21b6040b57b48d9cc350bc52d790a1c", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1" ], "author": { "name": "Yujie Liu", "email": "yujie.liu@intel.com", "time": "Fri Oct 27 12:13:14 2023 +0800" }, "committer": { "name": "Masami Hiramatsu (Google)", "email": "mhiramat@kernel.org", "time": "Fri Oct 27 22:20:28 2023 +0900" }, "message": "tracing/kprobes: Fix the description of variable length arguments\n\nFix the following kernel-doc warnings:\n\nkernel/trace/trace_kprobe.c:1029: warning: Excess function parameter \u0027args\u0027 description in \u0027__kprobe_event_gen_cmd_start\u0027\nkernel/trace/trace_kprobe.c:1097: warning: Excess function parameter \u0027args\u0027 description in \u0027__kprobe_event_add_fields\u0027\n\nRefer to the usage of variable length arguments elsewhere in the kernel\ncode, \"@...\" is the proper way to express it in the description.\n\nLink: https://lore.kernel.org/all/20231027041315.2613166-1-yujie.liu@intel.com/\n\nFixes: 2a588dd1d5d6 (\"tracing: Add kprobe event command generation functions\")\nReported-by: kernel test robot \u003clkp@intel.com\u003e\nCloses: https://lore.kernel.org/oe-kbuild-all/202310190437.paI6LYJF-lkp@intel.com/\nSigned-off-by: Yujie Liu \u003cyujie.liu@intel.com\u003e\nReviewed-by: Mukesh Ojha \u003cquic_mojha@quicinc.com\u003e\nAcked-by: Masami Hiramatsu (Google) \u003cmhiramat@kernel.org\u003e\nSigned-off-by: Masami Hiramatsu (Google) \u003cmhiramat@kernel.org\u003e\n" }, { "commit": "6e6c6d6bc6c96c2477ddfea24a121eb5ee12b7a3", "tree": "d76aa2991d69cbdf9790df77862f2445b05194c1", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1" ], "author": { "name": "Lu Baolu", "email": "baolu.lu@linux.intel.com", "time": "Thu Oct 26 16:49:42 2023 +0800" }, "committer": { "name": "Joerg Roedel", "email": "jroedel@suse.de", "time": "Fri Oct 27 08:57:09 2023 +0200" }, "message": "iommu: Avoid unnecessary cache invalidations\n\nThe iommu_create_device_direct_mappings() only needs to flush the caches\nwhen the mappings are changed in the affected domain. This is not true\nfor non-DMA domains, or for devices attached to the domain that have no\nreserved regions. To avoid unnecessary cache invalidations, add a check\nbefore iommu_flush_iotlb_all().\n\nFixes: a48ce36e2786 (\"iommu: Prevent RESV_DIRECT devices from blocking domains\")\nSigned-off-by: Lu Baolu \u003cbaolu.lu@linux.intel.com\u003e\nTested-by: Henry Willard \u003chenry.willard@oracle.com\u003e\nLink: https://lore.kernel.org/r/20231026084942.17387-1-baolu.lu@linux.intel.com\nSigned-off-by: Joerg Roedel \u003cjroedel@suse.de\u003e\n" }, { "commit": "750b95887e567848ac2c851dae47922cac6db946", "tree": "d80457c086f9881b3f21cc746d37f395f95fd962", "parents": [ "3a568e3a961ba330091cd031647e4c303fa0badb", "44117828ed5c129a8146585e81262c0025daa50f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 20:42:02 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 20:42:02 2023 -1000" }, "message": "Merge tag \u0027drm-fixes-2023-10-27\u0027 of git://anongit.freedesktop.org/drm/drm\n\nPull drm fixes from Dave Airlie:\n \"This is the final set of fixes for 6.6, just misc bits mainly in\n amdgpu and i915, nothing too noteworthy.\n\n amdgpu:\n - ignore duplicated BOs in CS parser\n - remove redundant call to amdgpu_ctx_priority_is_valid()\n - Extend VI APSM quirks to more platforms\n\n amdkfd:\n - reserve fence slot while locking BO\n\n dp_mst:\n - Fix NULL deref in get_mst_branch_device_by_guid_helper()\n\n logicvc:\n - Kconfig: Select REGMAP and REGMAP_MMIO\n\n ivpu:\n - Fix missing VPUIP interrupts\n\n i915:\n - Determine context valid in OA reports\n - Hold GT forcewake during steering operations\n - Check if PMU is closed before stopping event\"\n\n* tag \u0027drm-fixes-2023-10-27\u0027 of git://anongit.freedesktop.org/drm/drm:\n accel/ivpu/37xx: Fix missing VPUIP interrupts\n drm/amd: Disable ASPM for VI w/ all Intel systems\n drm/i915/pmu: Check if pmu is closed before stopping event\n drm/i915/mcr: Hold GT forcewake during steering operations\n drm/logicvc: Kconfig: select REGMAP and REGMAP_MMIO\n drm/i915/perf: Determine context valid in OA reports\n drm/amdkfd: reserve a fence slot while locking the BO\n drm/amdgpu: Remove redundant call to priority_is_valid()\n drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()\n drm/amdgpu: ignore duplicate BOs again\n" }, { "commit": "44117828ed5c129a8146585e81262c0025daa50f", "tree": "f8930133d690404545300d087f1024cfef07b66b", "parents": [ "5679dd241bbf36492d8fcddb99af48b22a5f99ec", "64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 12:13:29 2023 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 12:17:26 2023 +1000" }, "message": "Merge tag \u0027amd-drm-fixes-6.6-2023-10-25\u0027 of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes\n\namd-drm-fixes-6.6-2023-10-25:\n\namdgpu:\n- Extend VI APSM quirks to more platforms\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Alex Deucher \u003calexander.deucher@amd.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231026035452.14921-1-alexander.deucher@amd.com\n" }, { "commit": "5679dd241bbf36492d8fcddb99af48b22a5f99ec", "tree": "c220a5dce3db722d590eb90e33cf5c2e618002d7", "parents": [ "6366ffa6edd832de870aaef184d5949a2e09c0c2", "4cbed7702eb775cca22fff6827a549092cb59f61" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 11:58:28 2023 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 11:59:11 2023 +1000" }, "message": "Merge tag \u0027drm-intel-fixes-2023-10-26\u0027 of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes\n\n- Determine context valid in OA reports (Umesh)\n- Hold GT forcewake during steering operations (Matt Roper)\n- Check if PMU is closed before stopping event (Umesh)\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Rodrigo Vivi \u003crodrigo.vivi@intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/ZTp8IQ0wxzxVjN7J@intel.com\n" }, { "commit": "6366ffa6edd832de870aaef184d5949a2e09c0c2", "tree": "222377c8ba7408bff82a74b124c18c67372fb21f", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1", "b132ac51d7a50c37683be56c96ff64f8c887930f" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 11:50:51 2023 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri Oct 27 11:51:35 2023 +1000" }, "message": "Merge tag \u0027drm-misc-fixes-2023-10-26\u0027 of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes\n\nShort summary of fixes pull:\n\namdgpu:\n- ignore duplicated BOs in CS parser\n- remove redundant call to amdgpu_ctx_priority_is_valid()\n\namdkfd:\n- reserve fence slot while locking BO\n\ndp_mst:\n- Fix NULL deref in get_mst_branch_device_by_guid_helper()\n\nlogicvc:\n- Kconfig: Select REGMAP and REGMAP_MMIO\n\nivpu:\n- Fix missing VPUIP interrupts\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Thomas Zimmermann \u003ctzimmermann@suse.de\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231026110132.GA10591@linux-uq9g.fritz.box\n" }, { "commit": "24eca2dce0f8d19db808c972b0281298d0bafe99", "tree": "eef0dbcf867b084687b949f42201fe80f3fcf7c0", "parents": [ "626b13f015e080e434b1dee9a0c116ddbf4fb695" ], "author": { "name": "Damien Le Moal", "email": "dlemoal@kernel.org", "time": "Wed Oct 25 15:46:12 2023 +0900" }, "committer": { "name": "Damien Le Moal", "email": "dlemoal@kernel.org", "time": "Fri Oct 27 10:00:19 2023 +0900" }, "message": "scsi: sd: Introduce manage_shutdown device flag\n\nCommit aa3998dbeb3a (\"ata: libata-scsi: Disable scsi device\nmanage_system_start_stop\") change setting the manage_system_start_stop\nflag to false for libata managed disks to enable libata internal\nmanagement of disk suspend/resume. However, a side effect of this change\nis that on system shutdown, disks are no longer being stopped (set to\nstandby mode with the heads unloaded). While this is not a critical\nissue, this unclean shutdown is not recommended and shows up with\nincreased smart counters (e.g. the unexpected power loss counter\n\"Unexpect_Power_Loss_Ct\").\n\nInstead of defining a shutdown driver method for all ATA adapter\ndrivers (not all of them define that operation), this patch resolves\nthis issue by further refining the sd driver start/stop control of disks\nusing the new flag manage_shutdown. If this new flag is set to true by\na low level driver, the function sd_shutdown() will issue a\nSTART STOP UNIT command with the start argument set to 0 when a disk\nneeds to be powered off (suspended) on system power off, that is, when\nsystem_state is equal to SYSTEM_POWER_OFF.\n\nSimilarly to the other manage_xxx flags, the new manage_shutdown flag is\nexposed through sysfs as a read-write device attribute.\n\nTo avoid any confusion between manage_shutdown and\nmanage_system_start_stop, the comments describing these flags in\ninclude/scsi/scsi.h are also improved.\n\nFixes: aa3998dbeb3a (\"ata: libata-scsi: Disable scsi device manage_system_start_stop\")\nCc: stable@vger.kernel.org\nCloses: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218038\nLink: https://lore.kernel.org/all/cd397c88-bf53-4768-9ab8-9d107df9e613@gmail.com/\nSigned-off-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nReviewed-by: Niklas Cassel \u003cniklas.cassel@wdc.com\u003e\nReviewed-by: Hannes Reinecke \u003chare@suse.de\u003e\nReviewed-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\nAcked-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\n" }, { "commit": "3a568e3a961ba330091cd031647e4c303fa0badb", "tree": "77be118beb7508eec87b6ac693a793bd4eb17bd0", "parents": [ "c17cda15cc86e65e9725641daddcd7a63cc9ad01", "736a4aad8a9fdcf577ffa33b33df240c67557af8" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 08:17:26 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 08:17:26 2023 -1000" }, "message": "Merge tag \u0027soc-fixes-6.7-3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc\n\nPull ARM SoC fixes from Arnd Bergmann:\n \"A couple of platforms have some last-minute fixes, in particular:\n\n - riscv gets some fixes for noncoherent DMA on the renesas and thead\n platforms and dts fix for SPI on the visionfive 2 board\n\n - Qualcomm Snapdragon gets three dts fixes to address board specific\n regressions on the pmic and gpio nodes\n\n - Rockchip platforms get multiple dts fixes to address issues on the\n recent rk3399 platform as well as the older rk3128 platform that\n apparently regressed a while ago.\n\n - TI OMAP gets some trivial code and dts fixes and a regression fix\n for the omap1 ams-delta modem\n\n - NXP i.MX firmware has one fix for a use-after-free but in its error\n handling\"\n\n* tag \u0027soc-fixes-6.7-3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (25 commits)\n soc: renesas: ARCH_R9A07G043 depends on !RISCV_ISA_ZICBOM\n riscv: only select DMA_DIRECT_REMAP from RISCV_ISA_ZICBOM and ERRATA_THEAD_PBMT\n riscv: RISCV_NONSTANDARD_CACHE_OPS shouldn\u0027t depend on RISCV_DMA_NONCOHERENT\n riscv: dts: thead: set dma-noncoherent to soc bus\n arm64: dts: rockchip: Fix i2s0 pin conflict on ROCK Pi 4 boards\n arm64: dts: rockchip: Add i2s0-2ch-bus-bclk-off pins to RK3399\n clk: ti: Fix missing omap5 mcbsp functional clock and aliases\n clk: ti: Fix missing omap4 mcbsp functional clock and aliases\n ARM: OMAP1: ams-delta: Fix MODEM initialization failure\n soc: renesas: Make ARCH_R9A07G043 depend on required options\n riscv: dts: starfive: visionfive 2: correct spi\u0027s ss pin\n firmware/imx-dsp: Fix use_after_free in imx_dsp_setup_channels()\n ARM: OMAP: timer32K: fix all kernel-doc warnings\n ARM: omap2: fix a debug printk\n ARM: dts: rockchip: Fix timer clocks for RK3128\n ARM: dts: rockchip: Add missing quirk for RK3128\u0027s dma engine\n ARM: dts: rockchip: Add missing arm timer interrupt for RK3128\n ARM: dts: rockchip: Fix i2c0 register address for RK3128\n arm64: dts: rockchip: set codec system-clock-fixed on px30-ringneck-haikou\n arm64: dts: rockchip: use codec as clock master on px30-ringneck-haikou\n ...\n" }, { "commit": "c17cda15cc86e65e9725641daddcd7a63cc9ad01", "tree": "53d24854635133eeea0cea4f6491c128f4f68ad9", "parents": [ "611da07b89fdd53f140d7b33013f255bf0ed8f34", "53798666648af3aa0dd512c2380576627237a800" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 07:41:27 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 26 07:41:27 2023 -1000" }, "message": "Merge tag \u0027net-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net\n\nPull networking fixes from Paolo Abeni:\n \"Including fixes from WiFi and netfilter.\n\n Most regressions addressed here come from quite old versions, with the\n exceptions of the iavf one and the WiFi fixes. No known outstanding\n reports or investigation.\n\n Fixes to fixes:\n\n - eth: iavf: in iavf_down, disable queues when removing the driver\n\n Previous releases - regressions:\n\n - sched: act_ct: additional checks for outdated flows\n\n - tcp: do not leave an empty skb in write queue\n\n - tcp: fix wrong RTO timeout when received SACK reneging\n\n - wifi: cfg80211: pass correct pointer to rdev_inform_bss()\n\n - eth: i40e: sync next_to_clean and next_to_process for programming\n status desc\n\n - eth: iavf: initialize waitqueues before starting watchdog_task\n\n Previous releases - always broken:\n\n - eth: r8169: fix data-races\n\n - eth: igb: fix potential memory leak in igb_add_ethtool_nfc_entry\n\n - eth: r8152: avoid writing garbage to the adapter\u0027s registers\n\n - eth: gtp: fix fragmentation needed check with gso\"\n\n* tag \u0027net-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (43 commits)\n iavf: in iavf_down, disable queues when removing the driver\n vsock/virtio: initialize the_virtio_vsock before using VQs\n net: ipv6: fix typo in comments\n net: ipv4: fix typo in comments\n net/sched: act_ct: additional checks for outdated flows\n netfilter: flowtable: GC pushes back packets to classic path\n i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR\n gtp: fix fragmentation needed check with gso\n gtp: uapi: fix GTPA_MAX\n Fix NULL pointer dereference in cn_filter()\n sfc: cleanup and reduce netlink error messages\n net/handshake: fix file ref count in handshake_nl_accept_doit()\n wifi: mac80211: don\u0027t drop all unprotected public action frames\n wifi: cfg80211: fix assoc response warning on failed links\n wifi: cfg80211: pass correct pointer to rdev_inform_bss()\n isdn: mISDN: hfcsusb: Spelling fix in comment\n tcp: fix wrong RTO timeout when received SACK reneging\n r8152: Block future register access if register access fails\n r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE\n r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()\n ...\n" }, { "commit": "736a4aad8a9fdcf577ffa33b33df240c67557af8", "tree": "f61fa27fa108b1582758235249cb1cf07b270ecb", "parents": [ "291c0d3a98afb7b863485215c241a851be9e3435", "9eab43facdadb7d00456c2657001ae2e5353c814" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Thu Oct 26 17:06:37 2023 +0200" }, "committer": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Thu Oct 26 17:06:42 2023 +0200" }, "message": "Merge tag \u0027renesas-fixes-for-v6.6-tag3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel into arm/fixes\n\nRenesas fixes for v6.6 (take three)\n\n - Sort out a few Kconfig dependency issues for the rich set of RISC-V\n non-coherent DMA support.\n\n* tag \u0027renesas-fixes-for-v6.6-tag3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel:\n soc: renesas: ARCH_R9A07G043 depends on !RISCV_ISA_ZICBOM\n riscv: only select DMA_DIRECT_REMAP from RISCV_ISA_ZICBOM and ERRATA_THEAD_PBMT\n riscv: RISCV_NONSTANDARD_CACHE_OPS shouldn\u0027t depend on RISCV_DMA_NONCOHERENT\n\nLink: https://lore.kernel.org/r/cover.1698312384.git.geert+renesas@glider.be\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\n" }, { "commit": "9eab43facdadb7d00456c2657001ae2e5353c814", "tree": "c53b61637e1ca893d6582a13f4037fef4fc1a9ed", "parents": [ "381cae1698538ad2f90dd6ecd8ed155d194e072f" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed Oct 18 07:26:54 2023 +0200" }, "committer": { "name": "Geert Uytterhoeven", "email": "geert+renesas@glider.be", "time": "Thu Oct 26 09:42:38 2023 +0200" }, "message": "soc: renesas: ARCH_R9A07G043 depends on !RISCV_ISA_ZICBOM\n\nARCH_R9A07G043 has its own non-standard global pool based DMA coherent\nallocator, which conflicts with the remap based RISCV_ISA_ZICBOM version.\nAdd a proper dependency.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Lad Prabhakar \u003cprabhakar.mahadev-lad.rj@bp.renesas.com\u003e\nAcked-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nAcked-by: Geert Uytterhoeven \u003cgeert+renesas@glider.be\u003e\nLink: https://lore.kernel.org/r/20231018052654.50074-4-hch@lst.de\nSigned-off-by: Geert Uytterhoeven \u003cgeert+renesas@glider.be\u003e\n" }, { "commit": "381cae1698538ad2f90dd6ecd8ed155d194e072f", "tree": "c8470052d91aaf2bf1304c7eebe6b17f687a8541", "parents": [ "fd962781270e6452dd5b30c8aa0b3b0fbee06244" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed Oct 18 07:26:53 2023 +0200" }, "committer": { "name": "Geert Uytterhoeven", "email": "geert+renesas@glider.be", "time": "Thu Oct 26 09:42:38 2023 +0200" }, "message": "riscv: only select DMA_DIRECT_REMAP from RISCV_ISA_ZICBOM and ERRATA_THEAD_PBMT\n\nRISCV_DMA_NONCOHERENT is also used for whacky non-standard\nnon-coherent ops that use different hooks in dma-direct.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nReviewed-by: Robin Murphy \u003crobin.murphy@arm.com\u003e\nReviewed-by: Lad Prabhakar \u003cprabhakar.mahadev-lad.rj@bp.renesas.com\u003e\nTested-by: Samuel Holland \u003csamuel.holland@sifive.com\u003e\nLink: https://lore.kernel.org/r/20231018052654.50074-3-hch@lst.de\nSigned-off-by: Geert Uytterhoeven \u003cgeert+renesas@glider.be\u003e\n" }, { "commit": "fd962781270e6452dd5b30c8aa0b3b0fbee06244", "tree": "5350164b36f1dd1ae931ba57706462274e70aa48", "parents": [ "1531309aa2092a96c092fa662863ffa53da3ba93" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed Oct 18 07:26:52 2023 +0200" }, "committer": { "name": "Geert Uytterhoeven", "email": "geert+renesas@glider.be", "time": "Thu Oct 26 09:42:37 2023 +0200" }, "message": "riscv: RISCV_NONSTANDARD_CACHE_OPS shouldn\u0027t depend on RISCV_DMA_NONCOHERENT\n\nRISCV_NONSTANDARD_CACHE_OPS is also used for the pmem cache maintenance\nhelpers, which are built into the kernel unconditionally.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nAcked-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nLink: https://lore.kernel.org/r/20231018052654.50074-2-hch@lst.de\nSigned-off-by: Geert Uytterhoeven \u003cgeert+renesas@glider.be\u003e\n" }, { "commit": "b132ac51d7a50c37683be56c96ff64f8c887930f", "tree": "e45197b53c5f75f596bc2444f0fb5b9995b9eeee", "parents": [ "4e6c38c38723a954b85aa9ee62603bb4a37acbb4" ], "author": { "name": "Karol Wachowski", "email": "karol.wachowski@linux.intel.com", "time": "Tue Oct 24 18:19:52 2023 +0200" }, "committer": { "name": "Stanislaw Gruszka", "email": "stanislaw.gruszka@linux.intel.com", "time": "Thu Oct 26 07:43:28 2023 +0200" }, "message": "accel/ivpu/37xx: Fix missing VPUIP interrupts\n\nMove sequence of masking and unmasking global interrupts from buttress\ninterrupt handler to generic one that handles both VPUIP and BTRS\ninterrupts. Unmasking global interrupts will re-trigger MSI for any\npending interrupts.\n\nLack of this sequence will cause the driver to miss any\nVPUIP interrupt that comes after reading VPU_37XX_HOST_SS_ICB_STATUS_0\nand before clearing all active interrupt sources.\n\nFixes: 35b137630f08 (\"accel/ivpu: Introduce a new DRM driver for Intel VPU\")\nCc: stable@vger.kernel.org\nSigned-off-by: Karol Wachowski \u003ckarol.wachowski@linux.intel.com\u003e\nReviewed-by: Stanislaw Gruszka \u003cstanislaw.gruszka@linux.intel.com\u003e\nSigned-off-by: Stanislaw Gruszka \u003cstanislaw.gruszka@linux.intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231024161952.759914-1-stanislaw.gruszka@linux.intel.com\n" }, { "commit": "53798666648af3aa0dd512c2380576627237a800", "tree": "c5c59dbfe51bd8e25819718293eb68584e29e902", "parents": [ "5e5d8b94a4fa5fc4a4ea5c97393a29aa5bf3e4bb" ], "author": { "name": "Michal Schmidt", "email": "mschmidt@redhat.com", "time": "Wed Oct 25 11:32:13 2023 -0700" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Wed Oct 25 17:48:31 2023 -0700" }, "message": "iavf: in iavf_down, disable queues when removing the driver\n\nIn iavf_down, we\u0027re skipping the scheduling of certain operations if\nthe driver is being removed. However, the IAVF_FLAG_AQ_DISABLE_QUEUES\nrequest must not be skipped in this case, because iavf_close waits\nfor the transition to the __IAVF_DOWN state, which happens in\niavf_virtchnl_completion after the queues are released.\n\nWithout this fix, \"rmmod iavf\" takes half a second per interface that\u0027s\nup and prints the \"Device resources not yet released\" warning.\n\nFixes: c8de44b577eb (\"iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set\")\nSigned-off-by: Michal Schmidt \u003cmschmidt@redhat.com\u003e\nReviewed-by: Wojciech Drewek \u003cwojciech.drewek@intel.com\u003e\nTested-by: Rafal Romanowski \u003crafal.romanowski@intel.com\u003e\nTested-by: Jacob Keller \u003cjacob.e.keller@intel.com\u003e\nSigned-off-by: Jacob Keller \u003cjacob.e.keller@intel.com\u003e\nLink: https://lore.kernel.org/r/20231025183213.874283-1-jacob.e.keller@intel.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "5e5d8b94a4fa5fc4a4ea5c97393a29aa5bf3e4bb", "tree": "becedd8e088d898ce9ed3682a6ef37a6984d0228", "parents": [ "53b08c4985158430fd6d035fb49443bada535210", "a63b6622120cd03a304796dbccb80655b3a21798" ], "author": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Wed Oct 25 16:02:06 2023 -0700" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Wed Oct 25 16:02:06 2023 -0700" }, "message": "Merge tag \u0027nf-23-10-25\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf\n\nPablo Neira Ayuso says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nNetfilter fixes for net\n\nThis patch contains two late Netfilter\u0027s flowtable fixes for net:\n\n1) Flowtable GC pushes back packets to classic path in every GC run,\n ie. every second. This is because NF_FLOW_HW_ESTABLISHED is only\n used by sched/act_ct (never set) and IPS_SEEN_REPLY might be unset\n by the time the flow is offloaded (this status bit is only reliable\n in the sched/act_ct datapath).\n\n2) sched/act_ct logic to push back packets to classic path to reevaluate\n if UDP flow is unidirectional only applies if IPS_HW_OFFLOAD_BIT is\n set on and no hardware offload request is pending to be handled.\n From Vlad Buslov.\n\nThese two patches fixes two problems that were introduced in the\nprevious 6.5 development cycle.\n\n* tag \u0027nf-23-10-25\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf:\n net/sched: act_ct: additional checks for outdated flows\n netfilter: flowtable: GC pushes back packets to classic path\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://lore.kernel.org/r/20231025100819.2664-1-pablo@netfilter.org\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "53b08c4985158430fd6d035fb49443bada535210", "tree": "1332eda9a284020639cdbe00b75d99bc5bb774bc", "parents": [ "1711435e3e67e079d6a2bce54d96d1af21c7ef2c" ], "author": { "name": "Alexandru Matei", "email": "alexandru.matei@uipath.com", "time": "Tue Oct 24 22:17:42 2023 +0300" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Wed Oct 25 15:49:47 2023 -0700" }, "message": "vsock/virtio: initialize the_virtio_vsock before using VQs\n\nOnce VQs are filled with empty buffers and we kick the host, it can send\nconnection requests. If the_virtio_vsock is not initialized before,\nreplies are silently dropped and do not reach the host.\n\nvirtio_transport_send_pkt() can queue packets once the_virtio_vsock is\nset, but they won\u0027t be processed until vsock-\u003etx_run is set to true. We\nqueue vsock-\u003esend_pkt_work when initialization finishes to send those\npackets queued earlier.\n\nFixes: 0deab087b16a (\"vsock/virtio: use RCU to avoid use-after-free on the_virtio_vsock\")\nSigned-off-by: Alexandru Matei \u003calexandru.matei@uipath.com\u003e\nReviewed-by: Stefano Garzarella \u003csgarzare@redhat.com\u003e\nLink: https://lore.kernel.org/r/20231024191742.14259-1-alexandru.matei@uipath.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "f199bf5bf84c19a4f488a39d7d694ab10787de35", "tree": "95132b48f6a2f2f9984eeb1c8b68afac1f6bd7a3", "parents": [ "4dc5af1fee55e38b5016e45b66bec1e1312973f5" ], "author": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Oct 24 15:34:31 2023 +0100" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Oct 25 21:44:49 2023 +0200" }, "message": "irqchip/gic-v3-its: Don\u0027t override quirk settings with default values\n\nWhen splitting the allocation of the ITS node from its configuration,\nsome of the default settings were kept in the latter instead of\nbeing moved to the former.\n\nThis has the side effect of negating some of the quirk detections that\nhave happened in between, amongst which the dreaded Synquacer hack\n(that also affect Dominic\u0027s TI platform).\n\nMove the initialisation of these fields early, so that they can again be\noverriden by the Synquacer quirk.\n\nFixes: 9585a495ac93 (\"irqchip/gic-v3-its: Split allocation from initialisation of its_node\")\nReported by: Dominic Rath \u003cdominic.rath@ibv-augsburg.net\u003e\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nTested-by: Dominic Rath \u003cdominic.rath@ibv-augsburg.net\u003e\nLink: https://lore.kernel.org/r/20231024084831.GA3788@JADEVM-DRA\nLink: https://lore.kernel.org/r/20231024143431.2144579-1-maz@kernel.org\n\n" }, { "commit": "611da07b89fdd53f140d7b33013f255bf0ed8f34", "tree": "4c991cfc807b37191e634842789be44f4a14c250", "parents": [ "4f82870119a46b0d04d91ef4697ac4977a255a9d", "9b311b7313d6c104dd4a2d43ab54536dce07f960" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Oct 25 07:51:56 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Oct 25 07:51:56 2023 -1000" }, "message": "Merge tag \u0027acpi-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm\n\nPull ACPI fix from Rafael Wysocki:\n \"Unbreak the ACPI NFIT driver after a recent change that inadvertently\n altered its behavior (Xiang Chen)\"\n\n* tag \u0027acpi-6.6-rc8\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:\n ACPI: NFIT: Install Notify() handler before getting NFIT table\n" }, { "commit": "d5090484b021794271280ab64d20253883b7f6fd", "tree": "972e92c18aa040f2fd8040f22229fe07e2b25e74", "parents": [ "4f82870119a46b0d04d91ef4697ac4977a255a9d" ], "author": { "name": "Petr Tesarik", "email": "petr.tesarik1@huawei-partners.com", "time": "Wed Oct 25 10:44:25 2023 +0200" }, "committer": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed Oct 25 16:26:20 2023 +0200" }, "message": "swiotlb: do not try to allocate a TLB bigger than MAX_ORDER pages\n\nWhen allocating a new pool at runtime, reduce the number of slabs so\nthat the allocation order is at most MAX_ORDER. This avoids a kernel\nwarning in __alloc_pages().\n\nThe warning is relatively benign, because the pool size is subsequently\nreduced when allocation fails, but it is silly to start with a request\nthat is known to fail, especially since this is the default behavior if\nthe kernel is built with CONFIG_SWIOTLB_DYNAMIC\u003dy and booted without any\nswiotlb\u003d parameter.\n\nReported-by: Ben Greear \u003cgreearb@candelatech.com\u003e\nCloses: https://lore.kernel.org/netdev/4f173dd2-324a-0240-ff8d-abf5c191be18@candelatech.com/\nFixes: 1aaa736815eb (\"swiotlb: allocate a new memory pool when existing pools are full\")\nSigned-off-by: Petr Tesarik \u003cpetr.tesarik1@huawei-partners.com\u003e\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\n" }, { "commit": "838b35bb6a89c36da07ca39520ec071d9250334d", "tree": "598273089e020a7108b9957be3d277d96f09df0a", "parents": [ "7644b1a1c9a7ae8ab99175989bfc8676055edb46" ], "author": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Tue Oct 24 14:39:06 2023 -0600" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Wed Oct 25 08:02:29 2023 -0600" }, "message": "io_uring/rw: disable IOCB_DIO_CALLER_COMP\n\nIf an application does O_DIRECT writes with io_uring and the file system\nsupports IOCB_DIO_CALLER_COMP, then completions of the dio write side is\ndone from the task_work that will post the completion event for said\nwrite as well.\n\nWhenever a dio write is done against a file, the inode i_dio_count is\nelevated. This enables other callers to use inode_dio_wait() to wait for\nprevious writes to complete. If we defer the full dio completion to\ntask_work, we are dependent on that task_work being run before the\ninode i_dio_count can be decremented.\n\nIf the same task that issues io_uring dio writes with\nIOCB_DIO_CALLER_COMP performs a synchronous system call that calls\ninode_dio_wait(), then we can deadlock as we\u0027re blocked sleeping on\nthe event to become true, but not processing the completions that will\nresult in the inode i_dio_count being decremented.\n\nUntil we can guarantee that this is the case, then disable the deferred\ncaller completions.\n\nFixes: 099ada2c8726 (\"io_uring/rw: add write support for IOCB_DIO_CALLER_COMP\")\nReported-by: Andres Freund \u003candres@anarazel.de\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f", "tree": "ab70b5fb212920a16559a3085b9adff5800b0f2e", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1" ], "author": { "name": "Mario Limonciello", "email": "mario.limonciello@amd.com", "time": "Fri Oct 20 10:26:29 2023 -0500" }, "committer": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Wed Oct 25 09:53:17 2023 -0400" }, "message": "drm/amd: Disable ASPM for VI w/ all Intel systems\n\nOriginally we were quirking ASPM disabled specifically for VI when\nused with Alder Lake, but it appears to have problems with Rocket\nLake as well.\n\nLike we\u0027ve done in the case of dpm for newer platforms, disable\nASPM for all Intel systems.\n\nCc: stable@vger.kernel.org # 5.15+\nFixes: 0064b0ce85bb (\"drm/amd/pm: enable ASPM by default\")\nReported-and-tested-by: Paolo Gentili \u003cpaolo.gentili@canonical.com\u003e\nCloses: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742\nSigned-off-by: Mario Limonciello \u003cmario.limonciello@amd.com\u003e\nReviewed-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\n" }, { "commit": "7644b1a1c9a7ae8ab99175989bfc8676055edb46", "tree": "dfa13e49521a00400a40c955f9f927a2e41c9af4", "parents": [ "8b51a3956d44ea6ade962874ade14de9a7d16556" ], "author": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Sat Oct 21 12:30:29 2023 -0600" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Wed Oct 25 07:44:14 2023 -0600" }, "message": "io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid\n\nWe could race with SQ thread exit, and if we do, we\u0027ll hit a NULL pointer\ndereference when the thread is cleared. Grab the SQPOLL data lock before\nattempting to get the task cpu and pid for fdinfo, this ensures we have a\nstable view of it.\n\nCc: stable@vger.kernel.org\nLink: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218032\nReviewed-by: Gabriel Krisman Bertazi \u003ckrisman@suse.de\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "4cbed7702eb775cca22fff6827a549092cb59f61", "tree": "6eeb445b7401b6ff1479163eb5d44d68b8f38ed6", "parents": [ "78cc55e0b64c820673a796635daf82c7eadfe152" ], "author": { "name": "Umesh Nerlige Ramappa", "email": "umesh.nerlige.ramappa@intel.com", "time": "Fri Oct 20 08:24:41 2023 -0700" }, "committer": { "name": "Rodrigo Vivi", "email": "rodrigo.vivi@intel.com", "time": "Wed Oct 25 08:44:30 2023 -0400" }, "message": "drm/i915/pmu: Check if pmu is closed before stopping event\n\nWhen the driver unbinds, pmu is unregistered and i915-\u003euabi_engines is\nset to RB_ROOT. Due to this, when i915 PMU tries to stop the engine\nevents, it issues a warn_on because engine lookup fails.\n\nAll perf hooks are taking care of this using a pmu-\u003eclosed flag that is\nset when PMU unregisters. The stop event seems to have been left out.\n\nCheck for pmu-\u003eclosed in pmu_event_stop as well.\n\nBased on discussion here -\nhttps://patchwork.freedesktop.org/patch/492079/?series\u003d105790\u0026rev\u003d2\n\nv2: s/is/if/ in commit title\nv3: Add fixes tag and cc stable\n\nCc: \u003cstable@vger.kernel.org\u003e # v5.11+\nFixes: b00bccb3f0bb (\"drm/i915/pmu: Handle PCI unbind\")\nSigned-off-by: Umesh Nerlige Ramappa \u003cumesh.nerlige.ramappa@intel.com\u003e\nReviewed-by: Tvrtko Ursulin \u003ctvrtko.ursulin@intel.com\u003e\nReviewed-by: Andi Shyti \u003candi.shyti@linux.intel.com\u003e\nSigned-off-by: Andi Shyti \u003candi.shyti@linux.intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231020152441.3764850-1-umesh.nerlige.ramappa@intel.com\n(cherry picked from commit 31f6a06f0c543b43a38fab10f39e5fc45ad62aa2)\nSigned-off-by: Rodrigo Vivi \u003crodrigo.vivi@intel.com\u003e\n" }, { "commit": "78cc55e0b64c820673a796635daf82c7eadfe152", "tree": "4d33f98fd42c61959b4280985895d8d6857a118d", "parents": [ "cba94bbcff08d209710dd7bdc139caad675a6f8d" ], "author": { "name": "Matt Roper", "email": "matthew.d.roper@intel.com", "time": "Thu Oct 19 10:02:42 2023 -0700" }, "committer": { "name": "Rodrigo Vivi", "email": "rodrigo.vivi@intel.com", "time": "Wed Oct 25 08:44:26 2023 -0400" }, "message": "drm/i915/mcr: Hold GT forcewake during steering operations\n\nThe steering control and semaphore registers are inside an \"always on\"\npower domain with respect to RC6. However there are some issues if\nhigher-level platform sleep states are entering/exiting at the same time\nthese registers are accessed. Grabbing GT forcewake and holding it over\nthe entire lock/steer/unlock cycle ensures that those sleep states have\nbeen fully exited before we access these registers.\n\nThis is expected to become a formally documented/numbered workaround\nsoon.\n\nNote that this patch alone isn\u0027t expected to have an immediately\nnoticeable impact on MCR (mis)behavior; an upcoming pcode firmware\nupdate will also be necessary to provide the other half of this\nworkaround.\n\nv2:\n - Move the forcewake inside the Xe_LPG-specific IP version check. This\n should only be necessary on platforms that have a steering semaphore.\n\nFixes: 3100240bf846 (\"drm/i915/mtl: Add hardware-level lock for steering\")\nCc: Radhakrishna Sripada \u003cradhakrishna.sripada@intel.com\u003e\nCc: Jonathan Cavitt \u003cjonathan.cavitt@intel.com\u003e\nSigned-off-by: Matt Roper \u003cmatthew.d.roper@intel.com\u003e\nReviewed-by: Radhakrishna Sripada \u003cradhakrishna.sripada@intel.com\u003e\nReviewed-by: Jonathan Cavitt \u003cjonathan.cavitt@intel.com\u003e\nReviewed-by: Andi Shyti \u003candi.shyti@linux.intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231019170241.2102037-2-matthew.d.roper@intel.com\n(cherry picked from commit 8fa1c7cd1fe9cdfc426a603e1f1eecd3f463c487)\nSigned-off-by: Rodrigo Vivi \u003crodrigo.vivi@intel.com\u003e\n" }, { "commit": "4e6c38c38723a954b85aa9ee62603bb4a37acbb4", "tree": "947e6b37e03c6dcb8d2c064b668b1cd1ca33d36d", "parents": [ "4984fc578a911f3146965f4086d0a219a9806002" ], "author": { "name": "Sui Jingfeng", "email": "suijingfeng@loongson.cn", "time": "Thu Jun 08 10:42:07 2023 +0800" }, "committer": { "name": "Paul Kocialkowski", "email": "paul.kocialkowski@bootlin.com", "time": "Wed Oct 25 12:05:25 2023 +0200" }, "message": "drm/logicvc: Kconfig: select REGMAP and REGMAP_MMIO\n\ndrm/logicvc driver is depend on REGMAP and REGMAP_MMIO, should select this\ntwo kconfig option, otherwise the driver failed to compile on platform\nwithout REGMAP_MMIO selected:\n\nERROR: modpost: \"__devm_regmap_init_mmio_clk\" [drivers/gpu/drm/logicvc/logicvc-drm.ko] undefined!\nmake[1]: *** [scripts/Makefile.modpost:136: Module.symvers] Error 1\nmake: *** [Makefile:1978: modpost] Error 2\n\nSigned-off-by: Sui Jingfeng \u003csuijingfeng@loongson.cn\u003e\nAcked-by: Paul Kocialkowski \u003cpaul.kocialkowski@bootlin.com\u003e\nFixes: efeeaefe9be5 (\"drm: Add support for the LogiCVC display controller\")\nLink: https://patchwork.freedesktop.org/patch/msgid/20230608024207.581401-1-suijingfeng@loongson.cn\nSigned-off-by: Paul Kocialkowski \u003cpaul.kocialkowski@bootlin.com\u003e\n" }, { "commit": "1711435e3e67e079d6a2bce54d96d1af21c7ef2c", "tree": "8946950057cb88fc294998a742cc7ea02011c025", "parents": [ "197f9fba9663e765f8f3ae3b2375c6cc32b2e2b3" ], "author": { "name": "Deming Wang", "email": "wangdeming@inspur.com", "time": "Wed Oct 25 02:16:56 2023 -0400" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Oct 25 10:38:07 2023 +0100" }, "message": "net: ipv6: fix typo in comments\n\nThe word \"advertize\" should be replaced by \"advertise\".\n\nSigned-off-by: Deming Wang \u003cwangdeming@inspur.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "197f9fba9663e765f8f3ae3b2375c6cc32b2e2b3", "tree": "4f9de02ce87512fd0f5b99ddf405145a557b48f2", "parents": [ "77a8c982ff0d4c3a14022c6fe9e3dbfb327552ec" ], "author": { "name": "Deming Wang", "email": "wangdeming@inspur.com", "time": "Wed Oct 25 02:14:34 2023 -0400" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Oct 25 10:38:07 2023 +0100" }, "message": "net: ipv4: fix typo in comments\n\nThe word \"advertize\" should be replaced by \"advertise\".\n\nSigned-off-by: Deming Wang \u003cwangdeming@inspur.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "a63b6622120cd03a304796dbccb80655b3a21798", "tree": "bb5e9f5c3e235ddeb6afaf6ab9672ba609a9ca3f", "parents": [ "735795f68b37e9bb49f642407a0d49b1631ea1c7" ], "author": { "name": "Vlad Buslov", "email": "vladbu@nvidia.com", "time": "Tue Oct 24 21:58:57 2023 +0200" }, "committer": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Wed Oct 25 11:35:57 2023 +0200" }, "message": "net/sched: act_ct: additional checks for outdated flows\n\nCurrent nf_flow_is_outdated() implementation considers any flow table flow\nwhich state diverged from its underlying CT connection status for teardown\nwhich can be problematic in the following cases:\n\n- Flow has never been offloaded to hardware in the first place either\nbecause flow table has hardware offload disabled (flag\nNF_FLOWTABLE_HW_OFFLOAD is not set) or because it is still pending on \u0027add\u0027\nworkqueue to be offloaded for the first time. The former is incorrect, the\nlater generates excessive deletions and additions of flows.\n\n- Flow is already pending to be updated on the workqueue. Tearing down such\nflows will also generate excessive removals from the flow table, especially\non highly loaded system where the latency to re-offload a flow via \u0027add\u0027\nworkqueue can be quite high.\n\nWhen considering a flow for teardown as outdated verify that it is both\noffloaded to hardware and doesn\u0027t have any pending updates.\n\nFixes: 41f2c7c342d3 (\"net/sched: act_ct: Fix promotion of offloaded unreplied tuple\")\nReviewed-by: Paul Blakey \u003cpaulb@nvidia.com\u003e\nSigned-off-by: Vlad Buslov \u003cvladbu@nvidia.com\u003e\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\n" }, { "commit": "735795f68b37e9bb49f642407a0d49b1631ea1c7", "tree": "db5d84ee8206b6df761114f647a233c6b091979d", "parents": [ "d2a0fc372aca561556e765d0a9ec365c7c12f0ad" ], "author": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Tue Oct 24 21:09:47 2023 +0200" }, "committer": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Wed Oct 25 11:35:46 2023 +0200" }, "message": "netfilter: flowtable: GC pushes back packets to classic path\n\nSince 41f2c7c342d3 (\"net/sched: act_ct: Fix promotion of offloaded\nunreplied tuple\"), flowtable GC pushes back flows with IPS_SEEN_REPLY\nback to classic path in every run, ie. every second. This is because of\na new check for NF_FLOW_HW_ESTABLISHED which is specific of sched/act_ct.\n\nIn Netfilter\u0027s flowtable case, NF_FLOW_HW_ESTABLISHED never gets set on\nand IPS_SEEN_REPLY is unreliable since users decide when to offload the\nflow before, such bit might be set on at a later stage.\n\nFix it by adding a custom .gc handler that sched/act_ct can use to\ndeal with its NF_FLOW_HW_ESTABLISHED bit.\n\nFixes: 41f2c7c342d3 (\"net/sched: act_ct: Fix promotion of offloaded unreplied tuple\")\nReported-by: Vladimir Smelhaus \u003cvl.sm@email.cz\u003e\nReviewed-by: Paul Blakey \u003cpaulb@nvidia.com\u003e\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\n" }, { "commit": "47b8def9358c5eb888e78b24b7e5b7f2e2e97b8e", "tree": "0ab1a42009f9080e9c9f72f9a4e60273f3057657", "parents": [ "daa9ada2093ed23d52b4c1fe6e13cf78f55cc85f" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.ibm.com", "time": "Tue Oct 24 20:06:04 2023 +0530" }, "committer": { "name": "Michael Ellerman", "email": "mpe@ellerman.id.au", "time": "Wed Oct 25 16:08:46 2023 +1100" }, "message": "powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes\n\nWith commit 9fee28baa601 (\"powerpc: implement the new page table range\nAPI\") we added set_ptes to powerpc architecture. The implementation\nincluded calling arch_enter/leave_lazy_mmu() calls.\n\nThe patch removes the usage of arch_enter/leave_lazy_mmu() because\nset_pte is not supposed to be used when updating a pte entry. Powerpc\narchitecture uses this rule to skip the expensive tlb invalidate which\nis not needed when you are setting up the pte for the first time. See\ncommit 56eecdb912b5 (\"mm: Use ptep/pmdp_set_numa() for updating\n_PAGE_NUMA bit\") for more details\n\nThe patch also makes sure we are not using the interface to update a\nvalid/present pte entry by adding VM_WARN_ON check all the ptes we\nare setting up. Furthermore, we add a comment to set_pte_filter to\nclarify it can only update folio-related flags and cannot filter\npfn specific details in pte filtering.\n\nRemoval of arch_enter/leave_lazy_mmu() also will avoid nesting of\nthese functions that are not supported. For ex:\n\nremap_pte_range()\n -\u003e arch_enter_lazy_mmu()\n -\u003e set_ptes()\n -\u003e arch_enter_lazy_mmu()\n -\u003e arch_leave_lazy_mmu()\n -\u003e arch_leave_lazy_mmu()\n\nFixes: 9fee28baa601 (\"powerpc: implement the new page table range API\")\nSigned-off-by: \"Aneesh Kumar K.V\" \u003caneesh.kumar@linux.ibm.com\u003e\nSigned-off-by: Michael Ellerman \u003cmpe@ellerman.id.au\u003e\nLink: https://msgid.link/20231024143604.16749-1-aneesh.kumar@linux.ibm.com\n\n" }, { "commit": "77a8c982ff0d4c3a14022c6fe9e3dbfb327552ec", "tree": "91397770bcb37a1a0f8b91460e73141cf103b4f2", "parents": [ "00d67093e4f1874f713e5869dbcf34a00665dbb7" ], "author": { "name": "Ivan Vecera", "email": "ivecera@redhat.com", "time": "Mon Oct 23 14:27:14 2023 -0700" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Tue Oct 24 17:03:29 2023 -0700" }, "message": "i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR\n\nThe I40E_TXR_FLAGS_WB_ON_ITR is i40e_ring flag and not i40e_pf one.\n\nFixes: 8e0764b4d6be42 (\"i40e/i40evf: Add support for writeback on ITR feature for X722\")\nSigned-off-by: Ivan Vecera \u003civecera@redhat.com\u003e\nTested-by: Pucha Himasekhar Reddy \u003chimasekharx.reddy.pucha@intel.com\u003e (A Contingent worker at Intel)\nSigned-off-by: Jacob Keller \u003cjacob.e.keller@intel.com\u003e\nLink: https://lore.kernel.org/r/20231023212714.178032-1-jacob.e.keller@intel.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "00d67093e4f1874f713e5869dbcf34a00665dbb7", "tree": "702197f65be7b4a8a46d14829811d482f3ff2417", "parents": [ "cd8892c07876da0c4b50e020048a32a28596a074", "91535613b6090fc968c601d11d4e2f16b333713c" ], "author": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Tue Oct 24 13:10:53 2023 -0700" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Tue Oct 24 13:10:53 2023 -0700" }, "message": "Merge tag \u0027wireless-2023-10-24\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless\n\nJohannes Berg says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nThree more fixes:\n - don\u0027t drop all unprotected public action frames since\n some don\u0027t have a protected dual\n - fix pointer confusion in scanning code\n - fix warning in some connections with multiple links\n\n* tag \u0027wireless-2023-10-24\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless:\n wifi: mac80211: don\u0027t drop all unprotected public action frames\n wifi: cfg80211: fix assoc response warning on failed links\n wifi: cfg80211: pass correct pointer to rdev_inform_bss()\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://lore.kernel.org/r/20231024103540.19198-2-johannes@sipsolutions.net\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "4f82870119a46b0d04d91ef4697ac4977a255a9d", "tree": "55ef387f70ff7986d98f2fe3b2411730099c92ea", "parents": [ "d88520ad73b79e71e3ddf08de335b8520ae41c5c", "099d7439ce03d0e7bc8f0c3d7878b562f3a48d3d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Oct 24 09:52:16 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Oct 24 09:52:16 2023 -1000" }, "message": "Merge tag \u0027mm-hotfixes-stable-2023-10-24-09-40\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm\n\nPull misc fixes from Andrew Morton:\n \"20 hotfixes. 12 are cc:stable and the remainder address post-6.5\n issues or aren\u0027t considered necessary for earlier kernel versions\"\n\n* tag \u0027mm-hotfixes-stable-2023-10-24-09-40\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm:\n maple_tree: add GFP_KERNEL to allocations in mas_expected_entries()\n selftests/mm: include mman header to access MREMAP_DONTUNMAP identifier\n mailmap: correct email aliasing for Oleksij Rempel\n mailmap: map Bartosz\u0027s old address to the current one\n mm/damon/sysfs: check DAMOS regions update progress from before_terminate()\n MAINTAINERS: Ondrej has moved\n kasan: disable kasan_non_canonical_hook() for HW tags\n kasan: print the original fault addr when access invalid shadow\n hugetlbfs: close race between MADV_DONTNEED and page fault\n hugetlbfs: extend hugetlb_vma_lock to private VMAs\n hugetlbfs: clear resv_map pointer if mmap fails\n mm: zswap: fix pool refcount bug around shrink_worker()\n mm/migrate: fix do_pages_move for compat pointers\n riscv: fix set_huge_pte_at() for NAPOT mappings when a swap entry is set\n riscv: handle VM_FAULT_[HWPOISON|HWPOISON_LARGE] faults instead of panicking\n mmap: fix error paths with dup_anon_vma()\n mmap: fix vma_iterator in error path of vma_merge()\n mm: fix vm_brk_flags() to not bail out while holding lock\n mm/mempolicy: fix set_mempolicy_home_node() previous VMA pointer\n mm/page_alloc: correct start page when guard page debug is enabled\n" }, { "commit": "28926daf731f72d0537767fdbab2a3e06e31190a", "tree": "2721fe7bc6787fcf7bf68c1cdc211df31ae58b1c", "parents": [ "1e55c5200dc7efeb84d4582a82d289329255fd82" ], "author": { "name": "Jinjie Ruan", "email": "ruanjinjie@huawei.com", "time": "Mon Oct 23 11:28:57 2023 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 24 19:32:39 2023 +0200" }, "message": "fpga: Fix memory leak for fpga_region_test_class_find()\n\nfpga_region_class_find() in fpga_region_test_class_find() will call\nget_device() if the data is matched, which will increment refcount for\ndev-\u003ekobj, so it should call put_device() to decrement refcount for\ndev-\u003ekobj to free the region, because fpga_region_unregister() will call\nfpga_region_dev_release() only when the refcount for dev-\u003ekobj is zero\nbut fpga_region_test_init() call device_register() in\nfpga_region_register_full(), which also increment refcount.\n\nSo call put_device() after calling fpga_region_class_find() in\nfpga_region_test_class_find(). After applying this patch, the following\nmemory leak is never detected.\n\nunreferenced object 0xffff88810c8ef000 (size 1024):\n comm \"kunit_try_catch\", pid 1875, jiffies 4294715298 (age 836.836s)\n hex dump (first 32 bytes):\n b8 d1 fb 05 81 88 ff ff 08 f0 8e 0c 81 88 ff ff ................\n 08 f0 8e 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ................\n backtrace:\n [\u003cffffffff817ebad7\u003e] kmalloc_trace+0x27/0xa0\n [\u003cffffffffa02385e1\u003e] fpga_region_register_full+0x51/0x430 [fpga_region]\n [\u003cffffffffa0228e47\u003e] 0xffffffffa0228e47\n [\u003cffffffff829c479d\u003e] kunit_try_run_case+0xdd/0x250\n [\u003cffffffff829c9f2a\u003e] kunit_generic_run_threadfn_adapter+0x4a/0x90\n [\u003cffffffff81238b85\u003e] kthread+0x2b5/0x380\n [\u003cffffffff81097ded\u003e] ret_from_fork+0x2d/0x70\n [\u003cffffffff810034d1\u003e] ret_from_fork_asm+0x11/0x20\nunreferenced object 0xffff888105fbd1b8 (size 8):\n comm \"kunit_try_catch\", pid 1875, jiffies 4294715298 (age 836.836s)\n hex dump (first 8 bytes):\n 72 65 67 69 6f 6e 30 00 region0.\n backtrace:\n [\u003cffffffff817ec023\u003e] __kmalloc_node_track_caller+0x53/0x150\n [\u003cffffffff82995590\u003e] kvasprintf+0xb0/0x130\n [\u003cffffffff83f713b1\u003e] kobject_set_name_vargs+0x41/0x110\n [\u003cffffffff8304ac1b\u003e] dev_set_name+0xab/0xe0\n [\u003cffffffffa02388a2\u003e] fpga_region_register_full+0x312/0x430 [fpga_region]\n [\u003cffffffffa0228e47\u003e] 0xffffffffa0228e47\n [\u003cffffffff829c479d\u003e] kunit_try_run_case+0xdd/0x250\n [\u003cffffffff829c9f2a\u003e] kunit_generic_run_threadfn_adapter+0x4a/0x90\n [\u003cffffffff81238b85\u003e] kthread+0x2b5/0x380\n [\u003cffffffff81097ded\u003e] ret_from_fork+0x2d/0x70\n [\u003cffffffff810034d1\u003e] ret_from_fork_asm+0x11/0x20\nunreferenced object 0xffff88810b3b8a00 (size 256):\n comm \"kunit_try_catch\", pid 1875, jiffies 4294715298 (age 836.836s)\n hex dump (first 32 bytes):\n 00 00 00 00 00 00 00 00 08 8a 3b 0b 81 88 ff ff ..........;.....\n 08 8a 3b 0b 81 88 ff ff e0 ac 04 83 ff ff ff ff ..;.............\n backtrace:\n [\u003cffffffff817ebad7\u003e] kmalloc_trace+0x27/0xa0\n [\u003cffffffff83056d7a\u003e] device_add+0xa2a/0x15e0\n [\u003cffffffffa02388b1\u003e] fpga_region_register_full+0x321/0x430 [fpga_region]\n [\u003cffffffffa0228e47\u003e] 0xffffffffa0228e47\n [\u003cffffffff829c479d\u003e] kunit_try_run_case+0xdd/0x250\n [\u003cffffffff829c9f2a\u003e] kunit_generic_run_threadfn_adapter+0x4a/0x90\n [\u003cffffffff81238b85\u003e] kthread+0x2b5/0x380\n [\u003cffffffff81097ded\u003e] ret_from_fork+0x2d/0x70\n [\u003cffffffff810034d1\u003e] ret_from_fork_asm+0x11/0x20\n\nFixes: 64a5f972c93d (\"fpga: add an initial KUnit suite for the FPGA Region\")\nSigned-off-by: Jinjie Ruan \u003cruanjinjie@huawei.com\u003e\nReviewed-by: Marco Pagani \u003cmarpagan@redhat.com\u003e\nAcked-by: Xu Yilun \u003cyilun.xu@intel.com\u003e\nLink: https://lore.kernel.org/r/20231007094321.3447084-1-ruanjinjie@huawei.com\n[yilun.xu@intel.com: slightly changes the commit message]\nSigned-off-by: Xu Yilun \u003cyilun.xu@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20231023032857.902699-3-yilun.xu@linux.intel.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "1e55c5200dc7efeb84d4582a82d289329255fd82", "tree": "1a5071e6348a3aee4a78f5dab5e985bea704b68a", "parents": [ "3e4a7afde492c51c86da243ae41b22c002e1a5c9" ], "author": { "name": "Russ Weight", "email": "russell.h.weight@intel.com", "time": "Mon Oct 23 11:28:56 2023 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 24 19:32:39 2023 +0200" }, "message": "fpga: m10bmc-sec: Change contact for secure update driver\n\nChange the maintainer for the Intel MAX10 BMC Secure Update driver from\nRuss Weight to Peter Colberg. Update the ABI documentation contact\ninformation as well.\n\nSigned-off-by: Russ Weight \u003crussell.h.weight@intel.com\u003e\nAcked-by: Peter Colberg \u003cpeter.colberg@intel.com\u003e\nLink: https://lore.kernel.org/r/20230928164753.278684-1-russell.h.weight@intel.com\nSigned-off-by: Xu Yilun \u003cyilun.xu@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20231023032857.902699-2-yilun.xu@linux.intel.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "cba94bbcff08d209710dd7bdc139caad675a6f8d", "tree": "674c6faeaa67471afe267b6430381f14b3de460c", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1" ], "author": { "name": "Umesh Nerlige Ramappa", "email": "umesh.nerlige.ramappa@intel.com", "time": "Wed Aug 02 13:28:54 2023 -0700" }, "committer": { "name": "Rodrigo Vivi", "email": "rodrigo.vivi@intel.com", "time": "Tue Oct 24 09:41:56 2023 -0400" }, "message": "drm/i915/perf: Determine context valid in OA reports\n\nWhen supporting OA for TGL, it was seen that the context valid bit in\nthe report ID was not defined, however revisiting the spec seems to have\nthis bit defined. The bit is used to determine if a context is valid on\na context switch and is essential to determine active and idle periods\nfor a context. Re-enable the context valid bit for gen12 platforms.\n\nBSpec: 52196 (description of report_id)\n\nv2: Include BSpec reference (Ashutosh)\n\nFixes: 00a7f0d7155c (\"drm/i915/tgl: Add perf support on TGL\")\nSigned-off-by: Umesh Nerlige Ramappa \u003cumesh.nerlige.ramappa@intel.com\u003e\nReviewed-by: Ashutosh Dixit \u003cashutosh.dixit@intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20230802202854.1224547-1-umesh.nerlige.ramappa@intel.com\n(cherry picked from commit 7eeaedf79989a8f131939782832e21e9218ed2a0)\nSigned-off-by: Rodrigo Vivi \u003crodrigo.vivi@intel.com\u003e\n" }, { "commit": "a71ef31485bb51b846e8db8b3a35e432cc15afb5", "tree": "1c6217197d73dde27343af3224e19de97b95b75c", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1" ], "author": { "name": "Peter Zijlstra", "email": "peterz@infradead.org", "time": "Tue Oct 24 11:42:21 2023 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Oct 24 12:15:12 2023 +0200" }, "message": "perf/core: Fix potential NULL deref\n\nSmatch is awesome.\n\nFixes: 32671e3799ca (\"perf: Disallow mis-matched inherited group reads\")\nReported-by: Dan Carpenter \u003cdan.carpenter@linaro.org\u003e\nSigned-off-by: Peter Zijlstra (Intel) \u003cpeterz@infradead.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n" }, { "commit": "cd8892c07876da0c4b50e020048a32a28596a074", "tree": "806e7aac4724a7907dcdb16e650adde1508bb070", "parents": [ "9644bc49705723bf7c69aa9bf542bb5161b91dba", "4530e5b8e2dad63dcad2206232dd86e4b1489b6c" ], "author": { "name": "Paolo Abeni", "email": "pabeni@redhat.com", "time": "Tue Oct 24 12:02:03 2023 +0200" }, "committer": { "name": "Paolo Abeni", "email": "pabeni@redhat.com", "time": "Tue Oct 24 12:02:04 2023 +0200" }, "message": "Merge branch \u0027gtp-tunnel-driver-fixes\u0027\n\nPablo Neira Ayuso says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nGTP tunnel driver fixes\n\nThe following patchset contains two fixes for the GTP tunnel driver:\n\n1) Incorrect GTPA_MAX definition in UAPI headers. This is updating an\n existing UAPI definition but for a good reason, this is certainly\n broken. Similar fixes for incorrect _MAX definition in netlink\n headers were applied in the past too.\n\n2) Fix GTP driver PMTU with GRO packets, add missing call to\n skb_gso_validate_network_len() to handle GRO packets.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://lore.kernel.org/r/20231022202519.659526-1-pablo@netfilter.org\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n" }, { "commit": "4530e5b8e2dad63dcad2206232dd86e4b1489b6c", "tree": "806e7aac4724a7907dcdb16e650adde1508bb070", "parents": [ "adc8df12d91a2b8350b0cd4c7fec3e8546c9d1f8" ], "author": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Sun Oct 22 22:25:18 2023 +0200" }, "committer": { "name": "Paolo Abeni", "email": "pabeni@redhat.com", "time": "Tue Oct 24 12:02:02 2023 +0200" }, "message": "gtp: fix fragmentation needed check with gso\n\nCall skb_gso_validate_network_len() to check if packet is over PMTU.\n\nFixes: 459aa660eb1d (\"gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U)\")\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n" }, { "commit": "adc8df12d91a2b8350b0cd4c7fec3e8546c9d1f8", "tree": "944c4f13180790d12baf939b4793bfa5c88d16ac", "parents": [ "9644bc49705723bf7c69aa9bf542bb5161b91dba" ], "author": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Sun Oct 22 22:25:17 2023 +0200" }, "committer": { "name": "Paolo Abeni", "email": "pabeni@redhat.com", "time": "Tue Oct 24 12:02:02 2023 +0200" }, "message": "gtp: uapi: fix GTPA_MAX\n\nSubtract one to __GTPA_MAX, otherwise GTPA_MAX is off by 2.\n\nFixes: 459aa660eb1d (\"gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U)\")\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n" }, { "commit": "9644bc49705723bf7c69aa9bf542bb5161b91dba", "tree": "1ecf816f481ab9266bfb4e3c065d5601c97932b5", "parents": [ "d788c9338342a3146d115281922901c1e3e1cbff" ], "author": { "name": "Anjali Kulkarni", "email": "anjali.k.kulkarni@oracle.com", "time": "Fri Oct 20 16:40:58 2023 -0700" }, "committer": { "name": "Paolo Abeni", "email": "pabeni@redhat.com", "time": "Tue Oct 24 10:53:45 2023 +0200" }, "message": "Fix NULL pointer dereference in cn_filter()\n\nCheck that sk_user_data is not NULL, else return from cn_filter().\nCould not reproduce this issue, but Oliver Sang verified it has fixed\nthe \"Closes\" problem below.\n\nFixes: 2aa1f7a1f47c (\"connector/cn_proc: Add filtering to fix some bugs\")\nReported-by: kernel test robot \u003coliver.sang@intel.com\u003e\nCloses: https://lore.kernel.org/oe-lkp/202309201456.84c19e27-oliver.sang@intel.com/\nSigned-off-by: Anjali Kulkarni \u003canjali.k.kulkarni@oracle.com\u003e\nLink: https://lore.kernel.org/r/20231020234058.2232347-1-anjali.k.kulkarni@oracle.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n" }, { "commit": "d88520ad73b79e71e3ddf08de335b8520ae41c5c", "tree": "f90d00e0c711f0ff8ec067f73401c8e96ea44f29", "parents": [ "84186fcb834ecc55604efaf383e17e6b5e9baa50", "1aee9158bc978f91701c5992e395efbc6da2de3c" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 20:40:04 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 20:40:04 2023 -1000" }, "message": "Merge tag \u0027pull-nfsd-fix\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs\n\nPull nfsd fix from Al Viro:\n \"Catch from lock_rename() audit; nfsd_rename() checked that both\n directories belonged to the same filesystem, but only after having\n done lock_rename().\n\n Trivial fix, tested and acked by nfs folks\"\n\n* tag \u0027pull-nfsd-fix\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:\n nfsd: lock_rename() needs both directories to live on the same fs\n" }, { "commit": "84186fcb834ecc55604efaf383e17e6b5e9baa50", "tree": "01043ed69e366fdaf0f83933f261b99b0035f0a1", "parents": [ "e017769f4ce20dc0d3fa3220d4d359dcc4431274", "921992229b1f06df6b649860e4a5f3def1489866" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 14:19:11 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 14:19:11 2023 -1000" }, "message": "Merge tag \u0027urgent/nolibc.2023.10.16a\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu\n\nPull nolibc fixes from Paul McKenney:\n\n - tools/nolibc: i386: Fix a stack misalign bug on _start\n\n - MAINTAINERS: nolibc: update tree location\n\n - tools/nolibc: mark start_c as weak to avoid linker errors\n\n* tag \u0027urgent/nolibc.2023.10.16a\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu:\n tools/nolibc: mark start_c as weak\n MAINTAINERS: nolibc: update tree location\n tools/nolibc: i386: Fix a stack misalign bug on _start\n" }, { "commit": "d788c9338342a3146d115281922901c1e3e1cbff", "tree": "79bed85999a161daa45c5c4ab1170dd2c1195896", "parents": [ "7798b59409c345d4a6034a4326bceb9f7e2e8b58" ], "author": { "name": "Pieter Jansen van Vuuren", "email": "pieter.jansen-van-vuuren@amd.com", "time": "Fri Oct 20 15:01:49 2023 +0100" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Mon Oct 23 15:47:47 2023 -0700" }, "message": "sfc: cleanup and reduce netlink error messages\n\nReduce the length of netlink error messages as they are likely to be\ntruncated anyway. Additionally, reword netlink error messages so they\nare more consistent with previous messages.\n\nFixes: 9dbc8d2b9a02 (\"sfc: add decrement ipv6 hop limit by offloading set hop limit actions\")\nFixes: 3c9561c0a5b9 (\"sfc: support TC decap rules matching on enc_ip_tos\")\nReported-by: kernel test robot \u003clkp@intel.com\u003e\nCloses: https://lore.kernel.org/oe-kbuild-all/202310202136.4u7bv0hp-lkp@intel.com/\nSigned-off-by: Pieter Jansen van Vuuren \u003cpieter.jansen-van-vuuren@amd.com\u003e\nReviewed-by: Edward Cree \u003cecree.xilinx@gmail.com\u003e\nLink: https://lore.kernel.org/r/20231020140149.30490-1-pieter.jansen-van-vuuren@amd.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "291c0d3a98afb7b863485215c241a851be9e3435", "tree": "9c2a3356b9baf08f928bf01e47562ae3aea8a51c", "parents": [ "eaf16b92b18cec5584392172ee4c89f5cf471397", "1122a9c2ebe02435014a0f40dcc50f4333286f0f" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Mon Oct 23 21:01:45 2023 +0200" }, "committer": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Mon Oct 23 21:01:59 2023 +0200" }, "message": "Merge tag \u0027mvebu-fixes-6.6-1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu into arm/fixes\n\nmvebu fixes for 6.6 (part 1)\n\nUpdate MAINTAINERS for eDPU board\n\n* tag \u0027mvebu-fixes-6.6-1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu:\n MAINTAINERS: uDPU: add remaining Methode boards\n MAINTAINERS: uDPU: make myself maintainer of it\n\nLink: https://lore.kernel.org/r/875y32abqe.fsf@BL-laptop\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\n" }, { "commit": "e017769f4ce20dc0d3fa3220d4d359dcc4431274", "tree": "c92c35a3b9571f1c7bcedf68bf602604746c010e", "parents": [ "7c14564010fc1d0f16ca7d39b0ff948b43344209", "eb96e221937af3c7bb8a63208dbab813ca5d3d7e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 07:59:13 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 07:59:13 2023 -1000" }, "message": "Merge tag \u0027for-6.6-rc7-tag\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux\n\nPull btrfs fix from David Sterba:\n \"One more fix for a problem with snapshot of a newly created subvolume\n that can lead to inconsistent data under some circumstances. Kernel\n 6.5 added a performance optimization to skip transaction commit for\n subvolume creation but this could end up with newer data on disk but\n not linked to other structures.\n\n The fix itself is an added condition, the rest of the patch is a\n parameter added to several functions\"\n\n* tag \u0027for-6.6-rc7-tag\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:\n btrfs: fix unwritten extent buffer after snapshotting a new subvolume\n" }, { "commit": "7c14564010fc1d0f16ca7d39b0ff948b43344209", "tree": "5d2b1899c5ddd8df0160e7469f484266259c77a8", "parents": [ "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1", "061b39fdfe7fd98946e67637213bcbb10a318cca" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 07:42:48 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 23 07:42:48 2023 -1000" }, "message": "Merge tag \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost\n\nPull virtio fixes from Michael Tsirkin:\n \"A collection of small fixes that look like worth having in this\n release\"\n\n* tag \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost:\n virtio_pci: fix the common cfg map size\n virtio-crypto: handle config changed by work queue\n vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE\n vdpa/mlx5: Fix firmware error on creation of 1k VQs\n virtio_balloon: Fix endless deflation and inflation on arm64\n vdpa/mlx5: Fix double release of debugfs entry\n virtio-mmio: fix memory leak of vm_dev\n vdpa_sim_blk: Fix the potential leak of mgmt_dev\n tools/virtio: Add dma sync api for virtio test\n" }, { "commit": "7798b59409c345d4a6034a4326bceb9f7e2e8b58", "tree": "6274e5c929824616d2f6d062cf89b0a5ee385a2b", "parents": [ "13454e6e0df2ff37853596d546438ac84ca6a413" ], "author": { "name": "Moritz Wanzenböck", "email": "moritz.wanzenboeck@linbit.com", "time": "Thu Oct 19 14:58:47 2023 +0200" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Mon Oct 23 10:19:33 2023 -0700" }, "message": "net/handshake: fix file ref count in handshake_nl_accept_doit()\n\nIf req-\u003ehr_proto-\u003ehp_accept() fail, we call fput() twice:\nOnce in the error path, but also a second time because sock-\u003efile\nis at that point already associated with the file descriptor. Once\nthe task exits, as it would probably do after receiving an error\nreading from netlink, the fd is closed, calling fput() a second time.\n\nTo fix, we move installing the file after the error path for the\nhp_accept() call. In the case of errors we simply put the unused fd.\nIn case of success we can use fd_install() to link the sock-\u003efile\nto the reserved fd.\n\nFixes: 7ea9c1ec66bc (\"net/handshake: Fix handshake_dup() ref counting\")\nSigned-off-by: Moritz Wanzenböck \u003cmoritz.wanzenboeck@linbit.com\u003e\nReviewed-by: Chuck Lever \u003cchuck.lever@oracle.com\u003e\nLink: https://lore.kernel.org/r/20231019125847.276443-1-moritz.wanzenboeck@linbit.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "eb96e221937af3c7bb8a63208dbab813ca5d3d7e", "tree": "a60818be3a3b74f19adb4cfd08af735d5ed6a44d", "parents": [ "8a540e990d7da36813cb71a4a422712bfba448a4" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Oct 19 13:19:28 2023 +0100" }, "committer": { "name": "David Sterba", "email": "dsterba@suse.com", "time": "Mon Oct 23 17:17:30 2023 +0200" }, "message": "btrfs: fix unwritten extent buffer after snapshotting a new subvolume\n\nWhen creating a snapshot of a subvolume that was created in the current\ntransaction, we can end up not persisting a dirty extent buffer that is\nreferenced by the snapshot, resulting in IO errors due to checksum failures\nwhen trying to read the extent buffer later from disk. A sequence of steps\nthat leads to this is the following:\n\n1) At ioctl.c:create_subvol() we allocate an extent buffer, with logical\n address 36007936, for the leaf/root of a new subvolume that has an ID\n of 291. We mark the extent buffer as dirty, and at this point the\n subvolume tree has a single node/leaf which is also its root (level 0);\n\n2) We no longer commit the transaction used to create the subvolume at\n create_subvol(). We used to, but that was recently removed in\n commit 1b53e51a4a8f (\"btrfs: don\u0027t commit transaction for every subvol\n create\");\n\n3) The transaction used to create the subvolume has an ID of 33, so the\n extent buffer 36007936 has a generation of 33;\n\n4) Several updates happen to subvolume 291 during transaction 33, several\n files created and its tree height changes from 0 to 1, so we end up with\n a new root at level 1 and the extent buffer 36007936 is now a leaf of\n that new root node, which is extent buffer 36048896.\n\n The commit root remains as 36007936, since we are still at transaction\n 33;\n\n5) Creation of a snapshot of subvolume 291, with an ID of 292, starts at\n ioctl.c:create_snapshot(). This triggers a commit of transaction 33 and\n we end up at transaction.c:create_pending_snapshot(), in the critical\n section of a transaction commit.\n\n There we COW the root of subvolume 291, which is extent buffer 36048896.\n The COW operation returns extent buffer 36048896, since there\u0027s no need\n to COW because the extent buffer was created in this transaction and it\n was not written yet.\n\n The we call btrfs_copy_root() against the root node 36048896. During\n this operation we allocate a new extent buffer to turn into the root\n node of the snapshot, copy the contents of the root node 36048896 into\n this snapshot root extent buffer, set the owner to 292 (the ID of the\n snapshot), etc, and then we call btrfs_inc_ref(). This will create a\n delayed reference for each leaf pointed by the root node with a\n reference root of 292 - this includes a reference for the leaf\n 36007936.\n\n After that we set the bit BTRFS_ROOT_FORCE_COW in the root\u0027s state.\n\n Then we call btrfs_insert_dir_item(), to create the directory entry in\n in the tree of subvolume 291 that points to the snapshot. This ends up\n needing to modify leaf 36007936 to insert the respective directory\n items. Because the bit BTRFS_ROOT_FORCE_COW is set for the root\u0027s state,\n we need to COW the leaf. We end up at btrfs_force_cow_block() and then\n at update_ref_for_cow().\n\n At update_ref_for_cow() we call btrfs_block_can_be_shared() which\n returns false, despite the fact the leaf 36007936 is shared - the\n subvolume\u0027s root and the snapshot\u0027s root point to that leaf. The\n reason that it incorrectly returns false is because the commit root\n of the subvolume is extent buffer 36007936 - it was the initial root\n of the subvolume when we created it. So btrfs_block_can_be_shared()\n which has the following logic:\n\n int btrfs_block_can_be_shared(struct btrfs_root *root,\n struct extent_buffer *buf)\n {\n if (test_bit(BTRFS_ROOT_SHAREABLE, \u0026root-\u003estate) \u0026\u0026\n buf !\u003d root-\u003enode \u0026\u0026 buf !\u003d root-\u003ecommit_root \u0026\u0026\n (btrfs_header_generation(buf) \u003c\u003d\n btrfs_root_last_snapshot(\u0026root-\u003eroot_item) ||\n btrfs_header_flag(buf, BTRFS_HEADER_FLAG_RELOC)))\n return 1;\n\n return 0;\n }\n\n Returns false (0) since \u0027buf\u0027 (extent buffer 36007936) matches the\n root\u0027s commit root.\n\n As a result, at update_ref_for_cow(), we don\u0027t check for the number\n of references for extent buffer 36007936, we just assume it\u0027s not\n shared and therefore that it has only 1 reference, so we set the local\n variable \u0027refs\u0027 to 1.\n\n Later on, in the final if-else statement at update_ref_for_cow():\n\n static noinline int update_ref_for_cow(struct btrfs_trans_handle *trans,\n struct btrfs_root *root,\n struct extent_buffer *buf,\n struct extent_buffer *cow,\n int *last_ref)\n {\n (...)\n if (refs \u003e 1) {\n (...)\n } else {\n (...)\n btrfs_clear_buffer_dirty(trans, buf);\n *last_ref \u003d 1;\n }\n }\n\n So we mark the extent buffer 36007936 as not dirty, and as a result\n we don\u0027t write it to disk later in the transaction commit, despite the\n fact that the snapshot\u0027s root points to it.\n\n Attempting to access the leaf or dumping the tree for example shows\n that the extent buffer was not written:\n\n $ btrfs inspect-internal dump-tree -t 292 /dev/sdb\n btrfs-progs v6.2.2\n file tree key (292 ROOT_ITEM 33)\n node 36110336 level 1 items 2 free space 119 generation 33 owner 292\n node 36110336 flags 0x1(WRITTEN) backref revision 1\n checksum stored a8103e3e\n checksum calced a8103e3e\n fs uuid 90c9a46f-ae9f-4626-9aff-0cbf3e2e3a79\n chunk uuid e8c9c885-78f4-4d31-85fe-89e5f5fd4a07\n key (256 INODE_ITEM 0) block 36007936 gen 33\n key (257 EXTENT_DATA 0) block 36052992 gen 33\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n total bytes 107374182400\n bytes used 38572032\n uuid 90c9a46f-ae9f-4626-9aff-0cbf3e2e3a79\n\n The respective on disk region is full of zeroes as the device was\n trimmed at mkfs time.\n\n Obviously \u0027btrfs check\u0027 also detects and complains about this:\n\n $ btrfs check /dev/sdb\n Opening filesystem to check...\n Checking filesystem on /dev/sdb\n UUID: 90c9a46f-ae9f-4626-9aff-0cbf3e2e3a79\n generation: 33 (33)\n [1/7] checking root items\n [2/7] checking extents\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n bad tree block 36007936, bytenr mismatch, want\u003d36007936, have\u003d0\n owner ref check failed [36007936 4096]\n ERROR: errors found in extent allocation tree or chunk allocation\n [3/7] checking free space tree\n [4/7] checking fs roots\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n checksum verify failed on 36007936 wanted 0x00000000 found 0x86005f29\n bad tree block 36007936, bytenr mismatch, want\u003d36007936, have\u003d0\n The following tree block(s) is corrupted in tree 292:\n tree block bytenr: 36110336, level: 1, node key: (256, 1, 0)\n root 292 root dir 256 not found\n ERROR: errors found in fs roots\n found 38572032 bytes used, error(s) found\n total csum bytes: 16048\n total tree bytes: 1265664\n total fs tree bytes: 1118208\n total extent tree bytes: 65536\n btree space waste bytes: 562598\n file data blocks allocated: 65978368\n referenced 36569088\n\nFix this by updating btrfs_block_can_be_shared() to consider that an\nextent buffer may be shared if it matches the commit root and if its\ngeneration matches the current transaction\u0027s generation.\n\nThis can be reproduced with the following script:\n\n $ cat test.sh\n #!/bin/bash\n\n MNT\u003d/mnt/sdi\n DEV\u003d/dev/sdi\n\n # Use a filesystem with a 64K node size so that we have the same node\n # size on every machine regardless of its page size (on x86_64 default\n # node size is 16K due to the 4K page size, while on PPC it\u0027s 64K by\n # default). This way we can make sure we are able to create a btree for\n # the subvolume with a height of 2.\n mkfs.btrfs -f -n 64K $DEV\n mount $DEV $MNT\n\n btrfs subvolume create $MNT/subvol\n\n # Create a few empty files on the subvolume, this bumps its btree\n # height to 2 (root node at level 1 and 2 leaves).\n for ((i \u003d 1; i \u003c\u003d 300; i++)); do\n echo -n \u003e $MNT/subvol/file_$i\n done\n\n btrfs subvolume snapshot -r $MNT/subvol $MNT/subvol/snap\n\n umount $DEV\n\n btrfs check $DEV\n\nRunning it on a 6.5 kernel (or any 6.6-rc kernel at the moment):\n\n $ ./test.sh\n Create subvolume \u0027/mnt/sdi/subvol\u0027\n Create a readonly snapshot of \u0027/mnt/sdi/subvol\u0027 in \u0027/mnt/sdi/subvol/snap\u0027\n Opening filesystem to check...\n Checking filesystem on /dev/sdi\n UUID: bbdde2ff-7d02-45ca-8a73-3c36f23755a1\n [1/7] checking root items\n [2/7] checking extents\n parent transid verify failed on 30539776 wanted 7 found 5\n parent transid verify failed on 30539776 wanted 7 found 5\n parent transid verify failed on 30539776 wanted 7 found 5\n Ignoring transid failure\n owner ref check failed [30539776 65536]\n ERROR: errors found in extent allocation tree or chunk allocation\n [3/7] checking free space tree\n [4/7] checking fs roots\n parent transid verify failed on 30539776 wanted 7 found 5\n Ignoring transid failure\n Wrong key of child node/leaf, wanted: (256, 1, 0), have: (2, 132, 0)\n Wrong generation of child node/leaf, wanted: 5, have: 7\n root 257 root dir 256 not found\n ERROR: errors found in fs roots\n found 917504 bytes used, error(s) found\n total csum bytes: 0\n total tree bytes: 851968\n total fs tree bytes: 393216\n total extent tree bytes: 65536\n btree space waste bytes: 736550\n file data blocks allocated: 0\n referenced 0\n\nA test case for fstests will follow soon.\n\nFixes: 1b53e51a4a8f (\"btrfs: don\u0027t commit transaction for every subvol create\")\nCC: stable@vger.kernel.org # 6.5+\nReviewed-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: David Sterba \u003cdsterba@suse.com\u003e\n" }, { "commit": "4984fc578a911f3146965f4086d0a219a9806002", "tree": "875b0ceec2a4eca88d4e18a55e749438fe0b601d", "parents": [ "d3df66fd98557c25856860b7d9c3b8b93d449f0a" ], "author": { "name": "Christian König", "email": "christian.koenig@amd.com", "time": "Fri Oct 20 14:28:56 2023 +0200" }, "committer": { "name": "Christian König", "email": "christian.koenig@amd.com", "time": "Mon Oct 23 14:48:47 2023 +0200" }, "message": "drm/amdkfd: reserve a fence slot while locking the BO\n\nLooks like the KFD still needs this.\n\nSigned-off-by: Christian König \u003cchristian.koenig@amd.com\u003e\nFixes: 8abc1eb2987a (\"drm/amdkfd: switch over to using drm_exec v3\")\nAcked-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nAcked-by: Felix Kuehling \u003cFelix.Kuehling@amd.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20231020123306.43978-1-christian.koenig@amd.com\n" }, { "commit": "daa9ada2093ed23d52b4c1fe6e13cf78f55cc85f", "tree": "884019a9d328b641cd42a245dba05647428959ba", "parents": [ "f9bc9bbe8afdf83412728f0b464979a72a3b9ec2" ], "author": { "name": "Michael Ellerman", "email": "mpe@ellerman.id.au", "time": "Mon Oct 23 22:25:00 2023 +1100" }, "committer": { "name": "Michael Ellerman", "email": "mpe@ellerman.id.au", "time": "Mon Oct 23 22:50:15 2023 +1100" }, "message": "powerpc/mm: Fix boot crash with FLATMEM\n\nErhard reported that his G5 was crashing with v6.6-rc kernels:\n\n mpic: Setting up HT PICs workarounds for U3/U4\n BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe\n Faulting instruction address: 0xc00000000005dc40\n Oops: Kernel access of bad area, sig: 11 [#1]\n BE PAGE_SIZE\u003d4K MMU\u003dHash SMP NR_CPUS\u003d2 PowerMac\n Modules linked in:\n CPU: 0 PID: 0 Comm: swapper/0 Tainted: G T 6.6.0-rc3-PMacGS #1\n Hardware name: PowerMac11,2 PPC970MP 0x440101 PowerMac\n NIP: c00000000005dc40 LR: c000000000066660 CTR: c000000000007730\n REGS: c0000000022bf510 TRAP: 0380 Tainted: G T (6.6.0-rc3-PMacGS)\n MSR: 9000000000001032 \u003cSF,HV,ME,IR,DR,RI\u003e CR: 44004242 XER: 00000000\n IRQMASK: 3\n GPR00: 0000000000000000 c0000000022bf7b0 c0000000010c0b00 00000000000001ac\n GPR04: 0000000003c80000 0000000000000300 c0000000f20001ae 0000000000000300\n GPR08: 0000000000000006 feffbb62ffec65ff 0000000000000001 0000000000000000\n GPR12: 9000000000001032 c000000002362000 c000000000f76b80 000000000349ecd8\n GPR16: 0000000002367ba8 0000000002367f08 0000000000000006 0000000000000000\n GPR20: 00000000000001ac c000000000f6f920 c0000000022cd985 000000000000000c\n GPR24: 0000000000000300 00000003b0a3691d c0003e008030000e 0000000000000000\n GPR28: c00000000000000c c0000000f20001ee feffbb62ffec65fe 00000000000001ac\n NIP hash_page_do_lazy_icache+0x50/0x100\n LR __hash_page_4K+0x420/0x590\n Call Trace:\n hash_page_mm+0x364/0x6f0\n do_hash_fault+0x114/0x2b0\n data_access_common_virt+0x198/0x1f0\n --- interrupt: 300 at mpic_init+0x4bc/0x10c4\n NIP: c000000002020a5c LR: c000000002020a04 CTR: 0000000000000000\n REGS: c0000000022bf9f0 TRAP: 0300 Tainted: G T (6.6.0-rc3-PMacGS)\n MSR: 9000000000001032 \u003cSF,HV,ME,IR,DR,RI\u003e CR: 24004248 XER: 00000000\n DAR: c0003e008030000e DSISR: 40000000 IRQMASK: 1\n ...\n NIP mpic_init+0x4bc/0x10c4\n LR mpic_init+0x464/0x10c4\n --- interrupt: 300\n pmac_setup_one_mpic+0x258/0x2dc\n pmac_pic_init+0x28c/0x3d8\n init_IRQ+0x90/0x140\n start_kernel+0x57c/0x78c\n start_here_common+0x1c/0x20\n\nA bisect pointed to the breakage beginning with commit 9fee28baa601 (\"powerpc:\nimplement the new page table range API\").\n\nAnalysis of the oops pointed to a struct page with a corrupted\ncompound_head being loaded via page_folio() -\u003e _compound_head() in\nhash_page_do_lazy_icache().\n\nThe access by the mpic code is to an MMIO address, so the expectation\nis that the struct page for that address would be initialised by\ninit_unavailable_range(), as pointed out by Aneesh.\n\nInstrumentation showed that was not the case, which eventually lead to\nthe realisation that pfn_valid() was returning false for that address,\ncausing the struct page to not be initialised.\n\nBecause the system is using FLATMEM, the version of pfn_valid() in\nmemory_model.h is used:\n\nstatic inline int pfn_valid(unsigned long pfn)\n{\n\t...\n\treturn pfn \u003e\u003d pfn_offset \u0026\u0026 (pfn - pfn_offset) \u003c max_mapnr;\n}\n\nWhich relies on max_mapnr being initialised. Early in boot max_mapnr is\nzero meaning no PFNs are valid.\n\nmax_mapnr is initialised in mem_init() called via:\n\n start_kernel()\n mm_core_init() # init/main.c:928\n mem_init()\n\nBut that is too late for the usage in init_unavailable_range() called via:\n\n start_kernel()\n setup_arch() # init/main.c:893\n paging_init()\n free_area_init()\n init_unavailable_range()\n\nAlthough max_mapnr is currently set in mem_init(), the value is actually\nalready available much earlier, as soon as mem_topology_setup() has\ncompleted, which is also before paging_init() is called. So move the\ninitialisation there, which causes paging_init() to correctly initialise\nthe struct page and fixes the bug.\n\nThis bug seems to have been lurking for years, but went unnoticed\nbecause the pre-folio code was inspecting the uninitialised page-\u003eflags\nbut not dereferencing it.\n\nThanks to Erhard and Aneesh for help debugging.\n\nReported-by: Erhard Furtner \u003cerhard_f@mailbox.org\u003e\nCloses: https://lore.kernel.org/all/20230929132750.3cd98452@yea/\nSigned-off-by: Michael Ellerman \u003cmpe@ellerman.id.au\u003e\nLink: https://msgid.link/20231023112500.1550208-1-mpe@ellerman.id.au\n\n" }, { "commit": "91535613b6090fc968c601d11d4e2f16b333713c", "tree": "10352145554b1093719fcb77b63217615345c4d5", "parents": [ "c434b2be2d80d236bb090fdb493d4bd5ed589238" ], "author": { "name": "Avraham Stern", "email": "avraham.stern@intel.com", "time": "Mon Oct 16 14:52:48 2023 +0300" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Mon Oct 23 13:25:30 2023 +0200" }, "message": "wifi: mac80211: don\u0027t drop all unprotected public action frames\n\nNot all public action frames have a protected variant. When MFP is\nenabled drop only public action frames that have a dual protected\nvariant.\n\nFixes: 76a3059cf124 (\"wifi: mac80211: drop some unprotected action frames\")\nSigned-off-by: Avraham Stern \u003cavraham.stern@intel.com\u003e\nSigned-off-by: Gregory Greenman \u003cgregory.greenman@intel.com\u003e\nLink: https://lore.kernel.org/r/20231016145213.2973e3c8d3bb.I6198b8d3b04cf4a97b06660d346caec3032f232a@changeid\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "c434b2be2d80d236bb090fdb493d4bd5ed589238", "tree": "aad8870cfdfbc07aca57a6104b98381696ea2471", "parents": [ "3e3929ef889e650dd585dc0f4f7f18240688811a" ], "author": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Wed Oct 18 11:42:51 2023 +0200" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Mon Oct 23 13:25:30 2023 +0200" }, "message": "wifi: cfg80211: fix assoc response warning on failed links\n\nThe warning here shouldn\u0027t be done before we even set the\nbss field (or should\u0027ve used the input data). Move the\nassignment before the warning to fix it.\n\nWe noticed this now because of Wen\u0027s bugfix, where the bug\nfixed there had previously hidden this other bug.\n\nFixes: 53ad07e9823b (\"wifi: cfg80211: support reporting failed links\")\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "3e3929ef889e650dd585dc0f4f7f18240688811a", "tree": "1704648269ae2c32302f41b0a9f3f31b4578f985", "parents": [ "f2ac54ebf85615a6d78f5eb213a8bbeeb17ebe5d" ], "author": { "name": "Ben Greear", "email": "greearb@candelatech.com", "time": "Sat Oct 21 08:48:27 2023 -0700" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Mon Oct 23 13:24:51 2023 +0200" }, "message": "wifi: cfg80211: pass correct pointer to rdev_inform_bss()\n\nConfusing struct member names here resulted in passing\nthe wrong pointer, causing crashes. Pass the correct one.\n\nFixes: eb142608e2c4 (\"wifi: cfg80211: use a struct for inform_single_bss data\")\nSigned-off-by: Ben Greear \u003cgreearb@candelatech.com\u003e\nLink: https://lore.kernel.org/r/20231021154827.1142734-1-greearb@candelatech.com\n[rewrite commit message, add fixes]\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "13454e6e0df2ff37853596d546438ac84ca6a413", "tree": "fb60cddd564a6ca48c2e97e16980cbed67d0226e", "parents": [ "d2a0fc372aca561556e765d0a9ec365c7c12f0ad" ], "author": { "name": "Kunwu Chan", "email": "chentao@kylinos.cn", "time": "Mon Oct 23 14:37:58 2023 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Mon Oct 23 09:39:46 2023 +0100" }, "message": "isdn: mISDN: hfcsusb: Spelling fix in comment\n\nprotocoll -\u003e protocol\n\nSigned-off-by: Kunwu Chan \u003cchentao@kylinos.cn\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1", "tree": "92eb1e65aa9d8b46943a4e2e0cf6e856516b621e", "parents": [ "fe3cfe869d5e0453754cf2b4c75110276b5e8527" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 12:11:21 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 12:11:21 2023 -1000" }, "message": "Linux 6.6-rc7\n" }, { "commit": "fe3cfe869d5e0453754cf2b4c75110276b5e8527", "tree": "79cbc2f606a9090afb7c2a8bfec638c8a32accde", "parents": [ "70e65afc23b7670b775f0f086b9acd59b7fc4343", "089667aaaa6aa33715d22b21a72216b43af3e896" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 07:11:10 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 07:11:10 2023 -1000" }, "message": "Merge tag \u0027phy-fixes-6.6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy\n\nPull phy fixes from Vinod Koul:\n\n - mapphone-mdm6600 runtime pm \u0026 pinctrl handling fixes\n\n - Qualcomm qmp usb pcs register fixes, qmp pcie register size warning\n fix, m31 fixes for wrong pointer in PTR_ERR and dropping wrong vreg\n check, qmp combo fix for 8550 power config register\n\n - realtek usb fix for debugfs_create_dir() and kconfig dependency\n\n* tag \u0027phy-fixes-6.6\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy:\n phy: realtek: Realtek PHYs should depend on ARCH_REALTEK\n phy: qualcomm: Fix typos in comments\n phy: qcom-qmp-combo: initialize PCS_USB registers\n phy: qcom-qmp-combo: Square out 8550 POWER_STATE_CONFIG1\n phy: qcom: m31: Remove unwanted qphy-\u003evreg is NULL check\n phy: realtek: usb: Drop unnecessary error check for debugfs_create_dir()\n phy: qcom: phy-qcom-m31: change m31_ipq5332_regs to static\n phy: qcom: phy-qcom-m31: fix wrong pointer pass to PTR_ERR()\n dt-bindings: phy: qcom,ipq8074-qmp-pcie: fix warning regarding reg size\n phy: qcom-qmp-usb: split PCS_USB init table for sc8280xp and sa8775p\n phy: qcom-qmp-usb: initialize PCS_USB registers\n phy: mapphone-mdm6600: Fix pinctrl_pm handling for sleep pins\n phy: mapphone-mdm6600: Fix runtime PM for remove\n phy: mapphone-mdm6600: Fix runtime disable on probe\n" }, { "commit": "70e65afc23b7670b775f0f086b9acd59b7fc4343", "tree": "a180b386715501ff0e9bcf08b80bd56c14265152", "parents": [ "1acfd2bd3f0d9dc34ea1871a445c554220945d9f", "c03d21f05e76b25f907684bdf874308dcefab385" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 07:05:28 2023 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Oct 22 07:05:28 2023 -1000" }, "message": "Merge tag \u0027efi-fixes-for-v6.6-3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi\n\nPull EFI fixes from Ard Biesheuvel:\n \"The boot_params pointer fix uses a somewhat ugly extern struct\n declaration but this will be cleaned up the next cycle.\n\n - don\u0027t try to print warnings to the console when it is no longer\n available\n\n - fix theoretical memory leak in SSDT override handling\n\n - make sure that the boot_params global variable is set before the\n KASLR code attempts to hash it for \u0027randomness\u0027\n\n - avoid soft lockups in the memory acceptance code\"\n\n* tag \u0027efi-fixes-for-v6.6-3\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi:\n efi/unaccepted: Fix soft lockups caused by parallel memory acceptance\n x86/boot: efistub: Assign global boot_params variable\n efi: fix memory leak in krealloc failure handling\n x86/efistub: Don\u0027t try to print after ExitBootService()\n" }, { "commit": "d2a0fc372aca561556e765d0a9ec365c7c12f0ad", "tree": "45752d1d7b2fd126bea3885cbf9fd8b627d9a685", "parents": [ "a40614fe885a46758105bfcc6761594af2c9155e" ], "author": { "name": "Fred Chen", "email": "fred.chenchen03@gmail.com", "time": "Sat Oct 21 08:19:47 2023 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:47:44 2023 +0100" }, "message": "tcp: fix wrong RTO timeout when received SACK reneging\n\nThis commit fix wrong RTO timeout when received SACK reneging.\n\nWhen an ACK arrived pointing to a SACK reneging, tcp_check_sack_reneging()\nwill rearm the RTO timer for min(1/2*srtt, 10ms) into to the future.\n\nBut since the commit 62d9f1a6945b (\"tcp: fix TLP timer not set when\nCA_STATE changes from DISORDER to OPEN\") merged, the tcp_set_xmit_timer()\nis moved after tcp_fastretrans_alert()(which do the SACK reneging check),\nso the RTO timeout will be overwrited by tcp_set_xmit_timer() with\nicsk_rto instead of 1/2*srtt.\n\nHere is a packetdrill script to check this bug:\n0 socket(..., SOCK_STREAM, IPPROTO_TCP) \u003d 3\n+0 bind(3, ..., ...) \u003d 0\n+0 listen(3, 1) \u003d 0\n\n// simulate srtt to 100ms\n+0 \u003c S 0:0(0) win 32792 \u003cmss 1000, sackOK,nop,nop,nop,wscale 7\u003e\n+0 \u003e S. 0:0(0) ack 1 \u003cmss 1460,nop,nop,sackOK,nop,wscale 7\u003e\n+.1 \u003c . 1:1(0) ack 1 win 1024\n\n+0 accept(3, ..., ...) \u003d 4\n\n+0 write(4, ..., 10000) \u003d 10000\n+0 \u003e P. 1:10001(10000) ack 1\n\n// inject sack\n+.1 \u003c . 1:1(0) ack 1 win 257 \u003csack 1001:10001,nop,nop\u003e\n+0 \u003e . 1:1001(1000) ack 1\n\n// inject sack reneging\n+.1 \u003c . 1:1(0) ack 1001 win 257 \u003csack 9001:10001,nop,nop\u003e\n\n// we expect rto fired in 1/2*srtt (50ms)\n+.05 \u003e . 1001:2001(1000) ack 1\n\nThis fix remove the FLAG_SET_XMIT_TIMER from ack_flag when\ntcp_check_sack_reneging() set RTO timer with 1/2*srtt to avoid\nbeing overwrited later.\n\nFixes: 62d9f1a6945b (\"tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN\")\nSigned-off-by: Fred Chen \u003cfred.chenchen03@gmail.com\u003e\nReviewed-by: Neal Cardwell \u003cncardwell@google.com\u003e\nTested-by: Neal Cardwell \u003cncardwell@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "9b311b7313d6c104dd4a2d43ab54536dce07f960", "tree": "901f6836ea098d54f8282c905248d7c83a3ddaff", "parents": [ "f20f29cbcb438ca37962d22735f74a143cbeb28c" ], "author": { "name": "Xiang Chen", "email": "chenxiang66@hisilicon.com", "time": "Thu Oct 19 21:01:21 2023 +0800" }, "committer": { "name": "Rafael J. Wysocki", "email": "rafael.j.wysocki@intel.com", "time": "Sun Oct 22 12:47:43 2023 +0200" }, "message": "ACPI: NFIT: Install Notify() handler before getting NFIT table\n\nIf there is no NFIT at startup, it will return 0 immediately in function\nacpi_nfit_add() and will not install Notify() handler. If hotplugging\na nvdimm device later, it will not be identified as there is no Notify()\nhandler.\n\nInstall the handler before getting NFI table in function acpi_nfit_add()\nto avoid above issue.\n\nFixes: dcca12ab62a2 (\"ACPI: NFIT: Install Notify() handler directly\")\nSigned-off-by: Xiang Chen \u003cchenxiang66@hisilicon.com\u003e\n[ rjw: Subject and changelog edits ]\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\n" }, { "commit": "a40614fe885a46758105bfcc6761594af2c9155e", "tree": "292ca6f151c089c18882bef3473365688cdc167e", "parents": [ "51a32e828109b4a209efde44505baa356b37a4ce", "d9962b0d42029bcb40fe3c38bce06d1870fa4df4" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "Merge branch \u0027r8152-reg-garbage\u0027\n\nDouglas Anderson says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nr8152: Avoid writing garbage to the adapter\u0027s registers\n\nThis series is the result of a cooperative debug effort between\nRealtek and the ChromeOS team. On ChromeOS, we\u0027ve noticed that Realtek\nEthernet adapters can sometimes get so wedged that even a reboot of\nthe host can\u0027t get them to enumerate again, assuming that the adapter\nwas on a powered hub and din\u0027t lose power when the host rebooted. This\nis sometimes seen in the ChromeOS automated testing lab. The only way\nto recover adapters in this state is to manually power cycle them.\n\nI managed to reproduce one instance of this wedging (unknown if this\nis truly related to what the test lab sees) by doing this:\n1. Start a flood ping from a host to the device.\n2. Drop the device into kdb.\n3. Wait 90 seconds.\n4. Resume from kdb (the \"g\" command).\n5. Wait another 45 seconds.\n\nUpon analysis, Realtek realized this was happening:\n\n1. The Linux driver was getting a \"Tx timeout\" after resuming from kdb\n and then trying to reset itself.\n2. As part of the reset, the Linux driver was attempting to do a\n read-modify-write of the adapter\u0027s registers.\n3. The read would fail (due to a timeout) and the driver pretended\n that the register contained all 0xFFs. See commit f53a7ad18959\n (\"r8152: Set memory to all 0xFFs on failed reg reads\")\n4. The driver would take this value of all 0xFFs, modify it, and\n attempt to write it back to the adapter.\n5. By this time the USB channel seemed to recover and thus we\u0027d\n successfully write a value that was mostly 0xFFs to the adpater.\n6. The adapter didn\u0027t like this and would wedge itself.\n\nAnother Engineer also managed to reproduce wedging of the Realtek\nEthernet adpater during a reboot test on an AMD Chromebook. In that\ncase he was sometimes seeing -EPIPE returned from the control\ntransfers.\n\nThis patch series fixes both issues.\n\nChanges in v5:\n- (\"Run the unload routine if we have errors during probe\") new for v5.\n- (\"Cancel hw_phy_work if we have an error in probe\") new for v5.\n- (\"Release firmware if we have an error in probe\") new for v5.\n- Removed extra mutex_unlock() left over in v4.\n- Fixed minor typos.\n- Don\u0027t do queue an unbind/bind reset if probe fails; just retry probe.\n\nChanges in v4:\n- Took out some unnecessary locks/unlocks of the control mutex.\n- Added comment about reading version causing probe fail if 3 fails.\n- Added text to commit msg about the potential unbind/bind loop.\n\nChanges in v3:\n- Fixed v2 changelog ending up in the commit message.\n- farmework -\u003e framework in comments.\n\nChanges in v2:\n- (\"Check for unplug in rtl_phy_patch_request()\") new for v2.\n- (\"Check for unplug in r8153b_ups_en() / r8153c_ups_en()\") new for v2.\n- (\"Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE\") new for v2.\n- Reset patch no longer based on retry patch, since that was dropped.\n- Reset patch should be robust even if failures happen in probe.\n- Switched booleans to bits in the \"flags\" variable.\n- Check for -ENODEV instead of \"udev-\u003estate \u003d\u003d USB_STATE_NOTATTACHED\"\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "d9962b0d42029bcb40fe3c38bce06d1870fa4df4", "tree": "292ca6f151c089c18882bef3473365688cdc167e", "parents": [ "715f67f33af45ce2cc3a5b1ef133cc8c8e7787b0" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:59 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "r8152: Block future register access if register access fails\n\nEven though the functions to read/write registers can fail, most of\nthe places in the r8152 driver that read/write register values don\u0027t\ncheck error codes. The lack of error code checking is problematic in\nat least two ways.\n\nThe first problem is that the r8152 driver often uses code patterns\nsimilar to this:\n x \u003d read_register()\n x \u003d x | SOME_BIT;\n write_register(x);\n\n...with the above pattern, if the read_register() fails and returns\ngarbage then we\u0027ll end up trying to write modified garbage back to the\nRealtek adapter. If the write_register() succeeds that\u0027s bad. Note\nthat as of commit f53a7ad18959 (\"r8152: Set memory to all 0xFFs on\nfailed reg reads\") the \"garbage\" returned by read_register() will at\nleast be consistent garbage, but it is still garbage.\n\nIt turns out that this problem is very serious. Writing garbage to\nsome of the hardware registers on the Ethernet adapter can put the\nadapter in such a bad state that it needs to be power cycled (fully\nunplugged and plugged in again) before it can enumerate again.\n\nThe second problem is that the r8152 driver generally has functions\nthat are long sequences of register writes. Assuming everything will\nbe OK if a random register write fails in the middle isn\u0027t a great\nassumption.\n\nOne might wonder if the above two problems are real. You could ask if\nwe would really have a successful write after a failed read. It turns\nout that the answer appears to be \"yes, this can happen\". In fact,\nwe\u0027ve seen at least two distinct failure modes where this happens.\n\nOn a sc7180-trogdor Chromebook if you drop into kdb for a while and\nthen resume, you can see:\n1. We get a \"Tx timeout\"\n2. The \"Tx timeout\" queues up a USB reset.\n3. In rtl8152_pre_reset() we try to reinit the hardware.\n4. The first several (2-9) register accesses fail with a timeout, then\n things recover.\n\nThe above test case was actually fixed by the patch (\"r8152: Increase\nUSB control msg timeout to 5000ms as per spec\") but at least shows\nthat we really can see successful calls after failed ones.\n\nOn a different (AMD) based Chromebook with a particular adapter, we\nfound that during reboot tests we\u0027d also sometimes get a transitory\nfailure. In this case we saw -EPIPE being returned sometimes. Retrying\nworked, but retrying is not always safe for all register accesses\nsince reading/writing some registers might have side effects (like\nregisters that clear on read).\n\nLet\u0027s fully lock out all register access if a register access fails.\nWhen we do this, we\u0027ll try to queue up a USB reset and try to unlock\nregister access after the reset. This is slightly tricker than it\nsounds since the r8152 driver has an optimized reset sequence that\nonly works reliably after probe happens. In order to handle this, we\navoid the optimized reset if probe didn\u0027t finish. Instead, we simply\nretry the probe routine in this case.\n\nWhen locking out access, we\u0027ll use the existing infrastructure that\nthe driver was using when it detected we were unplugged. This keeps us\nfrom getting stuck in delay loops in some parts of the driver.\n\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "715f67f33af45ce2cc3a5b1ef133cc8c8e7787b0", "tree": "e880927bd6d770adeb34bc38c89ee0b1a356cad5", "parents": [ "bc65cc42af737a5a35f83842408ef2c6c79ba025" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:58 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE\n\nWhenever the RTL8152_UNPLUG is set that just tells the driver that all\naccesses will fail and we should just immediately bail. A future patch\nwill use this same concept at a time when the driver hasn\u0027t actually\nbeen unplugged but is about to be reset. Rename the flag in\npreparation for the future patch.\n\nThis is a no-op change and just a search and replace.\n\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "bc65cc42af737a5a35f83842408ef2c6c79ba025", "tree": "97ec29135e3bdf6db59b27c547100b24a7d36e0f", "parents": [ "dc90ba37a8c37042407fa6970b9830890cfe6047" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:57 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()\n\nIf the adapter is unplugged while we\u0027re looping in r8153b_ups_en() /\nr8153c_ups_en() we could end up looping for 10 seconds (20 ms * 500\nloops). Add code similar to what\u0027s done in other places in the driver\nto check for unplug and bail.\n\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "dc90ba37a8c37042407fa6970b9830890cfe6047", "tree": "35cb519954b69309ff9eeace5923364134add81e", "parents": [ "b8d35024d4059ca550cba11ac9ab23a6c238d929" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:56 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "r8152: Check for unplug in rtl_phy_patch_request()\n\nIf the adapter is unplugged while we\u0027re looping in\nrtl_phy_patch_request() we could end up looping for 10 seconds (2 ms *\n5000 loops). Add code similar to what\u0027s done in other places in the\ndriver to check for unplug and bail.\n\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "b8d35024d4059ca550cba11ac9ab23a6c238d929", "tree": "c2a5816733530ebcbfe70f52e0a20778716d1bda", "parents": [ "bb8adff9123e492598162ac1baad01a53891aef6" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:55 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:18 2023 +0100" }, "message": "r8152: Release firmware if we have an error in probe\n\nThe error handling in rtl8152_probe() is missing a call to release\nfirmware. Add it in to match what\u0027s in the cleanup code in\nrtl8152_disconnect().\n\nFixes: 9370f2d05a2a (\"r8152: support request_firmware for RTL8153\")\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "bb8adff9123e492598162ac1baad01a53891aef6", "tree": "e96cc463bbae48b3a2248e313b70609c395d3435", "parents": [ "5dd17689526971c5ae12bc8398f34bd68cd0499e" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:54 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:17 2023 +0100" }, "message": "r8152: Cancel hw_phy_work if we have an error in probe\n\nThe error handling in rtl8152_probe() is missing a call to cancel the\nhw_phy_work. Add it in to match what\u0027s in the cleanup code in\nrtl8152_disconnect().\n\nFixes: a028a9e003f2 (\"r8152: move the settings of PHY to a work queue\")\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "5dd17689526971c5ae12bc8398f34bd68cd0499e", "tree": "968d59f4b643a1ac30d2d392699a6bdaac1a2d9d", "parents": [ "a5feba71ec9c14a54c3babdc732c5b6866d8ee43" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:53 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:17 2023 +0100" }, "message": "r8152: Run the unload routine if we have errors during probe\n\nThe rtl8152_probe() function lacks a call to the chip-specific\nunload() routine when it sees an error in probe. Add it in to match\nthe cleanup code in rtl8152_disconnect().\n\nFixes: ac718b69301c (\"net/usb: new driver for RTL8152\")\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "a5feba71ec9c14a54c3babdc732c5b6866d8ee43", "tree": "a69c8de6c4050d34398a1e7a173a5a10d2d5a356", "parents": [ "51a32e828109b4a209efde44505baa356b37a4ce" ], "author": { "name": "Douglas Anderson", "email": "dianders@chromium.org", "time": "Fri Oct 20 14:06:52 2023 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:46:17 2023 +0100" }, "message": "r8152: Increase USB control msg timeout to 5000ms as per spec\n\nAccording to the comment next to USB_CTRL_GET_TIMEOUT and\nUSB_CTRL_SET_TIMEOUT, although sending/receiving control messages is\nusually quite fast, the spec allows them to take up to 5 seconds.\nLet\u0027s increase the timeout in the Realtek driver from 500ms to 5000ms\n(using the #defines) to account for this.\n\nThis is not just a theoretical change. The need for the longer timeout\nwas seen in testing. Specifically, if you drop a sc7180-trogdor based\nChromebook into the kdb debugger and then \"go\" again after sitting in\nthe debugger for a while, the next USB control message takes a long\ntime. Out of ~40 tests the slowest USB control message was 4.5\nseconds.\n\nWhile dropping into kdb is not exactly an end-user scenario, the above\nis similar to what could happen due to an temporary interrupt storm,\nwhat could happen if there was a host controller (HW or SW) issue, or\nwhat could happen if the Realtek device got into a confused state and\nneeded time to recover.\n\nThis change is fairly critical since the r8152 driver in Linux doesn\u0027t\nexpect register reads/writes (which are backed by USB control\nmessages) to fail.\n\nFixes: ac718b69301c (\"net/usb: new driver for RTL8152\")\nSuggested-by: Hayes Wang \u003chayeswang@realtek.com\u003e\nSigned-off-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Grant Grundler \u003cgrundler@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "51a32e828109b4a209efde44505baa356b37a4ce", "tree": "1a6a399ab7529813cb4792bae3b2891558d218c1", "parents": [ "9f771493da935299c6393ad3563b581255d01a37" ], "author": { "name": "Shigeru Yoshida", "email": "syoshida@redhat.com", "time": "Sat Oct 21 02:03:44 2023 +0900" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:39:26 2023 +0100" }, "message": "net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg\n\nsyzbot reported the following uninit-value access issue [1]:\n\nsmsc95xx 1-1:0.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x00000030: -32\nsmsc95xx 1-1:0.0 (unnamed net_device) (uninitialized): Error reading E2P_CMD\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nBUG: KMSAN: uninit-value in smsc95xx_reset+0x409/0x25f0 drivers/net/usb/smsc95xx.c:896\n smsc95xx_reset+0x409/0x25f0 drivers/net/usb/smsc95xx.c:896\n smsc95xx_bind+0x9bc/0x22e0 drivers/net/usb/smsc95xx.c:1131\n usbnet_probe+0x100b/0x4060 drivers/net/usb/usbnet.c:1750\n usb_probe_interface+0xc75/0x1210 drivers/usb/core/driver.c:396\n really_probe+0x506/0xf40 drivers/base/dd.c:658\n __driver_probe_device+0x2a7/0x5d0 drivers/base/dd.c:800\n driver_probe_device+0x72/0x7b0 drivers/base/dd.c:830\n __device_attach_driver+0x55a/0x8f0 drivers/base/dd.c:958\n bus_for_each_drv+0x3ff/0x620 drivers/base/bus.c:457\n __device_attach+0x3bd/0x640 drivers/base/dd.c:1030\n device_initial_probe+0x32/0x40 drivers/base/dd.c:1079\n bus_probe_device+0x3d8/0x5a0 drivers/base/bus.c:532\n device_add+0x16ae/0x1f20 drivers/base/core.c:3622\n usb_set_configuration+0x31c9/0x38c0 drivers/usb/core/message.c:2207\n usb_generic_driver_probe+0x109/0x2a0 drivers/usb/core/generic.c:238\n usb_probe_device+0x290/0x4a0 drivers/usb/core/driver.c:293\n really_probe+0x506/0xf40 drivers/base/dd.c:658\n __driver_probe_device+0x2a7/0x5d0 drivers/base/dd.c:800\n driver_probe_device+0x72/0x7b0 drivers/base/dd.c:830\n __device_attach_driver+0x55a/0x8f0 drivers/base/dd.c:958\n bus_for_each_drv+0x3ff/0x620 drivers/base/bus.c:457\n __device_attach+0x3bd/0x640 drivers/base/dd.c:1030\n device_initial_probe+0x32/0x40 drivers/base/dd.c:1079\n bus_probe_device+0x3d8/0x5a0 drivers/base/bus.c:532\n device_add+0x16ae/0x1f20 drivers/base/core.c:3622\n usb_new_device+0x15f6/0x22f0 drivers/usb/core/hub.c:2589\n hub_port_connect drivers/usb/core/hub.c:5440 [inline]\n hub_port_connect_change drivers/usb/core/hub.c:5580 [inline]\n port_event drivers/usb/core/hub.c:5740 [inline]\n hub_event+0x53bc/0x7290 drivers/usb/core/hub.c:5822\n process_one_work kernel/workqueue.c:2630 [inline]\n process_scheduled_works+0x104e/0x1e70 kernel/workqueue.c:2703\n worker_thread+0xf45/0x1490 kernel/workqueue.c:2784\n kthread+0x3e8/0x540 kernel/kthread.c:388\n ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\n\nLocal variable buf.i225 created at:\n smsc95xx_read_reg drivers/net/usb/smsc95xx.c:90 [inline]\n smsc95xx_reset+0x203/0x25f0 drivers/net/usb/smsc95xx.c:892\n smsc95xx_bind+0x9bc/0x22e0 drivers/net/usb/smsc95xx.c:1131\n\nCPU: 1 PID: 773 Comm: kworker/1:2 Not tainted 6.6.0-rc1-syzkaller-00125-ge42bebf6db29 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023\nWorkqueue: usb_hub_wq hub_event\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSimilar to e9c65989920f (\"net: usb: smsc75xx: Fix uninit-value access in\n__smsc75xx_read_reg\"), this issue is caused because usbnet_read_cmd() reads\nless bytes than requested (zero byte in the reproducer). In this case,\n\u0027buf\u0027 is not properly filled.\n\nThis patch fixes the issue by returning -ENODATA if usbnet_read_cmd() reads\nless bytes than requested.\n\nsysbot reported similar uninit-value access issue [2]. The root cause is\nthe same as mentioned above, and this patch addresses it as well.\n\nFixes: 2f7ca802bdae (\"net: Add SMSC LAN9500 USB2.0 10/100 ethernet adapter driver\")\nReported-and-tested-by: syzbot+c74c24b43c9ae534f0e0@syzkaller.appspotmail.com\nReported-and-tested-by: syzbot+2c97a98a5ba9ea9c23bd@syzkaller.appspotmail.com\nCloses: https://syzkaller.appspot.com/bug?extid\u003dc74c24b43c9ae534f0e0 [1]\nCloses: https://syzkaller.appspot.com/bug?extid\u003d2c97a98a5ba9ea9c23bd [2]\nSigned-off-by: Shigeru Yoshida \u003csyoshida@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "9f771493da935299c6393ad3563b581255d01a37", "tree": "82da07f229f75cd64864b4ccbc2012bd4bf9cae8", "parents": [ "ca082f019d8fbb983f03080487946da714154bae" ], "author": { "name": "Su Hui", "email": "suhui@nfschina.com", "time": "Fri Oct 20 17:27:59 2023 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:36:30 2023 +0100" }, "message": "net: chelsio: cxgb4: add an error code check in t4_load_phy_fw\n\nt4_set_params_timeout() can return -EINVAL if failed, add check\nfor this.\n\nSigned-off-by: Su Hui \u003csuhui@nfschina.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "ca082f019d8fbb983f03080487946da714154bae", "tree": "d009f06f735770eb8fdebac3810cbd2c735b52fb", "parents": [ "965f9b8c0c1b37fa2a0e3ef56e40d5666d4cbb5c" ], "author": { "name": "Christophe JAILLET", "email": "christophe.jaillet@wanadoo.fr", "time": "Sat Oct 21 20:03:53 2023 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Oct 22 11:28:43 2023 +0100" }, "message": "net: ieee802154: adf7242: Fix some potential buffer overflow in adf7242_stats_show()\n\nstrncat() usage in adf7242_debugfs_init() is wrong.\nThe size given to strncat() is the maximum number of bytes that can be\nwritten, excluding the trailing NULL.\n\nHere, the size that is passed, DNAME_INLINE_LEN, does not take into account\nthe size of \"adf7242-\" that is already in the array.\n\nIn order to fix it, use snprintf() instead.\n\nFixes: 7302b9d90117 (\"ieee802154/adf7242: Driver for ADF7242 MAC IEEE802154\")\nSigned-off-by: Christophe JAILLET \u003cchristophe.jaillet@wanadoo.fr\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "1acfd2bd3f0d9dc34ea1871a445c554220945d9f", "tree": "7891a7513ebc18345e4e4c37cad1be5ee102b352", "parents": [ "d537ae43f8a107761fb5a85c3f0cfce5ca79bcb1", "f9bc9bbe8afdf83412728f0b464979a72a3b9ec2" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 21 18:46:47 2023 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 21 18:46:47 2023 -0700" }, "message": "Merge tag \u0027powerpc-6.6-5\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux\n\nPull powerpc fixes from Michael Ellerman:\n\n - Fix stale propagated yield_cpu in qspinlocks leading to lockups\n\n - Fix broken hugepages on some configs due to ARCH_FORCE_MAX_ORDER\n\n - Fix a spurious warning when copros are in use at exit time\n\nThanks to Nicholas Piggin, Christophe Leroy, Nysal Jan K.A Sachin Sant,\nand Shrikanth Hegde.\n\n* tag \u0027powerpc-6.6-5\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:\n powerpc/qspinlock: Fix stale propagated yield_cpu\n powerpc/64s/radix: Don\u0027t warn on copros in radix__tlb_flush()\n powerpc/mm: Allow ARCH_FORCE_MAX_ORDER up to 12\n" }, { "commit": "d3df66fd98557c25856860b7d9c3b8b93d449f0a", "tree": "fc617225c84e117d69b7dfb028bdbfcd72abca48", "parents": [ "3d887d512494d678b17c57b835c32f4e48d34f26" ], "author": { "name": "Luben Tuikov", "email": "luben.tuikov@amd.com", "time": "Tue Oct 17 20:56:57 2023 -0400" }, "committer": { "name": "Luben Tuikov", "email": "luben.tuikov@amd.com", "time": "Sat Oct 21 20:27:15 2023 -0400" }, "message": "drm/amdgpu: Remove redundant call to priority_is_valid()\n\nRemove a redundant call to amdgpu_ctx_priority_is_valid() from\namdgpu_ctx_priority_permit(), which is called from amdgpu_ctx_init() which is\ncalled from amdgpu_ctx_alloc() which is called from amdgpu_ctx_ioctl(), where\nwe\u0027ve called amdgpu_ctx_priority_is_valid() already first thing in the\nfunction.\n\nCc: Alex Deucher \u003cAlexander.Deucher@amd.com\u003e\nCc: Christian König \u003cchristian.koenig@amd.com\u003e\nSigned-off-by: Luben Tuikov \u003cluben.tuikov@amd.com\u003e\nAcked-by: Christian König \u003cchristian.koenig@amd.com\u003e\nLink: https://lore.kernel.org/r/20231018010359.30393-1-luben.tuikov@amd.com\n" }, { "commit": "d537ae43f8a107761fb5a85c3f0cfce5ca79bcb1", "tree": "e0dacc279d77c1b1ca1498432de98e2b96140084", "parents": [ "03027aa3a5c698b8fe1a0254284198cb1423481e", "479ac419206b5fe4ce4e40de61ac3210a36711aa" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 21 12:59:18 2023 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Oct 21 12:59:18 2023 -0700" }, "message": "Merge tag \u0027gpio-fixes-for-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux\n\nPull gpio fixes from Bartosz Golaszewski:\n\n - fix interrupt handling in suspend and wakeup in gpio-vf610\n\n - fix a bug on setting direction to output in gpio-vf610\n\n - add a missing memset() in gpio ACPI code\n\n* tag \u0027gpio-fixes-for-v6.6-rc7\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:\n gpiolib: acpi: Add missing memset(0) to acpi_get_gpiod_from_data()\n gpio: vf610: set value before the direction to avoid a glitch\n gpio: vf610: mask the gpio irq in system suspend and support wakeup\n" } ], "next": "03027aa3a5c698b8fe1a0254284198cb1423481e" }