aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/rust/pin-init
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-07-27 09:31:32 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2025-07-27 09:31:32 -0700
commitb711733e89a3f84c8e1e56e2328f9a0fa5facc7c (patch)
tree73e93a338f15f4271a16de25a739e956fa0b0001 /rust/pin-init
parentMerge tag 'spi-fix-v6.16-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (diff)
parenttimekeeping: Zero initialize system_counterval when querying time from phc drivers (diff)
downloadwireguard-linux-b711733e89a3f84c8e1e56e2328f9a0fa5facc7c.tar.xz
wireguard-linux-b711733e89a3f84c8e1e56e2328f9a0fa5facc7c.zip
Merge tag 'timers-urgent-2025-07-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fix from Thomas Gleixner: "A single fix for the PTP systemcounter mechanism: The rework of this mechanism added a 'use_nsec' member to struct system_counterval. get_device_system_crosststamp() instantiates that struct on the stack and hands a pointer to the driver callback. Only the drivers which set use_nsec to true, initialize that field, but all others ignore it. As get_device_system_crosststamp() does not initialize the struct, the use_nsec field contains random stack content in those cases. That causes a miscalulation usually resulting in a failing range check in the best case. Initialize the structure before handing it to the drivers to cure that" * tag 'timers-urgent-2025-07-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: timekeeping: Zero initialize system_counterval when querying time from phc drivers
Diffstat (limited to 'rust/pin-init')
0 files changed, 0 insertions, 0 deletions