Pull hyperv updates from Wei Liu: "Minor patches from various people" * tag 'hyperv-next-signed-20220322' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux: x86/hyperv: Output host build info as normal Windows version number hv_balloon: rate-limit "Unhandled message" warning drivers: hv: log when enabling crash_kexec_post_notifiers hv_utils: Add comment about max VMbus packet size in VSS driver Drivers: hv: Compare cpumasks and not their weights in init_vp_index() Drivers: hv: Rename 'alloced' to 'allocated' Drivers: hv: vmbus: Use struct_size() helper in kmalloc()
Showing the changes to include/uapi/linux (1 of 8 files). Show all
Unified · Split
| @@ -90,6 +90,17 @@ struct hv_vss_check_dm_info { · 89 unmodified lines | |||
| 90 | __u32 flags; | 90 | __u32 flags; |
| 91 | } __attribute__((packed)); | 91 | } __attribute__((packed)); |
| 92 | 92 | ||
| 93 | /* | ||
| 94 | * struct hv_vss_msg encodes the fields that the Linux VSS | ||
| 95 | * driver accesses. However, FREEZE messages from Hyper-V contain | ||
| 96 | * additional LUN information that Linux doesn't use and are not | ||
| 97 | * represented in struct hv_vss_msg. A received FREEZE message may | ||
| 98 | * be as large as 6,260 bytes, so the driver must allocate at least | ||
| 99 | * that much space, not sizeof(struct hv_vss_msg). Other messages | ||
| 100 | * such as AUTO_RECOVER may be as large as 12,500 bytes. However, | ||
| 101 | * because the Linux VSS driver responds that it doesn't support | ||
| 102 | * auto-recovery, it should not receive such messages. | ||
| 103 | */ | ||
| 93 | struct hv_vss_msg { | 104 | struct hv_vss_msg { |
| 94 | union { | 105 | union { |
| 95 | struct hv_vss_hdr vss_hdr; | 106 | struct hv_vss_hdr vss_hdr; |