Module Name | vmlinux |
---|---|
Version #1 | 3.12 |
Version #2 | 3.13-rc4 |
CPU Type | x86 |
Subject | Binary Compatibility |
Total Header Files | 810 |
---|---|
Total Source Files | 1486 |
Total Objects | 1 |
Total Symbols / Types | 17363 / 9625 |
Verdict | Incompatible (51.2%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 320 |
Removed Symbols | High | 137 |
Problems with Data Types | High | 68 |
Medium | 237 | |
Low | 282 | |
Problems with Symbols | High | 38 |
Medium | 349 | |
Low | 65 | |
Problems with Constants | Low | 0 |
Other Changes in Data Types | - | 10 |
Change | Effect | |
---|---|---|
1 | Field csd 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 ref_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. |
3 | Field queuelist 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 flush_rq 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 use_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field id_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. |
3 | Field idr 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 c_models 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 bus_attrs 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 drv_attrs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field dev_attrs 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 dev_bin_attrs 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 synth_clock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field _vblank_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. |
2 | Field _vblank_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 counters 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 counts 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 ctx_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. |
6 | Field last_vblank has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
7 | Field last_vblank_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. |
8 | Field map_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. |
9 | Field pci_device has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
10 | Field pci_vendor has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
11 | Field types has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
12 | Field vbl_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
13 | Field vblank_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. |
14 | Field vblank_inmodeset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
15 | Field vblank_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. |
16 | Field work 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 gem_init_object 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 mode_fixup 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 interval 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 tt_usecs 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 ep 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 raw_mask 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 udev 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 usecs 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 c_usecs 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 dev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | 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. |
4 | Field 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. |
5 | Field tt_usecs 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 usecs 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 f_sb_list_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 mcast_groups 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 ops_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. |
Change | Effect | |
---|---|---|
1 | Field driver 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_clock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field exec_handle 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 exec_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. |
3 | Field exec_node 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 exec_entry has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field irq_mask 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 no_psr_reason 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 power_well 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 vlv_work 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 link_configuration 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 auth_flavor_len has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field daddr 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 rcv_saddr 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 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. |
2 | Field description 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 waiter 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 set_wake 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 nfct_reasm 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 enter_memory_pressure 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 parent_sd 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 drop 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 | The pointer level of 4th parameter data_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 | The pointer level of 4th parameter data_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 physid of type 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 clone_flags 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 | Type of 3rd parameter upper has been changed from bool (1 byte) to struct list_head* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 3rd parameter upper 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 cprm of type struct coredump_params* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter cprm of type struct coredump_params* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter family of type struct genl_family* 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 family of type struct genl_family* 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 ring of type struct intel_ring_buffer* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter pipe has been changed from int (4 bytes) to enum pipe (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | Parameter net of type struct net* 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 connector of type struct intel_connector* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter dev 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 pipe of type enum pipe 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 pipe of type enum pipe has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter sk of type struct sock 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. |
Change | Effect | |
---|---|---|
1 | Parameter _edit of type struct assoc_array_edit** has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter keyring 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 index_key of type struct keyring_index_key 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 _edit of type struct assoc_array_edit** 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 | 2nd middle parameter type 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 | 3rd middle parameter description 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 3rd parameter prealloc 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 ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 2nd middle parameter cred 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 vma of type struct vm_area_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 | Parameter ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter type 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 ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter type 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 resource_list_size of type acpi_size 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 sb of type struct super_block* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 1st middle parameter fstype 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 acked 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 | Field reqs 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 | Field callback_head 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 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. |
Change | Effect | |
---|---|---|
1 | Field mq_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 mq_ctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field unnamed3 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | 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. |
4 | Type of field cmd_flags has been changed from unsigned int (4 bytes) to u64 (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. |
5 | The relative position of field bio has been changed from 7 to 9. | 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 __sector has been changed from 6 to 8. | 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 unnamed0 has been changed from 10 to 0. | 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 biotail has been changed from 8 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 unnamed1 has been changed from 11 to 1. | 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 cpu has been changed from 4 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 hash has been changed from 9 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
12 | Size of field unnamed1 has been changed from 16 bytes to 20 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. |
13 | The relative position of field __data_len has been changed from 5 to 7. | Applications will access incorrect memory when attempting to access this field. |
14 | The relative position of field cmd_flags has been changed from 1 to 3. | Applications will access incorrect memory when attempting to access this field. |
15 | The relative position of field atomic_flags has been changed from 3 to 5. | Applications will access incorrect memory when attempting to access this field. |
16 | The relative position of field cmd_type has been changed from 2 to 4. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field mq_map has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 queue_ctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field mq_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. |
4 | Field nr_hw_queues has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mq_kobj has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
6 | Field nr_queues has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 queue_hw_ctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
8 | 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. |
9 | Type of field queue_lock has been changed from spinlock_t* (4 bytes) to spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field queuelist 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 rb_node has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
Change | Effect | |
---|---|---|
1 | Field csd 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 elv 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 running_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 | This type became opaque. | The internal structure of this type is hidden in the new library version and may be different. This may result in crash or incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The relative position of field c_x86_vendor has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field target_index has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 have_governor_per_policy has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field namespace 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 kdev has been changed from struct device (232 bytes) to struct device* (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 kdev 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 mode has been changed from 196 bytes to 192 bytes. | Previous accesses of applications and library functions to this field may be broken. |
2 | Size of field hwmode has been changed from 196 bytes to 192 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 vblank has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 irq_enabled has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
3 | Type of field vblank_disable_allowed has been changed from int (4 bytes) to bool (1 byte). | 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 ioctl_count has been changed from 4 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
2 | The relative position of field lock_count 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. |
3 | The relative position of field table_lock 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. |
4 | The relative position of field lhead 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. |
5 | The relative position of field object_idr 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. |
6 | The relative position of field filp has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
7 | The relative position of field is_master has been changed from 12 to 1. | Applications will access incorrect memory when attempting to access this field. |
8 | The relative position of field magic has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
9 | The relative position of field minor has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
10 | The relative position of field pid has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
11 | The relative position of field uid has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field driver_private has been removed from the middle position of this structural type. | 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. 2) Size of the inclusive type has been changed. |
Change | Effect | |
---|---|---|
1 | Type of field kdev has been changed from struct device (232 bytes) to struct device* (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 kdev 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 mutex 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 ps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 uperiod has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 c_usecs has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field ps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_files 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 filter has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mcgrp_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mcgrps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 n_mcgrps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 n_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. |
5 | Field 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 high_prio_bh has been changed from 32 bytes to 36 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 low_prio_bh has been changed from 32 bytes to 36 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 hcpriv has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 out_vol_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field preferred_dacs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tt 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 and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Value of member POWER_DOMAIN_TRANSCODER_EDP has been changed from 21 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
Change | Effect | |
---|---|---|
1 | Field bbstate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field framebuffer_references has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 base has been changed from 108 bytes to 104 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 context_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 pipe_crc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power_domains has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 psr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
6 | Size of field display 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. |
7 | Size of field gpu_error has been changed from 100 bytes to 104 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 l3_parity has been changed from 20 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. |
9 | Size of field mm has been changed from 268 bytes to 344 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 | Size of field opregion has been changed from 24 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. |
11 | Size of field regfile has been changed from 3084 bytes to 3096 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 | Size of field ring has been changed from 960 bytes to 976 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. |
13 | Size of field rps has been changed from 204 bytes to 140 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 uncore has been changed from 20 bytes to 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. |
15 | Size of field vbt has been changed from 68 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. |
16 | Size of field wm has been changed from 30 bytes to 88 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 idle_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. |
Change | Effect | |
---|---|---|
1 | Size of field hang_stats 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 | Field num_pt_pages has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | 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. |
3 | 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. |
Change | Effect | |
---|---|---|
1 | Field saveBLC_HIST_CTL_B has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 saveBLC_PWM_CTL2_B has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 saveBLC_PWM_CTL_B has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 is_preliminary 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 | Field ring_mask has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field has_blt_ring 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. |
4 | Field has_bsd_ring 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. |
5 | Field has_force_wake 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. |
6 | Field has_vebox_ring 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 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. |
2 | Field last_adj has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rp0_delay has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rp1_delay has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 swsci_gbda_sub_functions has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 swsci_sbcb_sub_functions has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 funcs has been changed from 8 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 | Base type of field child_dev has been changed from struct child_device_config to union child_device_config of different format. | This field may be incorrectly initialized or accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field csa_connection_drop_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field userspace_handles_dfs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 u has been changed from 700 bytes to 708 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 mesh_chansw_params_ie has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ap has been changed from 304 bytes to 328 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 ibss has been changed from 200 bytes to 220 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 mesh has been changed from 700 bytes to 708 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 regen_timer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tempaddr_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. |
3 | Field rndid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cnf has been changed from 96 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 | Field ifpub has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 regen_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. |
3 | Field tmp_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 icsk_inet has been changed from 568 bytes to 608 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 twchain 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 base has been changed from 28 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field sk has been changed from 432 bytes to 468 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 cork has been changed from 88 bytes to 92 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 __tw_common has been changed from 56 bytes to 88 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Type of this 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 | Size of field base has been changed from 864 bytes to 636 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field base has been changed from 796 bytes to 788 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 | Field primary_disabled 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 adjusted_mode has been changed from 196 bytes to 192 bytes. | Previous accesses of applications and library functions to this field may be broken. |
2 | Size of field requested_mode has been changed from 196 bytes to 192 bytes. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field dp has been changed from 560 bytes to 552 bytes. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Type of field rsvd has been changed from u8[102] (102 bytes) to u8[86] (86 bytes). | This field may be incorrectly initialized or accessed by applications. |
2 | Field cddv has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field iuer has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
4 | Field pcft 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. |
5 | Field srot 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 | Value of member HANGCHECK_ACTIVE 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 HANGCHECK_HUNG has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
3 | Value of member HANGCHECK_KICK has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
4 | Value of member HANGCHECK_WAIT has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
Change | Effect | |
---|---|---|
1 | Field outstanding_lazy_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field auth_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. |
Change | Effect | |
---|---|---|
1 | Field sysctl_local_ports 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 | Field sysctl_tcp_mem 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 temp_valid_lft has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field max_desync_factor has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 regen_max_retry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 use_tempaddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 temp_prefered_lft has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 def_lookup_type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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 | Field payload 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 bottom_up has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Type of field nr_ptes has been changed from unsigned long to atomic_long_t of different format. | This field may be incorrectly initialized or accessed by applications. |
2 | The relative position of field hiwater_rss has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
3 | The relative position of field mmlist has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
4 | The relative position of field exec_vm has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
5 | The relative position of field shared_vm has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
6 | The relative position of field nr_ptes has been changed from 24 to 11. | Applications will access incorrect memory when attempting to access this field. |
7 | The relative position of field locked_vm has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
8 | The relative position of field def_flags has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
9 | The relative position of field page_table_lock has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
10 | The relative position of field map_count has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
11 | The relative position of field mmap_sem has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
12 | The relative position of field pinned_vm has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
13 | The relative position of field hiwater_vm has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
14 | The relative position of field stack_vm has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
15 | The relative position of field total_vm has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Size of field unnamed0 has been changed from 12 bytes to 4 bytes. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
2 | Size of field unnamed1 has been changed from 8 bytes to 12 bytes. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
3 | Field mapping 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 lru 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 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. |
3 | Field callback_head 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. |
4 | Field unnamed0 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. |
5 | Field ptl 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. |
6 | Field private 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. |
7 | Field slab_cache 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 mnt_rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mnt_ghosts 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 m_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 | Field adj_list 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 | Field all_adj_list has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field fwd_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. |
4 | Field lower_dev_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 priv has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 call_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 | Field cl_mig_gen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 auth_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. |
2 | Field mig_status has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mig_gen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 super has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 is_pcie 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 percpu_batch_size 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 | Field percpu_max_size 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 intel_cp_status has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lbr_double_abort has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 apic_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field __req_common has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_idle_balance_cost has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 next_decay_max_lb_cost has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 imbalance has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 thread has been changed from 132 bytes to 136 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 fpu_counter 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 pad_until has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Type of field memory_allocated has been changed from struct res_counter* (4 bytes) to struct res_counter (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. |
2 | Type of field sockets_allocated has been changed from struct percpu_counter* (4 bytes) to struct percpu_counter (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 sysctl_mem has been changed from long* (4 bytes) to long[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 sk_max_pacing_rate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 __sk_common has been changed from 56 bytes to 88 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 skc_v6_rcv_saddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 skc_v6_daddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 known_smps_mode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field namespace 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 inet_conn has been changed from 836 bytes to 876 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 tclass has been changed from 80 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field class has been changed from 68 bytes to 60 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 suspend_wakeups has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 usb2_hw_lpm_allowed 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 this global data has been changed from 196 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter act 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 pointer level of 5th parameter mic has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | The pointer level of 5th parameter cdata has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter req 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 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter source 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 target 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 clnt 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter buf 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 cnt 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 dst 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter gchanges of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter accel_priv of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter parent_sd of type struct sysfs_dirent* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter parent_sd of type struct sysfs_dirent* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | 2nd parameter parent_sd has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | Parameter mark_deferred of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
2 | Parameter only_deferred of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter frame 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 mode 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 | The parameter dev 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 num_crtcs 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 | The parameter mode1 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 mode2 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 | The parameter dev 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 | 2nd parameter reliable 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 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Parameter last_e2bit of type u32 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | 2nd parameter size has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 3rd parameter limit has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | 3rd parameter size has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 4th parameter limit has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | The parameter cpu 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 cpu 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 table 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 older_than_this of type unsigned long 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter gov 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different 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. |
Change | Effect | |
---|---|---|
1 | Parameter slice of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | The parameter o 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 vma 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 dev_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 mask 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 pipe 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter dev has been changed from struct drm_device (956 bytes) to struct intel_connector (664 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 2nd parameter pipe has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter dev has been changed from struct drm_device (956 bytes) to struct intel_connector (664 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter dev has been changed from struct drm_device (956 bytes) to struct drm_crtc (788 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len 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 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | 3rd parameter _prealloc has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | 4th parameter _prealloc has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter type has been changed from struct key_type (60 bytes) to struct keyring_index_key (12 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 3rd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 4th parameter description has been removed from the calling stack. | This parameter will be ignored by the function. |
3 | 5th parameter match has been removed from the calling stack. | This parameter will be ignored by the function. |
4 | 6th parameter no_state_check has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | The parameter kobj 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 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter lockref 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 type of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | The parameter filp 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 fl 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 mddev 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 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Parameter flags of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | This parameter will not be initialized by old clients. |
2 | 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. |
3 | The parameter dir 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 dir 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 1332 bytes to 1368 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 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 8 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
6 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
7 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
8 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
9 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
10 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
11 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
12 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
13 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
15 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
16 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
17 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
18 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
19 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
20 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
21 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
22 | Size of this global data has been changed from 3060 bytes to 3068 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 252 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 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 8 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 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 134 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | 2nd parameter description has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 3rd parameter match has been removed from the calling stack. | This parameter will be ignored by the function. |
3 | 4th parameter no_state_check has been removed from the calling stack. | This parameter will be ignored by the function. |
4 | 5th parameter cred has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | 2nd parameter description has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 3rd parameter match has been removed from the calling stack. | This parameter will be ignored by the function. |
3 | 4th parameter cred has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | The parameter code 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 type 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 value 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 | Size of this global data has been changed from 252 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
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 offset 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 | Base type of 1st parameter linked_list_buffer has been changed from struct acpi_resource (66 bytes) to struct acpi_buffer (8 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter flags of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter rate64 of type u64 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 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 92 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
6 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
7 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
8 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
9 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
10 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
11 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
12 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
13 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
14 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
15 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
16 | Size of this global data has been changed from 92 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
17 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
18 | Size of this global data has been changed from 60 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
19 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
20 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
21 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
22 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
23 | Size of this global data has been changed from 12 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
24 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
25 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
26 | Size of this global data has been changed from 1188 bytes to 1296 bytes. | Applications will obtain a different value and execution may change. |
27 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
28 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
29 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
30 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
31 | Size of this global data has been changed from 140 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
32 | Size of this global data has been changed from 96 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
33 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
34 | Size of this global data has been changed from 432 bytes to 468 bytes. | Applications will obtain a different value and execution may change. |
35 | Size of this global data has been changed from 56 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
36 | Size of this global data has been changed from 192 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
37 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
38 | Size of this global data has been changed from 28 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
39 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
40 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
41 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
42 | Size of this global data has been changed from 92 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
43 | Size of this global data has been changed from 424 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
44 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
45 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
46 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
47 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
48 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
49 | Size of this global data has been changed from 20 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
50 | Size of this global data has been changed from 92 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
51 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
52 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
53 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
54 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
55 | Size of this global data has been changed from 132 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
56 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
58 | Size of this global data has been changed from 244 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
59 | Size of this global data has been changed from 1416 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
60 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
61 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
62 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
63 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
64 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
65 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
66 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
67 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
68 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
69 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
70 | Size of this global data has been changed from 1296 bytes to 1300 bytes. | Applications will obtain a different value and execution may change. |
71 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
72 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
73 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
74 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
75 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
76 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
77 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
78 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
79 | 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 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 244 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
6 | Size of this global data has been changed from 1416 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter c 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 m 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 | 2nd parameter behavior has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | 3rd parameter sid has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | The parameter name 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 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 | The parameter sb 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 datasync 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 file 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Parameter acked of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
2 | The parameter tp 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 sk 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 iter 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 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter call has been changed from struct ftrace_event_call (72 bytes) to struct ftrace_event_file (36 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter call has been changed from struct ftrace_event_call (72 bytes) to struct ftrace_event_file (36 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter call has been changed from struct ftrace_event_call (72 bytes) to struct ftrace_event_file (36 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | The parameter entry 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 s 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 seq 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 v 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 anchor 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 timeout 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 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
2 | Size of this global data has been changed from 344 bytes to 340 bytes. | Applications will obtain a different value and execution may change. |
3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
4 | Size of this global data has been changed from 68 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
5 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | The parameter from 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 n became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
3 | The parameter to 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 flags 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 24 bytes to 32 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 bool (1 byte). | Applications will obtain a different return value and execution may change. |
Change | Effect | |
---|---|---|
1 | Field ignore_parent 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 ignore 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 execve 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 | Field rcu 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 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 320 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 20 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 212 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 mq_usage_counter 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 all_q_node 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 mq_freeze_wq 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 1188 bytes to 1296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
5 | The pointer level of field queue_lock has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 12 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field completion_data has been renamed to ll_list. | 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 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field flush has been renamed to mq_flush_data. | 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 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field userspace_handles_dfs 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 supported_channels 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 supported_channels_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 | Field supported_oper_classes 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 supported_oper_classes_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. |
5 | Size of this type has been changed from 60 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ibss_dfs_possible 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 132 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 | Field cl_noretranstimeo 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 legacy_models has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 328 bytes to 380 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field c_size_cache has been renamed to legacy_cache_size. | 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. |
Change | Effect | |
---|---|---|
1 | Field rwsem 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 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field handle has been renamed to companion. | 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 84 bytes to 76 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 68 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 | 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 864 bytes to 636 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field stereo_allowed 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 796 bytes to 788 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 196 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field clock_index has been renamed to crtc_clock. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field const_type 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 | Added const qualifier to field ptr_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 ptr_const has been changed from void const** to void*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 956 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 | Size of this type has been changed from 252 bytes to 248 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_scanout_position has been changed from int(*)(struct drm_device*, int, int*, int*) to int(*)(struct drm_device*, int, int*, int*, ktime_t*, ktime_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field always_authenticated 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 172 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field stereo_allowed 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 108 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 316 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 52 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 2016 bytes to 1992 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field memmap 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 | Type of field allocate_pages has been changed from void* to efi_status_t(*)(int, int, unsigned long, efi_physical_addr_t*). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
2 | Type of field allocate_pool has been changed from void* to efi_status_t(*)(int, unsigned long, void**). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
3 | Type of field exit_boot_services has been changed from void* to efi_status_t(*)(efi_handle_t, unsigned long). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
4 | Type of field free_pages has been changed from void* to efi_status_t(*)(efi_physical_addr_t, unsigned long). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
5 | Type of field free_pool has been changed from void* to efi_status_t(*)(void*). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
6 | Type of field get_memory_map has been changed from void* to efi_status_t(*)(unsigned long*, void*, unsigned long*, unsigned long*, u32*). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
7 | Type of field handle_protocol has been changed from void* to efi_status_t(*)(efi_handle_t, efi_guid_t*, void**). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field scanning 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 2120 bytes to 2124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field deleting 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 bandwidth 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 tt_budget 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 tt_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Size of this type has been changed from 496 bytes to 632 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 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Type of field next_uframe has been changed from int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 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 | Field s_err_ratelimit_state 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 s_msg_ratelimit_state 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 s_warning_ratelimit_state 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 832 bytes to 896 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rcu 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 2284 bytes to 2292 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field buffers has been renamed to files. | 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 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 | Field rcu 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 fu_list has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field perf_perm 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 72 bytes to 76 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 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 76 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Base type of field post_doit has been changed from void(*)(struct genl_ops*, struct sk_buff*, struct genl_info*) to void(*)(struct genl_ops const*, struct sk_buff*, struct genl_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
3 | Base type of field pre_doit has been changed from int(*)(struct genl_ops*, struct sk_buff*, struct genl_info*) to int(*)(struct genl_ops const*, struct sk_buff*, struct genl_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field completing_ep has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 32 bytes to 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 304 bytes to 312 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field amd_resume_bug 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 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 2676 bytes to 2688 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field block_report 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 324 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 276 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 hw 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 30 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 84 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Base type of field update_wm has been changed from void(*)(struct drm_device*) to void(*)(struct drm_crtc*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
3 | Base type of field write_eld has been changed from void(*)(struct drm_connector*, struct drm_crtc*) to void(*)(struct drm_connector*, struct drm_crtc*, struct drm_display_mode*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of field cache_level has been changed from 2 bits to 3 bits. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Field hangcheck_action 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 hangcheck_score 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 784 bytes to 832 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 228 bytes to 204 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Type of field user_pin_count has been changed from uint32_t to unsigned long. | 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 9140 bytes to 9516 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field banned 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 guilty_ts 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. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 268 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field test_irq_rings 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 100 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field last_reset has been renamed to missed_irq_rings. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field link has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 32 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field remap_slice 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 168 bytes to 204 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field pd_offset has been renamed to pd_pages. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
3 | Field pt_dma_addr has been renamed to num_pd_pages. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
4 | Field pt_pages has been renamed to unnamed0. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 3084 bytes to 3096 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field exec_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. |
2 | Field exec_handle 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 exec_node 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 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 204 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 | Field which_slice 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 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Base type of field remap_info has been changed from unsigned int to u32*. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field asle_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 24 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field force_wake_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 20 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 | Field mmio_readb 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 mmio_readl 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 mmio_readq 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 mmio_readw has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field mmio_writeb has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field mmio_writel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field mmio_writeq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Field mmio_writew has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
9 | Size of this type has been changed from 8 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 ddi_port_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 | 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. |
3 | Field dsi 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 request_smps_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field driver_smps_mode 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 req_smps 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 304 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 200 bytes to 220 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field chsw_init 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 chsw_ttl 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 csa 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 700 bytes to 708 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
5 | Field pre_value 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 1780 bytes to 1788 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 144 bytes to 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 700 bytes to 708 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 424 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 156 bytes to 172 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 836 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 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 | Field priority 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 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. |
3 | Field ttl 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 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 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 568 bytes to 608 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 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Type of field tw_ttd has been changed from unsigned long to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
3 | Field tw_ipv6_offset has been renamed to tw_pad2. | 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 892 bytes to 664 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field enabled_power_domains 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 primary_enabled 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 wm 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 2176 bytes to 2284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field double_wide 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 pipe_src_h 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 pipe_src_w 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 712 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 560 bytes to 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 240 bytes to 244 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field outstanding_lazy_request has been renamed to preallocated_lazy_request. | 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 388 bytes to 436 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field auth_flavors has been renamed to selected_flavor. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field priority 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 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. |
3 | Field ttl 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 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 96 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 140 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 | Field trusted 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 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 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 | Base type of field tfm has been changed from struct crypto_cipher to struct crypto_aead. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field unnamed3 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 92 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 | Field join_ibss 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 leave_ibss 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 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 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 4 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field first_page has been renamed to slab_page. | 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 344 bytes to 340 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mnt_ex_mountpoint 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 140 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 | Type of field m_ts has been changed from int to size_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 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 | Base type of field set_peek_off has been changed from void(*)(struct sock*, int) to int(*)(struct sock*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Type of field irq has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
2 | Field upper_dev_list has been renamed to close_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field ndo_dfwd_add_station 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 ndo_dfwd_del_station 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 ndo_dfwd_start_xmit 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 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 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 | Base type has been changed from unsigned int()(unsigned int, struct sk_buff*, struct net_device const*, struct net_device const*, int(*)(struct sk_buff*)) to unsigned int()(struct nf_hook_ops const*, struct sk_buff*, struct net_device const*, struct net_device const*, int(*)(struct sk_buff*)). | Replacement of the base data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Field rx_hook has been renamed to rx_skb_hook. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field abort 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 commit 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 12 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 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 | Field mig_recovery_ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 44 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 528 bytes to 532 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 952 bytes to 1016 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field acpi has been renamed to companion. | 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 3060 bytes to 3068 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field txn 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 120 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 248 bytes to 252 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 92 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 ipv6_recv_error has been changed from int(*)(struct sock*, struct msghdr*, int) to int(*)(struct sock*, struct msghdr*, int, int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field prevent_deferred_probe 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 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 676 bytes to 680 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field fpu_counter 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. |
Change | Effect | |
---|---|---|
1 | Field s4 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 40 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 1416 bytes to 1424 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 select_task_rq has been changed from int(*)(struct task_struct*, int, int) to int(*)(struct task_struct*, int, int, 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 244 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field last_update has been renamed to max_newidle_lb_cost. | 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 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 wake_cpu 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 1296 bytes to 1300 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field no_write_same 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 resetting has been renamed to eh_deadline. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field no_write_same 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 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 96 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 192 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 28 bytes to 96 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 memory_pressure 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 | The pointer level of field memory_allocated 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. |
4 | The pointer level of field sysctl_mem 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. |
5 | The pointer level of field sockets_allocated 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. |
6 | Type of field memory_pressure has been changed from int* to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 432 bytes to 468 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 56 bytes to 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 936 bytes to 940 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 | Field attr has been renamed to unnamed0. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 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 | Field s_bin_attr has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Base type of field cong_avoid has been changed from void(*)(struct sock*, u32, u32) to void(*)(struct sock*, u32, u32, 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 1296 bytes to 1336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field preempt_count has been renamed to saved_preempt_count. | 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 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 80 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 24 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 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field msi_mask_irq 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 msix_mask_irq 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 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | 2nd parameter scratch has been renamed to b_0. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 3rd parameter cdata has been renamed to aad. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | 4th parameter data_len has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
4 | 5th parameter mic has been renamed to data_len. | Renaming of a parameter may indicate a change in its semantic meaning. |
5 | 6th parameter data has been renamed to mic. | Renaming of a parameter may indicate a change in its semantic meaning. |
6 | Type of 4th parameter data_len has been changed from size_t to u8*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
7 | Type of 5th parameter mic has been changed from u8* to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
8 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Replacement of parameter base type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter scratch has been renamed to b_0. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 3rd parameter data has been renamed to aad. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | 4th parameter data_len has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
4 | 5th parameter cdata has been renamed to data_len. | Renaming of a parameter may indicate a change in its semantic meaning. |
5 | Type of 5th parameter cdata has been changed from u8* to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
6 | Type of 4th parameter data_len has been changed from size_t to u8*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
7 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Replacement of parameter base type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Replacement of parameter base type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Base type of return value has been changed from struct crypto_cipher to struct crypto_aead. | Replacement of return 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 | 2nd parameter dma_mask has been renamed to max_addr. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from size_t to ssize_t. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter siginfo has been changed from siginfo_t* to siginfo_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 3rd parameter upper has been renamed to dev_list. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter ns has been renamed to name. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 3rd parameter name has been renamed to ns. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | Type of 3rd parameter name has been changed from unsigned char const* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
4 | Type of 2nd parameter ns has been changed from void const* to unsigned char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 3rd parameter new_ns has been renamed to new_name. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 4th parameter new_name has been renamed to new_ns. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | Type of 4th parameter new_name has been changed from char const* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
4 | Type of 3rd parameter new_ns has been changed from void const* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter files has been changed from struct drm_info_list* to struct drm_info_list const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter files has been changed from struct drm_info_list* to struct drm_info_list const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter link_status has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter link_status has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter link_status has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter link_status has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter dpcd has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter dpcd has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 6th parameter info has been changed from struct nl_info* to struct nl_info const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
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 bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter pipe has been changed from int to enum pipe. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter ns has been renamed to name. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 3rd parameter name has been renamed to ns. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | Type of 3rd parameter name has been changed from char const* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
4 | Type of 2nd parameter ns has been changed from void const* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to connector. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to connector. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to crtc. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter type has been renamed to index_key. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | 3rd parameter prealloc has been renamed to edit. | Renaming of a parameter may indicate a change in its semantic meaning. |
3 | Type of 3rd parameter prealloc has been changed from unsigned long to struct assoc_array_edit*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter len has been changed from int to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter len has been changed from int to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter propagate has been renamed to how. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter linked_list_buffer has been renamed to resource_list. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter from has been changed from siginfo_t* to siginfo_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter n has been changed from unsigned long 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 unsigned char*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Size of field reserved has been changed from 28 bits to 27 bits. | No effect. |
Change | Effect | |
---|---|---|
1 | Size of field unnamed0 has been changed from 12 bytes to 8 bytes. | No effect. |
Change | Effect | |
---|---|---|
1 | The member MODE_NO_STEREO with value 35 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The member POWER_DOMAIN_INIT with value 11 has been added. | No effect. |
2 | The member POWER_DOMAIN_NUM with value 12 has been added. | No effect. |
3 | The member POWER_DOMAIN_VGA with value 10 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The member INVALID_PIPE with value 18446744073709551615 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The member HANGCHECK_IDLE with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | Size of field unnamed2 has been changed from 4 bytes to 8 bytes. | No effect. |
Change | Effect | |
---|---|---|
1 | Type of field neigh_priv_len has been changed from unsigned char (1 byte) to unsigned short (2 bytes). | No effect. |
Module Name | vmlinux |
---|---|
Version #1 | 3.12 |
Version #2 | 3.13-rc4 |
CPU Type | x86 |
Subject | Source Compatibility |
Total Header Files | 810 |
---|---|
Total Source Files | 1486 |
Total Objects | 1 |
Total Symbols / Types | 17378 / 9625 |
Verdict | Incompatible (50.6%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 320 |
Removed Symbols | High | 137 |
Problems with Data Types | High | 116 |
Medium | 11 | |
Low | 227 | |
Problems with Symbols | High | 32 |
Medium | 59 | |
Low | 24 | |
Problems with Constants | Low | 0 |
Other Changes in Data Types | - | 56 |
Other Changes in Symbols | - | 33 |
Change | Effect | |
---|---|---|
1 | Field callback_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'callback_head'. |
Change | Effect | |
---|---|---|
1 | Field csd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request' has no member named 'csd'. |
2 | Field ref_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request' has no member named 'ref_count'. |
3 | Field queuelist has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request' has no member named 'queuelist'. |
Change | Effect | |
---|---|---|
1 | Field flush_rq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'flush_rq'. |
Change | Effect | |
---|---|---|
1 | Field rb_node has been removed from this union. | Recompilation of a client program may be broken. |
2 | Field completion_data has been renamed to ll_list. | Recompilation of a client program may be broken with the error message: anon-union-blkdev.h-121 has no member named completion_data. |
Change | Effect | |
---|---|---|
1 | Field elv has been removed from this union. | Recompilation of a client program may be broken. |
2 | Field flush has been renamed to mq_flush_data. | Recompilation of a client program may be broken with the error message: anon-union-blkdev.h-132 has no member named flush. |
Change | Effect | |
---|---|---|
1 | Field id_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'id_lock'. |
2 | Field use_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'use_id'. |
3 | Field idr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'idr'. |
Change | Effect | |
---|---|---|
1 | Field c_models has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpu_dev' has no member named 'c_models'. |
2 | Field c_size_cache has been renamed to legacy_cache_size. | Recompilation of a client program may be broken with the error message: struct cpu_dev has no member named c_size_cache. |
Change | Effect | |
---|---|---|
1 | Field have_governor_per_policy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpufreq_driver' has no member named 'have_governor_per_policy'. |
Change | Effect | |
---|---|---|
1 | Field handle has been renamed to companion. | Recompilation of a client program may be broken with the error message: struct acpi_dev_node has no member named handle. |
Change | Effect | |
---|---|---|
1 | Field bus_attrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bus_type' has no member named 'bus_attrs'. |
2 | Field drv_attrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bus_type' has no member named 'drv_attrs'. |
Change | Effect | |
---|---|---|
1 | Field dev_attrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct class' has no member named 'dev_attrs'. |
2 | Field dev_bin_attrs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct class' has no member named 'dev_bin_attrs'. |
Change | Effect | |
---|---|---|
1 | Field namespace has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct class_attribute' has no member named 'namespace'. |
Change | Effect | |
---|---|---|
1 | Field synth_clock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_mode' has no member named 'synth_clock'. |
2 | Field clock_index has been renamed to crtc_clock. | Recompilation of a client program may be broken with the error message: struct drm_display_mode has no member named clock_index. |
Change | Effect | |
---|---|---|
1 | Field _vblank_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named '_vblank_count'. |
2 | Field _vblank_time has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named '_vblank_time'. |
3 | Field counters has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'counters'. |
4 | Field counts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'counts'. |
5 | Field ctx_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'ctx_count'. |
6 | Field last_vblank has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'last_vblank'. |
7 | Field last_vblank_wait has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'last_vblank_wait'. |
8 | Field map_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'map_count'. |
9 | Field pci_device has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'pci_device'. |
10 | Field pci_vendor has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'pci_vendor'. |
11 | Field types has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'types'. |
12 | Field vbl_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'vbl_queue'. |
13 | Field vblank_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'vblank_enabled'. |
14 | Field vblank_inmodeset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'vblank_inmodeset'. |
15 | Field vblank_refcount has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'vblank_refcount'. |
16 | Field work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'work'. |
Change | Effect | |
---|---|---|
1 | Field gem_init_object has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'gem_init_object'. |
Change | Effect | |
---|---|---|
1 | Field mode_fixup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dvo_dev_ops' has no member named 'mode_fixup'. |
Change | Effect | |
---|---|---|
1 | Field mutex 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 'mutex'. |
Change | Effect | |
---|---|---|
1 | Field interval has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'interval'. |
2 | Field tt_usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'tt_usecs'. |
3 | Field c_usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'c_usecs'. |
4 | Field ep has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'ep'. |
5 | Field raw_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'raw_mask'. |
6 | Field udev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'udev'. |
7 | Field usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_iso_stream' has no member named 'usecs'. |
Change | Effect | |
---|---|---|
1 | Field c_usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'c_usecs'. |
2 | Field dev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'dev'. |
3 | Field period has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'period'. |
4 | Field start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'start'. |
5 | Field tt_usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'tt_usecs'. |
6 | Field usecs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ehci_qh' has no member named 'usecs'. |
Change | Effect | |
---|---|---|
1 | Field buffers has been renamed to files. | Recompilation of a client program may be broken with the error message: struct sysfs_open_dirent has no member named buffers. |
Change | Effect | |
---|---|---|
1 | Field f_sb_list_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct file' has no member named 'f_sb_list_cpu'. |
Change | Effect | |
---|---|---|
1 | Field s_files has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_files'. |
Change | Effect | |
---|---|---|
1 | Field fu_list has been removed from this union. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field mcast_groups has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct genl_family' has no member named 'mcast_groups'. |
2 | Field ops_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct genl_family' has no member named 'ops_list'. |
Change | Effect | |
---|---|---|
1 | Field driver has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i2c_client' has no member named 'driver'. |
Change | Effect | |
---|---|---|
1 | Field get_clock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'get_clock'. |
Change | Effect | |
---|---|---|
1 | Field exec_entry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'exec_entry'. |
2 | Field exec_handle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'exec_handle'. |
3 | Field exec_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'exec_list'. |
4 | Field exec_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'exec_node'. |
Change | Effect | |
---|---|---|
1 | Field irq_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'irq_mask'. |
2 | Field no_psr_reason 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 'no_psr_reason'. |
3 | Field power_well 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 'power_well'. |
Change | Effect | |
---|---|---|
1 | Field last_reset has been renamed to missed_irq_rings. | Recompilation of a client program may be broken with the error message: struct i915_gpu_error has no member named last_reset. |
Change | Effect | |
---|---|---|
1 | Field pd_offset has been renamed to pd_pages. | Recompilation of a client program may be broken with the error message: struct i915_hw_ppgtt has no member named pd_offset. |
2 | Field pt_dma_addr has been renamed to num_pd_pages. | Recompilation of a client program may be broken with the error message: struct i915_hw_ppgtt has no member named pt_dma_addr. |
3 | Field pt_pages has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct i915_hw_ppgtt has no member named pt_pages. |
Change | Effect | |
---|---|---|
1 | Field has_blt_ring has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'has_blt_ring'. |
2 | Field has_bsd_ring has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'has_bsd_ring'. |
3 | Field has_force_wake has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'has_force_wake'. |
4 | Field has_vebox_ring has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'has_vebox_ring'. |
Change | Effect | |
---|---|---|
1 | Field vlv_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_gen6_power_mgmt' has no member named 'vlv_work'. |
Change | Effect | |
---|---|---|
1 | Field twchain has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_ehash_bucket' has no member named 'twchain'. |
Change | Effect | |
---|---|---|
1 | Field tw_ipv6_offset has been renamed to tw_pad2. | Recompilation of a client program may be broken with the error message: struct inet_timewait_sock has no member named tw_ipv6_offset. |
Change | Effect | |
---|---|---|
1 | Field primary_disabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'primary_disabled'. |
Change | Effect | |
---|---|---|
1 | Field link_configuration has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dp' has no member named 'link_configuration'. |
Change | Effect | |
---|---|---|
1 | Field outstanding_lazy_request has been renamed to preallocated_lazy_request. | Recompilation of a client program may be broken with the error message: struct intel_ring_buffer has no member named outstanding_lazy_request. |
Change | Effect | |
---|---|---|
1 | Field auth_flavor_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_parsed_mount_data' has no member named 'auth_flavor_len'. |
2 | Field auth_flavors has been renamed to selected_flavor. | Recompilation of a client program may be broken with the error message: struct nfs_parsed_mount_data has no member named auth_flavors. |
Change | Effect | |
---|---|---|
1 | Field sysctl_tcp_mem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'sysctl_tcp_mem'. |
Change | Effect | |
---|---|---|
1 | Field daddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ipv6_pinfo' has no member named 'daddr'. |
2 | Field rcv_saddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ipv6_pinfo' has no member named 'rcv_saddr'. |
Change | Effect | |
---|---|---|
1 | Field type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct key' has no member named 'type'. |
2 | Field description has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct key' has no member named 'description'. |
3 | Field payload has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct key' has no member named 'payload'. |
Change | Effect | |
---|---|---|
1 | Field mapping has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct page' has no member named 'mapping'. |
Change | Effect | |
---|---|---|
1 | Field ptl has been removed from this union. | Recompilation of a client program may be broken. |
2 | Field slab_cache has been removed from this union. | Recompilation of a client program may be broken. |
3 | Field private has been removed from this union. | Recompilation of a client program may be broken. |
4 | Field first_page has been renamed to slab_page. | Recompilation of a client program may be broken with the error message: anon-union-mm_types.h-136 has no member named first_page. |
Change | Effect | |
---|---|---|
1 | Field waiter has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct module' has no member named 'waiter'. |
Change | Effect | |
---|---|---|
1 | Field mnt_ghosts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mount' has no member named 'mnt_ghosts'. |
Change | Effect | |
---|---|---|
1 | Field lower_dev_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 'lower_dev_list'. |
2 | Field upper_dev_list has been renamed to close_list. | Recompilation of a client program may be broken with the error message: struct net_device has no member named upper_dev_list. |
Change | Effect | |
---|---|---|
1 | Field rx_hook has been renamed to rx_skb_hook. | Recompilation of a client program may be broken with the error message: struct netpoll has no member named rx_hook. |
Change | Effect | |
---|---|---|
1 | Field is_pcie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_dev' has no member named 'is_pcie'. |
Change | Effect | |
---|---|---|
1 | Field acpi has been renamed to companion. | Recompilation of a client program may be broken with the error message: struct pci_sysdata has no member named acpi. |
Change | Effect | |
---|---|---|
1 | Field last_update has been renamed to max_newidle_lb_cost. | Recompilation of a client program may be broken with the error message: struct sched_domain has no member named last_update. |
Change | Effect | |
---|---|---|
1 | Field fpu_counter 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 'fpu_counter'. |
Change | Effect | |
---|---|---|
1 | Field resetting has been renamed to eh_deadline. | Recompilation of a client program may be broken with the error message: struct Scsi_Host has no member named resetting. |
Change | Effect | |
---|---|---|
1 | Field set_wake has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct uart_ops' has no member named 'set_wake'. |
Change | Effect | |
---|---|---|
1 | Field nfct_reasm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sk_buff' has no member named 'nfct_reasm'. |
Change | Effect | |
---|---|---|
1 | Field enter_memory_pressure has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cg_proto' has no member named 'enter_memory_pressure'. |
Change | Effect | |
---|---|---|
1 | Field parent_sd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysfs_addrm_cxt' has no member named 'parent_sd'. |
Change | Effect | |
---|---|---|
1 | Field attr has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct sysfs_elem_attr has no member named attr. |
Change | Effect | |
---|---|---|
1 | Field namespace has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysfs_ops' has no member named 'namespace'. |
Change | Effect | |
---|---|---|
1 | Field s_bin_attr has been removed from this union. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field preempt_count has been renamed to saved_preempt_count. | Recompilation of a client program may be broken with the error message: struct thread_info has no member named preempt_count. |
Change | Effect | |
---|---|---|
1 | Field drop has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_port_operations' has no member named 'drop'. |
Change | Effect | |
---|---|---|
1 | Parameter physid of type int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter clone_flags 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 cprm of type struct coredump_params* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter cprm of type struct coredump_params* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter family of type struct genl_family* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter family of type struct genl_family* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter ring of type struct intel_ring_buffer* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter connector of type struct intel_connector* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter pipe of type enum pipe has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter pipe of type enum pipe has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter sk of type struct sock const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter _edit of type struct assoc_array_edit** has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter keyring has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter index_key of type struct keyring_index_key const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | Parameter _edit of type struct assoc_array_edit** has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
3 | 2nd middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
4 | 3rd middle parameter description has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 2nd middle parameter cred has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter vma of type struct vm_area_struct* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter ctx of type struct keyring_search_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter resource_list_size of type acpi_size has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter sb of type struct super_block* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
2 | 1st middle parameter fstype has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter acked 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 | The pointer level of field queue_lock has been increased from 1 to 0. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | This type became opaque. | The internal structure of this type is hidden in the new library version and recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of field kdev has been increased from 0 to 1. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of field kdev has been increased from 0 to 1. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of field child_dev has been changed from struct child_device_config to union child_device_config of different format. | 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 nr_ptes has been changed from unsigned long to atomic_long_t of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of field memory_pressure has been increased from 1 to 0. | Recompilation of a client program may be broken. |
2 | The pointer level of field memory_allocated has been increased from 1 to 0. | Recompilation of a client program may be broken. |
3 | The pointer level of field sysctl_mem has been increased from 1 to 0. | Recompilation of a client program may be broken. |
4 | The pointer level of field sockets_allocated has been increased from 1 to 0. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of 4th parameter data_len has been increased from 0 to 1. | Recompilation of a client program may be broken. |
2 | The pointer level of 5th parameter mic has been increased from 1 to 0. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of 5th parameter cdata has been increased from 1 to 0. | Recompilation of a client program may be broken. |
2 | The pointer level of 4th parameter data_len has been increased from 0 to 1. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter gchanges of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | The pointer level of 3rd parameter upper has been increased from 0 to 1. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter accel_priv of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter parent_sd of type struct sysfs_dirent* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter parent_sd of type struct sysfs_dirent* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter parent_sd has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter mark_deferred of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
2 | Parameter only_deferred of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter reliable has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter last_e2bit of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter size has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 3rd parameter limit has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 3rd parameter size has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 4th parameter limit has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter older_than_this of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter slice 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 dev has been changed from struct drm_device to struct intel_connector of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter pipe has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter dev has been changed from struct drm_device to struct intel_connector of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter dev has been changed from struct drm_device to struct drm_crtc of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter addr_len of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 3rd parameter _prealloc has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 4th parameter _prealloc has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter type has been changed from struct key_type to struct keyring_index_key of different format. | Recompilation of a client program may be broken. |
2 | The pointer level of 3rd parameter prealloc has been increased from 0 to 1. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 3rd parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 4th parameter description has been removed from the calling stack. | Recompilation of a client program may be broken. |
3 | 5th parameter match has been removed from the calling stack. | Recompilation of a client program may be broken. |
4 | 6th parameter no_state_check has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter type of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter flags of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter delegated_inode of type struct inode** has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 3rd parameter dir has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter description has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 3rd parameter match has been removed from the calling stack. | Recompilation of a client program may be broken. |
3 | 4th parameter no_state_check has been removed from the calling stack. | Recompilation of a client program may be broken. |
4 | 5th parameter cred has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter description has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 3rd parameter match has been removed from the calling stack. | Recompilation of a client program may be broken. |
3 | 4th parameter cred has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter linked_list_buffer has been changed from struct acpi_resource to struct acpi_buffer of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter flags of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter rate64 of type u64 has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | 2nd parameter behavior has been removed from the calling stack. | Recompilation of a client program may be broken. |
2 | 3rd parameter sid has been removed from the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Parameter acked of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter call has been changed from struct ftrace_event_call to struct ftrace_event_file of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter call has been changed from struct ftrace_event_call to struct ftrace_event_file of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of parameter call has been changed from struct ftrace_event_call to struct ftrace_event_file of different format. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field ignore_parent has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ignore has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field reqs has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field entry has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mq_list has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mq_ctx has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Type of field cmd_flags has been changed from unsigned int to u64. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field mq_kobj has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field mq_ops has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field queue_hw_ctx has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field queue_ctx has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Field mq_map has been added to this type. | This field will not be initialized or used by old client applications. |
6 | Field mq_usage_counter has been added to this type. | This field will not be initialized or used by old client applications. |
7 | Field nr_hw_queues has been added to this type. | This field will not be initialized or used by old client applications. |
8 | Field nr_queues has been added to this type. | This field will not be initialized or used by old client applications. |
9 | Field all_q_node has been added to this type. | This field will not be initialized or used by old client applications. |
10 | Field mq_freeze_wq has been added to this type. | This field will not be initialized or used by old client applications. |
11 | Type of field queue_lock has been changed from spinlock_t* to spinlock_t. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field running_list has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field userspace_handles_dfs has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field supported_channels has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field supported_channels_len has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field supported_oper_classes has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field supported_oper_classes_len has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ibss_dfs_possible has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field cl_noretranstimeo has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field legacy_models has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field target_index has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rwsem has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field stereo_allowed has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Type of field kdev has been changed from struct device to struct device*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Added const qualifier to field ptr_const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'anon-union-drm_flip_work.h-66::ptr_const'. |
Change | Effect | |
---|---|---|
1 | Field vblank has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Type of field irq_enabled has been changed from int to bool. | Recompilation of a client program may be broken. |
3 | Type of field vblank_disable_allowed has been changed from int to bool. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of field get_scanout_position has been changed from int(*)(struct drm_device*, int, int*, int*) to int(*)(struct drm_device*, int, int*, int*, ktime_t*, ktime_t*). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field always_authenticated has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field stereo_allowed has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of field kdev has been changed from struct device to struct device*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field memmap has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of field allocate_pages has been changed from void* to efi_status_t(*)(int, int, unsigned long, efi_physical_addr_t*). | Recompilation of a client program may be broken. |
2 | Type of field allocate_pool has been changed from void* to efi_status_t(*)(int, unsigned long, void**). | Recompilation of a client program may be broken. |
3 | Type of field exit_boot_services has been changed from void* to efi_status_t(*)(efi_handle_t, unsigned long). | Recompilation of a client program may be broken. |
4 | Type of field free_pages has been changed from void* to efi_status_t(*)(efi_physical_addr_t, unsigned long). | Recompilation of a client program may be broken. |
5 | Type of field free_pool has been changed from void* to efi_status_t(*)(void*). | Recompilation of a client program may be broken. |
6 | Type of field get_memory_map has been changed from void* to efi_status_t(*)(unsigned long*, void*, unsigned long*, unsigned long*, u32*). | Recompilation of a client program may be broken. |
7 | Type of field handle_protocol has been changed from void* to efi_status_t(*)(efi_handle_t, efi_guid_t*, void**). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field deleting has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field scanning has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field tt_budget has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field tt_list has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field uperiod has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Type of field next_uframe has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field s_err_ratelimit_state has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field s_msg_ratelimit_state has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field s_warning_ratelimit_state has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field perf_perm has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field filter has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mcgrp_offset has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field mcgrps has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field n_mcgrps has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field n_ops has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Field ops has been added to this type. | This field will not be initialized or used by old client applications. |
6 | Base type of field post_doit has been changed from void(*)(struct genl_ops*, struct sk_buff*, struct genl_info*) to void(*)(struct genl_ops const*, struct sk_buff*, struct genl_info*). | Recompilation of a client program may be broken. |
7 | Base type of field pre_doit has been changed from int(*)(struct genl_ops*, struct sk_buff*, struct genl_info*) to int(*)(struct genl_ops const*, struct sk_buff*, struct genl_info*). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field completing_ep has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field amd_resume_bug has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field out_vol_mask has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field preferred_dacs has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field block_report has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field hw 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 update_wm has been changed from void(*)(struct drm_device*) to void(*)(struct drm_crtc*). | Recompilation of a client program may be broken. |
2 | Base type of field write_eld has been changed from void(*)(struct drm_connector*, struct drm_crtc*) to void(*)(struct drm_connector*, struct drm_crtc*, struct drm_display_mode*). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field bbstate has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field hangcheck_action has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field hangcheck_score has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field framebuffer_references has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Type of field user_pin_count has been changed from uint32_t to unsigned long. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field context_list has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field pipe_crc has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field power_domains has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field psr has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field banned has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field guilty_ts has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field idle_work has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field test_irq_rings has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field link has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field remap_slice has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field num_pt_pages has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field saveBLC_HIST_CTL_B has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field saveBLC_PWM_CTL2_B has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field saveBLC_PWM_CTL_B has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field exec_entry has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field exec_handle has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field exec_node has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field is_preliminary has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field ring_mask has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field enabled has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field last_adj has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field power has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field rp0_delay has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Field rp1_delay has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field which_slice has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Base type of field remap_info has been changed from unsigned int to u32*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field asle_work has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field swsci_gbda_sub_functions has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field swsci_sbcb_sub_functions has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field force_wake_work has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mmio_readb has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field mmio_readl has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field mmio_readq has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field mmio_readw has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Field mmio_writeb has been added to this type. | This field will not be initialized or used by old client applications. |
6 | Field mmio_writel has been added to this type. | This field will not be initialized or used by old client applications. |
7 | Field mmio_writeq has been added to this type. | This field will not be initialized or used by old client applications. |
8 | Field mmio_writew has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ddi_port_info has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field dsi has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field driver_smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field req_smps has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field request_smps_work has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field csa_connection_drop_work has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field userspace_handles_dfs has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field chsw_init has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field chsw_ttl has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field csa has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field pre_value has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mesh_chansw_params_ie has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field regen_timer has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field tempaddr_list has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field rndid has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field ifpub has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field regen_count has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field tmp_list has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field priority has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field tos has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field ttl has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of field tw_ttd has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field enabled_power_domains has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field primary_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field wm has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field double_wide has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field pipe_src_h has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field pipe_src_w has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field cddv has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field iuer has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field pcft has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field srot has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Type of field rsvd has been changed from u8[102] to u8[86]. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field outstanding_lazy_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field auth_info has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field priority has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field tos has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field ttl has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field sysctl_local_ports has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field max_desync_factor has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field regen_max_retry has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field temp_valid_lft has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field temp_prefered_lft has been added to this type. | This field will not be initialized or used by old client applications. |
5 | Field use_tempaddr has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field trusted has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field def_lookup_type 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 tfm has been changed from struct crypto_cipher to struct crypto_aead. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field join_ibss has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field leave_ibss has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field bottom_up has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mnt_ex_mountpoint has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field mnt_rcu has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of field m_ts has been changed from int to size_t. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field m_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 set_peek_off has been changed from void(*)(struct sock*, int) to int(*)(struct sock*, int). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field fwd_ops has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field adj_list has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field all_adj_list has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Type of field irq has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field ndo_dfwd_start_xmit has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field ndo_dfwd_add_station has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field ndo_dfwd_del_station 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 int()(unsigned int, struct sk_buff*, struct net_device const*, struct net_device const*, int(*)(struct sk_buff*)) to unsigned int()(struct nf_hook_ops const*, struct sk_buff*, struct net_device const*, struct net_device const*, int(*)(struct sk_buff*)). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field abort has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field commit has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field call_batch has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field mig_recovery_ops has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field cl_mig_gen has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field super has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field mig_gen has been added to this type. | This field will not be initialized or used by old client applications. |
3 | Field auth_info has been added to this type. | This field will not be initialized or used by old client applications. |
4 | Field mig_status has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field percpu_batch_size has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field percpu_max_size has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field intel_cp_status has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field txn has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field lbr_double_abort has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field rcu 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 ipv6_recv_error has been changed from int(*)(struct sock*, struct msghdr*, int) to int(*)(struct sock*, struct msghdr*, int, int*). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field prevent_deferred_probe has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field apic_id has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field fpu_counter has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field s4 has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field __req_common has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field max_idle_balance_cost 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 select_task_rq has been changed from int(*)(struct task_struct*, int, int) to int(*)(struct task_struct*, int, int, int). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field next_decay_max_lb_cost has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field imbalance has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field wake_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field no_write_same has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field no_write_same has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field pad_until has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of field memory_allocated has been changed from struct res_counter* to struct res_counter. | Recompilation of a client program may be broken. |
2 | Type of field memory_pressure has been changed from int* to int. | Recompilation of a client program may be broken. |
3 | Type of field sockets_allocated has been changed from struct percpu_counter* to struct percpu_counter. | Recompilation of a client program may be broken. |
4 | Type of field sysctl_mem has been changed from long* to long[3]. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field sk_max_pacing_rate has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field skc_v6_daddr has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field skc_v6_rcv_saddr has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field known_smps_mode 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 cong_avoid has been changed from void(*)(struct sock*, u32, u32) to void(*)(struct sock*, u32, u32, u32). | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Field suspend_wakeups has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field usb2_hw_lpm_allowed has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Field msi_mask_irq has been added to this type. | This field will not be initialized or used by old client applications. |
2 | Field msix_mask_irq has been added to this type. | This field will not be initialized or used by old client applications. |
Change | Effect | |
---|---|---|
1 | Type of 4th parameter data_len has been changed from size_t to u8*. | Recompilation of a client program may be broken. |
2 | Type of 5th parameter mic has been changed from u8* to size_t. | Recompilation of a client program may be broken. |
3 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 5th parameter cdata has been changed from u8* to size_t. | Recompilation of a client program may be broken. |
2 | Type of 4th parameter data_len has been changed from size_t to u8*. | Recompilation of a client program may be broken. |
3 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter tfm has been changed from struct crypto_cipher to struct crypto_aead. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of return value has been changed from struct crypto_cipher to struct crypto_aead. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from size_t to ssize_t. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter upper has been changed from bool to struct list_head*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter name has been changed from unsigned char const* to void const*. | Recompilation of a client program may be broken. |
2 | Type of 2nd parameter ns has been changed from void const* to unsigned char const*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 4th parameter new_name has been changed from char const* to void const*. | Recompilation of a client program may be broken. |
2 | Type of 3rd parameter new_ns has been changed from void const* to char const*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter pipe has been changed from int to enum pipe. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter pipe has been changed from int to enum pipe. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter name has been changed from char const* to void const*. | Recompilation of a client program may be broken. |
2 | Type of 2nd parameter ns has been changed from void const* to char const*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter prealloc has been changed from unsigned long to struct assoc_array_edit*. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter len has been changed from int to size_t. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter len has been changed from int to size_t. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter n has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void* to unsigned char*. | 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 | Field execve has been added to this type. | No effect. |
Change | Effect | |
---|---|---|
1 | The relative position of field cmd_type has been changed from 2 to 4. | No effect. |
2 | The relative position of field unnamed0 has been changed from 10 to 0. | No effect. |
3 | The relative position of field bio has been changed from 7 to 9. | No effect. |
4 | The relative position of field cmd_flags has been changed from 1 to 3. | No effect. |
5 | The relative position of field __sector has been changed from 6 to 8. | No effect. |
6 | The relative position of field atomic_flags has been changed from 3 to 5. | No effect. |
7 | The relative position of field __data_len has been changed from 5 to 7. | No effect. |
8 | The relative position of field biotail has been changed from 8 to 10. | No effect. |
9 | The relative position of field hash has been changed from 9 to 11. | No effect. |
10 | The relative position of field unnamed1 has been changed from 11 to 1. | No effect. |
11 | The relative position of field cpu has been changed from 4 to 6. | No effect. |
Change | Effect | |
---|---|---|
1 | Field queuelist has been added to this type. | No effect. |
Change | Effect | |
---|---|---|
1 | Field csd has been added to this type. | No effect. |
Change | Effect | |
---|---|---|
1 | The relative position of field c_x86_vendor has been changed from 8 to 7. | No effect. |
Change | Effect | |
---|---|---|
1 | The member MODE_NO_STEREO with value 35 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | Field const_type has been added to this type. | No effect. |
Change | Effect | |
---|---|---|
1 | The relative position of field filp has been changed from 10 to 11. | No effect. |
2 | The relative position of field ioctl_count has been changed from 4 to 5. | No effect. |
3 | The relative position of field is_master has been changed from 12 to 1. | No effect. |
4 | The relative position of field lock_count has been changed from 7 to 8. | No effect. |
5 | The relative position of field magic has been changed from 3 to 4. | No effect. |
6 | The relative position of field minor has been changed from 6 to 7. | No effect. |
7 | The relative position of field object_idr has been changed from 8 to 9. | No effect. |
8 | The relative position of field pid has been changed from 1 to 2. | No effect. |
9 | The relative position of field uid has been changed from 2 to 3. | No effect. |
10 | The relative position of field lhead has been changed from 5 to 6. | No effect. |
11 | The relative position of field table_lock has been changed from 9 to 10. | No effect. |
Change | Effect | |
---|---|---|
1 | The member POWER_DOMAIN_INIT with value 11 has been added. | No effect. |
2 | The member POWER_DOMAIN_NUM with value 12 has been added. | No effect. |
3 | The member POWER_DOMAIN_VGA with value 10 has been added. | No effect. |
4 | Value of member POWER_DOMAIN_TRANSCODER_EDP has been changed from 21 to 9. | No effect. |
Change | Effect | |
---|---|---|
1 | The member INVALID_PIPE with value 18446744073709551615 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The member HANGCHECK_IDLE with value 0 has been added. | No effect. |
2 | Value of member HANGCHECK_ACTIVE has been changed from 1 to 2. | No effect. |
3 | Value of member HANGCHECK_HUNG has been changed from 3 to 4. | No effect. |
4 | Value of member HANGCHECK_KICK has been changed from 2 to 3. | No effect. |
5 | Value of member HANGCHECK_WAIT has been changed from 0 to 1. | No effect. |
Change | Effect | |
---|---|---|
1 | The relative position of field page_table_lock has been changed from 12 to 13. | No effect. |
2 | The relative position of field pinned_vm has been changed from 19 to 20. | No effect. |
3 | The relative position of field mmap_sem has been changed from 13 to 14. | No effect. |
4 | The relative position of field stack_vm has been changed from 22 to 23. | No effect. |
5 | The relative position of field exec_vm has been changed from 21 to 22. | No effect. |
6 | The relative position of field shared_vm has been changed from 20 to 21. | No effect. |
7 | The relative position of field map_count has been changed from 11 to 12. | No effect. |
8 | The relative position of field hiwater_vm has been changed from 16 to 17. | No effect. |
9 | The relative position of field hiwater_rss has been changed from 15 to 16. | No effect. |
10 | The relative position of field mmlist has been changed from 14 to 15. | No effect. |
11 | The relative position of field locked_vm has been changed from 18 to 19. | No effect. |
12 | The relative position of field total_vm has been changed from 17 to 18. | No effect. |
13 | The relative position of field def_flags has been changed from 23 to 24. | No effect. |
14 | The relative position of field nr_ptes has been changed from 24 to 11. | No effect. |
Change | Effect | |
---|---|---|
1 | Field lru has been added to this type. | No effect. |
2 | Field list has been added to this type. | No effect. |
3 | Field callback_head has been added to this type. | No effect. |
4 | Field unnamed0 has been added to this type. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter scratch has been renamed to b_0. | No effect. |
2 | 3rd parameter cdata has been renamed to aad. | No effect. |
3 | 4th parameter data_len has been renamed to data. | No effect. |
4 | 5th parameter mic has been renamed to data_len. | No effect. |
5 | 6th parameter data has been renamed to mic. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter scratch has been renamed to b_0. | No effect. |
2 | 3rd parameter data has been renamed to aad. | No effect. |
3 | 4th parameter data_len has been renamed to data. | No effect. |
4 | 5th parameter cdata has been renamed to data_len. | No effect. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to int. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter dma_mask has been renamed to max_addr. | No effect. |
Change | Effect | |
---|---|---|
1 | 3rd parameter upper has been renamed to dev_list. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter ns has been renamed to name. | No effect. |
2 | 3rd parameter name has been renamed to ns. | No effect. |
Change | Effect | |
---|---|---|
1 | 3rd parameter new_ns has been renamed to new_name. | No effect. |
2 | 4th parameter new_name has been renamed to new_ns. | No effect. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to bool. | 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 bool. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter ns has been renamed to name. | No effect. |
2 | 3rd parameter name has been renamed to ns. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to connector. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to connector. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter dev has been renamed to crtc. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter type has been renamed to index_key. | No effect. |
2 | 3rd parameter prealloc has been renamed to edit. | No effect. |
Change | Effect | |
---|---|---|
1 | 2nd parameter propagate has been renamed to how. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter linked_list_buffer has been renamed to resource_list. | No effect. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from void to int. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | No effect. |
Change | Effect | |
---|---|---|
1 | 1st parameter call has been renamed to file. | No effect. |