| Module Name | vmlinux |
|---|---|
| Version #1 | 3.14.4 |
| Version #2 | 3.15-rc6 |
| CPU Type | x86_64 |
| Subject | Binary Compatibility |
| Total Header Files | 832 |
|---|---|
| Total Source Files | 1526 |
| Total Objects | 1 |
| Total Symbols / Types | 17930 / 10047 |
| Verdict | Incompatible (49.8%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 387 |
| Removed Symbols | High | 194 |
| Problems with Data Types | High | 79 |
| Medium | 399 | |
| Low | 355 | |
| Problems with Symbols | High | 40 |
| Medium | 198 | |
| Low | 49 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 28 |
| Change | Effect | |
|---|---|---|
| 1 | Field clk has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field single has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tc_array has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field tc_array_len has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field files has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field subsys_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tmpl has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unconfirmed has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_on_last_close has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field refcount has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field shutdown_sleep has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_mapping has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field head has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field blocked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field master_list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field device has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hints has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field init_verbs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field user_pins has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hid_get_raw_report has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field hid_output_raw_report has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidinput_input_event has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field oss_dev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_plane has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acthd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field bbaddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field bbstate has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field cpu_ring_head has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field cpu_ring_tail has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field ctl has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field faddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field fault_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field head has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field instdone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field instpm has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 12 | Field instps has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field ipehr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field ipeir has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field rc_psmi has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field semaphore_mboxes has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | Field semaphore_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 18 | Field seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Field tail has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 20 | Field waiting has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_received has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field num_plane has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field pc8 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saveDPFC_CB_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field saveFBC_CFB_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field saveFBC_CONTROL2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field saveFBC_LL_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chsw_init has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field adapter has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field algo has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ifb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_weight has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_poll has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vendor_radiotap_bitmap has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vendor_radiotap_len has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field module has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field rx_skb_hook has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_lock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field neigh_tx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field rx_flags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field rx_np has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field pde has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unmap has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field map has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_req has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pre_schedule has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ew has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field min_cwnd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter type_mask has been changed from unsigned int (4 bytes) to unsigned long (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter portid of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter type has been changed from snd_device_type_t (4 bytes) to enum snd_device_type (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter acxt has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scops of type struct kernfs_syscall_ops* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 1st middle parameter kdops has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter devices has been changed from struct pci_dev*** (8 bytes) to struct dmar_dev_scope** (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter request_level has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter prefix has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th middle parameter ppos has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tim became passed at the different offset on the stack (-96 instead of -120). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 4th middle parameter map_and_fenceable has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter to of type struct i915_hw_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 6th middle parameter mappable has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter dev_priv has been changed from drm_i915_private_t* (8 bytes) to struct drm_i915_private* (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cmd of type unsigned int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type enum dev_pm_qos_req_type has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 9th parameter flags has been changed from int (4 bytes) to u64 (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 10th parameter flags has been changed from int (4 bytes) to u64 (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter memcg has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter user_ns has been changed from struct user_namespace* (8 bytes) to bool (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unbind has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field got_runtime_pm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field phy has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field target_pwr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field requests_done has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ivsize has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field blocksize has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wait_for_init_deassert has been changed from void(*)(atomic_t*) (8 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcomm has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed3 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field unnamed0 has been changed from 40 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 3 | Size of field unnamed2 has been changed from 32 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ipi_list has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field hash has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field completion_data has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 4 | Field rb_node has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field completion_data has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field flush has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field fifo_time has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of field csd has been changed from 40 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bssid_hint has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field channel_hint has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cur_cset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field dst_csets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field src_csets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field idx has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field kf_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field refcnt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field xattrs has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field base_cftset has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field module has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field mg_dst_cset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mg_node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field mg_preload_node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mg_src_cgrp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field mg_tasks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bound_on has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field release_completion has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Type of field card_dev has been changed from struct device* (8 bytes) to struct device (456 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field stop_cpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field freq_table has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field suspend_freq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field power has been changed from 88 bytes to 96 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field mode has been changed from 216 bytes to 208 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field hwmode has been changed from 216 bytes to 208 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field private_size has been removed from the middle position of this structural type. | 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field plane_type_property has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field anon_inode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field master_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field mode_config has been changed from 680 bytes to 688 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | The relative position of field agp_buffer_token has been changed from 39 to 43. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field buf_alloc has been changed from 7 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field buf_use has been changed from 6 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field context_flag has been changed from 17 to 24. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field control has been changed from 40 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field count_lock has been changed from 3 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field ctx_idr has been changed from 13 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field ctxlist has been changed from 11 to 18. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field ctxlist_mutex has been changed from 12 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field dev has been changed from 28 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field dma has been changed from 15 to 22. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field driver has been changed from 37 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field event_lock has been changed from 26 to 33. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field filelist has been changed from 8 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field irq_enabled has been changed from 16 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field last_context has been changed from 18 to 25. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field map_hash has been changed from 10 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 21 | The relative position of field maplist has been changed from 9 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 22 | The relative position of field max_vblank_count has been changed from 24 to 31. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 23 | The relative position of field mode_config has been changed from 43 to 44. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 24 | The relative position of field object_name_idr has been changed from 45 to 46. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 25 | The relative position of field open_count has been changed from 5 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 26 | The relative position of field pdev has been changed from 29 to 35. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 27 | The relative position of field primary has been changed from 41 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 28 | The relative position of field render has been changed from 42 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 29 | The relative position of field sigdata has been changed from 35 to 40. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 30 | The relative position of field struct_mutex has been changed from 4 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 31 | The relative position of field unplugged has been changed from 48 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 32 | The relative position of field vbl_lock has been changed from 22 to 29. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 33 | The relative position of field vblank_disable_allowed has been changed from 19 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 34 | The relative position of field vblank_disable_timer has been changed from 23 to 30. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 35 | The relative position of field vblank_event_list has been changed from 25 to 32. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 36 | The relative position of field vblank_time_lock has been changed from 21 to 28. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 37 | The relative position of field vma_offset_manager has been changed from 46 to 47. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 38 | The relative position of field vmalist has been changed from 14 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 39 | The relative position of field agp has been changed from 27 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field agp_buffer_map has been changed from 38 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field num_crtcs has been changed from 33 to 39. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field object_name_lock has been changed from 44 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field platformdev has been changed from 30 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field sg has been changed from 32 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field sigmask has been changed from 36 to 41. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field switch_power_state has been changed from 47 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field usbdev has been changed from 31 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field vblank has been changed from 20 to 27. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field vfs_inode has been changed from 560 bytes to 568 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_mb_cache has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field jited has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field orig_prog has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nrshadows has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field i_data has been changed from 168 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename2 has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field part0 has been changed from 560 bytes to 568 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field __dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_report has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field raw_request has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field groups has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_DOMAIN_AUDIO has been changed from 11 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_DOMAIN_INIT has been changed from 12 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_DOMAIN_NUM has been changed from 13 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member POWER_DOMAIN_VGA has been changed from 10 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member TRANSCODER_EDP has been changed from 15 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field present has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_plane_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field update_primary_plane has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acthd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field bbaddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field bbstate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field cpu_ring_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field fault_reg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field hangcheck_action has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field hangcheck_score has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field hws has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field hws_page has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field instps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 12 | Field ipehr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field rc_psmi has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field semaphore_mboxes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field semaphore_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field wa_batchbuffer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | The relative position of field num_requests has been changed from 5 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field requests has been changed from 4 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field batchbuffer has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field ctx has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field ringbuffer has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field error_msg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gab_ctl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field gac_eco has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field gam_ecochk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field gfx_mode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field reset_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field suspend_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field ring has been changed from 192 bytes to 928 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | The relative position of field done_reg has been changed from 11 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field extra_instdone has been changed from 10 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field fence has been changed from 12 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field forcewake has been changed from 6 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field overlay has been changed from 19 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field pipestat has been changed from 7 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field ring has been changed from 14 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field time has been changed from 13 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | Field hangcheck_action has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | Field hangcheck_score has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field active_bo has been changed from 15 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field active_bo_count has been changed from 17 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field ccid has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field derrmr has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field display has been changed from 20 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field eir has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field ier has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field pgtbl_er has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field pinned_bo has been changed from 16 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field pinned_bo_count has been changed from 18 to 20. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipestat_irq_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field regfile has been changed from 3088 bytes to 3072 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field uncore has been changed from 232 bytes to 184 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field display has been changed from 200 bytes to 208 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field gmbus has been changed from 4560 bytes to 4608 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Size of field pm has been changed from 1 byte to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Size of field power_domains has been changed from 112 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Size of field ring has been changed from 1536 bytes to 1760 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Type of field info has been changed from struct intel_device_info const* (8 bytes) to struct intel_device_info const (84 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field ref has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | The relative position of field pd_pages has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Size of field unnamed0 has been changed from 8 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 6 | The relative position of field unnamed0 has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field num_pt_pages has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field domain_use_count has been changed from int[13] (52 bytes) to int[24] (96 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_enabled has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field adapter has been changed from 672 bytes to 680 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_wake_work has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gen8_pt_pages has been changed from struct page* (8 bytes) to struct page**[4] (32 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 2 | The pointer level of field gen8_pt_pages has been increased from 1 to 2. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_role has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field hw has been changed from 152 bytes to 144 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field u has been changed from 880 bytes to 888 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field wdev has been changed from 272 bytes to 296 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mesh has been changed from 880 bytes to 888 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field unregister has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_cursor_height has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field max_cursor_width has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field new_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field new_enabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field plane_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Size of field base has been changed from 896 bytes to 888 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Size of field config has been changed from 608 bytes to 592 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field requested_mode has been changed from 216 bytes to 208 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field adjusted_mode has been changed from 216 bytes to 208 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 192 bytes to 200 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field dp has been changed from 920 bytes to 984 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field aux has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field last_backlight_off has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field last_power_cycle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field last_power_on has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cloneable has been changed from bool (1 byte) to unsigned int (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 192 bytes to 200 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field acthd has been changed from u32 (4 bytes) to u64 (8 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field acthd has been changed from 2 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field deadlock has been changed from 0 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field action has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field score has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_release_resources has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field irq_request_resources has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field chip has been changed from 192 bytes to 208 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field atomic_write_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dir_ops has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field argv has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field device has been changed from 3312 bytes to 3328 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field link has been changed from 4136 bytes to 4160 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field tdev has been changed from 448 bytes to 456 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field pm_result has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_flag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vendor_radiotap_align has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field vendor_radiotap_oui has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | Field vendor_radiotap_subns has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field o_list has been changed from struct list_head to struct hlist_bl_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field e_block_list has been changed from struct list_head to struct hlist_bl_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field map_pages has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_cache has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NR_ANON_TRANSPARENT_HUGEPAGES has been changed from 33 to 36. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member NR_FREE_CMA_PAGES has been changed from 34 to 37. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 35 to 38. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[35] (35 bytes) to s8[38] (38 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field node_zones has been changed from 6144 bytes to 6400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field inactive_age has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field vm_stat has been changed from atomic_long_t[35] (280 bytes) to atomic_long_t[38] (304 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from int (4 bytes) to u64 (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ct has been changed from 504 bytes to 488 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field xfrm has been changed from 896 bytes to 1152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field dev_port has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field tx_dropped has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field carrier_changes has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field csd has been changed from 40 bytes to 32 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field len has been changed from u8 (1 byte) to u16 (2 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field offset has been changed from u8[4] (4 bytes) to u16[4] (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field max_duration has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mstate has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field mtask has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field soft_reset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field aneg_done has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_wakeup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_latency_tolerance has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member DEV_PM_QOS_FLAGS has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_tolerance has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field latency_tolerance_req has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field resume_latency_req has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_constraint_value has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field n_pins has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field pin_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pincfg_mux has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field private_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field hrtick_csd has been changed from 40 bytes to 32 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | The relative position of field avg has been changed from 52 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field cfs_tasks has been changed from 33 to 34. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field cpu_power has been changed from 25 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field hrtick_csd has been changed from 42 to 43. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field hrtick_timer has been changed from 43 to 44. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field idle_balance has been changed from 26 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field nr_iowait has been changed from 22 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field rq_sched_info has been changed from 44 to 45. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field ttwu_local has been changed from 50 to 51. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field wake_list has been changed from 51 to 52. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field active_balance_work has been changed from 30 to 31. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field calc_load_active has been changed from 40 to 41. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field clock_task has been changed from 21 to 22. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field hrtick_csd_pending has been changed from 41 to 42. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field online has been changed from 32 to 33. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field push_cpu has been changed from 29 to 30. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field rq_cpu_time has been changed from 45 to 46. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field calc_load_update has been changed from 39 to 40. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field clock has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field cpu has been changed from 31 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field idle has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field next_balance has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field nr_uninterruptible has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field post_schedule has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field prev_mm has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field rd has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field sched_goidle has been changed from 48 to 49. | Applications will access incorrect memory when attempting to access this field. |
| 29 | The relative position of field sd has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 30 | The relative position of field active_balance has been changed from 28 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field age_stamp has been changed from 35 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field avg_idle has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field curr has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field idle_stamp has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field max_idle_balance_cost has been changed from 38 to 39. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field rt_avg has been changed from 34 to 35. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field sched_count has been changed from 47 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field stop has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field ttwu_count has been changed from 49 to 50. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field yld_count has been changed from 46 to 47. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field depth has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmacache has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vmacache_seqnum has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field se has been changed from 376 bytes to 384 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vpd_pg80_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vpd_pg83 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field vpd_pg80 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field vpd_pg83_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field sdev_dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Size of field sdev_gendev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field reap_ref has been changed from unsigned int to struct kref of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field shost_dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field shost_gendev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field firmware_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed0 has been changed from 11 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field unnamed1 has been changed from 42 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field unnamed2 has been changed from 44 to 43. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field tstamp has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field skb_mstamp has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field tstamp has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field unnamed0 has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 4 | Field csum has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field params has been changed from 216 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field llist has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unnamed0 has been removed from the middle position of this structural type. | 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[97] (776 bytes) to unsigned long[103] (824 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_rx_rate_vht_flag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field all_timers has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field enabled has been changed from bool (1 byte) to int (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field enabled has been changed from 19 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field print_max has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field ep0 has been changed from 64 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field monotonic_time_coarse has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field sys_tz has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field wall_time_coarse has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | Type of field seq has been changed from seqcount_t to unsigned int of different format. | This field may be incorrectly initialized or accessed by applications. |
| 5 | The relative position of field monotonic_time_sec has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field monotonic_time_snsec has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field wall_time_sec has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field wall_time_snsec has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[60] (480 bytes) to unsigned long[62] (496 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 448 bytes to 456 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field xfrm_policy_sk_bundle_lock has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field km has been changed from 24 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from union acpi_predefined_info[291] const (2037 bytes) to union acpi_predefined_info[293] const (2051 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2037 bytes to 2051 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been decreased from 1 to 0. | Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash. |
| 2 | Type of return value has been changed from struct tcf_common* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been decreased from 1 to 0. | Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash. |
| 2 | Type of return value has been changed from struct tcf_common* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter hinfo has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter hinfo has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter hinfo has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter bind became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_device_id[7] const (224 bytes) to struct pci_device_id[8] const (256 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter notify of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter desc has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter run_callbacks has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tset became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pos became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter root became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to char* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter radar_detect of type u8* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct pci_bus* (8 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter utv became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ts became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter uts became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter utv became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pinned of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter driver_data became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prev of type struct task_struct* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cmd has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter device_data became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ops became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter type became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter t became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 448 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter devices has been decreased from 3 to 2. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | The parameter cnt became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter devices became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter plane became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter encoder became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter link_bw became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter link_rate became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter file_priv became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter aflags of type enum drm_mm_allocator_flags has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter aflags of type enum drm_mm_allocator_flags has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mode became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter maxPitch has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter prime_fpriv became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 33 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 224 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shadow of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter ppos has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gfp_mask became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mapping became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter page became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gfp_mask became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mapping became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter page became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter i became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter udev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter drvdata became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter groups became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter name became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nonblocking has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter to_id has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter nonblocking has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wedged of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter error_msg of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mask became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pipe became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fmt of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter server became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter downclock_mode of type struct drm_display_mode* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1328 bytes) to struct drm_i915_private (14400 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mbox became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter val became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mbox became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter val became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 (4 bytes) to u64 (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mx of type struct nlattr* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter mx_len of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter allow_ipv6 of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter trig became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter inode has been changed from struct inode (560 bytes) to struct file (256 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tlb became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mm became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter newprot became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 3840 bytes to 4032 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter gfp has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 448 bytes to 440 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 448 bytes to 440 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 448 bytes to 440 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter handler became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter obj_handle became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter handle has been decreased from 2 to 1. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter page_mkwrite has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter size became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter vaddr became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 448 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 560 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 132 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rate_control_ops (96 bytes) to struct rate_control_ops const (88 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 96 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 3 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter handle became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 2200 bytes to 2248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 2592 bytes to 2584 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter dev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter q became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter req became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ret became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter starget became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 328 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter user_ns has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter name has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[316] const (2528 bytes) to sys_call_ptr_t[317] const (2536 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2528 bytes to 2536 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[353] const (2824 bytes) to sys_call_ptr_t[354] const (2832 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2824 bytes to 2832 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 128 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 128 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter call became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter data became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from char (1 byte) to struct tracepoint (40 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from char (1 byte) to struct tracepoint (40 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lend became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter lstart became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mapping became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 9696 bytes to 9760 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 480 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[35] (280 bytes) to atomic_long_t[38] (304 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 280 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[97] const (776 bytes) to char const*[102] const (816 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 776 bytes to 816 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 112 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter encap_type became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nexthdr became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter spi became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter net became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type struct xfrm_address_filter* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1016 bytes to 1032 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hotplug_notify has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field is_dock_station has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cleanup has been changed from int(*)(struct tc_action*, int) to void(*)(struct tc_action*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field start_engine has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alignmask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cipher_blocksize has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field walk_blocksize has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 112 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field wait_for_init_deassert has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proctitle has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 864 bytes to 880 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_bl_on has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field use_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 600 bytes to 648 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 360 bytes to 352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field elv has been renamed to rb_node. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ssid became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Field bssid became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Field ie became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 5 | Type of field ssid has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field bssid has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field ie has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rssi_thold has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 33 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field start_radar_detection has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_chan_def*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_chan_def*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field tdls_mgmt has been changed from int(*)(struct wiphy*, struct net_device*, u8*, u8, u8, u16, u8 const*, size_t) to int(*)(struct wiphy*, struct net_device*, u8*, u8, u8, u16, u32, u8 const*, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rssi_thold has been renamed to min_rssi_thold. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_cac_ms has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 56 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_ap_assoc_sta has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cac_time_ms has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 272 bytes to 296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cur_cgrp has been renamed to cur_task. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 176 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field write_string has been changed from int(*)(struct cgroup_subsys_state*, struct cftype*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, char*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 424 bytes to 392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field root has been changed from struct cgroupfs_root (4680 bytes) to struct cgroup_root (4640 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field dentry has been renamed to kn. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field name has been renamed to subsys_mask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field root has been changed from struct cgroupfs_root (4680 bytes) to struct cgroup_root (4640 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field id has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field cftsets has been renamed to cfts. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 504 bytes to 488 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field generation has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field dying has been renamed to pcpu_lists. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 784 bytes to 792 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 688 bytes to 1104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field card_dev has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 456 bytes to 464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field transition_lock has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field transition_ongoing has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field transition_wait has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 296 bytes to 336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ll has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 448 bytes to 456 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field devices has been decreased from 2 to 1. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 2 | Type of field devices has been changed from struct pci_dev** to struct dmar_dev_scope*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 896 bytes to 888 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field fb has been renamed to primary. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 680 bytes to 688 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field num_total_plane has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field num_plane has been renamed to num_overlay_plane. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 384 bytes to 392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1328 bytes to 1392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The relative position of private field dev_private has been changed from 34 to 5. | Size of the inclusive type has been changed. |
| 3 | Field ref has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field universal_planes has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 648 bytes to 656 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct sock*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 224 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field phys_stack has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 32 bytes to 33 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 464 bytes to 472 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 960 bytes to 968 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field bpf_func has been changed from unsigned int(*)(struct sk_buff const*, struct sock_filter const*) to unsigned int(*)(struct sk_buff const*, struct sock_filter_int const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field insnsi has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field is_partially_uptodate has been changed from int(*)(struct page*, read_descriptor_t*, unsigned long) to int(*)(struct page*, unsigned long, unsigned long). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 560 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been renamed to unnamed0. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 712 bytes to 720 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 560 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field can_do_streams has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1360 bytes to 1744 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 7296 bytes to 7288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 472 bytes to 480 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field port_owner has been changed from struct dev_state to struct usb_dev_state. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 672 bytes to 680 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 504 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 200 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field comm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field pid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field vm_info has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 48 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field cpu_ring_tail has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field ctl has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field faddr has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field instdone has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field instpm has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 10 | Field ipeir has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 11 | Field seqno has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 12 | Field tail has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 13 | Field waiting has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1008 bytes to 1472 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 14248 bytes to 14400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field display_irqs_enabled has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field pm_rps_events has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field suspend_count has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | The pointer level of field info has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field clear_range has been changed from void(*)(struct i915_address_space*, unsigned int, unsigned int, bool) to void(*)(struct i915_address_space*, uint64_t, uint64_t, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field insert_entries has been changed from void(*)(struct i915_address_space*, struct sg_table*, unsigned int, enum i915_cache_level) to void(*)(struct i915_address_space*, struct sg_table*, uint64_t, enum i915_cache_level). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field busy has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ring has been renamed to last_ring. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field debug_dump has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field switch_mm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 392 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Base type of field enable has been changed from int(*)(struct drm_device*) to int(*)(struct i915_hw_ppgtt*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field num_pd_pages has been changed from int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field data has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | Type of field data has been changed from void* to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field set has been renamed to ops. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field irqs_disabled has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field regsave has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 1 byte to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3088 bytes to 3072 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind_vma has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field pin_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field unbind_vma has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 168 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rp0_freq has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cur_delay has been renamed to cur_freq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field hw_max has been renamed to rp1_freq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field max_delay has been renamed to max_freq_softlimit. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 5 | Field min_delay has been renamed to min_freq_softlimit. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 6 | Field rp0_delay has been renamed to efficient_freq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 7 | Field rp1_delay has been renamed to min_freq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field rpe_delay has been renamed to max_freq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 760 bytes to 768 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_wake_timer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 232 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 880 bytes to 888 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2416 bytes to 2448 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 880 bytes to 888 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field queue_xmit has been changed from int(*)(struct sk_buff*, struct flowi*) to int(*)(struct sock*, struct sk_buff*, struct flowi*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1088 bytes to 1096 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field segment has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 800 bytes to 808 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2480 bytes to 2488 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 608 bytes to 592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1160 bytes to 1232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_aux_clock_divider has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field get_aux_send_ctl has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 920 bytes to 984 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field use_tps3 has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field preferred_bpp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 328 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 296 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_table_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cmd_tables has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field get_cmd_length_mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field master_reg_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field master_reg_table has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field reg_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field reg_table has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Size of this type has been changed from 384 bytes to 440 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Size of field hangcheck has been changed from 20 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field deactivate_waitq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field syscall_ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 64 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2312 bytes to 2336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1656 bytes to 1664 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4136 bytes to 4160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field status_driver_data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field ack_signal has been changed from int to s32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 592 bytes to 584 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field sched_scan_stop has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_vif*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field status has been changed from 20 bytes to 40 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field c_block_hash has been changed from struct list_head (16 bytes) to struct hlist_bl_head (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Base type of field c_index_hash has been changed from struct list_head (16 bytes) to struct hlist_bl_head (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_block_hash_p has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field e_index_hash_p has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 88 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field e_refcnt has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_pgoff has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field pte has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 32 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmacache_seqnum has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 15616 bytes to 15872 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1536 bytes to 1600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field spin_mlock has been renamed to osq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3840 bytes to 4032 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field ndo_netpoll_setup has been changed from int(*)(struct net_device*, struct netpoll_info*, gfp_t) to int(*)(struct net_device*, struct netpoll_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 136 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 264 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 448 bytes to 440 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NL80211_ATTR_MAX has been changed from 199 to 203. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member __NL80211_ATTR_AFTER_LAST has been changed from 200 to 204. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 48 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 752 bytes to 760 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1568 bytes to 1576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 488 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 480 bytes to 488 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 840 bytes to 848 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 808 bytes to 816 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field has_fixups has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 496 bytes to 504 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_late_suspended has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field is_noirq_suspended has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 88 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 1 has been changed from DEV_PM_QOS_LATENCY to DEV_PM_QOS_RESUME_LATENCY. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field latency has been renamed to resume_latency. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 592 bytes to 600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 688 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 560 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field verify has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 88 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_attr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field pin_attr_group has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field pin_dev_attr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 4512 bytes to 4600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 560 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field height has been renamed to path. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field parent has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field ops has been changed from struct rate_control_ops* to struct rate_control_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 112 has been changed from BOOT_CF9 to BOOT_CF9_FORCE. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 113 has been changed from BOOT_CF9_COND to BOOT_CF9_SAFE. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_cac_ms has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1000 bytes to 1008 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2592 bytes to 2584 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 208 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field pick_next_task has been changed from struct task_struct*(*)(struct rq*) to struct task_struct*(*)(struct rq*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 376 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2200 bytes to 2248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1304 bytes to 1352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 576 bytes to 544 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1328 bytes to 1344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_pool has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cmd_size has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 328 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field insns has been renamed to insnsi. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 680 bytes to 816 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rxhash has been renamed to hash. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field l4_rxhash has been renamed to l4_hash. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_id has been renamed to csum. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field dma_cookie has been renamed to unnamed0. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved_tailroom has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 2 | Field mark has been renamed to napi_id. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field dropcount has been renamed to dma_cookie. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 776 bytes to 824 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sk_data_ready has been changed from void(*)(struct sock*, int) to void(*)(struct sock*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1040 bytes to 1048 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1584 bytes to 1592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcpi_max_pacing_rate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field tcpi_pacing_rate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 104 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mdev has been renamed to mdev_us. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field mdev_max has been renamed to mdev_max_us. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field rttvar has been renamed to rttvar_us. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field srtt has been renamed to srtt_us. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 576 bytes to 584 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 800 bytes to 808 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allow_instances has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Base type of field flag_changed has been changed from int(*)(struct tracer*, u32, int) to int(*)(struct trace_array*, u32, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field set_flag has been changed from int(*)(u32, u32, int) to int(*)(struct trace_array*, u32, u32, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1056 bytes to 1072 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field streams has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 544 bytes to 552 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cycle_last has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field monotonic_time_coarse_nsec has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field monotonic_time_coarse_sec has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field mult has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field tz_minuteswest has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field wall_time_coarse_nsec has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field wall_time_coarse_sec has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Size of this type has been changed from 112 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 10 | Field shift has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 11 | Field tz_dsttime has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 12 | Field vclock_mode has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 13 | Type of field monotonic_time_sec has been changed from time_t to gtod_long_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 14 | Type of field wall_time_sec has been changed from time_t to gtod_long_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 480 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 456 bytes to 464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flow_cache_gc_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field flow_cache_gc_lock has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field flow_cache_gc_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field flow_cache_genid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field flow_cache_flush_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field flow_flush_sem has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field flow_cache_global has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Size of this type has been changed from 896 bytes to 1152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_alive has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 80 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 752 bytes to 760 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct sock*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field filter has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field proto has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field unnamed0 has been renamed to dying. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter iov has been changed from struct sg_iovec* to struct sg_iovec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter iov has been changed from struct sg_iovec* to struct sg_iovec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter iov has been changed from struct sg_iovec* to struct sg_iovec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Base type of 2nd parameter init has been changed from void(*)(void*, struct blk_mq_hw_ctx*, struct request*, unsigned int) to int(*)(void*, struct blk_mq_hw_ctx*, struct request*, unsigned int). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter desc has been renamed to from. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter from has been renamed to count. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter desc has been changed from read_descriptor_t* to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct cfg80211_ops to struct cfg80211_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 0 to 1. | Applications will treat the return value as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mask has been renamed to bars. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter handle has been renamed to adev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter handle has been changed from acpi_handle to struct acpi_device*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter priv has been renamed to is_primary. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter flags has been renamed to sflags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter flags has been renamed to sflags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter lace has been renamed to interlaced. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter buf has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mask has been renamed to status_mask. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mask has been renamed to status_mask. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter dev_priv has been changed from drm_i915_private_t* to struct drm_i915_private*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from void* to void const*const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter handle has been changed from acpi_handle* to acpi_handle. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter reason has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter reason has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ops has been changed from struct rate_control_ops* to struct rate_control_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ops has been changed from struct rate_control_ops* to struct rate_control_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rate_control_ops to struct rate_control_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter channel has been renamed to rx_channel. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter channel has been renamed to rx_channel. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter user_ns has been renamed to may_report_filterinfo. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to tp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to tp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field reserved has been changed from 3 bytes to 22 bits. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed1 has been changed from 24 bytes to 16 bytes. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member DRM_MM_SEARCH_BELOW with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_DOMAIN_PORT_CRT with value 19 has been added. | No effect. |
| 2 | The member POWER_DOMAIN_PORT_DDI_A_2_LANES with value 10 has been added. | No effect. |
| 3 | The member POWER_DOMAIN_PORT_DDI_A_4_LANES with value 11 has been added. | No effect. |
| 4 | The member POWER_DOMAIN_PORT_DDI_B_2_LANES with value 12 has been added. | No effect. |
| 5 | The member POWER_DOMAIN_PORT_DDI_B_4_LANES with value 13 has been added. | No effect. |
| 6 | The member POWER_DOMAIN_PORT_DDI_C_2_LANES with value 14 has been added. | No effect. |
| 7 | The member POWER_DOMAIN_PORT_DDI_C_4_LANES with value 15 has been added. | No effect. |
| 8 | The member POWER_DOMAIN_PORT_DDI_D_2_LANES with value 16 has been added. | No effect. |
| 9 | The member POWER_DOMAIN_PORT_DDI_D_4_LANES with value 17 has been added. | No effect. |
| 10 | The member POWER_DOMAIN_PORT_DSI with value 18 has been added. | No effect. |
| 11 | The member POWER_DOMAIN_PORT_OTHER with value 20 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member _PIPE_EDP with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_MAX_TRANSCODERS with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member WORKINGSET_ACTIVATE with value 34 has been added. | No effect. |
| 2 | The member WORKINGSET_NODERECLAIM with value 35 has been added. | No effect. |
| 3 | The member WORKINGSET_REFAULT with value 33 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_ATTR_MAC_HINT with value 200 has been added. | No effect. |
| 2 | The member NL80211_ATTR_MAX_AP_ASSOC_STA with value 202 has been added. | No effect. |
| 3 | The member NL80211_ATTR_TDLS_PEER_CAPABILITY with value 203 has been added. | No effect. |
| 4 | The member NL80211_ATTR_WIPHY_FREQ_HINT with value 201 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_QSGMII with value 15 has been added. | No effect. |
| 2 | The member PHY_INTERFACE_MODE_MAX with value 16 has been added. | No effect. |
| 3 | The member PHY_INTERFACE_MODE_MOCA with value 14 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member DEV_PM_QOS_LATENCY_TOLERANCE with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed0 has been changed from 4 bytes to 8 bytes. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.14.4 |
| Version #2 | 3.15-rc6 |
| CPU Type | x86_64 |
| Subject | Source Compatibility |
| Total Header Files | 832 |
|---|---|
| Total Source Files | 1526 |
| Total Objects | 1 |
| Total Symbols / Types | 18022 / 10047 |
| Verdict | Incompatible (46.4%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 393 |
| Removed Symbols | High | 271 |
| Problems with Data Types | High | 150 |
| Medium | 18 | |
| Low | 273 | |
| Problems with Symbols | High | 32 |
| Medium | 62 | |
| Low | 29 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 166 |
| Other Changes in Symbols | - | 29 |
| Change | Effect | |
|---|---|---|
| 1 | Field clk has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ahci_host_priv' has no member named 'clk'. |
| Change | Effect | |
|---|---|---|
| 1 | Field blocksize has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct blkcipher_walk' has no member named 'blocksize'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcomm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct linux_binprm' has no member named 'tcomm'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request' has no member named 'hash'. |
| Change | Effect | |
|---|---|---|
| 1 | Field completion_data has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field rb_node has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field elv has been renamed to rb_node. | Recompilation of a client program may be broken with the error message: anon-union-blkdev.h-137 has no member named elv. |
| Change | Effect | |
|---|---|---|
| 1 | Field rssi_thold has been renamed to min_rssi_thold. | Recompilation of a client program may be broken with the error message: struct cfg80211_sched_scan_request has no member named rssi_thold. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'channel'. |
| Change | Effect | |
|---|---|---|
| 1 | Field idx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_taskset' has no member named 'idx'. |
| 2 | Field single has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_taskset' has no member named 'single'. |
| 3 | Field tc_array has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_taskset' has no member named 'tc_array'. |
| 4 | Field tc_array_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_taskset' has no member named 'tc_array_len'. |
| 5 | Field cur_cgrp has been renamed to cur_task. | Recompilation of a client program may be broken with the error message: struct cgroup_taskset has no member named cur_cgrp. |
| Change | Effect | |
|---|---|---|
| 1 | Field xattrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'xattrs'. |
| 2 | Field files has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'files'. |
| 3 | Field name has been renamed to subsys_mask. | Recompilation of a client program may be broken with the error message: struct cgroup has no member named name. |
| 4 | Field dentry has been renamed to kn. | Recompilation of a client program may be broken with the error message: struct cgroup has no member named dentry. |
| Change | Effect | |
|---|---|---|
| 1 | Field module has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'module'. |
| 2 | Field base_cftset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'base_cftset'. |
| 3 | Field subsys_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'subsys_id'. |
| 4 | Field cftsets has been renamed to cfts. | Recompilation of a client program may be broken with the error message: struct cgroup_subsys has no member named cftsets. |
| Change | Effect | |
|---|---|---|
| 1 | Field tmpl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ct' has no member named 'tmpl'. |
| 2 | Field unconfirmed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ct' has no member named 'unconfirmed'. |
| 3 | Field dying has been renamed to pcpu_lists. | Recompilation of a client program may be broken with the error message: struct netns_ct has no member named dying. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_on_last_close has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snd_card' has no member named 'free_on_last_close'. |
| 2 | Field refcount has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snd_card' has no member named 'refcount'. |
| 3 | Field shutdown_sleep has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snd_card' has no member named 'shutdown_sleep'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ll has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb has been renamed to primary. | Recompilation of a client program may be broken with the error message: struct drm_crtc has no member named fb. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_plane has been renamed to num_overlay_plane. | Recompilation of a client program may be broken with the error message: struct drm_mode_config has no member named num_plane. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_mapping has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'dev_mapping'. |
| Change | Effect | |
|---|---|---|
| 1 | Field head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_master' has no member named 'head'. |
| 2 | Field blocked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_master' has no member named 'blocked'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_minor' has no member named 'device'. |
| 2 | Field master_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_minor' has no member named 'master_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct ftrace_event_call has no member named name. |
| Change | Effect | |
|---|---|---|
| 1 | Field hints has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_codec' has no member named 'hints'. |
| 2 | Field init_verbs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_codec' has no member named 'init_verbs'. |
| 3 | Field user_pins has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_codec' has no member named 'user_pins'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hid_get_raw_report has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hid_device' has no member named 'hid_get_raw_report'. |
| 2 | Field hid_output_raw_report has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hid_device' has no member named 'hid_output_raw_report'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidinput_input_event has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hid_ll_driver' has no member named 'hidinput_input_event'. |
| Change | Effect | |
|---|---|---|
| 1 | Field oss_dev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snd_hwdep' has no member named 'oss_dev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_plane has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'update_plane'. |
| Change | Effect | |
|---|---|---|
| 1 | Field acthd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'acthd'. |
| 2 | Field bbaddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bbaddr'. |
| 3 | Field bbstate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bbstate'. |
| 4 | Field cpu_ring_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'cpu_ring_head'. |
| 5 | Field cpu_ring_tail has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'cpu_ring_tail'. |
| 6 | Field ctl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'ctl'. |
| 7 | Field faddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'faddr'. |
| 8 | Field fault_reg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'fault_reg'. |
| 9 | Field hangcheck_action has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'hangcheck_action'. |
| 10 | Field hangcheck_score has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'hangcheck_score'. |
| 11 | Field head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'head'. |
| 12 | Field instdone has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'instdone'. |
| 13 | Field instpm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'instpm'. |
| 14 | Field instps has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'instps'. |
| 15 | Field ipehr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'ipehr'. |
| 16 | Field ipeir has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'ipeir'. |
| 17 | Field rc_psmi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'rc_psmi'. |
| 18 | Field semaphore_mboxes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'semaphore_mboxes'. |
| 19 | Field semaphore_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'semaphore_seqno'. |
| 20 | Field seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'seqno'. |
| 21 | Field tail has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'tail'. |
| 22 | Field waiting has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'waiting'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'pin_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_received has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'irq_received'. |
| 2 | Field num_plane has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'num_plane'. |
| 3 | Field pc8 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'pc8'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ring has been renamed to last_ring. | Recompilation of a client program may be broken with the error message: struct i915_hw_context has no member named ring. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_pt_pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'num_pt_pages'. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_power_well' has no member named 'is_enabled'. |
| 2 | Field set has been renamed to ops. | Recompilation of a client program may be broken with the error message: struct i915_power_well has no member named set. |
| Change | Effect | |
|---|---|---|
| 1 | Field saveDPFC_CB_BASE has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_suspend_saved_registers' has no member named 'saveDPFC_CB_BASE'. |
| 2 | Field saveFBC_CFB_BASE has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_suspend_saved_registers' has no member named 'saveFBC_CFB_BASE'. |
| 3 | Field saveFBC_CONTROL2 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_suspend_saved_registers' has no member named 'saveFBC_CONTROL2'. |
| 4 | Field saveFBC_LL_BASE has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_suspend_saved_registers' has no member named 'saveFBC_LL_BASE'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_delay has been renamed to cur_freq. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named cur_delay. |
| 2 | Field hw_max has been renamed to rp1_freq. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named hw_max. |
| 3 | Field max_delay has been renamed to max_freq_softlimit. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named max_delay. |
| 4 | Field min_delay has been renamed to min_freq_softlimit. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named min_delay. |
| 5 | Field rp0_delay has been renamed to efficient_freq. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named rp0_delay. |
| 6 | Field rp1_delay has been renamed to min_freq. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named rp1_delay. |
| 7 | Field rpe_delay has been renamed to max_freq. | Recompilation of a client program may be broken with the error message: struct intel_gen6_power_mgmt has no member named rpe_delay. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_wake_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_uncore' has no member named 'force_wake_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field chsw_init has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_mesh' has no member named 'chsw_init'. |
| Change | Effect | |
|---|---|---|
| 1 | Field adapter has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dp' has no member named 'adapter'. |
| 2 | Field algo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dp' has no member named 'algo'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ifb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_fbdev' has no member named 'ifb'. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kernfs_node' has no member named 'u'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir_ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kernfs_root' has no member named 'dir_ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_result has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'pm_result'. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_weight has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_hw' has no member named 'napi_weight'. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_poll has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_ops' has no member named 'napi_poll'. |
| Change | Effect | |
|---|---|---|
| 1 | Field vendor_radiotap_align has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'vendor_radiotap_align'. |
| 2 | Field vendor_radiotap_bitmap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'vendor_radiotap_bitmap'. |
| 3 | Field vendor_radiotap_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'vendor_radiotap_len'. |
| 4 | Field vendor_radiotap_oui has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'vendor_radiotap_oui'. |
| 5 | Field vendor_radiotap_subns has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'vendor_radiotap_subns'. |
| Change | Effect | |
|---|---|---|
| 1 | Field module has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rate_control_ops' has no member named 'module'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_cache has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'mmap_cache'. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field spin_mlock has been renamed to osq. | Recompilation of a client program may be broken with the error message: struct mutex has no member named spin_mlock. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll' has no member named 'rx'. |
| 2 | Field rx_skb_hook has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll' has no member named 'rx_skb_hook'. |
| Change | Effect | |
|---|---|---|
| 1 | Field neigh_tx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll_info' has no member named 'neigh_tx'. |
| 2 | Field rx_np has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll_info' has no member named 'rx_np'. |
| 3 | Field rx_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll_info' has no member named 'rx_lock'. |
| 4 | Field rx_flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll_info' has no member named 'rx_flags'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_rpc_ops' has no member named 'rename'. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct device_node' has no member named 'kref'. |
| 2 | Field pde has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct device_node' has no member named 'pde'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mstate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_sriov' has no member named 'mstate'. |
| 2 | Field mtask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_sriov' has no member named 'mtask'. |
| Change | Effect | |
|---|---|---|
| 1 | Field map has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pipe_buf_operations' has no member named 'map'. |
| 2 | Field unmap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pipe_buf_operations' has no member named 'unmap'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 1 has been changed from DEV_PM_QOS_LATENCY to DEV_PM_QOS_RESUME_LATENCY. | Recompilation of a client program may be broken with the error message: 'DEV_PM_QOS_LATENCY' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_req has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dev_pm_qos' has no member named 'latency_req'. |
| 2 | Field latency has been renamed to resume_latency. | Recompilation of a client program may be broken with the error message: struct dev_pm_qos has no member named latency. |
| Change | Effect | |
|---|---|---|
| 1 | Field height has been renamed to path. | Recompilation of a client program may be broken with the error message: struct radix_tree_node has no member named height. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 112 has been changed from BOOT_CF9 to BOOT_CF9_FORCE. | Recompilation of a client program may be broken with the error message: 'BOOT_CF9' was not declared in this scope. |
| 2 | Name of member with value 113 has been changed from BOOT_CF9_COND to BOOT_CF9_SAFE. | Recompilation of a client program may be broken with the error message: 'BOOT_CF9_COND' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field pre_schedule has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_class' has no member named 'pre_schedule'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ew has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct scsi_target' has no member named 'ew'. |
| Change | Effect | |
|---|---|---|
| 1 | Field insns has been renamed to insnsi. | Recompilation of a client program may be broken with the error message: struct seccomp_filter has no member named insns. |
| Change | Effect | |
|---|---|---|
| 1 | Field tstamp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sk_buff' has no member named 'tstamp'. |
| 2 | Field rxhash has been renamed to hash. | Recompilation of a client program may be broken with the error message: struct sk_buff has no member named rxhash. |
| 3 | Field l4_rxhash has been renamed to l4_hash. | Recompilation of a client program may be broken with the error message: struct sk_buff has no member named l4_rxhash. |
| Change | Effect | |
|---|---|---|
| 1 | Field csum has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field unnamed0 has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_id has been renamed to csum. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-519 has no member named napi_id. |
| 2 | Field dma_cookie has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-519 has no member named dma_cookie. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved_tailroom has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field dropcount has been renamed to dma_cookie. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-527 has no member named dropcount. |
| 3 | Field mark has been renamed to napi_id. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-527 has no member named mark. |
| Change | Effect | |
|---|---|---|
| 1 | Field min_cwnd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_congestion_ops' has no member named 'min_cwnd'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mdev has been renamed to mdev_us. | Recompilation of a client program may be broken with the error message: struct tcp_sock has no member named mdev. |
| 2 | Field mdev_max has been renamed to mdev_max_us. | Recompilation of a client program may be broken with the error message: struct tcp_sock has no member named mdev_max. |
| 3 | Field rttvar has been renamed to rttvar_us. | Recompilation of a client program may be broken with the error message: struct tcp_sock has no member named rttvar. |
| 4 | Field srtt has been renamed to srtt_us. | Recompilation of a client program may be broken with the error message: struct tcp_sock has no member named srtt. |
| Change | Effect | |
|---|---|---|
| 1 | Field clock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vsyscall_gtod_data' has no member named 'clock'. |
| 2 | Field monotonic_time_coarse has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vsyscall_gtod_data' has no member named 'monotonic_time_coarse'. |
| 3 | Field sys_tz has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vsyscall_gtod_data' has no member named 'sys_tz'. |
| 4 | Field wall_time_coarse has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vsyscall_gtod_data' has no member named 'wall_time_coarse'. |
| Change | Effect | |
|---|---|---|
| 1 | Field xfrm_policy_sk_bundle_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_xfrm' has no member named 'xfrm_policy_sk_bundle_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been renamed to dying. | Recompilation of a client program may be broken with the error message: struct xfrm_state_walk has no member named unnamed0. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter a of type struct tc_action* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter p has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter portid of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter acxt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scops of type struct kernfs_syscall_ops* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 3 | 1st middle parameter kdops has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter request_level has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter prefix has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th middle parameter ppos has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 4th middle parameter map_and_fenceable has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter to of type struct i915_hw_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 6th middle parameter mappable has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cmd of type unsigned int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type enum dev_pm_qos_req_type has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter memcg has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sk of type struct sock* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field wait_for_init_deassert has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bssid became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct cfg80211_connect_params::bssid'. |
| 2 | Field ssid became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct cfg80211_connect_params::ssid'. |
| 3 | Field ie became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct cfg80211_connect_params::ie'. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field root has been changed from struct cgroupfs_root to struct cgroup_root of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field root has been changed from struct cgroupfs_root to struct cgroup_root of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field card_dev has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field devices has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field info has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field data has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field gen8_pt_pages has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field o_list has been changed from struct list_head to struct hlist_bl_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field c_block_hash has been changed from struct list_head to struct hlist_bl_head of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of field c_index_hash has been changed from struct list_head to struct hlist_bl_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field e_block_list has been changed from struct list_head to struct hlist_bl_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rate_control_ref::ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field reap_ref has been changed from unsigned int to struct kref of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field seq has been changed from seqcount_t to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter hinfo has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter hinfo has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter hinfo has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter notify of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter desc has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter run_callbacks has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter radar_detect of type u8* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct pci_bus* (8 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pinned of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prev of type struct task_struct* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cmd has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter devices has been increased from 3 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter aflags of type enum drm_mm_allocator_flags has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter aflags of type enum drm_mm_allocator_flags has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter maxPitch has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shadow of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter ppos has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nonblocking has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter to_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter nonblocking has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wedged of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter error_msg of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fmt of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter downclock_mode of type struct drm_display_mode* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_i915_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mx of type struct nlattr* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter mx_len of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter allow_ipv6 of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter inode has been changed from struct inode to struct file of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter gfp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter handle has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter page_mkwrite has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter user_ns has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter name has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from char to struct tracepoint of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from char to struct tracepoint of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type struct xfrm_address_filter* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hotplug_notify has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_dock_station has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unbind has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cleanup has been changed from int(*)(struct tc_action*, int) to void(*)(struct tc_action*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field clks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field got_runtime_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field phy has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field start_engine has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field target_pwr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field requests_done has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alignmask has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cipher_blocksize has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ivsize has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field walk_blocksize has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wait_for_init_deassert has been changed from void(*)(atomic_t*) to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field proctitle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_bl_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field use_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bssid_hint has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field channel_hint has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rssi_thold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field start_radar_detection has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_chan_def*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_chan_def*, u32). | Recompilation of a client program may be broken. |
| 2 | Base type of field tdls_mgmt has been changed from int(*)(struct wiphy*, struct net_device*, u8*, u8, u8, u16, u8 const*, size_t) to int(*)(struct wiphy*, struct net_device*, u8*, u8, u8, u16, u32, u8 const*, size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_cac_ms has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_ap_assoc_sta has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cac_time_ms has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csets has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cur_cset has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dst_csets has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field src_csets has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kf_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field write_string has been changed from int(*)(struct cgroup_subsys_state*, struct cftype*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, char*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mg_dst_cset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mg_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mg_tasks has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mg_src_cgrp has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mg_preload_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bound_on has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field generation has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field release_completion has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field card_dev has been changed from struct device* to struct device. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field stop_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field freq_table has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field suspend_freq has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field transition_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field transition_ongoing has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field transition_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field devices has been changed from struct pci_dev** to struct dmar_dev_scope*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_total_plane has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field plane_type_property has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field anon_inode has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field master_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ref has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field universal_planes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct sock*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field phys_stack has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_mb_cache has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field jited has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field orig_prog has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field bpf_func has been changed from unsigned int(*)(struct sk_buff const*, struct sock_filter const*) to unsigned int(*)(struct sk_buff const*, struct sock_filter_int const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nrshadows has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field is_partially_uptodate has been changed from int(*)(struct page*, read_descriptor_t*, unsigned long) to int(*)(struct page*, unsigned long, unsigned long). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename2 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field can_do_streams has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_report has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field raw_request has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field port_owner has been changed from struct dev_state to struct usb_dev_state. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field groups has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field present has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_plane_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field update_primary_plane has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acthd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bbaddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field bbstate has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field comm has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cpu_ring_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field cpu_ring_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ctl has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field faddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field fault_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field hangcheck_action has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field hangcheck_score has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field head has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field hws has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field hws_page has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field instdone has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field instpm has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field instps has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field ipehr has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field ipeir has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field pid has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field rc_psmi has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field semaphore_mboxes has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field semaphore_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Field tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 26 | Field vm_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 27 | Field wa_batchbuffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 28 | Field waiting has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field error_msg has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gab_ctl has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gac_eco has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field gam_ecochk has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field gfx_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field reset_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field suspend_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field display_irqs_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pipestat_irq_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pm_rps_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field suspend_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field info has been changed from struct intel_device_info const* to struct intel_device_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field clear_range has been changed from void(*)(struct i915_address_space*, unsigned int, unsigned int, bool) to void(*)(struct i915_address_space*, uint64_t, uint64_t, bool). | Recompilation of a client program may be broken. |
| 2 | Base type of field insert_entries has been changed from void(*)(struct i915_address_space*, struct sg_table*, unsigned int, enum i915_cache_level) to void(*)(struct i915_address_space*, struct sg_table*, uint64_t, enum i915_cache_level). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field busy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field debug_dump has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ref has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field switch_mm has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Base type of field enable has been changed from int(*)(struct drm_device*) to int(*)(struct i915_hw_ppgtt*). | Recompilation of a client program may be broken. |
| 7 | Type of field num_pd_pages has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field domain_use_count has been changed from int[13] to int[24]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from void* to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irqs_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field regsave has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind_vma has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pin_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field unbind_vma has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rp0_freq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_wake_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gen8_pt_pages has been changed from struct page* to struct page**[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_role has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field queue_xmit has been changed from int(*)(struct sk_buff*, struct flowi*) to int(*)(struct sock*, struct sk_buff*, struct flowi*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field segment has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unregister has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_cursor_height has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_cursor_width has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field new_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field new_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field plane_config has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aux has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_aux_clock_divider has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field get_aux_send_ctl has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field last_backlight_off has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field last_power_cycle has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field last_power_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field use_tps3 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cloneable has been changed from bool to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field preferred_bpp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_table_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cmd_tables has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field get_cmd_length_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field master_reg_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field master_reg_table has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field reg_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field reg_table has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field acthd has been changed from u32 to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_release_resources has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field irq_request_resources has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field atomic_write_len has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field syscall_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field deactivate_waitq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field argv has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field status_driver_data has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sched_scan_stop has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_vif*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_flag has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_block_hash_p has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field e_index_hash_p has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field e_refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_pgoff has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pte has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field map_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmacache_seqnum has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[35] to s8[38]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field inactive_age has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field vm_stat has been changed from atomic_long_t[35] to atomic_long_t[38]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from int to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tx_dropped has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dev_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field carrier_changes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field ndo_netpoll_setup has been changed from int(*)(struct net_device*, struct netpoll_info*, gfp_t) to int(*)(struct net_device*, struct netpoll_info*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field len has been changed from u8 to u16. | Recompilation of a client program may be broken. |
| 2 | Type of field offset has been changed from u8[4] to u16[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_duration has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_fixups has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aneg_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field soft_reset has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_late_suspended has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_noirq_suspended has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_latency_tolerance has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_tolerance has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field latency_tolerance_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field resume_latency_req has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_constraint_value has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field n_pins has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pin_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field verify has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_attr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pin_attr_group has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pin_dev_attr has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pincfg_mux has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_cac_ms has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field pick_next_task has been changed from struct task_struct*(*)(struct rq*) to struct task_struct*(*)(struct rq*, struct task_struct*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field depth has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmacache has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vmacache_seqnum has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vpd_pg80_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vpd_pg83 has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field vpd_pg80 has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vpd_pg83_len has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_pool has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cmd_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field firmware_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field llist has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[97] to unsigned long[103]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sk_data_ready has been changed from void(*)(struct sock*, int) to void(*)(struct sock*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_rx_rate_vht_flag has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcpi_max_pacing_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tcpi_pacing_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field all_timers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allow_instances has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field flag_changed has been changed from int(*)(struct tracer*, u32, int) to int(*)(struct trace_array*, u32, int). | Recompilation of a client program may be broken. |
| 3 | Base type of field set_flag has been changed from int(*)(u32, u32, int) to int(*)(struct trace_array*, u32, u32, int). | Recompilation of a client program may be broken. |
| 4 | Type of field enabled has been changed from bool to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field streams has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cycle_last has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field monotonic_time_coarse_nsec has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field monotonic_time_coarse_sec has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mult has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field shift has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tz_dsttime has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field tz_minuteswest has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field vclock_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field wall_time_coarse_nsec has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field wall_time_coarse_sec has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Type of field monotonic_time_sec has been changed from time_t to gtod_long_t. | Recompilation of a client program may be broken. |
| 13 | Type of field wall_time_sec has been changed from time_t to gtod_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[60] to unsigned long[62]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flow_flush_sem has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flow_cache_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field flow_cache_gc_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field flow_cache_gc_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field flow_cache_gc_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field flow_cache_global has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field flow_cache_flush_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_alive has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct sock*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field filter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field proto has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from union acpi_predefined_info[291] const to union acpi_predefined_info[293] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct tcf_common* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct tcf_common* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_device_id[7] const to struct pci_device_id[8] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter init has been changed from void(*)(void*, struct blk_mq_hw_ctx*, struct request*, unsigned int) to int(*)(void*, struct blk_mq_hw_ctx*, struct request*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter desc has been changed from read_descriptor_t* to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter type_mask has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct cfg80211_ops to struct cfg80211_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to char*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter type has been changed from snd_device_type_t to enum snd_device_type. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter devices has been changed from struct pci_dev*** to struct dmar_dev_scope**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter handle has been changed from acpi_handle to struct acpi_device*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter owner has been changed from struct dev_state to struct usb_dev_state. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from void* to void const*const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter handle has been changed from acpi_handle* to acpi_handle. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rate_control_ops to struct rate_control_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 9th parameter flags has been changed from int to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 10th parameter flags has been changed from int to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter user_ns has been changed from struct user_namespace* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[316] const to sys_call_ptr_t[317] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[353] const to sys_call_ptr_t[354] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[35] to atomic_long_t[38]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[97] const to char const*[102] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ipi_list has been added to this type. | No effect. |
| 2 | Field hash has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field completion_data has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field fifo_time has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member DRM_MM_SEARCH_BELOW with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field agp has been changed from 27 to 34. | No effect. |
| 2 | The relative position of field agp_buffer_map has been changed from 38 to 42. | No effect. |
| 3 | The relative position of field agp_buffer_token has been changed from 39 to 43. | No effect. |
| 4 | The relative position of field buf_alloc has been changed from 7 to 14. | No effect. |
| 5 | The relative position of field buf_use has been changed from 6 to 13. | No effect. |
| 6 | The relative position of field context_flag has been changed from 17 to 24. | No effect. |
| 7 | The relative position of field control has been changed from 40 to 6. | No effect. |
| 8 | The relative position of field count_lock has been changed from 3 to 10. | No effect. |
| 9 | The relative position of field ctx_idr has been changed from 13 to 20. | No effect. |
| 10 | The relative position of field ctxlist has been changed from 11 to 18. | No effect. |
| 11 | The relative position of field ctxlist_mutex has been changed from 12 to 19. | No effect. |
| 12 | The relative position of field dev has been changed from 28 to 3. | No effect. |
| 13 | The relative position of field dma has been changed from 15 to 22. | No effect. |
| 14 | The relative position of field driver has been changed from 37 to 4. | No effect. |
| 15 | The relative position of field event_lock has been changed from 26 to 33. | No effect. |
| 16 | The relative position of field filelist has been changed from 8 to 15. | No effect. |
| 17 | The relative position of field irq_enabled has been changed from 16 to 23. | No effect. |
| 18 | The relative position of field last_context has been changed from 18 to 25. | No effect. |
| 19 | The relative position of field map_hash has been changed from 10 to 17. | No effect. |
| 20 | The relative position of field maplist has been changed from 9 to 16. | No effect. |
| 21 | The relative position of field max_vblank_count has been changed from 24 to 31. | No effect. |
| 22 | The relative position of field mode_config has been changed from 43 to 44. | No effect. |
| 23 | The relative position of field num_crtcs has been changed from 33 to 39. | No effect. |
| 24 | The relative position of field object_name_idr has been changed from 45 to 46. | No effect. |
| 25 | The relative position of field object_name_lock has been changed from 44 to 45. | No effect. |
| 26 | The relative position of field open_count has been changed from 5 to 12. | No effect. |
| 27 | The relative position of field pdev has been changed from 29 to 35. | No effect. |
| 28 | The relative position of field platformdev has been changed from 30 to 36. | No effect. |
| 29 | The relative position of field primary has been changed from 41 to 7. | No effect. |
| 30 | The relative position of field render has been changed from 42 to 8. | No effect. |
| 31 | The relative position of field sg has been changed from 32 to 38. | No effect. |
| 32 | The relative position of field sigdata has been changed from 35 to 40. | No effect. |
| 33 | The relative position of field sigmask has been changed from 36 to 41. | No effect. |
| 34 | The relative position of field struct_mutex has been changed from 4 to 11. | No effect. |
| 35 | The relative position of field switch_power_state has been changed from 47 to 48. | No effect. |
| 36 | The relative position of field unplugged has been changed from 48 to 9. | No effect. |
| 37 | The relative position of field usbdev has been changed from 31 to 37. | No effect. |
| 38 | The relative position of field vbl_lock has been changed from 22 to 29. | No effect. |
| 39 | The relative position of field vblank has been changed from 20 to 27. | No effect. |
| 40 | The relative position of field vblank_disable_allowed has been changed from 19 to 26. | No effect. |
| 41 | The relative position of field vblank_disable_timer has been changed from 23 to 30. | No effect. |
| 42 | The relative position of field vblank_event_list has been changed from 25 to 32. | No effect. |
| 43 | The relative position of field vblank_time_lock has been changed from 21 to 28. | No effect. |
| 44 | The relative position of field vma_offset_manager has been changed from 46 to 47. | No effect. |
| 45 | The relative position of field vmalist has been changed from 14 to 21. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field insnsi has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_DOMAIN_PORT_CRT with value 19 has been added. | No effect. |
| 2 | The member POWER_DOMAIN_PORT_DDI_A_2_LANES with value 10 has been added. | No effect. |
| 3 | The member POWER_DOMAIN_PORT_DDI_A_4_LANES with value 11 has been added. | No effect. |
| 4 | The member POWER_DOMAIN_PORT_DDI_B_2_LANES with value 12 has been added. | No effect. |
| 5 | The member POWER_DOMAIN_PORT_DDI_B_4_LANES with value 13 has been added. | No effect. |
| 6 | The member POWER_DOMAIN_PORT_DDI_C_2_LANES with value 14 has been added. | No effect. |
| 7 | The member POWER_DOMAIN_PORT_DDI_C_4_LANES with value 15 has been added. | No effect. |
| 8 | The member POWER_DOMAIN_PORT_DDI_D_2_LANES with value 16 has been added. | No effect. |
| 9 | The member POWER_DOMAIN_PORT_DDI_D_4_LANES with value 17 has been added. | No effect. |
| 10 | The member POWER_DOMAIN_PORT_DSI with value 18 has been added. | No effect. |
| 11 | The member POWER_DOMAIN_PORT_OTHER with value 20 has been added. | No effect. |
| 12 | Value of member POWER_DOMAIN_AUDIO has been changed from 11 to 22. | No effect. |
| 13 | Value of member POWER_DOMAIN_INIT has been changed from 12 to 23. | No effect. |
| 14 | Value of member POWER_DOMAIN_NUM has been changed from 13 to 24. | No effect. |
| 15 | Value of member POWER_DOMAIN_VGA has been changed from 10 to 21. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member _PIPE_EDP with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_MAX_TRANSCODERS with value 4 has been added. | No effect. |
| 2 | Value of member TRANSCODER_EDP has been changed from 15 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field batchbuffer has been changed from 2 to 3. | No effect. |
| 2 | The relative position of field ctx has been changed from 3 to 4. | No effect. |
| 3 | The relative position of field num_requests has been changed from 5 to 1. | No effect. |
| 4 | The relative position of field requests has been changed from 4 to 5. | No effect. |
| 5 | The relative position of field ringbuffer has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field active_bo has been changed from 15 to 17. | No effect. |
| 2 | The relative position of field active_bo_count has been changed from 17 to 19. | No effect. |
| 3 | The relative position of field ccid has been changed from 4 to 5. | No effect. |
| 4 | The relative position of field derrmr has been changed from 5 to 6. | No effect. |
| 5 | The relative position of field display has been changed from 20 to 15. | No effect. |
| 6 | The relative position of field done_reg has been changed from 11 to 10. | No effect. |
| 7 | The relative position of field eir has been changed from 1 to 2. | No effect. |
| 8 | The relative position of field extra_instdone has been changed from 10 to 11. | No effect. |
| 9 | The relative position of field fence has been changed from 12 to 13. | No effect. |
| 10 | The relative position of field forcewake has been changed from 6 to 7. | No effect. |
| 11 | The relative position of field ier has been changed from 3 to 4. | No effect. |
| 12 | The relative position of field overlay has been changed from 19 to 14. | No effect. |
| 13 | The relative position of field pgtbl_er has been changed from 2 to 3. | No effect. |
| 14 | The relative position of field pinned_bo has been changed from 16 to 18. | No effect. |
| 15 | The relative position of field pinned_bo_count has been changed from 18 to 20. | No effect. |
| 16 | The relative position of field pipestat has been changed from 7 to 12. | No effect. |
| 17 | The relative position of field ring has been changed from 14 to 16. | No effect. |
| 18 | The relative position of field time has been changed from 13 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pd_pages has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field unnamed0 has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field acthd has been changed from 2 to 0. | No effect. |
| 2 | The relative position of field action has been changed from 4 to 3. | No effect. |
| 3 | The relative position of field deadlock has been changed from 0 to 4. | No effect. |
| 4 | The relative position of field score has been changed from 3 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member WORKINGSET_ACTIVATE with value 34 has been added. | No effect. |
| 2 | The member WORKINGSET_NODERECLAIM with value 35 has been added. | No effect. |
| 3 | The member WORKINGSET_REFAULT with value 33 has been added. | No effect. |
| 4 | Value of member NR_ANON_TRANSPARENT_HUGEPAGES has been changed from 33 to 36. | No effect. |
| 5 | Value of member NR_FREE_CMA_PAGES has been changed from 34 to 37. | No effect. |
| 6 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 35 to 38. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_ATTR_MAC_HINT with value 200 has been added. | No effect. |
| 2 | The member NL80211_ATTR_MAX_AP_ASSOC_STA with value 202 has been added. | No effect. |
| 3 | The member NL80211_ATTR_TDLS_PEER_CAPABILITY with value 203 has been added. | No effect. |
| 4 | The member NL80211_ATTR_WIPHY_FREQ_HINT with value 201 has been added. | No effect. |
| 5 | Value of member NL80211_ATTR_MAX has been changed from 199 to 203. | No effect. |
| 6 | Value of member __NL80211_ATTR_AFTER_LAST has been changed from 200 to 204. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_MAX with value 16 has been added. | No effect. |
| 2 | The member PHY_INTERFACE_MODE_QSGMII with value 15 has been added. | No effect. |
| 3 | The member PHY_INTERFACE_MODE_MOCA with value 14 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member DEV_PM_QOS_LATENCY_TOLERANCE with value 2 has been added. | No effect. |
| 2 | Value of member DEV_PM_QOS_FLAGS has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field sched_count has been changed from 47 to 48. | No effect. |
| 2 | The relative position of field post_schedule has been changed from 27 to 28. | No effect. |
| 3 | The relative position of field cpu has been changed from 31 to 32. | No effect. |
| 4 | The relative position of field rq_cpu_time has been changed from 45 to 46. | No effect. |
| 5 | The relative position of field clock has been changed from 20 to 21. | No effect. |
| 6 | The relative position of field ttwu_count has been changed from 49 to 50. | No effect. |
| 7 | The relative position of field clock_task has been changed from 21 to 22. | No effect. |
| 8 | The relative position of field rt_avg has been changed from 34 to 35. | No effect. |
| 9 | The relative position of field stop has been changed from 17 to 18. | No effect. |
| 10 | The relative position of field online has been changed from 32 to 33. | No effect. |
| 11 | The relative position of field avg has been changed from 52 to 14. | No effect. |
| 12 | The relative position of field ttwu_local has been changed from 50 to 51. | No effect. |
| 13 | The relative position of field calc_load_active has been changed from 40 to 41. | No effect. |
| 14 | The relative position of field hrtick_timer has been changed from 43 to 44. | No effect. |
| 15 | The relative position of field nr_uninterruptible has been changed from 14 to 15. | No effect. |
| 16 | The relative position of field nr_iowait has been changed from 22 to 23. | No effect. |
| 17 | The relative position of field cfs_tasks has been changed from 33 to 34. | No effect. |
| 18 | The relative position of field next_balance has been changed from 18 to 19. | No effect. |
| 19 | The relative position of field wake_list has been changed from 51 to 52. | No effect. |
| 20 | The relative position of field idle has been changed from 16 to 17. | No effect. |
| 21 | The relative position of field calc_load_update has been changed from 39 to 40. | No effect. |
| 22 | The relative position of field idle_balance has been changed from 26 to 27. | No effect. |
| 23 | The relative position of field prev_mm has been changed from 19 to 20. | No effect. |
| 24 | The relative position of field hrtick_csd_pending has been changed from 41 to 42. | No effect. |
| 25 | The relative position of field hrtick_csd has been changed from 42 to 43. | No effect. |
| 26 | The relative position of field sd has been changed from 24 to 25. | No effect. |
| 27 | The relative position of field active_balance has been changed from 28 to 29. | No effect. |
| 28 | The relative position of field max_idle_balance_cost has been changed from 38 to 39. | No effect. |
| 29 | The relative position of field rq_sched_info has been changed from 44 to 45. | No effect. |
| 30 | The relative position of field yld_count has been changed from 46 to 47. | No effect. |
| 31 | The relative position of field cpu_power has been changed from 25 to 26. | No effect. |
| 32 | The relative position of field rd has been changed from 23 to 24. | No effect. |
| 33 | The relative position of field sched_goidle has been changed from 48 to 49. | No effect. |
| 34 | The relative position of field active_balance_work has been changed from 30 to 31. | No effect. |
| 35 | The relative position of field age_stamp has been changed from 35 to 36. | No effect. |
| 36 | The relative position of field avg_idle has been changed from 37 to 38. | No effect. |
| 37 | The relative position of field curr has been changed from 15 to 16. | No effect. |
| 38 | The relative position of field idle_stamp has been changed from 36 to 37. | No effect. |
| 39 | The relative position of field push_cpu has been changed from 29 to 30. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed1 has been changed from 42 to 12. | No effect. |
| 2 | The relative position of field unnamed2 has been changed from 44 to 43. | No effect. |
| 3 | The relative position of field unnamed0 has been changed from 11 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field skb_mstamp has been added to this type. | No effect. |
| 2 | Field tstamp has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field enabled has been changed from 19 to 18. | No effect. |
| 2 | The relative position of field print_max has been changed from 18 to 19. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field monotonic_time_sec has been changed from 4 to 3. | No effect. |
| 2 | The relative position of field monotonic_time_snsec has been changed from 3 to 4. | No effect. |
| 3 | The relative position of field wall_time_sec has been changed from 1 to 2. | No effect. |
| 4 | The relative position of field wall_time_snsec has been changed from 2 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter desc has been renamed to from. | No effect. |
| 2 | 3rd parameter from has been renamed to count. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mask has been renamed to bars. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter handle has been renamed to adev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter priv has been renamed to is_primary. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter flags has been renamed to sflags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter flags has been renamed to sflags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter lace has been renamed to interlaced. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mask has been renamed to status_mask. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mask has been renamed to status_mask. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to dev_priv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter channel has been renamed to rx_channel. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter channel has been renamed to rx_channel. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter user_ns has been renamed to may_report_filterinfo. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to tp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to tp. | No effect. |