| Module Name | vmlinux |
|---|---|
| Version #1 | 3.0.101 |
| Version #2 | 3.2.52 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 740 |
|---|---|
| Total Source Files | 1359 |
| Total Objects | 1 |
| Total Symbols / Types | 14699 / 8294 |
| Verdict | Incompatible (49.8%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 458 |
| Removed Symbols | High | 122 |
| Problems with Data Types | High | 56 |
| Medium | 988 | |
| Low | 436 | |
| Problems with Symbols | High | 32 |
| Medium | 993 | |
| Low | 112 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 6 |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled 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 period 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 logattrs 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 bi_comp_cpu 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 last_state 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 states 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 driver_data 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 time 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 usage 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 debugfs_nodes 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 hh 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 phy_info_timer 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 tx_fifo_stall_timer 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 vlgrp 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 watchdog_timer 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 get_rx_ntuple 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 i_nlink 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 i_alloc_sem 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 spdif_ctls 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 spdif_status 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 cfb_fence 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 cfb_offset 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 cfb_pitch 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 panel_fixed_mode 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 panel_t12 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 panel_t3 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 i2c_speed 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 ethertype 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 vgrp 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 ctl_key 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 offchannel_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. |
| 2 | Field offchannel_tx_cancel_wait 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 oom_disable_count 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 hh_next 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 hh_output 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 hh_type 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 ndo_set_multicast_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 ndo_vlan_rx_register 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 change_attr 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 path 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field lookupfh 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field a_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field fs_excl 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 dirties 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 pri_active 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field tlet 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 flaglock 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 s_sibling 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 encountered_congestion 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 nonblocking 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 older_than_this 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 wb_start 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 resend 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 | 2nd middle parameter scratch 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 start of type loff_t 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 3rd parameter now has been changed from ktime_t (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 prev of type struct task_struct* 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 | 3rd middle parameter nmi 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 | 2nd middle parameter nmi 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 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 start of type loff_t 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 nr_pages of type long 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 start of type loff_t 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 context of type void* 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 start of type loff_t 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 start of type loff_t 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 | 1st middle parameter node_id 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 no_cck of type bool 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 neigh of type struct neighbour* 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 neigh of type struct neighbour* 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 neigh of type struct neighbour* 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 | 1st middle parameter path 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 | 1st middle parameter path 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 | 1st middle parameter path 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 2nd parameter kill has been changed from int (4 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 indices of type unsigned long* 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 initxattrs of type initxattrs const 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 fs_data of type void* 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 | 4th middle parameter name 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. |
| 4 | 5th middle parameter value 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 pointer level of 4th parameter payload_len has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ratemask 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 | Parameter num_prealloc 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 xprt of type struct rpc_xprt* 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 xprt of type struct rpc_xprt* 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 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field probe 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 208 bytes to 216 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 tcfc_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mapped_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ring_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ki_batch 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 ctx_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field state 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fs_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field lookup_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field written_stamp 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 dirty_ratelimit 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 write_bandwidth 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 avg_write_bandwidth 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 balanced_dirty_ratelimit 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 dirtied_stamp 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 bw_time_stamp 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 wb_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 9 | Size of field wb has been changed from 96 bytes to 100 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. |
| 10 | Type of field bdi_stat has been changed from struct percpu_counter[2] (48 bytes) to struct percpu_counter[4] (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 | Size of field dev has been changed from 208 bytes to 216 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 bio2 has been changed from 72 bytes to 68 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field bio1 has been changed from 72 bytes to 68 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed1 has been changed from 12 bytes to 16 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 bsg_job_size 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 bsg_job_fn 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 __queue_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field flush_rq has been changed from 208 bytes to 212 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 backing_dev_info has been changed from 304 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. |
| 6 | The relative position of field dma_drain_size has been changed from 28 to 27. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field dma_drain_buffer has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field bounce_gfp has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field queue_flags has been changed from 19 to 18. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field flush has been changed from 12 bytes to 16 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 rates 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 match_sets 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 n_match_sets 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 eap_identity_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 sta_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 max_match_sets 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 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. |
| 3 | Size of field dev has been changed from 208 bytes to 216 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 event_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field mgmt_registrations_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field event_list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id_lock has been changed from spinlock_t to struct rwlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cl_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_next_ktime 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 vread has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field queue_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nf_conntrack_event_cb 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 nf_expect_event_cb 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 read_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 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 bss_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field wiphy has been changed from 384 bytes to 416 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 files_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_bsp_init 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 states_usage 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 prepare 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 safe_state 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 power_specified has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field state_usage 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field d_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_prune 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field iommu_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field devres_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field power has been changed from 40 bytes to 48 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 job_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field region_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field deferred_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field uevent_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field flush_bio has been changed from 72 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 4 | Field saved_make_request_fn 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field audio_latency 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 dvi_dual 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 eld 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 latency_present 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 max_tmds_clock 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 video_latency 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 | Size of field display_info has been changed from 76 bytes to 80 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 kdev has been changed from 208 bytes to 216 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 cea_rev 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 unused_lock has been changed from 4 bytes to 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field count_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field event_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field object_name_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field vblank_time_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 5 | Size of field vbl_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_close_object 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 gem_open_object 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 table_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field spinlock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field debugfs_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. |
| 2 | Field debugfs_lock 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 kdev has been changed from 208 bytes to 216 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 waitlist has been changed from 28 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field read_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field write_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 flags has been changed from 19 to 11. | 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 neigh_lookup 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 active_vlans 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 watchdog_task 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 stats_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Type of field fifo_stall_task has been changed from struct work_struct (16 bytes) to struct delayed_work (68 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 | Type of field phy_info_task has been changed from struct work_struct (16 bytes) to struct delayed_work (68 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field alloc_rx_buff_failed has been changed from 44 to 43. | 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 clean_rx has been changed from 36 to 35. | 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 discarding has been changed from 67 to 66. | 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 fc_autoneg has been changed from 18 to 17. | 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 flags has been changed from 63 to 62. | 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 gorcl has been changed from 48 to 47. | 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 gorcl_old has been changed from 49 to 48. | 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 gotcl_old has been changed from 25 to 24. | 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 hw has been changed from 52 to 51. | 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 hw_csum_err has been changed from 42 to 41. | 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 msg_enable has been changed from 59 to 58. | 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 napi has been changed from 39 to 38. | 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 netdev has been changed from 50 to 49. | 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 num_tx_queues has been changed from 40 to 39. | 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 pcix_82544 has been changed from 34 to 33. | 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 phy_info has been changed from 54 to 53. | 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 phy_stats has been changed from 55 to 54. | 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 reset_task has been changed from 17 to 67. | 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 rx_csum has been changed from 47 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 stats has been changed from 53 to 52. | 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 test_icr has been changed from 56 to 55. | 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 test_rx_ring has been changed from 58 to 57. | 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 test_tx_ring has been changed from 57 to 56. | 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 tso_force has been changed from 60 to 59. | 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 tx_fifo_stall has been changed from 33 to 32. | 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 tx_ring has been changed from 19 to 18. | 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 tx_timeout_count has been changed from 28 to 27. | 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 tx_timeout_factor has been changed from 32 to 31. | 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 alloc_rx_buf has been changed from 37 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field bars has been changed from 65 to 64. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field colc_old has been changed from 27 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field detect_tx_hung has been changed from 35 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field eeprom_wol has been changed from 64 to 63. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field gotcl has been changed from 24 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field hw_csum_good has been changed from 43 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field need_ioport has been changed from 66 to 65. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field num_rx_queues has been changed from 41 to 40. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field pdev has been changed from 51 to 50. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field quad_port_a has been changed from 62 to 61. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field restart_queue has been changed from 20 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field rx_abs_int_delay has been changed from 46 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field rx_int_delay has been changed from 45 to 44. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field rx_ring has been changed from 38 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 49 | The relative position of field smart_power_down has been changed from 61 to 60. | Applications will access incorrect memory when attempting to access this field. |
| 50 | The relative position of field tpt_old has been changed from 26 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 51 | The relative position of field tx_abs_int_delay has been changed from 23 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 52 | The relative position of field tx_fifo_head has been changed from 29 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 53 | The relative position of field tx_fifo_size has been changed from 31 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 54 | The relative position of field tx_head_addr has been changed from 30 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 55 | The relative position of field tx_int_delay has been changed from 22 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 56 | The relative position of field txd_cmd has been changed from 21 to 20. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_capsule_caps 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 query_variable_info 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 runtime_version 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 update_capsule 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 lock has been changed from 4 bytes to 2 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 208 bytes to 216 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 348 bytes to 332 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 inode_hash_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field file_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tree_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fa_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field f_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_downgrade_time 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 fl_flags has been changed from unsigned char (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 i_alloc_sem_key has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed2 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 i_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | The relative position of field i_bytes has been changed from 27 to 17. | 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 i_rdev has been changed from 18 to 12. | 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 i_writecount has been changed from 38 to 32. | 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 i_dquot has been changed from 32 to 36. | 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 i_version has been changed from 20 to 31. | 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 i_blocks has been changed from 26 to 18. | 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 i_devices has been changed from 33 to 37. | 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 i_state has been changed from 7 to 21. | 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 dirtied_when has been changed from 10 to 23. | 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 i_data has been changed from 31 to 35. | 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 i_fop has been changed from 28 to 33. | 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 i_security has been changed from 8 to 9. | 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 i_size_seqcount has been changed from 22 to 20. | 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 i_mutex has been changed from 9 to 22. | 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 i_sb_list has been changed from 14 to 27. | 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 i_size has been changed from 21 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | Size of field unnamed0 has been changed from 8 bytes to 4 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. |
| 20 | Size of field unnamed1 has been changed from 4 bytes to 8 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. |
| 21 | The relative position of field i_flags has been changed from 6 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field i_fsnotify_mask has been changed from 36 to 39. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field i_lru has been changed from 13 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field i_blkbits has been changed from 19 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field i_default_acl has been changed from 40 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field i_sb has been changed from 4 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field i_lock has been changed from 5 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field i_atime has been changed from 23 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 29 | The relative position of field i_generation has been changed from 35 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 30 | The relative position of field i_ctime has been changed from 25 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field i_mapping has been changed from 30 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field i_acl has been changed from 39 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field i_mtime has been changed from 24 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field i_count has been changed from 17 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field i_ino has been changed from 16 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field i_hash has been changed from 11 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field i_op has been changed from 3 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field i_wb_list has been changed from 12 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field i_fsnotify_marks has been changed from 37 to 40. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field unnamed0 has been changed from 15 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field i_flock has been changed from 29 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field unnamed1 has been changed from 34 to 28. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_inode_lru 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 s_inode_lru_lock 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 s_nr_inodes_unused 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 __i_nlink 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 i_nlink 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 i_dentry 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 i_rcu 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 i_dentry 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 i_rcu 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 i_bdev 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 i_cdev 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. |
| 5 | Field i_pipe 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mark_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field idr_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ent_size 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field part0 has been changed from 280 bytes to 288 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 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field spdif_out 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 patch_ops has been changed from 32 bytes to 44 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 post_suspend 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 pre_resume 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 set_power_state 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 hp_out_nid 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 extra_out_nid has been changed from hda_nid_t[3] (6 bytes) to hda_nid_t[5] (10 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 eld_buffer 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 driver_lock 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 208 bytes to 216 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 dyn_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field read_reg_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. |
| 2 | Field set_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. |
| 3 | Field write_reg_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 208 bytes to 216 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 gtt_space has been changed from 92 bytes to 88 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field stolen has been changed from 92 bytes to 88 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field inactive_shrinker has been changed from 20 bytes 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_eld 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 backlight 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 bios_lvds_val 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 cfb_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. |
| 4 | Field fbc_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. |
| 5 | Field gt_fifo_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. |
| 6 | Field gt_lock 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 int_edp_connector 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 lvds_val 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 | Size of field error_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 10 | Size of field irq_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 11 | Size of field mm has been changed from 400 bytes to 396 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 12 | Size of field rps_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 13 | Size of field display has been changed from 48 bytes to 64 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. |
| 14 | Size of field ring has been changed from 576 bytes to 648 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. |
| 15 | Size of field sdvo_mappings has been changed from 14 bytes to 12 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. |
| 16 | Type of field pipe_to_crtc_mapping has been changed from struct drm_crtc*[2] (8 bytes) to struct drm_crtc*[3] (12 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. |
| 17 | Type of field plane_to_crtc_mapping has been changed from struct drm_crtc*[2] (8 bytes) to struct drm_crtc*[3] (12 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. |
| 18 | The relative position of field backlight_enabled has been changed from 52 to 53. | 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 backlight_level 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. |
| 20 | The relative position of field bridge_dev 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. |
| 21 | The relative position of field busy has been changed from 244 to 245. | 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 cfb_y has been changed from 48 to 49. | 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 chipset_power has been changed from 260 to 261. | 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 corr has been changed from 266 to 267. | 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 counter 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. |
| 26 | The relative position of field crt_ddc_pin has been changed from 64 to 65. | 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 display has been changed from 76 to 77. | 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 edp has been changed from 61 to 62. | 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 error_completion has been changed from 74 to 75. | 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 fence_regs has been changed from 65 to 66. | 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 first_error has been changed from 72 to 73. | 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 fstart has been changed from 257 to 258. | 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 hangcheck_timer has been changed from 39 to 40. | 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 hotplug_supported_mask 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. |
| 35 | The relative position of field hotplug_work has been changed from 27 to 28. | 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 hws_map has been changed from 11 to 12. | 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 idle_timer has been changed from 243 to 244. | 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 idle_work has been changed from 242 to 243. | 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 int_lvds_connector has been changed from 248 to 249. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 40 | The relative position of field irq_lock 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. |
| 41 | The relative position of field last_count1 has been changed from 258 to 259. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 42 | The relative position of field last_time2 has been changed from 262 to 263. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 43 | The relative position of field lid_notifier has been changed from 63 to 64. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 44 | The relative position of field lvds_downclock has been changed from 241 to 242. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 45 | The relative position of field lvds_downclock_avail has been changed from 240 to 241. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 46 | The relative position of field lvds_ssc_freq has been changed from 60 to 61. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 47 | The relative position of field mch_res has been changed from 14 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 48 | The relative position of field mchbar_need_disable has been changed from 249 to 250. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 49 | The relative position of field mm has been changed from 230 to 231. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 50 | The relative position of field no_aux_handshake has been changed from 62 to 63. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 51 | The relative position of field num_pipe has been changed from 38 to 39. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 52 | The relative position of field opregion has been changed from 49 to 50. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 53 | The relative position of field orig_clock has been changed from 245 to 246. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 54 | The relative position of field pch_pf_size has been changed from 234 to 235. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 55 | The relative position of field pending_flip_queue has been changed from 237 to 238. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 56 | The relative position of field pipe_to_crtc_mapping has been changed from 236 to 237. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 57 | The relative position of field pipestat 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. |
| 58 | The relative position of field pm_iir has been changed from 252 to 253. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 59 | The relative position of field quirks has been changed from 78 to 79. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 60 | The relative position of field r_t has been changed from 265 to 266. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 61 | The relative position of field renderctx has been changed from 13 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 62 | The relative position of field ring has been changed from 7 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 63 | The relative position of field rps_work has been changed from 250 to 251. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 64 | The relative position of field saveAR has been changed from 186 to 187. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 65 | The relative position of field saveAR_INDEX has been changed from 185 to 186. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 66 | The relative position of field saveCR has been changed from 188 to 189. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 67 | The relative position of field saveDACMASK has been changed from 187 to 188. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 68 | The relative position of field saveFENCE has been changed from 189 to 190. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 69 | The relative position of field saveGR has been changed from 184 to 185. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 70 | The relative position of field saveLBB has been changed from 80 to 81. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 71 | The relative position of field saveMI_ARB_STATE has been changed from 178 to 179. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 72 | The relative position of field saveMSR has been changed from 182 to 183. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 73 | The relative position of field savePCH_PORT_HOTPLUG has been changed from 229 to 230. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 74 | The relative position of field savePFIT_CONTROL has been changed from 160 to 161. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 75 | The relative position of field saveSR has been changed from 183 to 184. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 76 | The relative position of field saveSWF1 has been changed from 180 to 181. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 77 | The relative position of field saveSWF2 has been changed from 181 to 182. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 78 | The relative position of field save_palette_b has been changed from 162 to 163. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 79 | The relative position of field sdvo_mappings has been changed from 231 to 232. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 80 | The relative position of field wq has been changed from 75 to 76. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 81 | Type of field forcewake_count has been changed from struct atomic_t to unsigned int of different format. | This field may be incorrectly initialized or accessed by applications. |
| 82 | The relative position of field adpa has been changed from 32 to 33. | Applications will access incorrect memory when attempting to access this field. |
| 83 | The relative position of field agp_heap has been changed from 30 to 31. | Applications will access incorrect memory when attempting to access this field. |
| 84 | The relative position of field allow_batchbuffer has been changed from 29 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 85 | The relative position of field back_offset has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 86 | The relative position of field broadcast_rgb_property has been changed from 273 to 274. | Applications will access incorrect memory when attempting to access this field. |
| 87 | The relative position of field c_m has been changed from 264 to 265. | Applications will access incorrect memory when attempting to access this field. |
| 88 | The relative position of field cfb_plane has been changed from 47 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 89 | The relative position of field cfb_size has been changed from 46 to 47. | Applications will access incorrect memory when attempting to access this field. |
| 90 | The relative position of field child_dev has been changed from 247 to 248. | Applications will access incorrect memory when attempting to access this field. |
| 91 | The relative position of field child_dev_num has been changed from 246 to 247. | Applications will access incorrect memory when attempting to access this field. |
| 92 | The relative position of field compressed_fb has been changed from 269 to 270. | Applications will access incorrect memory when attempting to access this field. |
| 93 | The relative position of field compressed_llb has been changed from 270 to 271. | Applications will access incorrect memory when attempting to access this field. |
| 94 | The relative position of field cpp has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 95 | The relative position of field cur_delay has been changed from 253 to 254. | Applications will access incorrect memory when attempting to access this field. |
| 96 | The relative position of field current_page has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 97 | The relative position of field dvob has been changed from 34 to 35. | Applications will access incorrect memory when attempting to access this field. |
| 98 | The relative position of field dvoc has been changed from 35 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 99 | The relative position of field error_lock has been changed from 71 to 72. | Applications will access incorrect memory when attempting to access this field. |
| 100 | The relative position of field error_work has been changed from 73 to 74. | Applications will access incorrect memory when attempting to access this field. |
| 101 | The relative position of field fbdev has been changed from 272 to 273. | Applications will access incorrect memory when attempting to access this field. |
| 102 | The relative position of field fence_reg_start has been changed from 66 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 103 | The relative position of field flip_pending_is_done has been changed from 238 to 239. | Applications will access incorrect memory when attempting to access this field. |
| 104 | The relative position of field fmax has been changed from 256 to 257. | Applications will access incorrect memory when attempting to access this field. |
| 105 | The relative position of field force_audio_property has been changed from 274 to 275. | Applications will access incorrect memory when attempting to access this field. |
| 106 | The relative position of field forcewake_count has been changed from 275 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 107 | The relative position of field front_offset has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 108 | The relative position of field fsb_freq has been changed from 68 to 69. | Applications will access incorrect memory when attempting to access this field. |
| 109 | The relative position of field gfx_power has been changed from 263 to 264. | Applications will access incorrect memory when attempting to access this field. |
| 110 | The relative position of field gmbus has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 111 | The relative position of field gt_irq_mask has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 112 | The relative position of field hangcheck_count has been changed from 40 to 41. | Applications will access incorrect memory when attempting to access this field. |
| 113 | The relative position of field int_crt_support has been changed from 58 to 59. | Applications will access incorrect memory when attempting to access this field. |
| 114 | The relative position of field int_tv_support has been changed from 55 to 56. | Applications will access incorrect memory when attempting to access this field. |
| 115 | The relative position of field irq_mask has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 116 | The relative position of field irq_received has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 117 | The relative position of field is_ddr3 has been changed from 70 to 71. | Applications will access incorrect memory when attempting to access this field. |
| 118 | The relative position of field last_acthd has been changed from 41 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 119 | The relative position of field last_acthd_blt has been changed from 43 to 44. | Applications will access incorrect memory when attempting to access this field. |
| 120 | The relative position of field last_acthd_bsd has been changed from 42 to 43. | Applications will access incorrect memory when attempting to access this field. |
| 121 | The relative position of field last_count2 has been changed from 261 to 262. | Applications will access incorrect memory when attempting to access this field. |
| 122 | The relative position of field last_gpu_reset has been changed from 271 to 272. | Applications will access incorrect memory when attempting to access this field. |
| 123 | The relative position of field last_instdone has been changed from 44 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 124 | The relative position of field last_instdone1 has been changed from 45 to 46. | Applications will access incorrect memory when attempting to access this field. |
| 125 | The relative position of field last_time1 has been changed from 259 to 260. | Applications will access incorrect memory when attempting to access this field. |
| 126 | The relative position of field lfp_lvds_vbt_mode has been changed from 53 to 54. | Applications will access incorrect memory when attempting to access this field. |
| 127 | The relative position of field lvds has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 128 | The relative position of field lvds_border_bits has been changed from 232 to 233. | Applications will access incorrect memory when attempting to access this field. |
| 129 | The relative position of field lvds_dither has been changed from 56 to 57. | Applications will access incorrect memory when attempting to access this field. |
| 130 | The relative position of field lvds_use_ssc has been changed from 59 to 60. | Applications will access incorrect memory when attempting to access this field. |
| 131 | The relative position of field lvds_vbt has been changed from 57 to 58. | Applications will access incorrect memory when attempting to access this field. |
| 132 | The relative position of field max_delay has been changed from 255 to 256. | Applications will access incorrect memory when attempting to access this field. |
| 133 | The relative position of field mchdev_lock has been changed from 267 to 268. | Applications will access incorrect memory when attempting to access this field. |
| 134 | The relative position of field mem_freq has been changed from 69 to 70. | Applications will access incorrect memory when attempting to access this field. |
| 135 | The relative position of field min_delay has been changed from 254 to 255. | Applications will access incorrect memory when attempting to access this field. |
| 136 | The relative position of field modeset_on_lid has been changed from 79 to 80. | Applications will access incorrect memory when attempting to access this field. |
| 137 | The relative position of field next_seqno has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 138 | The relative position of field no_fbc_reason has been changed from 268 to 269. | Applications will access incorrect memory when attempting to access this field. |
| 139 | The relative position of field num_fence_regs has been changed from 67 to 68. | Applications will access incorrect memory when attempting to access this field. |
| 140 | The relative position of field overlay has been changed from 50 to 51. | Applications will access incorrect memory when attempting to access this field. |
| 141 | The relative position of field page_flipping has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 142 | The relative position of field pch_irq_mask has been changed from 25 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 143 | The relative position of field pch_pf_pos has been changed from 233 to 234. | Applications will access incorrect memory when attempting to access this field. |
| 144 | The relative position of field pch_type has been changed from 77 to 78. | Applications will access incorrect memory when attempting to access this field. |
| 145 | The relative position of field plane_to_crtc_mapping has been changed from 235 to 236. | Applications will access incorrect memory when attempting to access this field. |
| 146 | The relative position of field ppcr has been changed from 33 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 147 | The relative position of field pwrctx has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 148 | The relative position of field render_reclock_avail has been changed from 239 to 240. | Applications will access incorrect memory when attempting to access this field. |
| 149 | The relative position of field rps_lock has been changed from 251 to 252. | Applications will access incorrect memory when attempting to access this field. |
| 150 | The relative position of field saveADPA has been changed from 149 to 150. | Applications will access incorrect memory when attempting to access this field. |
| 151 | The relative position of field saveBCLRPAT_A has been changed from 99 to 100. | Applications will access incorrect memory when attempting to access this field. |
| 152 | The relative position of field saveBCLRPAT_B has been changed from 130 to 131. | Applications will access incorrect memory when attempting to access this field. |
| 153 | The relative position of field saveBLC_CPU_PWM_CTL has been changed from 118 to 119. | Applications will access incorrect memory when attempting to access this field. |
| 154 | The relative position of field saveBLC_CPU_PWM_CTL2 has been changed from 119 to 120. | Applications will access incorrect memory when attempting to access this field. |
| 155 | The relative position of field saveBLC_HIST_CTL has been changed from 115 to 116. | Applications will access incorrect memory when attempting to access this field. |
| 156 | The relative position of field saveBLC_PWM_CTL has been changed from 116 to 117. | Applications will access incorrect memory when attempting to access this field. |
| 157 | The relative position of field saveBLC_PWM_CTL2 has been changed from 117 to 118. | Applications will access incorrect memory when attempting to access this field. |
| 158 | The relative position of field saveCACHE_MODE_0 has been changed from 177 to 178. | Applications will access incorrect memory when attempting to access this field. |
| 159 | The relative position of field saveCURABASE has been changed from 192 to 193. | Applications will access incorrect memory when attempting to access this field. |
| 160 | The relative position of field saveCURACNTR has been changed from 190 to 191. | Applications will access incorrect memory when attempting to access this field. |
| 161 | The relative position of field saveCURAPOS has been changed from 191 to 192. | Applications will access incorrect memory when attempting to access this field. |
| 162 | The relative position of field saveCURBBASE has been changed from 195 to 196. | Applications will access incorrect memory when attempting to access this field. |
| 163 | The relative position of field saveCURBCNTR has been changed from 193 to 194. | Applications will access incorrect memory when attempting to access this field. |
| 164 | The relative position of field saveCURBPOS has been changed from 194 to 195. | Applications will access incorrect memory when attempting to access this field. |
| 165 | The relative position of field saveCURSIZE has been changed from 196 to 197. | Applications will access incorrect memory when attempting to access this field. |
| 166 | The relative position of field saveDEIER has been changed from 171 to 172. | Applications will access incorrect memory when attempting to access this field. |
| 167 | The relative position of field saveDEIMR has been changed from 172 to 173. | Applications will access incorrect memory when attempting to access this field. |
| 168 | The relative position of field saveDISP_ARB_CTL has been changed from 219 to 220. | Applications will access incorrect memory when attempting to access this field. |
| 169 | The relative position of field saveDPFC_CB_BASE has been changed from 163 to 164. | Applications will access incorrect memory when attempting to access this field. |
| 170 | The relative position of field saveDPLL_A has been changed from 91 to 92. | Applications will access incorrect memory when attempting to access this field. |
| 171 | The relative position of field saveDPLL_A_MD has been changed from 92 to 93. | Applications will access incorrect memory when attempting to access this field. |
| 172 | The relative position of field saveDPLL_B has been changed from 122 to 123. | Applications will access incorrect memory when attempting to access this field. |
| 173 | The relative position of field saveDPLL_B_MD has been changed from 123 to 124. | Applications will access incorrect memory when attempting to access this field. |
| 174 | The relative position of field saveDP_B has been changed from 197 to 198. | Applications will access incorrect memory when attempting to access this field. |
| 175 | The relative position of field saveDP_C has been changed from 198 to 199. | Applications will access incorrect memory when attempting to access this field. |
| 176 | The relative position of field saveDP_D has been changed from 199 to 200. | Applications will access incorrect memory when attempting to access this field. |
| 177 | The relative position of field saveDSPAADDR has been changed from 111 to 112. | Applications will access incorrect memory when attempting to access this field. |
| 178 | The relative position of field saveDSPACNTR has been changed from 81 to 82. | Applications will access incorrect memory when attempting to access this field. |
| 179 | The relative position of field saveDSPAPOS has been changed from 110 to 111. | Applications will access incorrect memory when attempting to access this field. |
| 180 | The relative position of field saveDSPARB has been changed from 83 to 84. | Applications will access incorrect memory when attempting to access this field. |
| 181 | The relative position of field saveDSPASIZE has been changed from 109 to 110. | Applications will access incorrect memory when attempting to access this field. |
| 182 | The relative position of field saveDSPASTRIDE has been changed from 108 to 109. | Applications will access incorrect memory when attempting to access this field. |
| 183 | The relative position of field saveDSPASURF has been changed from 112 to 113. | Applications will access incorrect memory when attempting to access this field. |
| 184 | The relative position of field saveDSPATILEOFF has been changed from 113 to 114. | Applications will access incorrect memory when attempting to access this field. |
| 185 | The relative position of field saveDSPBADDR has been changed from 142 to 143. | Applications will access incorrect memory when attempting to access this field. |
| 186 | The relative position of field saveDSPBCNTR has been changed from 82 to 83. | Applications will access incorrect memory when attempting to access this field. |
| 187 | The relative position of field saveDSPBPOS has been changed from 141 to 142. | Applications will access incorrect memory when attempting to access this field. |
| 188 | The relative position of field saveDSPBSIZE has been changed from 140 to 141. | Applications will access incorrect memory when attempting to access this field. |
| 189 | The relative position of field saveDSPBSTRIDE has been changed from 139 to 140. | Applications will access incorrect memory when attempting to access this field. |
| 190 | The relative position of field saveDSPBSURF has been changed from 143 to 144. | Applications will access incorrect memory when attempting to access this field. |
| 191 | The relative position of field saveDSPBTILEOFF has been changed from 144 to 145. | Applications will access incorrect memory when attempting to access this field. |
| 192 | The relative position of field saveDVOA has been changed from 153 to 154. | Applications will access incorrect memory when attempting to access this field. |
| 193 | The relative position of field saveDVOB has been changed from 154 to 155. | Applications will access incorrect memory when attempting to access this field. |
| 194 | The relative position of field saveDVOC has been changed from 155 to 156. | Applications will access incorrect memory when attempting to access this field. |
| 195 | The relative position of field saveFBC_CFB_BASE has been changed from 164 to 165. | Applications will access incorrect memory when attempting to access this field. |
| 196 | The relative position of field saveFBC_CONTROL has been changed from 166 to 167. | Applications will access incorrect memory when attempting to access this field. |
| 197 | The relative position of field saveFBC_CONTROL2 has been changed from 167 to 168. | Applications will access incorrect memory when attempting to access this field. |
| 198 | The relative position of field saveFBC_LL_BASE has been changed from 165 to 166. | Applications will access incorrect memory when attempting to access this field. |
| 199 | The relative position of field saveFDI_RXA_CTL has been changed from 208 to 209. | Applications will access incorrect memory when attempting to access this field. |
| 200 | The relative position of field saveFDI_RXA_IMR has been changed from 175 to 176. | Applications will access incorrect memory when attempting to access this field. |
| 201 | The relative position of field saveFDI_RXB_CTL has been changed from 210 to 211. | Applications will access incorrect memory when attempting to access this field. |
| 202 | The relative position of field saveFDI_RXB_IMR has been changed from 176 to 177. | Applications will access incorrect memory when attempting to access this field. |
| 203 | The relative position of field saveFDI_TXA_CTL has been changed from 209 to 210. | Applications will access incorrect memory when attempting to access this field. |
| 204 | The relative position of field saveFDI_TXB_CTL has been changed from 211 to 212. | Applications will access incorrect memory when attempting to access this field. |
| 205 | The relative position of field saveFPA0 has been changed from 89 to 90. | Applications will access incorrect memory when attempting to access this field. |
| 206 | The relative position of field saveFPA1 has been changed from 90 to 91. | Applications will access incorrect memory when attempting to access this field. |
| 207 | The relative position of field saveFPB0 has been changed from 120 to 121. | Applications will access incorrect memory when attempting to access this field. |
| 208 | The relative position of field saveFPB1 has been changed from 121 to 122. | Applications will access incorrect memory when attempting to access this field. |
| 209 | The relative position of field saveGTIER has been changed from 173 to 174. | Applications will access incorrect memory when attempting to access this field. |
| 210 | The relative position of field saveGTIMR has been changed from 174 to 175. | Applications will access incorrect memory when attempting to access this field. |
| 211 | The relative position of field saveHBLANK_A has been changed from 94 to 95. | Applications will access incorrect memory when attempting to access this field. |
| 212 | The relative position of field saveHBLANK_B has been changed from 125 to 126. | Applications will access incorrect memory when attempting to access this field. |
| 213 | The relative position of field saveHSYNC_A has been changed from 95 to 96. | Applications will access incorrect memory when attempting to access this field. |
| 214 | The relative position of field saveHSYNC_B has been changed from 126 to 127. | Applications will access incorrect memory when attempting to access this field. |
| 215 | The relative position of field saveHTOTAL_A has been changed from 93 to 94. | Applications will access incorrect memory when attempting to access this field. |
| 216 | The relative position of field saveHTOTAL_B has been changed from 124 to 125. | Applications will access incorrect memory when attempting to access this field. |
| 217 | The relative position of field saveHWS has been changed from 84 to 85. | Applications will access incorrect memory when attempting to access this field. |
| 218 | The relative position of field saveIER has been changed from 168 to 169. | Applications will access incorrect memory when attempting to access this field. |
| 219 | The relative position of field saveIIR has been changed from 169 to 170. | Applications will access incorrect memory when attempting to access this field. |
| 220 | The relative position of field saveIMR has been changed from 170 to 171. | Applications will access incorrect memory when attempting to access this field. |
| 221 | The relative position of field saveLVDS has been changed from 150 to 151. | Applications will access incorrect memory when attempting to access this field. |
| 222 | The relative position of field saveMCHBAR_RENDER_STANDBY has been changed from 228 to 229. | Applications will access incorrect memory when attempting to access this field. |
| 223 | The relative position of field savePCH_DREF_CONTROL has been changed from 218 to 219. | Applications will access incorrect memory when attempting to access this field. |
| 224 | The relative position of field savePFA_CTL_1 has been changed from 212 to 213. | Applications will access incorrect memory when attempting to access this field. |
| 225 | The relative position of field savePFA_WIN_POS has been changed from 216 to 217. | Applications will access incorrect memory when attempting to access this field. |
| 226 | The relative position of field savePFA_WIN_SZ has been changed from 214 to 215. | Applications will access incorrect memory when attempting to access this field. |
| 227 | The relative position of field savePFB_CTL_1 has been changed from 213 to 214. | Applications will access incorrect memory when attempting to access this field. |
| 228 | The relative position of field savePFB_WIN_POS has been changed from 217 to 218. | Applications will access incorrect memory when attempting to access this field. |
| 229 | The relative position of field savePFB_WIN_SZ has been changed from 215 to 216. | Applications will access incorrect memory when attempting to access this field. |
| 230 | The relative position of field savePFIT_PGM_RATIOS has been changed from 114 to 115. | Applications will access incorrect memory when attempting to access this field. |
| 231 | The relative position of field savePIPEACONF has been changed from 85 to 86. | Applications will access incorrect memory when attempting to access this field. |
| 232 | The relative position of field savePIPEASRC has been changed from 87 to 88. | Applications will access incorrect memory when attempting to access this field. |
| 233 | The relative position of field savePIPEASTAT has been changed from 107 to 108. | Applications will access incorrect memory when attempting to access this field. |
| 234 | The relative position of field savePIPEA_DATA_M1 has been changed from 220 to 221. | Applications will access incorrect memory when attempting to access this field. |
| 235 | The relative position of field savePIPEA_DATA_N1 has been changed from 221 to 222. | Applications will access incorrect memory when attempting to access this field. |
| 236 | The relative position of field savePIPEA_DP_LINK_M has been changed from 204 to 205. | Applications will access incorrect memory when attempting to access this field. |
| 237 | The relative position of field savePIPEA_DP_LINK_N has been changed from 206 to 207. | Applications will access incorrect memory when attempting to access this field. |
| 238 | The relative position of field savePIPEA_GMCH_DATA_M has been changed from 200 to 201. | Applications will access incorrect memory when attempting to access this field. |
| 239 | The relative position of field savePIPEA_GMCH_DATA_N has been changed from 202 to 203. | Applications will access incorrect memory when attempting to access this field. |
| 240 | The relative position of field savePIPEA_LINK_M1 has been changed from 222 to 223. | Applications will access incorrect memory when attempting to access this field. |
| 241 | The relative position of field savePIPEA_LINK_N1 has been changed from 223 to 224. | Applications will access incorrect memory when attempting to access this field. |
| 242 | The relative position of field savePIPEBCONF has been changed from 86 to 87. | Applications will access incorrect memory when attempting to access this field. |
| 243 | The relative position of field savePIPEBSRC has been changed from 88 to 89. | Applications will access incorrect memory when attempting to access this field. |
| 244 | The relative position of field savePIPEBSTAT has been changed from 138 to 139. | Applications will access incorrect memory when attempting to access this field. |
| 245 | The relative position of field savePIPEB_DATA_M1 has been changed from 224 to 225. | Applications will access incorrect memory when attempting to access this field. |
| 246 | The relative position of field savePIPEB_DATA_N1 has been changed from 225 to 226. | Applications will access incorrect memory when attempting to access this field. |
| 247 | The relative position of field savePIPEB_DP_LINK_M has been changed from 205 to 206. | Applications will access incorrect memory when attempting to access this field. |
| 248 | The relative position of field savePIPEB_DP_LINK_N has been changed from 207 to 208. | Applications will access incorrect memory when attempting to access this field. |
| 249 | The relative position of field savePIPEB_GMCH_DATA_M has been changed from 201 to 202. | Applications will access incorrect memory when attempting to access this field. |
| 250 | The relative position of field savePIPEB_GMCH_DATA_N has been changed from 203 to 204. | Applications will access incorrect memory when attempting to access this field. |
| 251 | The relative position of field savePIPEB_LINK_M1 has been changed from 226 to 227. | Applications will access incorrect memory when attempting to access this field. |
| 252 | The relative position of field savePIPEB_LINK_N1 has been changed from 227 to 228. | Applications will access incorrect memory when attempting to access this field. |
| 253 | The relative position of field savePP_CONTROL has been changed from 158 to 159. | Applications will access incorrect memory when attempting to access this field. |
| 254 | The relative position of field savePP_DIVISOR has been changed from 159 to 160. | Applications will access incorrect memory when attempting to access this field. |
| 255 | The relative position of field savePP_OFF has been changed from 157 to 158. | Applications will access incorrect memory when attempting to access this field. |
| 256 | The relative position of field savePP_OFF_DELAYS has been changed from 152 to 153. | Applications will access incorrect memory when attempting to access this field. |
| 257 | The relative position of field savePP_ON has been changed from 156 to 157. | Applications will access incorrect memory when attempting to access this field. |
| 258 | The relative position of field savePP_ON_DELAYS has been changed from 151 to 152. | Applications will access incorrect memory when attempting to access this field. |
| 259 | The relative position of field saveSWF0 has been changed from 179 to 180. | Applications will access incorrect memory when attempting to access this field. |
| 260 | The relative position of field saveTRANSACONF has been changed from 100 to 101. | Applications will access incorrect memory when attempting to access this field. |
| 261 | The relative position of field saveTRANSBCONF has been changed from 131 to 132. | Applications will access incorrect memory when attempting to access this field. |
| 262 | The relative position of field saveTRANS_HBLANK_A has been changed from 102 to 103. | Applications will access incorrect memory when attempting to access this field. |
| 263 | The relative position of field saveTRANS_HBLANK_B has been changed from 133 to 134. | Applications will access incorrect memory when attempting to access this field. |
| 264 | The relative position of field saveTRANS_HSYNC_A has been changed from 103 to 104. | Applications will access incorrect memory when attempting to access this field. |
| 265 | The relative position of field saveTRANS_HSYNC_B has been changed from 134 to 135. | Applications will access incorrect memory when attempting to access this field. |
| 266 | The relative position of field saveTRANS_HTOTAL_A has been changed from 101 to 102. | Applications will access incorrect memory when attempting to access this field. |
| 267 | The relative position of field saveTRANS_HTOTAL_B has been changed from 132 to 133. | Applications will access incorrect memory when attempting to access this field. |
| 268 | The relative position of field saveTRANS_VBLANK_A has been changed from 105 to 106. | Applications will access incorrect memory when attempting to access this field. |
| 269 | The relative position of field saveTRANS_VBLANK_B has been changed from 136 to 137. | Applications will access incorrect memory when attempting to access this field. |
| 270 | The relative position of field saveTRANS_VSYNC_A has been changed from 106 to 107. | Applications will access incorrect memory when attempting to access this field. |
| 271 | The relative position of field saveTRANS_VSYNC_B has been changed from 137 to 138. | Applications will access incorrect memory when attempting to access this field. |
| 272 | The relative position of field saveTRANS_VTOTAL_A has been changed from 104 to 105. | Applications will access incorrect memory when attempting to access this field. |
| 273 | The relative position of field saveTRANS_VTOTAL_B has been changed from 135 to 136. | Applications will access incorrect memory when attempting to access this field. |
| 274 | The relative position of field saveVBLANK_A has been changed from 97 to 98. | Applications will access incorrect memory when attempting to access this field. |
| 275 | The relative position of field saveVBLANK_B has been changed from 128 to 129. | Applications will access incorrect memory when attempting to access this field. |
| 276 | The relative position of field saveVGA0 has been changed from 145 to 146. | Applications will access incorrect memory when attempting to access this field. |
| 277 | The relative position of field saveVGA1 has been changed from 146 to 147. | Applications will access incorrect memory when attempting to access this field. |
| 278 | The relative position of field saveVGACNTRL has been changed from 148 to 149. | Applications will access incorrect memory when attempting to access this field. |
| 279 | The relative position of field saveVGA_PD has been changed from 147 to 148. | Applications will access incorrect memory when attempting to access this field. |
| 280 | The relative position of field saveVSYNC_A has been changed from 98 to 99. | Applications will access incorrect memory when attempting to access this field. |
| 281 | The relative position of field saveVSYNC_B has been changed from 129 to 130. | Applications will access incorrect memory when attempting to access this field. |
| 282 | The relative position of field saveVTOTAL_A has been changed from 96 to 97. | Applications will access incorrect memory when attempting to access this field. |
| 283 | The relative position of field saveVTOTAL_B has been changed from 127 to 128. | Applications will access incorrect memory when attempting to access this field. |
| 284 | The relative position of field save_palette_a has been changed from 161 to 162. | Applications will access incorrect memory when attempting to access this field. |
| 285 | The relative position of field sdvo_lvds_vbt_mode has been changed from 54 to 55. | Applications will access incorrect memory when attempting to access this field. |
| 286 | The relative position of field sr01 has been changed from 31 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 287 | The relative position of field status_page_dmah has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 288 | The relative position of field tex_lru_log_granularity has been changed from 28 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 289 | The relative position of field vblank_pipe has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_force_wake 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 adapter has been changed from 344 bytes to 352 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 idmap_user_hash has been changed from 17924 bytes to 8 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field idmap_group_hash has been changed from 17924 bytes to 8 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 | Type of field h_entries has been changed from struct idmap_hashent[128] (17920 bytes) to struct idmap_hashent* (4 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 h_entries has been increased from 0 to 1. | 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 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rann_interval 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 num_gates 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 mesh_preq_queue_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field mshcfg has been changed from 36 bytes to 40 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 | Size of field mshstats has been changed from 24 bytes to 28 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 filter_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field queue_stop_reason_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field sta_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Field hw_offchan_tx_cookie 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 security_idx 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 crypto_tx_tailroom_needed_cnt 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 tx_conf 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 u has been changed from 380 bytes to 392 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 | Size of field vif has been changed from 88 bytes to 128 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 dropped_frames_congestion 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 mesh has been changed from 336 bytes to 348 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field mgd has been changed from 380 bytes to 392 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 aca_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mca_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field stats has been changed from 20 bytes to 16 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 mc_lock has been changed from 4 bytes to 2 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field state_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ipv6 has been changed from struct ipstats_mib*[2] (8 bytes) to struct ipstats_mib*[1] (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 | Size of field lock has been changed from 4 bytes to 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vlan_tag has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field death_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tw_pad has been changed from 14 bits to 6 bits. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mc_tomb_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmtu_orig 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 rate_last 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 metrics 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 pmtu_expires 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 pmtu_learned 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 rate_tokens 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 redirect_genid 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 redirect_learned 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 unnamed1 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 | The relative position of field refcnt has been changed from 5 to 6. | 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 unnamed0 has been changed from 6 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | Field unused 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. |
| 13 | The relative position of field dtime has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field gc_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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field event_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 208 bytes to 216 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 i2c_speed has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field rsvd has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 592 bytes to 760 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 pending has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field semaphore_register 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 signal_mbox 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 sync_to 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 | Size of field irq_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field curr_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field percpu_dev_id 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dst has been changed from 84 bytes to 80 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_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. |
| 2 | Size of field securetcp_lock has been changed from 4 bytes to 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. |
| 3 | Size of field dropentry_lock has been changed from 4 bytes to 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. |
| 4 | Size of field droppacket_lock has been changed from 4 bytes to 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. |
| 5 | Size of field est_lock has been changed from 4 bytes to 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. |
| 6 | Size of field sync_buff_lock has been changed from 4 bytes to 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. |
| 7 | Size of field sync_lock has been changed from 4 bytes to 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field shm_rmid_forced 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 domain 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 hwirq 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 llnode 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 owner 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 percpu_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. |
| 3 | Field timer_rand_state 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 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 5 | Size of field irq_data has been changed from 32 bytes to 40 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 j_list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field j_revoke_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field j_state_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field t_handle_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field txlock 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 tx has been changed from 20 bytes 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. |
| 3 | Type of field rx has been changed from struct tkip_ctx[17] (340 bytes) to struct tkip_ctx[16] (384 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tx_pn has been changed from u8[6] (6 bytes) to struct atomic64_t (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. |
| 2 | Field rx_crypto_buf 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 tx_crypto_buf 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 tx_pn has been changed from u8[6] (6 bytes) to struct atomic64_t (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. |
| 2 | Field rx_crypto_buf 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 tx_crypto_buf 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 u has been changed from 360 bytes to 416 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 p1k_iv32 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 aes_cmac has been changed from 88 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. |
| 2 | Size of field ccmp has been changed from 316 bytes to 120 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field tkip has been changed from 360 bytes to 412 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 k_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 208 bytes to 216 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 2680 bytes to 2696 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 3244 bytes to 3268 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 tdev has been changed from 208 bytes to 216 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 sk_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field h_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field a_args has been changed from 312 bytes to 320 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 a_res has been changed from 292 bytes to 300 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 cancel_hw_scan 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 finish_tx_sync 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 set_rekey_data 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 tx_sync 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 bss_conf has been changed from 76 bytes to 116 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field icmp_statistics has been changed from struct icmp_mib*[2] (8 bytes) to struct icmp_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field udplite_stats_in6 has been changed from struct udp_mib*[2] (8 bytes) to struct udp_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field icmpv6_statistics has been changed from struct icmpv6_mib*[2] (8 bytes) to struct icmpv6_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 4 | Type of field ip_statistics has been changed from struct ipstats_mib*[2] (8 bytes) to struct ipstats_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 5 | Type of field ipv6_statistics has been changed from struct ipstats_mib*[2] (8 bytes) to struct ipstats_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 6 | Type of field net_statistics has been changed from struct linux_mib*[2] (8 bytes) to struct linux_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 7 | Type of field udp_statistics has been changed from struct udp_mib*[2] (8 bytes) to struct udp_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 8 | Type of field udp_stats_in6 has been changed from struct udp_mib*[2] (8 bytes) to struct udp_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 9 | Type of field udplite_statistics has been changed from struct udp_mib*[2] (8 bytes) to struct udp_mib*[1] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 10 | Type of field icmpmsg_statistics has been changed from struct icmpmsg_mib*[2] (8 bytes) to struct icmpmsg_mib*[1] (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. |
| 11 | Type of field tcp_statistics has been changed from struct tcp_mib*[2] (8 bytes) to struct tcp_mib*[1] (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. |
| 12 | Type of field icmpv6msg_statistics has been changed from struct icmpv6msg_mib*[2] (8 bytes) to struct icmpv6msg_mib*[1] (4 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field batch 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 nr 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 mapping has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_legacy_base 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 pinned_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. |
| 3 | Size of field ioctx_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field page_table_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed0 has been changed from 4 bytes to 12 bytes. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 2 | Field lru 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 25 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member NR_DIRTIED has been changed from 23 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member NR_ISOLATED_ANON has been changed from 20 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member NR_ISOLATED_FILE has been changed from 21 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member NR_SHMEM has been changed from 22 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 26 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member NR_WRITEBACK_TEMP has been changed from 19 to 20. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member NR_WRITTEN has been changed from 24 to 25. | 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[26] (26 bytes) to s8[27] (27 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field lru_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Type of field vm_stat has been changed from atomic_long_t[26] (104 bytes) to atomic_long_t[27] (108 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 m has been changed from 68 bytes to 72 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 event has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field wait_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hh_output 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 queue_xmit 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 hh has been changed from struct hh_cache* (4 bytes) to struct hh_cache (108 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 rules_mod_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field ct has been changed from 80 bytes to 88 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field mib has been changed from 100 bytes to 52 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Field dev_base_seq 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 | The relative position of field hh_len has been changed from 1 to 0. | 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 poll_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field addr_list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field tx_global_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field dev has been changed from 208 bytes to 216 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field uc_promisc has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 5 | Field ethtool_ntuple_list 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 ndo_set_vf_spoofchk 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 _xmit_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_match 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 prev_seq 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 seq 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 rx_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field call_rcu_sched 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 find_root_sec 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 state_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field so_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | 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 348 bytes to 332 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 dentry 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 slot_tbl_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cl_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field cl_layouts 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 layouts 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 pnfs_ld_data 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 pnfs_blksize 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 | Size of field backing_dev_info has been changed from 304 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. |
| 5 | Type of field attr_bitmask has been changed from u32[2] (8 bytes) to u32[3] (12 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 pg_ops 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. |
| 2 | The relative position of field pg_lseg has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field pg_doio 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 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 | Field 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sklist_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 pcie_type has been changed from 1 byte to 4 bits. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field extra_reg has been changed from unsigned int (4 bytes) to struct hw_perf_event_extra (20 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 2 | Field extra_config 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 extra_alloc 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 overflow_handler_context 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 rb_entry 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 pending has been changed from 8 bytes to 12 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 | Field mmap_user 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. |
| 5 | Field buffer 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | The relative position of field rcu_head has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field nr_cgroups has been changed from 21 to 20. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field nmi 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 sample 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 | Value of member PHY_INTERFACE_MODE_GMII has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member PHY_INTERFACE_MODE_MII has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member PHY_INTERFACE_MODE_RGMII has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member PHY_INTERFACE_MODE_RGMII_ID has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member PHY_INTERFACE_MODE_RGMII_RXID has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member PHY_INTERFACE_MODE_RGMII_TXID has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member PHY_INTERFACE_MODE_RMII has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member PHY_INTERFACE_MODE_RTBI has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 9 | Value of member PHY_INTERFACE_MODE_SGMII has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 10 | Value of member PHY_INTERFACE_MODE_TBI has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 208 bytes to 216 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 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 208 bytes to 216 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 208 bytes to 216 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 it_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 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 pde_unload_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Type of field namelen has been changed from unsigned int (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 3 | The relative position of field size has been changed from 7 to 5. | 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 mode has been changed from 3 to 1. | 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 nlink has been changed from 4 to 2. | 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 pde_openers has been changed from 20 to 17. | 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 proc_fops has been changed from 9 to 7. | 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 gid has been changed from 6 to 4. | 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 name has been changed from 2 to 20. | 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 uid has been changed from 5 to 3. | 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 data has been changed from 13 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field namelen has been changed from 1 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field count has been changed from 16 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field proc_iops has been changed from 8 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field read_proc has been changed from 14 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field subdir has been changed from 12 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field pde_unload_completion has been changed from 19 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field pde_users has been changed from 17 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field next has been changed from 10 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field parent has been changed from 11 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field write_proc has been changed from 15 to 13. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field power has been changed from 1424 bytes to 868 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 828 bytes to 272 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 lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fqslock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field onofflock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries_bytes 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 read_bytes 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 lock has been changed from 4 bytes to 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. |
| 4 | Type of field reader_lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dst has been changed from 84 bytes to 80 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 irq_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field irq_task_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field dev has been changed from 208 bytes to 216 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 wait_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field raw_lock has been changed from struct arch_rwlock_t to union arch_rwlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wait_lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field busylock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_nr_running 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 cpupri has been changed from 1272 bytes to 848 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | The relative position of field rcu has been changed from 1 to 2. | 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 rto_count 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. |
| 4 | The relative position of field online has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field rto_mask has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field span has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field avg_load_per_task has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field rt_runtime_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field siglock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_dirtied 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 nr_dirtied_pause 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 pi_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field alloc_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field pri_to_cpu has been changed from 1224 bytes to 816 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 count has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field sdev_dev has been changed from 208 bytes to 216 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. |
| 3 | Size of field sdev_gendev has been changed from 208 bytes to 216 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 208 bytes to 216 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 default_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field free_list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field shost_dev has been changed from 208 bytes to 216 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 | Size of field shost_gendev has been changed from 208 bytes to 216 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 host_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t (4 bytes) to raw_spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sync_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field check_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field owner_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field handle_irq 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 lock has been changed from 4 bytes to 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_partial 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 partial 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 list_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sk_dst_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field slock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this type has been changed from struct to union. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field slock 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 raw_lock has been changed from 4 bytes to 2 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 rlock has been changed from 4 bytes to 2 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 thread_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 208 bytes to 216 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 tid_rx_stop_requested 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 driver_buffered_tids 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 dummy 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field ampdu_mlme has been changed from 252 bytes to 256 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 sta has been changed from 40 bytes to 44 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 6 | Type of field ps_tx_buf has been changed from struct sk_buff_head (16 bytes) to struct sk_buff_head[4] (64 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 | Type of field tx_filtered has been changed from struct sk_buff_head (16 bytes) to struct sk_buff_head[4] (64 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 reorder_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field suspend_again 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 daddrlen 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 daddr has been changed from union svc_addr_u (16 bytes) to struct __kernel_sockaddr_storage (128 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 sp_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_cachetype 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 rq_daddrlen 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 rq_daddr has been changed from union svc_addr_u (16 bytes) to struct __kernel_sockaddr_storage (128 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 rq_cred 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. |
| 5 | The relative position of field rq_daddr has been changed from 27 to 5. | 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 rq_vec has been changed from 20 to 21. | 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 rq_xprt_hlen has been changed from 14 to 15. | 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 rq_flavor has been changed from 9 to 10. | 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_pages has been changed from 17 to 18. | 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 rq_prot 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. |
| 11 | The relative position of field rq_res has been changed from 16 to 17. | 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 rq_resused has been changed from 19 to 20. | 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 rq_secure 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. |
| 14 | The relative position of field rq_arg has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field rq_authop has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field rq_deferred has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field rq_pool has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field rq_proc has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field rq_procinfo has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field rq_prog has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field rq_respages has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field rq_server has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field rq_usedeferral has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field rq_vers has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field rq_xid has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field rq_xprt_ctxt has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sv_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field xpt_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field poll 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 inode_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. |
| 2 | Field name_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 u 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 | Size of field unnamed0 has been changed from 8 bytes to 16 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 | Size of field s_dir has been changed from 8 bytes to 16 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 | Type of field seq_fops has been changed from struct file_operations (104 bytes) to struct file_operations const* (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. |
| 2 | The pointer level of field seq_fops has been increased from 0 to 1. | 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 prior_cwnd 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 prr_delivered 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 prr_out 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 208 bytes to 216 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 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field read_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field ctrl_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field seq_fops has been changed from struct file_operations (104 bytes) to struct file_operations const* (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. |
| 2 | The pointer level of field seq_fops has been increased from 0 to 1. | 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 | Size of field lock has been changed from 4 bytes to 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field bos 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 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 208 bytes to 216 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_func 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 nr_drainers 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 more_io has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_nmi_reason 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 wallclock_init 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 lock has been changed from 252 bytes to 260 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 fl has been changed from 100 bytes to 108 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 lock has been changed from 252 bytes to 260 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 lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_reqs 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 reserve_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field transport_lock has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | The relative position of field max_reqs has been changed from 16 to 15. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_slot 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 this global data has been changed from 144 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_flags of type gfp_t 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 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sdata has been changed from struct ieee80211_sub_if_data (1180 bytes) to struct ieee80211_vif (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter period 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 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter q became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rq became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 248 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter context of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nmi has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 5th parameter sample 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 36 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter inode became passed in eax 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 __u32 (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev_id became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter irq became passed in edx 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 in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pool became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter file_priv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter handlep became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter obj became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | Size of this global data has been changed from 10 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter facility of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter q became passed in eax 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 struct request* (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type __be16 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 216 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mapping became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter offset became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter page became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gc_at became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter name became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pseudoflavor became passed on stack instead of eax 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 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hcd became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter irqflags became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter irqnum became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cvt_nid of type hda_nid_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter context of type void* 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter idp became passed in eax 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 path has been changed from struct path (8 bytes) to struct dentry (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter handle became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter inode became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter is_metadata became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags 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 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter l3 has been changed from struct amd_l3_cache (12 bytes) to struct amd_northbridge (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter l3 has been changed from struct amd_l3_cache (12 bytes) to struct amd_northbridge (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct intel_quirk[9] (144 bytes) to struct intel_quirk[16] (256 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 144 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 960 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 36044 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 492 bytes to 488 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 100 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 17924 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 756 bytes to 856 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 444 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 348 bytes to 332 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 48 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tclass of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter addr has been changed from struct in6_addr (16 bytes) to struct rt6_info (256 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 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 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter check 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 36 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 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 36 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 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter deadline became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter link became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nbcfg has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of return value has been changed from struct mdk_thread_s to struct md_thread of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter threadp has been changed from struct mdk_thread_s to struct md_thread of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter thread has been changed from struct mdk_thread_s to struct md_thread of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter rdev has been changed from struct mdk_rdev_s (188 bytes) to struct md_rdev (236 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 4th parameter check_acl has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 5th parameter nd has been changed from struct nameidata (96 bytes) to struct path (8 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter dentry became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mnt became passed on stack instead of edx 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 ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mnt became passed on stack instead of eax 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[39] (156 bytes) to struct nf_conntrack_l3proto*[40] (160 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const (8 bytes) to u32[3] const (12 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter doio has been changed from int(*)(struct nfs_pageio_descriptor*) (4 bytes) to struct nfs_pageio_ops (12 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mod has been changed from struct module (340 bytes) to struct module_kobject (48 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 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 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| 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 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 264 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 36 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 130 bytes to 129 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 960 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 36044 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 492 bytes to 488 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 100 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 17924 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 756 bytes to 856 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 444 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 348 bytes to 332 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 48 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 20 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 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 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 36 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 31 | 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 31 | 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 | Parameter check_access of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu of type 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 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter new_mask became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter action became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter q became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter task became passed on stack instead of edx 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 960 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 36044 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 492 bytes to 488 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 100 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 17924 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 756 bytes to 856 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 444 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 348 bytes to 332 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 48 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 960 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 36044 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 492 bytes to 488 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 100 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 17924 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 756 bytes to 856 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 444 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 348 bytes to 332 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 48 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 164 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter len has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gfp became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter index became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mapping became passed on stack instead of eax 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 | The parameter skb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter skb_size became passed in edx 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 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter use_effective has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter block became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter hw became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pubsta became passed in edx 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 2nd parameter regs has been changed from struct pt_regs (68 bytes) to struct stack_trace (16 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter trace has been changed from struct stack_trace (16 bytes) to struct pt_regs (68 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter node of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter rqstp became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter xprt became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter file became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter start became passed on stack instead of edx 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 304 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 380 bytes to 388 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 208 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 280 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 1024 bytes to 1116 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 1272 bytes to 848 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 1300 bytes to 876 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 1256 bytes to 1244 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 520 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 960 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36044 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 172 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 492 bytes to 488 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 100 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 72 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 17924 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 756 bytes to 856 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 444 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 348 bytes to 332 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 432 bytes to 436 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 48 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been decreased from 2 to 1. | Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from u8* to u8 const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter iv16 has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 5th parameter ta 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. |
| 2 | Base type of 3rd parameter pos has been changed from unsigned char (1 byte) to struct sk_buff (184 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buffer became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter flags became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pc became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nsec became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event_call became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter filter became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rec became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter jh became passed in eax 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 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 2 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 5980 bytes to 5960 bytes. | Applications will obtain a different 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 | 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 | Parameter directed of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ratemask of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter directed of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter no_cck of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ptes of type pte_t** 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 atomic_long_t[26] (104 bytes) to atomic_long_t[27] (108 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 104 bytes to 108 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*[77] const (308 bytes) to char const*[78] const (312 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 308 bytes to 312 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter local has been changed from struct ieee80211_local (3392 bytes) to struct ieee80211_sub_if_data (1268 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter task became passed on stack instead of eax 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 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max_alloc 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 type has been changed from 28 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 764 bytes to 772 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 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 tc_action_ops* to struct tc_action_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field act has been changed from int(*)(struct sk_buff*, struct tc_action*, struct tcf_result*) to int(*)(struct sk_buff*, struct tc_action const*, struct tcf_result*). | 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 112 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 44 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field function has been changed from void(*)(struct alarm*) to enum alarmtimer_restart(*)(struct alarm*, ktime_t). | 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 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field instr has been renamed to instr_offset. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field replacement has been renamed to repl_offset. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field l3_cache 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 8 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 | Field names_length 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 names_ptr 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 72 bytes to 84 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 enumerated has been changed from 72 bytes to 84 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 304 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 | Field list_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 | Size of this type has been changed from 96 bytes to 100 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 288 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 176 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 136 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field mddev has been changed from struct mddev_s (692 bytes) to struct mddev (688 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_end_io 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 12 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 208 bytes to 212 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 1024 bytes to 1116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*, struct bio*) to void()(struct request_queue*, struct bio*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 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 | Field set_rekey_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 | Field tdls_mgmt 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 tdls_oper 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 248 bytes to 260 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, u64*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, u64*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field set_txq_params has been changed from int(*)(struct wiphy*, struct ieee80211_txq_params*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_txq_params*). | 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 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field no_cck 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 32 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 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field four_way_handshake 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 gtk_rekey_failure 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 rfkill_release 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 dot11MeshGateAnnouncementProtocol 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 dot11MeshHWMPRannInterval 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 36 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 | Field assoc_req_ies 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 assoc_req_ies_len 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 80 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 384 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field max_sched_scan_ie_len 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 max_sched_scan_ssids 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 maxadj 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. |
| Change | Effect | |
|---|---|---|
| 1 | 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 640 bytes to 672 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 320 bytes to 324 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 828 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 | Field power_specified 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 safe_state_index 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 state_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. |
| 4 | Field states 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 | Size of this type has been changed from 20 bytes to 576 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 disable has been changed from void(*)(struct cpuidle_device*) to void(*)(struct cpuidle_driver*, struct cpuidle_device*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field enable has been changed from int(*)(struct cpuidle_device*) to int(*)(struct cpuidle_driver*, struct cpuidle_device*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field reflect has been changed from void(*)(struct cpuidle_device*) to void(*)(struct cpuidle_device*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field select has been changed from int(*)(struct cpuidle_device*) to int(*)(struct cpuidle_driver*, struct cpuidle_device*). | 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 88 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field enter has been changed from int(*)(struct cpuidle_device*, struct cpuidle_state*) to int(*)(struct cpuidle_device*, struct cpuidle_driver*, 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 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field discard_zeroes_data_unsupported 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 | Base type has been changed from int(*)(struct dm_target*, status_type_t, char*, unsigned int) to void(*)(struct dm_target*, status_type_t, char*, unsigned int). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace 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 16 bytes to 20 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 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field pwr_domain has been renamed to pm_domain. | 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 196 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field singleton 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 discards_supported has been renamed to immutable_target_type. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field immutable_target_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 332 bytes to 328 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 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 76 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 | Size of this type has been changed from 92 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 916 bytes to 912 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 316 bytes to 324 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 300 bytes to 316 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 100 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 28 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 328 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 | Size of this type has been changed from 84 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 default_mtu has been renamed to mtu. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex 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 1428 bytes to 1972 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mac_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 | Field nvm_ops 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 phy_ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Type of field mac_ops has been changed from struct e1000_mac_operations* to struct e1000_mac_operations const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field nvm_ops has been changed from struct e1000_nvm_operations* to struct e1000_nvm_operations const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field phy_ops has been changed from struct e1000_phy_operations* to struct e1000_phy_operations const*. | 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 80 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 | Field query_capsule_caps 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 query_variable_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. |
| 3 | Field update_capsule 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 68 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 query_variable_store 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 12 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 | Field efi_pstore_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. |
| 2 | Field walk_entry 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 28 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 | Base type has been changed from efi_status_t()(efi_char16_t*, efi_guid_t*, unsigned long, unsigned long, void*) to efi_status_t()(efi_char16_t*, efi_guid_t*, u32, unsigned long, void*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 bytes to 224 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 212 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field get_rxnfc has been changed from int(*)(struct net_device*, struct ethtool_rxnfc*, void*) to int(*)(struct net_device*, struct ethtool_rxnfc*, u32*). | 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 504 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 100 bytes to 108 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 fsync has been changed from int(*)(struct file*, int) to int(*)(struct file*, loff_t, loff_t, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dio_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 | Size of this type has been changed from 348 bytes to 332 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field i_opflags 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 | Base type of field permission has been changed from int(*)(struct inode*, int, unsigned int) to int(*)(struct inode*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Field check_acl has been renamed to get_acl. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_change has been renamed to lm_change. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field fl_break has been renamed to lm_break. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field fl_notify has been renamed to lm_notify. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field fl_grant has been renamed to lm_grant. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 5 | Field fl_compare_owner has been renamed to lm_compare_owner. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_shrink 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 444 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_cached_objects 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 free_cached_objects 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 84 bytes to 92 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 4 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 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 | Size of this type has been changed from 8328 bytes to 8332 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 380 bytes to 388 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 280 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 | Field set_usb2_hw_lpm 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 152 bytes to 156 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 664 bytes to 688 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ignore_misc_bit 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 no_jack_detect 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 32 bytes to 44 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 84 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 468 bytes to 724 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 3732 bytes to 3756 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 76 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 344 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 252 bytes to 260 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 400 bytes to 396 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_get 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 force_wake_put 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 update_plane 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 64 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 5012 bytes to 5108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field display_clock_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. |
| 3 | Type of field cfb_plane has been changed from int to enum plane. | 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 352 bytes to 360 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 7 bytes to 6 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 36044 bytes to 212 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 17924 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 | Size of this type has been changed from 17 bytes to 21 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field self_prot 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 tdls_discover_resp 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. |
| 3 | Field plink_action has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field synced 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 synced 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 last_ave_beacon_signal 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 rssi_max_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. |
| 3 | Field rssi_min_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. |
| 4 | Size of this type has been changed from 380 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 336 bytes to 348 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field queue has been renamed to seqno_idx. | 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 1180 bytes to 1268 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 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field peer_link has been renamed to peering. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field peer_link_len has been renamed to peering_len. | 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 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 380 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 280 bytes to 276 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 140 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 20 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 112 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sin_family has been changed from sa_family_t to __kernel_sa_family_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 72 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_tos 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 156 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 108 bytes to 8 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu has been renamed to gc_rcu. | 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 664 bytes to 672 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field do_idle_maps 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 device_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field t12 has been renamed to t11_t12. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field t3 has been renamed to t1_t3. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field t7 has been renamed to t8. | 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 596 bytes to 764 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 | Field no_pll 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 1356 bytes to 1364 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field use_pll_a 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 spd 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 192 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tos 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 | Type of field next_offset has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field target_offset has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flags has been changed from u_int8_t to __u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field invflags has been changed from u_int8_t to __u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field proto has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field tos has been changed from u_int8_t to __u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field next_offset has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field target_offset has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flags has been changed from u_int8_t to __u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field invflags has been changed from u_int8_t to __u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field proto has been changed from u_int16_t to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field state_transition has been changed from int(*)(struct ip_vs_conn*, int, struct sk_buff const*, struct ip_vs_proto_data*) to void(*)(struct ip_vs_conn*, int, struct sk_buff const*, struct ip_vs_proto_data*). | 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 804 bytes to 820 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 232 bytes to 236 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 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 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field next has been renamed to flags. | 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 128 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 | Type of field b_cow_tid has been changed from unsigned int to tid_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 360 bytes to 412 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 316 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 88 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 400 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 | 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 360 bytes to 416 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 1340 bytes to 1348 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 3244 bytes to 3268 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 9472 bytes to 9536 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 700 bytes to 716 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_ssid 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 ssid 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 ssid_len 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 76 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allow_buffered_frames 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 release_buffered_frames 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 rssi_callback 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 196 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field conf_tx has been changed from int(*)(struct ieee80211_hw*, u16, struct ieee80211_tx_queue_params const*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, u16, struct ieee80211_tx_queue_params const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field get_tsf has been changed from u64(*)(struct ieee80211_hw*) to u64(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field reset_tsf has been changed from void(*)(struct ieee80211_hw*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field set_tsf has been changed from void(*)(struct ieee80211_hw*, u64) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, u64). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_sp 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 uapsd_queues 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 wme 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 40 bytes to 44 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 88 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 | Size of this type has been changed from 100 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_in_batch 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 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pobjects 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 pages 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 432 bytes to 436 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _count has been renamed to mapping. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru 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 ptl has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 3 | Field first_page has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 4 | Field slab has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field first_page 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 ptl 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. |
| 3 | Field slab 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. |
| 4 | Field freelist has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 5 | Field index has been renamed to private. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show has been changed from ssize_t(*)(struct module_attribute*, struct module*, char*) to ssize_t(*)(struct module_attribute*, struct module_kobject*, char*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct module_attribute*, struct module*, char const*, size_t) to ssize_t(*)(struct module_attribute*, struct module_kobject*, char const*, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash_mask has been renamed to hash_shift. | 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 28 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field connected_output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | 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 172 bytes to 276 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | The pointer level of field hh 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 cache has been changed from int(*)(struct neighbour const*, struct hh_cache*) to int(*)(struct neighbour const*, struct hh_cache*, __be16). | 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 192 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field hh_refcnt has been renamed to __pad. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request. | 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 144 bytes to 140 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 44 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 44 bytes to 52 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 12 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 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 | Base type of field sched_state_renewal has been changed from int(*)(struct nfs_client*, struct rpc_cred*) to int(*)(struct nfs_client*, struct rpc_cred*, unsigned 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 652 bytes to 628 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 60 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field server_scope 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 492 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 756 bytes to 856 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_recoalesce 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 pg_test has been renamed to pg_rpc_callops. | 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 432 bytes to 436 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 172 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 460 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 360 bytes to 368 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pme_poll 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 892 bytes to 900 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field pcie_mpss 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 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 | Type of field latency_pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request. | 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 48 bytes to 52 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 520 bytes to 528 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mmap_locked has been renamed to rb. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field exclude_guest 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 exclude_host 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 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 buffer has been renamed to rb. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(struct perf_event*, int, struct perf_sample_data*, struct pt_regs*) to void(*)(struct perf_event*, struct perf_sample_data*, struct pt_regs*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 412 bytes to 420 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 404 bytes to 412 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 232 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 | Field constraints 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 subsys_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. |
| 3 | Field wakeup_path 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 40 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field ignore_children 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 308 bytes to 316 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 368 bytes to 376 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 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alarmtimer has been renamed to alarm. | 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 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 | Size of this type has been changed from 88 bytes to 80 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 name 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 name has been changed from char const* to char[]. | 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 1660 bytes to 1104 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 1424 bytes to 868 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field microcode 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 rsp 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 132 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field passed_quiesc has been renamed to passed_quiesce. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field passed_quiesc_completed has been renamed to passed_quiesce_gpnum. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(int, struct die_args*) to void(*)(int, struct pt_regs*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field synflood_warned 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 88 bytes to 92 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 148 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 | Field uie_unsupported 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 536 bytes to 548 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 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 Qdisc_ops* to struct Qdisc_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field classify has been changed from int(*)(struct sk_buff*, struct tcf_proto*, struct tcf_result*) to int(*)(struct sk_buff*, struct tcf_proto const*, struct tcf_result*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | 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. |
| 3 | Type of field ops has been changed from struct tcf_proto_ops* to struct tcf_proto_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field classify has been changed from int(*)(struct sk_buff*, struct tcf_proto*, struct tcf_result*) to int(*)(struct sk_buff*, struct tcf_proto const*, struct tcf_result*). | 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 144 bytes to 148 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 1300 bytes to 876 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 cfs has been changed from 144 bytes to 148 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | The pointer level of field wake_list 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 wake_list has been changed from struct task_struct* to struct llist_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field idle_at_tick has been renamed to idle_balance. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfs_bandwidth 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 1256 bytes to 1244 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 wake_entry 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 wake_entry has been changed from struct task_struct* to struct llist_node. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field group_stop has been renamed to jobctl. | 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 1272 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 12 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 | Size of this type has been changed from 640 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 | Field match 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 52 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 292 bytes to 300 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 676 bytes to 692 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 164 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 | Base type of field inode_permission has been changed from int(*)(struct inode*, int, unsigned int) to int(*)(struct inode*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field poll_event 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 68 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 156 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 160 bytes to 164 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 164 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 364 bytes to 368 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field shm_creator 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 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field l4_rxhash 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 | The pointer level of field page 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 reserved_tailroom 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 112 bytes to 116 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 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ss_family has been changed from unsigned short to __kernel_sa_family_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from unsigned short to __kernel_sa_family_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | 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 4 bytes to 2 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 4 bytes to 2 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 4 bytes to 2 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 4 bytes to 2 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4 bytes to 2 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 | Size of this type has been changed from 252 bytes to 256 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 588 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field flags has been changed from u32 to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field failed_bar_ssn 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 bar_pending 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 92 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 36 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 192 bytes to 308 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 3496 bytes to 3616 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 36 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 48 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 inode_tree 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 name_tree 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 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field children has been renamed to subdirs. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace 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 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 | Size of this type has been changed from 8 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 128 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field seq_fops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1224 bytes to 1236 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 calc_md5_hash has been changed from int(*)(char*, struct tcp_md5sig_key*, struct sock*, struct request_sock*, struct sk_buff*) to int(*)(char*, struct tcp_md5sig_key*, struct sock const*, struct request_sock const*, struct sk_buff const*). | 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 248 bytes to 256 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 396 bytes to 404 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 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 | Base type of field module has been changed from struct module (340 bytes) to struct tp_module (16 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field seq_fops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 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 660 bytes to 672 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field lpm_capable 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 usb2_hw_lpm_capable 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 usb2_hw_lpm_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 260 bytes to 268 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 224 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 60 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 | Size of this type has been changed from 84 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 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 28 bytes to 36 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 312 bytes to 320 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 252 bytes to 260 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 292 bytes to 300 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 844 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field slot has been renamed to min_reqs. | 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 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field reserve_xprt has been changed from int(*)(struct rpc_task*) to int(*)(struct rpc_xprt*, struct rpc_task*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter act has been changed from struct tc_action* to struct tc_action const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sdata has been renamed to vif. | 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 | Base type of 3rd parameter function has been changed from void(*)(struct alarm*) to enum alarmtimer_restart(*)(struct alarm*, ktime_t). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nr_iovecs has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nr_iovecs has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter now has been renamed to force. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ops has been changed from struct acpi_dock_ops* to struct acpi_dock_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 e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter max_effects has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter flen has been changed from int to unsigned int. | 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 long (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nid has been renamed to associated_nid. | 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 | 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 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 1st parameter page has been changed from struct page* to struct page 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 unsigned int to int. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter daddr has been changed from struct inetpeer_addr* to struct inetpeer_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter path has been renamed to dentry. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter l3 has been renamed to nb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter l3 has been renamed to nb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter avi_if has been renamed to frame. | 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 id has been renamed to ioapic_idx. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to ioapic_idx. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to ioapic_idx. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter addr has been renamed to rt. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter arg has been changed from struct ip_reply_arg* to struct ip_reply_arg const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to work. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to work. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter a has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct mce*, u32) to void(*)(int, struct mce*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct mce*, u32) to void(*)(int, struct mce*). | Replacement of parameter base 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. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter run has been changed from void(*)(mddev_t*) to void(*)(struct mddev*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter p has been changed from struct mdk_personality to struct md_personality. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter p has been changed from struct mdk_personality to struct md_personality. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nd has been renamed to path. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter doio has been renamed to pg_ops. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mod has been renamed to mk. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops to struct pci_raw_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops* to struct pci_raw_ops const*. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops* to struct pci_raw_ops const*. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dep has been renamed to req. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter dep has been changed from struct pm_qos_request_list to struct pm_qos_request. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pm_qos_req has been renamed to req. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter req has been changed from struct pm_qos_request_list to struct pm_qos_request. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pm_qos_req has been renamed to req. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode_p has been changed from mode_t* to umode_t*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter mode has been changed from mode_t to umode_t. | 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 thermal_cooling_device_ops to struct thermal_cooling_device_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter kill has been renamed to ignore_state. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter tp has been changed from struct tcf_proto* to struct tcf_proto const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter tp has been changed from struct tcf_proto* to struct tcf_proto const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter daddr has been changed from __be32* to __be32 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter saddr has been changed from __be32* to __be32 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter add_head has been renamed to realloc_head. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter in has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter W has been renamed to array. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter start has been renamed to lstart. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter end has been renamed to lend. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to swap. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trace has been renamed to regs. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter regs has been renamed to trace. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter skb has been changed from struct sk_buff* to struct sk_buff 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 struct tcp_md5sig_pool** to struct tcp_md5sig_pool*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock* to struct sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter th has been changed from struct tcphdr* to struct tcphdr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter key has been changed from struct tcp_md5sig_key* to struct tcp_md5sig_key const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dst has been changed from struct dst_entry* to struct dst_entry const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter tp has been changed from struct tcp_sock* to struct tcp_sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter th has been changed from struct tcphdr* to struct tcphdr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from u8* to u8 const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter hvpp has been changed from u8** to u8 const**. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter th has been changed from struct tcphdr* to struct tcphdr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter th has been changed from struct tcphdr* to struct tcphdr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter req has been changed from struct request_sock* to struct request_sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter sk has been changed from struct sock* to struct sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 5th parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock* to struct sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock* to struct sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pos has been renamed to skb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 4th parameter payload_len has been renamed to payload. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 5th parameter ta has been renamed to payload_len. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | Type of 4th parameter payload_len has been changed from size_t to u8*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 5 | Type of 5th parameter ta has been changed from u8* to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter old has been renamed to oldsize. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter new has been renamed to newsize. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter offset has been renamed to newsize. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter offset has been renamed to lstart. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter end has been renamed to lend. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter size has been changed from int to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member HID_TYPE_USBNONE with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_QUEUE_STOP_REASON_CHTYPE_CHANGE with value 6 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_VMSCAN_IMMEDIATE with value 19 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_NA with value 0 has been added. | No effect. |
| 2 | The member PHY_INTERFACE_MODE_SMII with value 11 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.0.101 |
| Version #2 | 3.2.52 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 740 |
|---|---|
| Total Source Files | 1359 |
| Total Objects | 1 |
| Total Symbols / Types | 14718 / 8298 |
| Verdict | Incompatible (55.6%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 458 |
| Removed Symbols | High | 122 |
| Problems with Data Types | High | 133 |
| Medium | 44 | |
| Low | 318 | |
| Problems with Symbols | High | 29 |
| Medium | 117 | |
| Low | 44 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 457 |
| Other Changes in Symbols | - | 45 |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct alarm' has no member named 'enabled'. |
| 2 | Field period has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct alarm' has no member named 'period'. |
| Change | Effect | |
|---|---|---|
| 1 | Field instr has been renamed to instr_offset. | Recompilation of a client program may be broken with the error message: struct alt_instr has no member named instr. |
| 2 | Field replacement has been renamed to repl_offset. | Recompilation of a client program may be broken with the error message: struct alt_instr has no member named replacement. |
| Change | Effect | |
|---|---|---|
| 1 | Field logattrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'logattrs'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bi_comp_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bio' has no member named 'bi_comp_cpu'. |
| Change | Effect | |
|---|---|---|
| 1 | Field vread has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct clocksource' has no member named 'vread'. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'last_state'. |
| 2 | Field power_specified has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'power_specified'. |
| 3 | Field prepare has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'prepare'. |
| 4 | Field safe_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'safe_state'. |
| 5 | Field states has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'states'. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_state' has no member named 'driver_data'. |
| 2 | Field time has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_state' has no member named 'time'. |
| 3 | Field usage has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_state' has no member named 'usage'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pwr_domain has been renamed to pm_domain. | Recompilation of a client program may be broken with the error message: struct device has no member named pwr_domain. |
| Change | Effect | |
|---|---|---|
| 1 | Field discards_supported has been renamed to immutable_target_type. | Recompilation of a client program may be broken with the error message: struct dm_table has no member named discards_supported. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_make_request_fn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mapped_device' has no member named 'saved_make_request_fn'. |
| Change | Effect | |
|---|---|---|
| 1 | Field debugfs_nodes 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 'debugfs_nodes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hh has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dst_entry' has no member named 'hh'. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_mtu has been renamed to mtu. | Recompilation of a client program may be broken with the error message: struct dst_ops has no member named default_mtu. |
| Change | Effect | |
|---|---|---|
| 1 | Field phy_info_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'phy_info_timer'. |
| 2 | Field tx_fifo_stall_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'tx_fifo_stall_timer'. |
| 3 | Field vlgrp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'vlgrp'. |
| 4 | Field watchdog_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'watchdog_timer'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_rx_ntuple has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_rx_ntuple'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_alloc_sem_key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct file_system_type' has no member named 'i_alloc_sem_key'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_alloc_sem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'i_alloc_sem'. |
| 2 | Field i_nlink has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'i_nlink'. |
| Change | Effect | |
|---|---|---|
| 1 | Field check_acl has been renamed to get_acl. | Recompilation of a client program may be broken with the error message: struct inode_operations has no member named check_acl. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_break has been renamed to lm_break. | Recompilation of a client program may be broken with the error message: struct lock_manager_operations has no member named fl_break. |
| 2 | Field fl_change has been renamed to lm_change. | Recompilation of a client program may be broken with the error message: struct lock_manager_operations has no member named fl_change. |
| 3 | Field fl_compare_owner has been renamed to lm_compare_owner. | Recompilation of a client program may be broken with the error message: struct lock_manager_operations has no member named fl_compare_owner. |
| 4 | Field fl_grant has been renamed to lm_grant. | Recompilation of a client program may be broken with the error message: struct lock_manager_operations has no member named fl_grant. |
| 5 | Field fl_notify has been renamed to lm_notify. | Recompilation of a client program may be broken with the error message: struct lock_manager_operations has no member named fl_notify. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dentry has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field i_rcu has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_bdev has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field i_cdev has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field i_pipe has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field spdif_ctls 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 'spdif_ctls'. |
| 2 | Field spdif_status 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 'spdif_status'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfb_fence 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 'cfb_fence'. |
| 2 | Field cfb_offset 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 'cfb_offset'. |
| 3 | Field cfb_pitch 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 'cfb_pitch'. |
| 4 | Field panel_fixed_mode 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 'panel_fixed_mode'. |
| 5 | Field panel_t12 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 'panel_t12'. |
| 6 | Field panel_t3 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 'panel_t3'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i2c_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sdvo_device_mapping' has no member named 'i2c_speed'. |
| Change | Effect | |
|---|---|---|
| 1 | Field plink_action has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_offchan_tx_cookie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'hw_offchan_tx_cookie'. |
| Change | Effect | |
|---|---|---|
| 1 | Field queue has been renamed to seqno_idx. | Recompilation of a client program may be broken with the error message: struct ieee80211_rx_data has no member named queue. |
| Change | Effect | |
|---|---|---|
| 1 | Field ethertype has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_tx_data' has no member named 'ethertype'. |
| Change | Effect | |
|---|---|---|
| 1 | Field peer_link has been renamed to peering. | Recompilation of a client program may be broken with the error message: struct ieee802_11_elems has no member named peer_link. |
| 2 | Field peer_link_len has been renamed to peering_len. | Recompilation of a client program may be broken with the error message: struct ieee802_11_elems has no member named peer_link_len. |
| Change | Effect | |
|---|---|---|
| 1 | Field vgrp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_lro_desc' has no member named 'vgrp'. |
| 2 | Field vlan_tag has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_lro_desc' has no member named 'vlan_tag'. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field rcu has been renamed to gc_rcu. | Recompilation of a client program may be broken with the error message: anon-union-inetpeer.h-44 has no member named rcu. |
| Change | Effect | |
|---|---|---|
| 1 | Field i2c_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct child_device_config' has no member named 'i2c_speed'. |
| 2 | Field rsvd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct child_device_config' has no member named 'rsvd'. |
| Change | Effect | |
|---|---|---|
| 1 | Field t12 has been renamed to t11_t12. | Recompilation of a client program may be broken with the error message: struct edp_power_seq has no member named t12. |
| 2 | Field t3 has been renamed to t1_t3. | Recompilation of a client program may be broken with the error message: struct edp_power_seq has no member named t3. |
| 3 | Field t7 has been renamed to t8. | Recompilation of a client program may be broken with the error message: struct edp_power_seq has no member named t7. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'ctl_key'. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been renamed to flags. | Recompilation of a client program may be broken with the error message: struct irq_work has no member named next. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_crypto_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-key.h-80' has no member named 'rx_crypto_buf'. |
| 2 | Field tx_crypto_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-key.h-80' has no member named 'tx_crypto_buf'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_crypto_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-key.h-98' has no member named 'rx_crypto_buf'. |
| 2 | Field tx_crypto_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-key.h-98' has no member named 'tx_crypto_buf'. |
| Change | Effect | |
|---|---|---|
| 1 | Field offchannel_tx 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 'offchannel_tx'. |
| 2 | Field offchannel_tx_cancel_wait 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 'offchannel_tx_cancel_wait'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct shrinker' has no member named 'nr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mapping has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-mm_types.h-63' has no member named 'mapping'. |
| Change | Effect | |
|---|---|---|
| 1 | Field oom_disable_count 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 'oom_disable_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct page' has no member named 'lru'. |
| 2 | Field _count has been renamed to mapping. | Recompilation of a client program may be broken with the error message: struct page has no member named _count. |
| Change | Effect | |
|---|---|---|
| 1 | Field ptl has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field first_page has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field slab has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field freelist has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field index has been renamed to private. | Recompilation of a client program may be broken with the error message: anon-union-mm_types.h-85 has no member named index. |
| Change | Effect | |
|---|---|---|
| 1 | Field event has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct proc_mounts' has no member named 'event'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash_mask has been renamed to hash_shift. | Recompilation of a client program may be broken with the error message: struct neigh_hash_table has no member named hash_mask. |
| Change | Effect | |
|---|---|---|
| 1 | Field queue_xmit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct neigh_ops' has no member named 'queue_xmit'. |
| 2 | Field hh_output has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct neigh_ops' has no member named 'hh_output'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hh_next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hh_cache' has no member named 'hh_next'. |
| 2 | Field hh_output has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hh_cache' has no member named 'hh_output'. |
| 3 | Field hh_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hh_cache' has no member named 'hh_type'. |
| 4 | Field hh_refcnt has been renamed to __pad. | Recompilation of a client program may be broken with the error message: struct hh_cache has no member named hh_refcnt. |
| Change | Effect | |
|---|---|---|
| 1 | Field ethtool_ntuple_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'ethtool_ntuple_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_vlan_rx_register has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device_ops' has no member named 'ndo_vlan_rx_register'. |
| 2 | Field ndo_set_multicast_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device_ops' has no member named 'ndo_set_multicast_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field change_attr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_inode' has no member named 'change_attr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field path has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_open_context' has no member named 'path'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_layouts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_client' has no member named 'cl_layouts'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_doio has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_pageio_descriptor' has no member named 'pg_doio'. |
| 2 | Field pg_test has been renamed to pg_rpc_callops. | Recompilation of a client program may be broken with the error message: struct nfs_pageio_descriptor has no member named pg_test. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'flags'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lookupfh 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 'lookupfh'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'flags'. |
| Change | Effect | |
|---|---|---|
| 1 | Field extra_alloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-perf_event.h-545' has no member named 'extra_alloc'. |
| 2 | Field extra_config has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-perf_event.h-545' has no member named 'extra_config'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_user has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event' has no member named 'mmap_user'. |
| 2 | Field buffer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event' has no member named 'buffer'. |
| 3 | Field mmap_locked has been renamed to rb. | Recompilation of a client program may be broken with the error message: struct perf_event has no member named mmap_locked. |
| Change | Effect | |
|---|---|---|
| 1 | Field nmi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_output_handle' has no member named 'nmi'. |
| 2 | Field sample has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_output_handle' has no member named 'sample'. |
| 3 | Field buffer has been renamed to rb. | Recompilation of a client program may be broken with the error message: struct perf_output_handle has no member named buffer. |
| Change | Effect | |
|---|---|---|
| 1 | Field alarmtimer has been renamed to alarm. | Recompilation of a client program may be broken with the error message: anon-union-posix-timers.h-72 has no member named alarmtimer. |
| Change | Effect | |
|---|---|---|
| 1 | Field a_refcount has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct posix_acl' has no member named 'a_refcount'. |
| Change | Effect | |
|---|---|---|
| 1 | Field passed_quiesc has been renamed to passed_quiesce. | Recompilation of a client program may be broken with the error message: struct rcu_data has no member named passed_quiesc. |
| 2 | Field passed_quiesc_completed has been renamed to passed_quiesce_gpnum. | Recompilation of a client program may be broken with the error message: struct rcu_data has no member named passed_quiesc_completed. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg_load_per_task has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'avg_load_per_task'. |
| 2 | Field idle_at_tick has been renamed to idle_balance. | Recompilation of a client program may be broken with the error message: struct rq has no member named idle_at_tick. |
| Change | Effect | |
|---|---|---|
| 1 | Field dirties has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_struct' has no member named 'dirties'. |
| 2 | Field fs_excl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_struct' has no member named 'fs_excl'. |
| 3 | Field group_stop has been renamed to jobctl. | Recompilation of a client program may be broken with the error message: struct task_struct has no member named group_stop. |
| Change | Effect | |
|---|---|---|
| 1 | Field pri_active has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpupri' has no member named 'pri_active'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpupri_vec' has no member named 'lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tlet has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct uart_state' has no member named 'tlet'. |
| Change | Effect | |
|---|---|---|
| 1 | Field slock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct arch_spinlock' has no member named 'slock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flaglock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_info' has no member named 'flaglock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_sibling has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysfs_dirent' has no member named 's_sibling'. |
| Change | Effect | |
|---|---|---|
| 1 | Field children has been renamed to subdirs. | Recompilation of a client program may be broken with the error message: struct sysfs_elem_dir has no member named children. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been renamed to ops. | Recompilation of a client program may be broken with the error message: struct filter_pred has no member named unnamed0. |
| Change | Effect | |
|---|---|---|
| 1 | Field encountered_congestion has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'encountered_congestion'. |
| 2 | Field more_io has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'more_io'. |
| 3 | Field nonblocking has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'nonblocking'. |
| 4 | Field older_than_this has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'older_than_this'. |
| 5 | Field wb_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'wb_start'. |
| Change | Effect | |
|---|---|---|
| 1 | Field resend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_xprt' has no member named 'resend'. |
| 2 | Field slot has been renamed to min_reqs. | Recompilation of a client program may be broken with the error message: struct rpc_xprt has no member named slot. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter scratch has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter start of type loff_t has been added to the calling stack at the middle position. | 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 at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter nmi has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter nmi 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 start of type loff_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nr_pages of type long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter start of type loff_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter context of type void* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter start of type loff_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter start of type loff_t 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 node_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter no_cck of type bool has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter neigh of type struct neighbour* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter neigh of type struct neighbour* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter neigh of type struct neighbour* 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 path has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter path has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter path has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter indices of type unsigned long* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter initxattrs of type initxattrs const has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter fs_data of type void* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 3 | 4th middle parameter name has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 5th middle parameter value has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ratemask 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 | Parameter num_prealloc 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 xprt of type struct rpc_xprt* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter xprt of type struct rpc_xprt* has been added to the calling stack at the middle position. | 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 tc_action::ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id_lock has been changed from spinlock_t to struct rwlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fifo_stall_task has been changed from struct work_struct to struct delayed_work of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field phy_info_task has been changed from struct work_struct to struct delayed_work of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mac_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct e1000_info::mac_ops'. |
| 2 | Field nvm_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct e1000_info::nvm_ops'. |
| 3 | Field phy_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct e1000_info::phy_ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field forcewake_count has been changed from struct atomic_t to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field h_entries has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pending has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tx_pn has been changed from u8[6] to struct atomic64_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tx_pn has been changed from u8[6] to struct atomic64_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field hh has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field latency_pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field extra_reg has been changed from unsigned int to struct hw_perf_event_extra of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field reader_lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field raw_lock has been changed from struct arch_rwlock_t to union arch_rwlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wait_lock has been changed from spinlock_t to raw_spinlock_t 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 Qdisc::ops'. |
| 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 tcf_proto::ops'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field wake_list has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field wake_entry has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field count has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field page has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this type has been changed from struct to union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ps_tx_buf has been changed from struct sk_buff_head to struct sk_buff_head[4] of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field tx_filtered has been changed from struct sk_buff_head to struct sk_buff_head[4] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field daddr has been changed from union svc_addr_u to struct __kernel_sockaddr_storage of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rq_daddr has been changed from union svc_addr_u to struct __kernel_sockaddr_storage of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field seq_fops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct tcp_seq_afinfo::seq_fops'. |
| 2 | The pointer level of field seq_fops has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field module has been changed from struct module to struct tp_module of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field seq_fops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct udp_seq_afinfo::seq_fops'. |
| 2 | The pointer level of field seq_fops has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_flags of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sdata has been changed from struct ieee80211_sub_if_data to struct ieee80211_vif of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter period has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of parameter now has been changed from ktime_t to bool of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter context of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nmi has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 5th parameter sample has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from __u32 (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags 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 | This global data became const. | 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 | This global data became const. | 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 | This global data became const. | 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 | This global data became const. | 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 | This global data became const. | 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 | Parameter facility of type int 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 request* (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type __be16 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum wb_reason has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cvt_nid of type hda_nid_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter context of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter path has been changed from struct path to struct dentry of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter l3 has been changed from struct amd_l3_cache to struct amd_northbridge of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter l3 has been changed from struct amd_l3_cache to struct amd_northbridge of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tclass of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter addr has been changed from struct in6_addr to struct rt6_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter check of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nbcfg has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev_s to struct mddev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter rdev has been changed from struct mdk_rdev_s to struct md_rdev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th parameter check_acl has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter nd has been changed from struct nameidata to struct path of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mod has been changed from struct module to struct module_kobject of different format. | 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 | This global data became const. | 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 dep has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter req has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter pm_qos_req has been changed from struct pm_qos_request_list to struct pm_qos_request of different format. | 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 | Parameter check_access of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter use_effective has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter regs has been changed from struct pt_regs to struct stack_trace of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter trace has been changed from struct stack_trace to struct pt_regs of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter node of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from u8* to u8 const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter iv16 has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter pos has been changed from unsigned char to struct sk_buff of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 4th parameter payload_len has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 5th parameter ta has been increased from 1 to 0. | 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 directed of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ratemask of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter directed of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter no_cck of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ptes of type pte_t** has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter local has been changed from struct ieee80211_local to struct ieee80211_sub_if_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max_alloc of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field probe 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 act has been changed from int(*)(struct sk_buff*, struct tc_action*, struct tcf_result*) to int(*)(struct sk_buff*, struct tc_action const*, struct tcf_result*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ki_batch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field function has been changed from void(*)(struct alarm*) to enum alarmtimer_restart(*)(struct alarm*, ktime_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field report has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field l3_cache has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field names_length has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field names_ptr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field written_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field write_bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field balanced_dirty_ratelimit has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field dirtied_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field bw_time_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field avg_write_bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field dirty_ratelimit has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Type of field bdi_stat has been changed from struct percpu_counter[2] to struct percpu_counter[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field list_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysfs_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_end_io has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bsg_job_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bsg_job_fn has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*, struct bio*) to void()(struct request_queue*, struct bio*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_rekey_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tdls_mgmt has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tdls_oper has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, u64*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, u64*). | Recompilation of a client program may be broken. |
| 5 | Base type of field set_txq_params has been changed from int(*)(struct wiphy*, struct ieee80211_txq_params*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_txq_params*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_cck has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rates has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field match_sets has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field n_match_sets has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eap_identity_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field four_way_handshake has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gtk_rekey_failure has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rfkill_release has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshGateAnnouncementProtocol has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dot11MeshHWMPRannInterval has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field assoc_req_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field assoc_req_ies_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sta_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_match_sets has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field registered has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field max_sched_scan_ie_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field max_sched_scan_ssids has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_next_ktime has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field maxadj has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nf_expect_event_cb has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nf_conntrack_event_cb has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_bsp_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field states_usage has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field power_specified has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field safe_state_index has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field state_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field states 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 disable has been changed from void(*)(struct cpuidle_device*) to void(*)(struct cpuidle_driver*, struct cpuidle_device*). | Recompilation of a client program may be broken. |
| 2 | Base type of field enable has been changed from int(*)(struct cpuidle_device*) to int(*)(struct cpuidle_driver*, struct cpuidle_device*). | Recompilation of a client program may be broken. |
| 3 | Base type of field reflect has been changed from void(*)(struct cpuidle_device*) to void(*)(struct cpuidle_device*, int). | Recompilation of a client program may be broken. |
| 4 | Base type of field select has been changed from int(*)(struct cpuidle_device*) to int(*)(struct cpuidle_driver*, struct cpuidle_device*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field enter has been changed from int(*)(struct cpuidle_device*, struct cpuidle_state*) to int(*)(struct cpuidle_device*, struct cpuidle_driver*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field state_usage has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_prune has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field discard_zeroes_data_unsupported has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct dm_target*, status_type_t, char*, unsigned int) to void(*)(struct dm_target*, status_type_t, char*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field iommu_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field singleton has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field immutable_target_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field audio_latency has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dvi_dual has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field eld has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field latency_present has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field max_tmds_clock has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field video_latency has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cea_rev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_close_object has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gem_open_object has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field debugfs_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field debugfs_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field neigh_lookup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_vlans has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field watchdog_task has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_capsule_caps has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field query_variable_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field runtime_version has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field update_capsule has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_capsule_caps has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field query_variable_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field update_capsule has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_variable_store has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field efi_pstore_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field walk_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from efi_status_t()(efi_char16_t*, efi_guid_t*, unsigned long, unsigned long, void*) to efi_status_t()(efi_char16_t*, efi_guid_t*, u32, unsigned long, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field get_rxnfc has been changed from int(*)(struct net_device*, struct ethtool_rxnfc*, void*) to int(*)(struct net_device*, struct ethtool_rxnfc*, u32*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_downgrade_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field fl_flags has been changed from unsigned char to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field fsync has been changed from int(*)(struct file*, int) to int(*)(struct file*, loff_t, loff_t, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dio_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field i_opflags 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 permission has been changed from int(*)(struct inode*, int, unsigned int) to int(*)(struct inode*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_inode_lru_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field s_shrink has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field s_inode_lru has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field s_nr_inodes_unused has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_cached_objects has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_cached_objects has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ent_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_usb2_hw_lpm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ignore_misc_bit has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field no_jack_detect has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field spdif_out has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field post_suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pre_resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_power_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hp_out_nid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field extra_out_nid has been changed from hda_nid_t[3] to hda_nid_t[5]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field eld_buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field read_reg_page has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_page has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field write_reg_page has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_wake_get has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field force_wake_put has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field update_plane has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field write_eld has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bios_lvds_val has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cfb_fb has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field display_clock_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field fbc_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field gt_fifo_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field gt_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field int_edp_connector has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field lvds_val has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Type of field cfb_plane has been changed from int to enum plane. | Recompilation of a client program may be broken. |
| 11 | Type of field pipe_to_crtc_mapping has been changed from struct drm_crtc*[2] to struct drm_crtc*[3]. | Recompilation of a client program may be broken. |
| 12 | Type of field plane_to_crtc_mapping has been changed from struct drm_crtc*[2] to struct drm_crtc*[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_force_wake has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field h_entries has been changed from struct idmap_hashent[128] to struct idmap_hashent*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rann_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field synced has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field synced has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_ave_beacon_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rssi_max_thold has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rssi_min_thold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_gates has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field security_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crypto_tx_tailroom_needed_cnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tx_conf has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dropped_frames_congestion has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ipv6 has been changed from struct ipstats_mib*[2] to struct ipstats_mib*[1]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_tos has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmtu_learned has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rate_tokens has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pmtu_expires has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pmtu_orig has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field redirect_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field metrics has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field redirect_learned has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field rate_last has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field do_idle_maps has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field no_pll has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field use_pll_a has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field semaphore_register has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field signal_mbox has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sync_to has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field percpu_dev_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tos 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 state_transition has been changed from int(*)(struct ip_vs_conn*, int, struct sk_buff const*, struct ip_vs_proto_data*) to void(*)(struct ip_vs_conn*, int, struct sk_buff const*, struct ip_vs_proto_data*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field shm_rmid_forced has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field domain has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hwirq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field llnode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field percpu_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field timer_rand_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field txlock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rx has been changed from struct tkip_ctx[17] to struct tkip_ctx[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field p1k_iv32 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_ssid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ssid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ssid_len has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allow_buffered_frames has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cancel_hw_scan has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field finish_tx_sync has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field release_buffered_frames has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rssi_callback has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field set_rekey_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tx_sync has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Base type of field conf_tx has been changed from int(*)(struct ieee80211_hw*, u16, struct ieee80211_tx_queue_params const*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, u16, struct ieee80211_tx_queue_params const*). | Recompilation of a client program may be broken. |
| 9 | Base type of field get_tsf has been changed from u64(*)(struct ieee80211_hw*) to u64(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Recompilation of a client program may be broken. |
| 10 | Base type of field reset_tsf has been changed from void(*)(struct ieee80211_hw*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Recompilation of a client program may be broken. |
| 11 | Base type of field set_tsf has been changed from void(*)(struct ieee80211_hw*, u64) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, u64). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_sp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field uapsd_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field wme has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ipv6_statistics has been changed from struct ipstats_mib*[2] to struct ipstats_mib*[1]. | Recompilation of a client program may be broken. |
| 2 | Type of field icmp_statistics has been changed from struct icmp_mib*[2] to struct icmp_mib*[1]. | Recompilation of a client program may be broken. |
| 3 | Type of field tcp_statistics has been changed from struct tcp_mib*[2] to struct tcp_mib*[1]. | Recompilation of a client program may be broken. |
| 4 | Type of field icmpv6_statistics has been changed from struct icmpv6_mib*[2] to struct icmpv6_mib*[1]. | Recompilation of a client program may be broken. |
| 5 | Type of field udp_stats_in6 has been changed from struct udp_mib*[2] to struct udp_mib*[1]. | Recompilation of a client program may be broken. |
| 6 | Type of field net_statistics has been changed from struct linux_mib*[2] to struct linux_mib*[1]. | Recompilation of a client program may be broken. |
| 7 | Type of field udp_statistics has been changed from struct udp_mib*[2] to struct udp_mib*[1]. | Recompilation of a client program may be broken. |
| 8 | Type of field udplite_stats_in6 has been changed from struct udp_mib*[2] to struct udp_mib*[1]. | Recompilation of a client program may be broken. |
| 9 | Type of field ip_statistics has been changed from struct ipstats_mib*[2] to struct ipstats_mib*[1]. | Recompilation of a client program may be broken. |
| 10 | Type of field udplite_statistics has been changed from struct udp_mib*[2] to struct udp_mib*[1]. | Recompilation of a client program may be broken. |
| 11 | Type of field icmpmsg_statistics has been changed from struct icmpmsg_mib*[2] to struct icmpmsg_mib*[1]. | Recompilation of a client program may be broken. |
| 12 | Type of field icmpv6msg_statistics has been changed from struct icmpv6msg_mib*[2] to struct icmpv6msg_mib*[1]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field batch has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_in_batch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pobjects has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pinned_vm has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mmap_legacy_base 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[26] to s8[27]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat has been changed from atomic_long_t[26] to atomic_long_t[27]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show has been changed from ssize_t(*)(struct module_attribute*, struct module*, char*) to ssize_t(*)(struct module_attribute*, struct module_kobject*, char*). | Recompilation of a client program may be broken. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct module_attribute*, struct module*, char const*, size_t) to ssize_t(*)(struct module_attribute*, struct module_kobject*, char const*, size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | Recompilation of a client program may be broken. |
| 2 | Base type of field connected_output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field output has been changed from int(*)(struct sk_buff*) to int(*)(struct neighbour*, struct sk_buff*). | Recompilation of a client program may be broken. |
| 2 | Type of field hh has been changed from struct hh_cache* to struct hh_cache. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_base_seq 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 cache has been changed from int(*)(struct neighbour const*, struct hh_cache*) to int(*)(struct neighbour const*, struct hh_cache*, __be16). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field uc_promisc has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_set_vf_spoofchk has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_match has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field call_rcu_sched has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field find_root_sec 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_state_renewal has been changed from int(*)(struct nfs_client*, struct rpc_cred*) to int(*)(struct nfs_client*, struct rpc_cred*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field server_scope has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field layouts has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pnfs_blksize has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pnfs_ld_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field attr_bitmask has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pg_recoalesce has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcie_mpss has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pme_poll has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rb_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field overflow_handler_context has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field exclude_guest has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field exclude_host has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(struct perf_event*, int, struct perf_sample_data*, struct pt_regs*) to void(*)(struct perf_event*, struct perf_sample_data*, struct pt_regs*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field constraints has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ignore_children has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field subsys_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field wakeup_path has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field name has been changed from char const* to char[]. | Recompilation of a client program may be broken. |
| 2 | Type of field namelen has been changed from unsigned int to u8. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field microcode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rsp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(int, struct die_args*) to void(*)(int, struct pt_regs*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field synflood_warned has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries_bytes has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field read_bytes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field uie_unsupported 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 classify has been changed from int(*)(struct sk_buff*, struct tcf_proto*, struct tcf_result*) to int(*)(struct sk_buff*, struct tcf_proto const*, struct tcf_result*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field classify has been changed from int(*)(struct sk_buff*, struct tcf_proto*, struct tcf_result*) to int(*)(struct sk_buff*, struct tcf_proto const*, struct tcf_result*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_nr_running has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wake_list has been changed from struct task_struct* to struct llist_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfs_bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_dirtied has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_dirtied_pause has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field wake_entry has been changed from struct task_struct* to struct llist_node. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field match has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field host_reset 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 inode_permission has been changed from int(*)(struct inode*, int, unsigned int) to int(*)(struct inode*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field poll_event has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handle_irq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field shm_creator has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field l4_rxhash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_partial has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field partial has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from unsigned short to __kernel_sa_family_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tid_rx_stop_requested has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_buffered_tids has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dummy has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field flags has been changed from u32 to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bar_pending has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field failed_bar_ssn has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field suspend_again has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field daddrlen has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_cachetype has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rq_daddrlen has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field poll has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inode_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field name_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field u has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inode_tree has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field name_tree has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field seq_fops has been changed from struct file_operations to struct file_operations const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field prior_cwnd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prr_delivered has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field prr_out 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 calc_md5_hash has been changed from int(*)(char*, struct tcp_md5sig_key*, struct sock*, struct request_sock*, struct sk_buff*) to int(*)(char*, struct tcp_md5sig_key*, struct sock const*, struct request_sock const*, struct sk_buff const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field seq_fops has been changed from struct file_operations to struct file_operations const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bos has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field usb2_hw_lpm_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field lpm_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field usb2_hw_lpm_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_func has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_drainers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_nmi_reason has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field wallclock_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_reqs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_slot has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field reserve_xprt has been changed from int(*)(struct rpc_task*) to int(*)(struct rpc_xprt*, struct rpc_task*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter function has been changed from void(*)(struct alarm*) to enum alarmtimer_restart(*)(struct alarm*, ktime_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nr_iovecs has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nr_iovecs has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct e1000_info to struct e1000_info const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter max_effects has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter flen has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct intel_quirk[9] to struct intel_quirk[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct mce*, u32) to void(*)(int, struct mce*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct mce*, u32) to void(*)(int, struct mce*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct mdk_thread_s to struct md_thread. | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter run has been changed from void(*)(mddev_t*) to void(*)(struct mddev*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter threadp has been changed from struct mdk_thread_s to struct md_thread. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter thread has been changed from struct mdk_thread_s to struct md_thread. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter p has been changed from struct mdk_personality to struct md_personality. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter p has been changed from struct mdk_personality to struct md_personality. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[39] to struct nf_conntrack_l3proto*[40]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const to u32[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter doio has been changed from int(*)(struct nfs_pageio_descriptor*) to struct nfs_pageio_ops. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops to struct pci_raw_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops* to struct pci_raw_ops const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_raw_ops* to struct pci_raw_ops const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct thermal_cooling_device_ops to struct thermal_cooling_device_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kill 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 struct tcp_md5sig_pool** to struct tcp_md5sig_pool*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter payload_len has been changed from size_t to u8*. | Recompilation of a client program may be broken. |
| 2 | Type of 5th parameter ta has been changed from u8* to size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[26] to atomic_long_t[27]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[77] const to char const*[78] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter size has been changed from int to size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bounce_gfp has been changed from 18 to 19. | No effect. |
| 2 | The relative position of field dma_drain_buffer has been changed from 27 to 28. | No effect. |
| 3 | The relative position of field dma_drain_size has been changed from 28 to 27. | No effect. |
| 4 | The relative position of field queue_flags has been changed from 19 to 18. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field flags has been changed from 19 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field alloc_rx_buf has been changed from 37 to 36. | No effect. |
| 2 | The relative position of field alloc_rx_buff_failed has been changed from 44 to 43. | No effect. |
| 3 | The relative position of field bars has been changed from 65 to 64. | No effect. |
| 4 | The relative position of field clean_rx has been changed from 36 to 35. | No effect. |
| 5 | The relative position of field colc_old has been changed from 27 to 26. | No effect. |
| 6 | The relative position of field detect_tx_hung has been changed from 35 to 34. | No effect. |
| 7 | The relative position of field discarding has been changed from 67 to 66. | No effect. |
| 8 | The relative position of field eeprom_wol has been changed from 64 to 63. | No effect. |
| 9 | The relative position of field fc_autoneg has been changed from 18 to 17. | No effect. |
| 10 | The relative position of field flags has been changed from 63 to 62. | No effect. |
| 11 | The relative position of field gorcl has been changed from 48 to 47. | No effect. |
| 12 | The relative position of field gorcl_old has been changed from 49 to 48. | No effect. |
| 13 | The relative position of field gotcl has been changed from 24 to 23. | No effect. |
| 14 | The relative position of field gotcl_old has been changed from 25 to 24. | No effect. |
| 15 | The relative position of field hw has been changed from 52 to 51. | No effect. |
| 16 | The relative position of field hw_csum_err has been changed from 42 to 41. | No effect. |
| 17 | The relative position of field hw_csum_good has been changed from 43 to 42. | No effect. |
| 18 | The relative position of field msg_enable has been changed from 59 to 58. | No effect. |
| 19 | The relative position of field napi has been changed from 39 to 38. | No effect. |
| 20 | The relative position of field need_ioport has been changed from 66 to 65. | No effect. |
| 21 | The relative position of field netdev has been changed from 50 to 49. | No effect. |
| 22 | The relative position of field num_rx_queues has been changed from 41 to 40. | No effect. |
| 23 | The relative position of field num_tx_queues has been changed from 40 to 39. | No effect. |
| 24 | The relative position of field pcix_82544 has been changed from 34 to 33. | No effect. |
| 25 | The relative position of field pdev has been changed from 51 to 50. | No effect. |
| 26 | The relative position of field phy_info has been changed from 54 to 53. | No effect. |
| 27 | The relative position of field phy_stats has been changed from 55 to 54. | No effect. |
| 28 | The relative position of field quad_port_a has been changed from 62 to 61. | No effect. |
| 29 | The relative position of field reset_task has been changed from 17 to 67. | No effect. |
| 30 | The relative position of field restart_queue has been changed from 20 to 19. | No effect. |
| 31 | The relative position of field rx_abs_int_delay has been changed from 46 to 45. | No effect. |
| 32 | The relative position of field rx_csum has been changed from 47 to 46. | No effect. |
| 33 | The relative position of field rx_int_delay has been changed from 45 to 44. | No effect. |
| 34 | The relative position of field rx_ring has been changed from 38 to 37. | No effect. |
| 35 | The relative position of field smart_power_down has been changed from 61 to 60. | No effect. |
| 36 | The relative position of field stats has been changed from 53 to 52. | No effect. |
| 37 | The relative position of field test_icr has been changed from 56 to 55. | No effect. |
| 38 | The relative position of field test_rx_ring has been changed from 58 to 57. | No effect. |
| 39 | The relative position of field test_tx_ring has been changed from 57 to 56. | No effect. |
| 40 | The relative position of field tpt_old has been changed from 26 to 25. | No effect. |
| 41 | The relative position of field tso_force has been changed from 60 to 59. | No effect. |
| 42 | The relative position of field tx_abs_int_delay has been changed from 23 to 22. | No effect. |
| 43 | The relative position of field tx_fifo_head has been changed from 29 to 28. | No effect. |
| 44 | The relative position of field tx_fifo_size has been changed from 31 to 30. | No effect. |
| 45 | The relative position of field tx_fifo_stall has been changed from 33 to 32. | No effect. |
| 46 | The relative position of field tx_head_addr has been changed from 30 to 29. | No effect. |
| 47 | The relative position of field tx_int_delay has been changed from 22 to 21. | No effect. |
| 48 | The relative position of field tx_ring has been changed from 19 to 18. | No effect. |
| 49 | The relative position of field tx_timeout_count has been changed from 28 to 27. | No effect. |
| 50 | The relative position of field tx_timeout_factor has been changed from 32 to 31. | No effect. |
| 51 | The relative position of field txd_cmd has been changed from 21 to 20. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dirtied_when has been changed from 10 to 23. | No effect. |
| 2 | The relative position of field i_acl has been changed from 39 to 4. | No effect. |
| 3 | The relative position of field i_atime has been changed from 23 to 13. | No effect. |
| 4 | The relative position of field i_blkbits has been changed from 19 to 30. | No effect. |
| 5 | The relative position of field i_blocks has been changed from 26 to 18. | No effect. |
| 6 | The relative position of field i_bytes has been changed from 27 to 17. | No effect. |
| 7 | The relative position of field i_count has been changed from 17 to 29. | No effect. |
| 8 | The relative position of field i_ctime has been changed from 25 to 15. | No effect. |
| 9 | The relative position of field i_data has been changed from 31 to 35. | No effect. |
| 10 | The relative position of field i_default_acl has been changed from 40 to 5. | No effect. |
| 11 | The relative position of field i_devices has been changed from 33 to 37. | No effect. |
| 12 | The relative position of field i_dquot has been changed from 32 to 36. | No effect. |
| 13 | The relative position of field i_flags has been changed from 6 to 3. | No effect. |
| 14 | The relative position of field i_flock has been changed from 29 to 34. | No effect. |
| 15 | The relative position of field i_fop has been changed from 28 to 33. | No effect. |
| 16 | The relative position of field i_fsnotify_marks has been changed from 37 to 40. | No effect. |
| 17 | The relative position of field i_fsnotify_mask has been changed from 36 to 39. | No effect. |
| 18 | The relative position of field i_generation has been changed from 35 to 38. | No effect. |
| 19 | The relative position of field i_hash has been changed from 11 to 24. | No effect. |
| 20 | The relative position of field i_ino has been changed from 16 to 10. | No effect. |
| 21 | The relative position of field i_lock has been changed from 5 to 16. | No effect. |
| 22 | The relative position of field i_lru has been changed from 13 to 26. | No effect. |
| 23 | The relative position of field i_mapping has been changed from 30 to 8. | No effect. |
| 24 | The relative position of field i_mtime has been changed from 24 to 14. | No effect. |
| 25 | The relative position of field i_mutex has been changed from 9 to 22. | No effect. |
| 26 | The relative position of field i_op has been changed from 3 to 6. | No effect. |
| 27 | The relative position of field i_rdev has been changed from 18 to 12. | No effect. |
| 28 | The relative position of field i_sb has been changed from 4 to 7. | No effect. |
| 29 | The relative position of field i_sb_list has been changed from 14 to 27. | No effect. |
| 30 | The relative position of field i_security has been changed from 8 to 9. | No effect. |
| 31 | The relative position of field i_size has been changed from 21 to 19. | No effect. |
| 32 | The relative position of field i_size_seqcount has been changed from 22 to 20. | No effect. |
| 33 | The relative position of field i_state has been changed from 7 to 21. | No effect. |
| 34 | The relative position of field i_version has been changed from 20 to 31. | No effect. |
| 35 | The relative position of field i_wb_list has been changed from 12 to 25. | No effect. |
| 36 | The relative position of field i_writecount has been changed from 38 to 32. | No effect. |
| 37 | The relative position of field unnamed0 has been changed from 15 to 11. | No effect. |
| 38 | The relative position of field unnamed1 has been changed from 34 to 28. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field __i_nlink has been added to this type. | No effect. |
| 2 | Field i_nlink has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dentry has been added to this type. | No effect. |
| 2 | Field i_rcu has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member HID_TYPE_USBNONE with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field adpa has been changed from 32 to 33. | No effect. |
| 2 | The relative position of field agp_heap has been changed from 30 to 31. | No effect. |
| 3 | The relative position of field allow_batchbuffer has been changed from 29 to 30. | No effect. |
| 4 | The relative position of field back_offset has been changed from 16 to 17. | No effect. |
| 5 | The relative position of field backlight_enabled has been changed from 52 to 53. | No effect. |
| 6 | The relative position of field backlight_level has been changed from 51 to 52. | No effect. |
| 7 | The relative position of field bridge_dev has been changed from 6 to 7. | No effect. |
| 8 | The relative position of field broadcast_rgb_property has been changed from 273 to 274. | No effect. |
| 9 | The relative position of field busy has been changed from 244 to 245. | No effect. |
| 10 | The relative position of field c_m has been changed from 264 to 265. | No effect. |
| 11 | The relative position of field cfb_plane has been changed from 47 to 48. | No effect. |
| 12 | The relative position of field cfb_size has been changed from 46 to 47. | No effect. |
| 13 | The relative position of field cfb_y has been changed from 48 to 49. | No effect. |
| 14 | The relative position of field child_dev has been changed from 247 to 248. | No effect. |
| 15 | The relative position of field child_dev_num has been changed from 246 to 247. | No effect. |
| 16 | The relative position of field chipset_power has been changed from 260 to 261. | No effect. |
| 17 | The relative position of field compressed_fb has been changed from 269 to 270. | No effect. |
| 18 | The relative position of field compressed_llb has been changed from 270 to 271. | No effect. |
| 19 | The relative position of field corr has been changed from 266 to 267. | No effect. |
| 20 | The relative position of field counter has been changed from 10 to 11. | No effect. |
| 21 | The relative position of field cpp has been changed from 15 to 16. | No effect. |
| 22 | The relative position of field crt_ddc_pin has been changed from 64 to 65. | No effect. |
| 23 | The relative position of field cur_delay has been changed from 253 to 254. | No effect. |
| 24 | The relative position of field current_page has been changed from 18 to 19. | No effect. |
| 25 | The relative position of field display has been changed from 76 to 77. | No effect. |
| 26 | The relative position of field dvob has been changed from 34 to 35. | No effect. |
| 27 | The relative position of field dvoc has been changed from 35 to 36. | No effect. |
| 28 | The relative position of field edp has been changed from 61 to 62. | No effect. |
| 29 | The relative position of field error_completion has been changed from 74 to 75. | No effect. |
| 30 | The relative position of field error_lock has been changed from 71 to 72. | No effect. |
| 31 | The relative position of field error_work has been changed from 73 to 74. | No effect. |
| 32 | The relative position of field fbdev has been changed from 272 to 273. | No effect. |
| 33 | The relative position of field fence_reg_start has been changed from 66 to 67. | No effect. |
| 34 | The relative position of field fence_regs has been changed from 65 to 66. | No effect. |
| 35 | The relative position of field first_error has been changed from 72 to 73. | No effect. |
| 36 | The relative position of field flip_pending_is_done has been changed from 238 to 239. | No effect. |
| 37 | The relative position of field fmax has been changed from 256 to 257. | No effect. |
| 38 | The relative position of field force_audio_property has been changed from 274 to 275. | No effect. |
| 39 | The relative position of field forcewake_count has been changed from 275 to 5. | No effect. |
| 40 | The relative position of field front_offset has been changed from 17 to 18. | No effect. |
| 41 | The relative position of field fsb_freq has been changed from 68 to 69. | No effect. |
| 42 | The relative position of field fstart has been changed from 257 to 258. | No effect. |
| 43 | The relative position of field gfx_power has been changed from 263 to 264. | No effect. |
| 44 | The relative position of field gmbus has been changed from 5 to 6. | No effect. |
| 45 | The relative position of field gt_irq_mask has been changed from 24 to 25. | No effect. |
| 46 | The relative position of field hangcheck_count has been changed from 40 to 41. | No effect. |
| 47 | The relative position of field hangcheck_timer has been changed from 39 to 40. | No effect. |
| 48 | The relative position of field hotplug_supported_mask has been changed from 26 to 27. | No effect. |
| 49 | The relative position of field hotplug_work has been changed from 27 to 28. | No effect. |
| 50 | The relative position of field hws_map has been changed from 11 to 12. | No effect. |
| 51 | The relative position of field idle_timer has been changed from 243 to 244. | No effect. |
| 52 | The relative position of field idle_work has been changed from 242 to 243. | No effect. |
| 53 | The relative position of field int_crt_support has been changed from 58 to 59. | No effect. |
| 54 | The relative position of field int_lvds_connector has been changed from 248 to 249. | No effect. |
| 55 | The relative position of field int_tv_support has been changed from 55 to 56. | No effect. |
| 56 | The relative position of field irq_lock has been changed from 21 to 22. | No effect. |
| 57 | The relative position of field irq_mask has been changed from 23 to 24. | No effect. |
| 58 | The relative position of field irq_received has been changed from 20 to 21. | No effect. |
| 59 | The relative position of field is_ddr3 has been changed from 70 to 71. | No effect. |
| 60 | The relative position of field last_acthd has been changed from 41 to 42. | No effect. |
| 61 | The relative position of field last_acthd_blt has been changed from 43 to 44. | No effect. |
| 62 | The relative position of field last_acthd_bsd has been changed from 42 to 43. | No effect. |
| 63 | The relative position of field last_count1 has been changed from 258 to 259. | No effect. |
| 64 | The relative position of field last_count2 has been changed from 261 to 262. | No effect. |
| 65 | The relative position of field last_gpu_reset has been changed from 271 to 272. | No effect. |
| 66 | The relative position of field last_instdone has been changed from 44 to 45. | No effect. |
| 67 | The relative position of field last_instdone1 has been changed from 45 to 46. | No effect. |
| 68 | The relative position of field last_time1 has been changed from 259 to 260. | No effect. |
| 69 | The relative position of field last_time2 has been changed from 262 to 263. | No effect. |
| 70 | The relative position of field lfp_lvds_vbt_mode has been changed from 53 to 54. | No effect. |
| 71 | The relative position of field lid_notifier has been changed from 63 to 64. | No effect. |
| 72 | The relative position of field lvds has been changed from 36 to 37. | No effect. |
| 73 | The relative position of field lvds_border_bits has been changed from 232 to 233. | No effect. |
| 74 | The relative position of field lvds_dither has been changed from 56 to 57. | No effect. |
| 75 | The relative position of field lvds_downclock has been changed from 241 to 242. | No effect. |
| 76 | The relative position of field lvds_downclock_avail has been changed from 240 to 241. | No effect. |
| 77 | The relative position of field lvds_ssc_freq has been changed from 60 to 61. | No effect. |
| 78 | The relative position of field lvds_use_ssc has been changed from 59 to 60. | No effect. |
| 79 | The relative position of field lvds_vbt has been changed from 57 to 58. | No effect. |
| 80 | The relative position of field max_delay has been changed from 255 to 256. | No effect. |
| 81 | The relative position of field mch_res has been changed from 14 to 15. | No effect. |
| 82 | The relative position of field mchbar_need_disable has been changed from 249 to 250. | No effect. |
| 83 | The relative position of field mchdev_lock has been changed from 267 to 268. | No effect. |
| 84 | The relative position of field mem_freq has been changed from 69 to 70. | No effect. |
| 85 | The relative position of field min_delay has been changed from 254 to 255. | No effect. |
| 86 | The relative position of field mm has been changed from 230 to 231. | No effect. |
| 87 | The relative position of field modeset_on_lid has been changed from 79 to 80. | No effect. |
| 88 | The relative position of field next_seqno has been changed from 8 to 9. | No effect. |
| 89 | The relative position of field no_aux_handshake has been changed from 62 to 63. | No effect. |
| 90 | The relative position of field no_fbc_reason has been changed from 268 to 269. | No effect. |
| 91 | The relative position of field num_fence_regs has been changed from 67 to 68. | No effect. |
| 92 | The relative position of field num_pipe has been changed from 38 to 39. | No effect. |
| 93 | The relative position of field opregion has been changed from 49 to 50. | No effect. |
| 94 | The relative position of field orig_clock has been changed from 245 to 246. | No effect. |
| 95 | The relative position of field overlay has been changed from 50 to 51. | No effect. |
| 96 | The relative position of field page_flipping has been changed from 19 to 20. | No effect. |
| 97 | The relative position of field pch_irq_mask has been changed from 25 to 26. | No effect. |
| 98 | The relative position of field pch_pf_pos has been changed from 233 to 234. | No effect. |
| 99 | The relative position of field pch_pf_size has been changed from 234 to 235. | No effect. |
| 100 | The relative position of field pch_type has been changed from 77 to 78. | No effect. |
| 101 | The relative position of field pending_flip_queue has been changed from 237 to 238. | No effect. |
| 102 | The relative position of field pipe_to_crtc_mapping has been changed from 236 to 237. | No effect. |
| 103 | The relative position of field pipestat has been changed from 22 to 23. | No effect. |
| 104 | The relative position of field plane_to_crtc_mapping has been changed from 235 to 236. | No effect. |
| 105 | The relative position of field pm_iir has been changed from 252 to 253. | No effect. |
| 106 | The relative position of field ppcr has been changed from 33 to 34. | No effect. |
| 107 | The relative position of field pwrctx has been changed from 12 to 13. | No effect. |
| 108 | The relative position of field quirks has been changed from 78 to 79. | No effect. |
| 109 | The relative position of field r_t has been changed from 265 to 266. | No effect. |
| 110 | The relative position of field render_reclock_avail has been changed from 239 to 240. | No effect. |
| 111 | The relative position of field renderctx has been changed from 13 to 14. | No effect. |
| 112 | The relative position of field ring has been changed from 7 to 8. | No effect. |
| 113 | The relative position of field rps_lock has been changed from 251 to 252. | No effect. |
| 114 | The relative position of field rps_work has been changed from 250 to 251. | No effect. |
| 115 | The relative position of field saveADPA has been changed from 149 to 150. | No effect. |
| 116 | The relative position of field saveAR has been changed from 186 to 187. | No effect. |
| 117 | The relative position of field saveAR_INDEX has been changed from 185 to 186. | No effect. |
| 118 | The relative position of field saveBCLRPAT_A has been changed from 99 to 100. | No effect. |
| 119 | The relative position of field saveBCLRPAT_B has been changed from 130 to 131. | No effect. |
| 120 | The relative position of field saveBLC_CPU_PWM_CTL has been changed from 118 to 119. | No effect. |
| 121 | The relative position of field saveBLC_CPU_PWM_CTL2 has been changed from 119 to 120. | No effect. |
| 122 | The relative position of field saveBLC_HIST_CTL has been changed from 115 to 116. | No effect. |
| 123 | The relative position of field saveBLC_PWM_CTL has been changed from 116 to 117. | No effect. |
| 124 | The relative position of field saveBLC_PWM_CTL2 has been changed from 117 to 118. | No effect. |
| 125 | The relative position of field saveCACHE_MODE_0 has been changed from 177 to 178. | No effect. |
| 126 | The relative position of field saveCR has been changed from 188 to 189. | No effect. |
| 127 | The relative position of field saveCURABASE has been changed from 192 to 193. | No effect. |
| 128 | The relative position of field saveCURACNTR has been changed from 190 to 191. | No effect. |
| 129 | The relative position of field saveCURAPOS has been changed from 191 to 192. | No effect. |
| 130 | The relative position of field saveCURBBASE has been changed from 195 to 196. | No effect. |
| 131 | The relative position of field saveCURBCNTR has been changed from 193 to 194. | No effect. |
| 132 | The relative position of field saveCURBPOS has been changed from 194 to 195. | No effect. |
| 133 | The relative position of field saveCURSIZE has been changed from 196 to 197. | No effect. |
| 134 | The relative position of field saveDACMASK has been changed from 187 to 188. | No effect. |
| 135 | The relative position of field saveDEIER has been changed from 171 to 172. | No effect. |
| 136 | The relative position of field saveDEIMR has been changed from 172 to 173. | No effect. |
| 137 | The relative position of field saveDISP_ARB_CTL has been changed from 219 to 220. | No effect. |
| 138 | The relative position of field saveDPFC_CB_BASE has been changed from 163 to 164. | No effect. |
| 139 | The relative position of field saveDPLL_A has been changed from 91 to 92. | No effect. |
| 140 | The relative position of field saveDPLL_A_MD has been changed from 92 to 93. | No effect. |
| 141 | The relative position of field saveDPLL_B has been changed from 122 to 123. | No effect. |
| 142 | The relative position of field saveDPLL_B_MD has been changed from 123 to 124. | No effect. |
| 143 | The relative position of field saveDP_B has been changed from 197 to 198. | No effect. |
| 144 | The relative position of field saveDP_C has been changed from 198 to 199. | No effect. |
| 145 | The relative position of field saveDP_D has been changed from 199 to 200. | No effect. |
| 146 | The relative position of field saveDSPAADDR has been changed from 111 to 112. | No effect. |
| 147 | The relative position of field saveDSPACNTR has been changed from 81 to 82. | No effect. |
| 148 | The relative position of field saveDSPAPOS has been changed from 110 to 111. | No effect. |
| 149 | The relative position of field saveDSPARB has been changed from 83 to 84. | No effect. |
| 150 | The relative position of field saveDSPASIZE has been changed from 109 to 110. | No effect. |
| 151 | The relative position of field saveDSPASTRIDE has been changed from 108 to 109. | No effect. |
| 152 | The relative position of field saveDSPASURF has been changed from 112 to 113. | No effect. |
| 153 | The relative position of field saveDSPATILEOFF has been changed from 113 to 114. | No effect. |
| 154 | The relative position of field saveDSPBADDR has been changed from 142 to 143. | No effect. |
| 155 | The relative position of field saveDSPBCNTR has been changed from 82 to 83. | No effect. |
| 156 | The relative position of field saveDSPBPOS has been changed from 141 to 142. | No effect. |
| 157 | The relative position of field saveDSPBSIZE has been changed from 140 to 141. | No effect. |
| 158 | The relative position of field saveDSPBSTRIDE has been changed from 139 to 140. | No effect. |
| 159 | The relative position of field saveDSPBSURF has been changed from 143 to 144. | No effect. |
| 160 | The relative position of field saveDSPBTILEOFF has been changed from 144 to 145. | No effect. |
| 161 | The relative position of field saveDVOA has been changed from 153 to 154. | No effect. |
| 162 | The relative position of field saveDVOB has been changed from 154 to 155. | No effect. |
| 163 | The relative position of field saveDVOC has been changed from 155 to 156. | No effect. |
| 164 | The relative position of field saveFBC_CFB_BASE has been changed from 164 to 165. | No effect. |
| 165 | The relative position of field saveFBC_CONTROL has been changed from 166 to 167. | No effect. |
| 166 | The relative position of field saveFBC_CONTROL2 has been changed from 167 to 168. | No effect. |
| 167 | The relative position of field saveFBC_LL_BASE has been changed from 165 to 166. | No effect. |
| 168 | The relative position of field saveFDI_RXA_CTL has been changed from 208 to 209. | No effect. |
| 169 | The relative position of field saveFDI_RXA_IMR has been changed from 175 to 176. | No effect. |
| 170 | The relative position of field saveFDI_RXB_CTL has been changed from 210 to 211. | No effect. |
| 171 | The relative position of field saveFDI_RXB_IMR has been changed from 176 to 177. | No effect. |
| 172 | The relative position of field saveFDI_TXA_CTL has been changed from 209 to 210. | No effect. |
| 173 | The relative position of field saveFDI_TXB_CTL has been changed from 211 to 212. | No effect. |
| 174 | The relative position of field saveFENCE has been changed from 189 to 190. | No effect. |
| 175 | The relative position of field saveFPA0 has been changed from 89 to 90. | No effect. |
| 176 | The relative position of field saveFPA1 has been changed from 90 to 91. | No effect. |
| 177 | The relative position of field saveFPB0 has been changed from 120 to 121. | No effect. |
| 178 | The relative position of field saveFPB1 has been changed from 121 to 122. | No effect. |
| 179 | The relative position of field saveGR has been changed from 184 to 185. | No effect. |
| 180 | The relative position of field saveGTIER has been changed from 173 to 174. | No effect. |
| 181 | The relative position of field saveGTIMR has been changed from 174 to 175. | No effect. |
| 182 | The relative position of field saveHBLANK_A has been changed from 94 to 95. | No effect. |
| 183 | The relative position of field saveHBLANK_B has been changed from 125 to 126. | No effect. |
| 184 | The relative position of field saveHSYNC_A has been changed from 95 to 96. | No effect. |
| 185 | The relative position of field saveHSYNC_B has been changed from 126 to 127. | No effect. |
| 186 | The relative position of field saveHTOTAL_A has been changed from 93 to 94. | No effect. |
| 187 | The relative position of field saveHTOTAL_B has been changed from 124 to 125. | No effect. |
| 188 | The relative position of field saveHWS has been changed from 84 to 85. | No effect. |
| 189 | The relative position of field saveIER has been changed from 168 to 169. | No effect. |
| 190 | The relative position of field saveIIR has been changed from 169 to 170. | No effect. |
| 191 | The relative position of field saveIMR has been changed from 170 to 171. | No effect. |
| 192 | The relative position of field saveLBB has been changed from 80 to 81. | No effect. |
| 193 | The relative position of field saveLVDS has been changed from 150 to 151. | No effect. |
| 194 | The relative position of field saveMCHBAR_RENDER_STANDBY has been changed from 228 to 229. | No effect. |
| 195 | The relative position of field saveMI_ARB_STATE has been changed from 178 to 179. | No effect. |
| 196 | The relative position of field saveMSR has been changed from 182 to 183. | No effect. |
| 197 | The relative position of field savePCH_DREF_CONTROL has been changed from 218 to 219. | No effect. |
| 198 | The relative position of field savePCH_PORT_HOTPLUG has been changed from 229 to 230. | No effect. |
| 199 | The relative position of field savePFA_CTL_1 has been changed from 212 to 213. | No effect. |
| 200 | The relative position of field savePFA_WIN_POS has been changed from 216 to 217. | No effect. |
| 201 | The relative position of field savePFA_WIN_SZ has been changed from 214 to 215. | No effect. |
| 202 | The relative position of field savePFB_CTL_1 has been changed from 213 to 214. | No effect. |
| 203 | The relative position of field savePFB_WIN_POS has been changed from 217 to 218. | No effect. |
| 204 | The relative position of field savePFB_WIN_SZ has been changed from 215 to 216. | No effect. |
| 205 | The relative position of field savePFIT_CONTROL has been changed from 160 to 161. | No effect. |
| 206 | The relative position of field savePFIT_PGM_RATIOS has been changed from 114 to 115. | No effect. |
| 207 | The relative position of field savePIPEACONF has been changed from 85 to 86. | No effect. |
| 208 | The relative position of field savePIPEASRC has been changed from 87 to 88. | No effect. |
| 209 | The relative position of field savePIPEASTAT has been changed from 107 to 108. | No effect. |
| 210 | The relative position of field savePIPEA_DATA_M1 has been changed from 220 to 221. | No effect. |
| 211 | The relative position of field savePIPEA_DATA_N1 has been changed from 221 to 222. | No effect. |
| 212 | The relative position of field savePIPEA_DP_LINK_M has been changed from 204 to 205. | No effect. |
| 213 | The relative position of field savePIPEA_DP_LINK_N has been changed from 206 to 207. | No effect. |
| 214 | The relative position of field savePIPEA_GMCH_DATA_M has been changed from 200 to 201. | No effect. |
| 215 | The relative position of field savePIPEA_GMCH_DATA_N has been changed from 202 to 203. | No effect. |
| 216 | The relative position of field savePIPEA_LINK_M1 has been changed from 222 to 223. | No effect. |
| 217 | The relative position of field savePIPEA_LINK_N1 has been changed from 223 to 224. | No effect. |
| 218 | The relative position of field savePIPEBCONF has been changed from 86 to 87. | No effect. |
| 219 | The relative position of field savePIPEBSRC has been changed from 88 to 89. | No effect. |
| 220 | The relative position of field savePIPEBSTAT has been changed from 138 to 139. | No effect. |
| 221 | The relative position of field savePIPEB_DATA_M1 has been changed from 224 to 225. | No effect. |
| 222 | The relative position of field savePIPEB_DATA_N1 has been changed from 225 to 226. | No effect. |
| 223 | The relative position of field savePIPEB_DP_LINK_M has been changed from 205 to 206. | No effect. |
| 224 | The relative position of field savePIPEB_DP_LINK_N has been changed from 207 to 208. | No effect. |
| 225 | The relative position of field savePIPEB_GMCH_DATA_M has been changed from 201 to 202. | No effect. |
| 226 | The relative position of field savePIPEB_GMCH_DATA_N has been changed from 203 to 204. | No effect. |
| 227 | The relative position of field savePIPEB_LINK_M1 has been changed from 226 to 227. | No effect. |
| 228 | The relative position of field savePIPEB_LINK_N1 has been changed from 227 to 228. | No effect. |
| 229 | The relative position of field savePP_CONTROL has been changed from 158 to 159. | No effect. |
| 230 | The relative position of field savePP_DIVISOR has been changed from 159 to 160. | No effect. |
| 231 | The relative position of field savePP_OFF has been changed from 157 to 158. | No effect. |
| 232 | The relative position of field savePP_OFF_DELAYS has been changed from 152 to 153. | No effect. |
| 233 | The relative position of field savePP_ON has been changed from 156 to 157. | No effect. |
| 234 | The relative position of field savePP_ON_DELAYS has been changed from 151 to 152. | No effect. |
| 235 | The relative position of field saveSR has been changed from 183 to 184. | No effect. |
| 236 | The relative position of field saveSWF0 has been changed from 179 to 180. | No effect. |
| 237 | The relative position of field saveSWF1 has been changed from 180 to 181. | No effect. |
| 238 | The relative position of field saveSWF2 has been changed from 181 to 182. | No effect. |
| 239 | The relative position of field saveTRANSACONF has been changed from 100 to 101. | No effect. |
| 240 | The relative position of field saveTRANSBCONF has been changed from 131 to 132. | No effect. |
| 241 | The relative position of field saveTRANS_HBLANK_A has been changed from 102 to 103. | No effect. |
| 242 | The relative position of field saveTRANS_HBLANK_B has been changed from 133 to 134. | No effect. |
| 243 | The relative position of field saveTRANS_HSYNC_A has been changed from 103 to 104. | No effect. |
| 244 | The relative position of field saveTRANS_HSYNC_B has been changed from 134 to 135. | No effect. |
| 245 | The relative position of field saveTRANS_HTOTAL_A has been changed from 101 to 102. | No effect. |
| 246 | The relative position of field saveTRANS_HTOTAL_B has been changed from 132 to 133. | No effect. |
| 247 | The relative position of field saveTRANS_VBLANK_A has been changed from 105 to 106. | No effect. |
| 248 | The relative position of field saveTRANS_VBLANK_B has been changed from 136 to 137. | No effect. |
| 249 | The relative position of field saveTRANS_VSYNC_A has been changed from 106 to 107. | No effect. |
| 250 | The relative position of field saveTRANS_VSYNC_B has been changed from 137 to 138. | No effect. |
| 251 | The relative position of field saveTRANS_VTOTAL_A has been changed from 104 to 105. | No effect. |
| 252 | The relative position of field saveTRANS_VTOTAL_B has been changed from 135 to 136. | No effect. |
| 253 | The relative position of field saveVBLANK_A has been changed from 97 to 98. | No effect. |
| 254 | The relative position of field saveVBLANK_B has been changed from 128 to 129. | No effect. |
| 255 | The relative position of field saveVGA0 has been changed from 145 to 146. | No effect. |
| 256 | The relative position of field saveVGA1 has been changed from 146 to 147. | No effect. |
| 257 | The relative position of field saveVGACNTRL has been changed from 148 to 149. | No effect. |
| 258 | The relative position of field saveVGA_PD has been changed from 147 to 148. | No effect. |
| 259 | The relative position of field saveVSYNC_A has been changed from 98 to 99. | No effect. |
| 260 | The relative position of field saveVSYNC_B has been changed from 129 to 130. | No effect. |
| 261 | The relative position of field saveVTOTAL_A has been changed from 96 to 97. | No effect. |
| 262 | The relative position of field saveVTOTAL_B has been changed from 127 to 128. | No effect. |
| 263 | The relative position of field save_palette_a has been changed from 161 to 162. | No effect. |
| 264 | The relative position of field save_palette_b has been changed from 162 to 163. | No effect. |
| 265 | The relative position of field sdvo_lvds_vbt_mode has been changed from 54 to 55. | No effect. |
| 266 | The relative position of field sdvo_mappings has been changed from 231 to 232. | No effect. |
| 267 | The relative position of field sr01 has been changed from 31 to 32. | No effect. |
| 268 | The relative position of field status_page_dmah has been changed from 9 to 10. | No effect. |
| 269 | The relative position of field tex_lru_log_granularity has been changed from 28 to 29. | No effect. |
| 270 | The relative position of field vblank_pipe has been changed from 37 to 38. | No effect. |
| 271 | The relative position of field wq has been changed from 75 to 76. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field self_prot has been added to this type. | No effect. |
| 2 | Field tdls_discover_resp has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_QUEUE_STOP_REASON_CHTYPE_CHANGE with value 6 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed0 has been changed from 6 to 4. | No effect. |
| 2 | The relative position of field dtime has been changed from 4 to 5. | No effect. |
| 3 | The relative position of field refcnt has been changed from 5 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field gc_list has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field spd has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field ptl has been added to this type. | No effect. |
| 2 | Field first_page has been added to this type. | No effect. |
| 3 | Field slab has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_VMSCAN_IMMEDIATE with value 19 has been added. | No effect. |
| 2 | Value of member NR_ANON_TRANSPARENT_HUGEPAGES has been changed from 25 to 26. | No effect. |
| 3 | Value of member NR_DIRTIED has been changed from 23 to 24. | No effect. |
| 4 | Value of member NR_ISOLATED_ANON has been changed from 20 to 21. | No effect. |
| 5 | Value of member NR_ISOLATED_FILE has been changed from 21 to 22. | No effect. |
| 6 | Value of member NR_SHMEM has been changed from 22 to 23. | No effect. |
| 7 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 26 to 27. | No effect. |
| 8 | Value of member NR_WRITEBACK_TEMP has been changed from 19 to 20. | No effect. |
| 9 | Value of member NR_WRITTEN has been changed from 24 to 25. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field hh_len has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pg_lseg has been changed from 9 to 10. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rcu_head has been changed from 20 to 21. | No effect. |
| 2 | The relative position of field nr_cgroups has been changed from 21 to 20. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_SMII with value 11 has been added. | No effect. |
| 2 | The member PHY_INTERFACE_MODE_NA with value 0 has been added. | No effect. |
| 3 | Value of member PHY_INTERFACE_MODE_GMII has been changed from 1 to 2. | No effect. |
| 4 | Value of member PHY_INTERFACE_MODE_RGMII_TXID has been changed from 8 to 9. | No effect. |
| 5 | Value of member PHY_INTERFACE_MODE_MII has been changed from 0 to 1. | No effect. |
| 6 | Value of member PHY_INTERFACE_MODE_TBI has been changed from 3 to 4. | No effect. |
| 7 | Value of member PHY_INTERFACE_MODE_RGMII_RXID has been changed from 7 to 8. | No effect. |
| 8 | Value of member PHY_INTERFACE_MODE_RGMII has been changed from 5 to 6. | No effect. |
| 9 | Value of member PHY_INTERFACE_MODE_RTBI has been changed from 9 to 10. | No effect. |
| 10 | Value of member PHY_INTERFACE_MODE_RGMII_ID has been changed from 6 to 7. | No effect. |
| 11 | Value of member PHY_INTERFACE_MODE_RMII has been changed from 4 to 5. | No effect. |
| 12 | Value of member PHY_INTERFACE_MODE_SGMII has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| 2 | The relative position of field count has been changed from 16 to 14. | No effect. |
| 3 | The relative position of field data has been changed from 13 to 11. | No effect. |
| 4 | The relative position of field gid has been changed from 6 to 4. | No effect. |
| 5 | The relative position of field mode has been changed from 3 to 1. | No effect. |
| 6 | The relative position of field name has been changed from 2 to 20. | No effect. |
| 7 | The relative position of field namelen has been changed from 1 to 19. | No effect. |
| 8 | The relative position of field next has been changed from 10 to 8. | No effect. |
| 9 | The relative position of field nlink has been changed from 4 to 2. | No effect. |
| 10 | The relative position of field parent has been changed from 11 to 9. | No effect. |
| 11 | The relative position of field pde_openers has been changed from 20 to 17. | No effect. |
| 12 | The relative position of field pde_unload_completion has been changed from 19 to 16. | No effect. |
| 13 | The relative position of field pde_users has been changed from 17 to 15. | No effect. |
| 14 | The relative position of field proc_fops has been changed from 9 to 7. | No effect. |
| 15 | The relative position of field proc_iops has been changed from 8 to 6. | No effect. |
| 16 | The relative position of field read_proc has been changed from 14 to 12. | No effect. |
| 17 | The relative position of field size has been changed from 7 to 5. | No effect. |
| 18 | The relative position of field subdir has been changed from 12 to 10. | No effect. |
| 19 | The relative position of field uid has been changed from 5 to 3. | No effect. |
| 20 | The relative position of field write_proc has been changed from 15 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rto_count has been changed from 5 to 1. | No effect. |
| 2 | The relative position of field online has been changed from 3 to 4. | No effect. |
| 3 | The relative position of field rcu has been changed from 1 to 2. | No effect. |
| 4 | The relative position of field span has been changed from 2 to 3. | No effect. |
| 5 | The relative position of field rto_mask has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved_tailroom has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rq_arg has been changed from 15 to 16. | No effect. |
| 2 | The relative position of field rq_authop has been changed from 8 to 9. | No effect. |
| 3 | The relative position of field rq_cred has been changed from 10 to 11. | No effect. |
| 4 | The relative position of field rq_daddr has been changed from 27 to 5. | No effect. |
| 5 | The relative position of field rq_deferred has been changed from 12 to 13. | No effect. |
| 6 | The relative position of field rq_flavor has been changed from 9 to 10. | No effect. |
| 7 | The relative position of field rq_pages has been changed from 17 to 18. | No effect. |
| 8 | The relative position of field rq_pool has been changed from 6 to 7. | No effect. |
| 9 | The relative position of field rq_proc has been changed from 24 to 25. | No effect. |
| 10 | The relative position of field rq_procinfo has been changed from 7 to 8. | No effect. |
| 11 | The relative position of field rq_prog has been changed from 22 to 23. | No effect. |
| 12 | The relative position of field rq_prot has been changed from 25 to 26. | No effect. |
| 13 | The relative position of field rq_res has been changed from 16 to 17. | No effect. |
| 14 | The relative position of field rq_respages has been changed from 18 to 19. | No effect. |
| 15 | The relative position of field rq_resused has been changed from 19 to 20. | No effect. |
| 16 | The relative position of field rq_secure has been changed from 26 to 27. | No effect. |
| 17 | The relative position of field rq_server has been changed from 5 to 6. | No effect. |
| 18 | The relative position of field rq_usedeferral has been changed from 13 to 14. | No effect. |
| 19 | The relative position of field rq_vec has been changed from 20 to 21. | No effect. |
| 20 | The relative position of field rq_vers has been changed from 23 to 24. | No effect. |
| 21 | The relative position of field rq_xid has been changed from 21 to 22. | No effect. |
| 22 | The relative position of field rq_xprt_ctxt has been changed from 11 to 12. | No effect. |
| 23 | The relative position of field rq_xprt_hlen has been changed from 14 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field max_reqs has been changed from 16 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sdata has been renamed to vif. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter now has been renamed to force. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to long. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nid has been renamed to associated_nid. | 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 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter path has been renamed to dentry. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter l3 has been renamed to nb. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter l3 has been renamed to nb. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter avi_if has been renamed to frame. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to ioapic_idx. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to ioapic_idx. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to ioapic_idx. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter addr has been renamed to rt. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to work. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to work. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter a has been renamed to m. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nd has been renamed to path. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter doio has been renamed to pg_ops. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mod has been renamed to mk. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dep has been renamed to req. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pm_qos_req has been renamed to req. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pm_qos_req has been renamed to req. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter kill has been renamed to ignore_state. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter add_head has been renamed to realloc_head. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter in has been renamed to data. | No effect. |
| 2 | 3rd parameter W has been renamed to array. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter start has been renamed to lstart. | No effect. |
| 2 | 3rd parameter end has been renamed to lend. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to swap. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trace has been renamed to regs. | No effect. |
| 2 | 2nd parameter regs has been renamed to trace. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pos has been renamed to skb. | No effect. |
| 2 | 4th parameter payload_len has been renamed to payload. | No effect. |
| 3 | 5th parameter ta has been renamed to payload_len. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter old has been renamed to oldsize. | No effect. |
| 2 | 3rd parameter new has been renamed to newsize. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter offset has been renamed to newsize. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter offset has been renamed to lstart. | No effect. |
| 2 | 3rd parameter end has been renamed to lend. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | No effect. |