| Module Name | vmlinux |
|---|---|
| Version #1 | 3.2.52 |
| Version #2 | 3.4.69 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 748 |
|---|---|
| Total Source Files | 1374 |
| Total Objects | 1 |
| Total Symbols / Types | 15033 / 8463 |
| Verdict | Incompatible (50.3%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 727 |
| Removed Symbols | High | 316 |
| Problems with Data Types | High | 95 |
| Medium | 425 | |
| Low | 571 | |
| Problems with Symbols | High | 82 |
| Medium | 1688 | |
| Low | 127 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 14 |
| Change | Effect | |
|---|---|---|
| 1 | Field timer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field names 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 cr_magic 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_bsses 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 authtry_bsses 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 attach_task 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 can_attach_task 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 pre_attach 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 cl_path has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cl_inline_name 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 cl_server 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 force_encoder_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 initial_x 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 initial_y 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 connector_count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pitch has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field conn_limit 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 crtc_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_flags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field get_rx_csum 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 get_sg 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 get_tso 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 get_tx_csum 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 get_ufo 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 set_flags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field set_rx_csum 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 set_rx_ntuple has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field set_sg 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 set_tso 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 set_tx_csum 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 set_ufo 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 batchbuffer 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 bcs_acthd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field bcs_instdone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field bcs_ipehr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field bcs_ipeir has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field bcs_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field ringbuffer 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 vcs_acthd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field vcs_instdone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field vcs_ipehr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field vcs_ipeir has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 12 | Field vcs_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field agp_heap 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 sta_finish_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. |
| 2 | Field sta_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 sta_pending_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. |
| 4 | Field uapsd_max_sp_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. |
| 5 | Field uapsd_queues 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 wifi_wme_noack_test 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 work_skb_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field filter_ta 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 redirect_genid 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 ioprio_changed 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 radix_root 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 j_barrier 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 cpustat 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 memory_size 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 mmap_legacy_base has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_longterm 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 mnt_mountpoint 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 mnt_mounts 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 mnt_parent 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 mnt_pcp 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 mnt_hash has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field mnt_child 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 kmem_cachep 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 me 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 range_to_nlattr 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 ls_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 ls_sequence 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 sequence 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 nfs_page_tree 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 block_ucfg_access 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 fw_addr 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 has_fpu 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 balance_iterator 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 tasks 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 task_weight has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sched_switch 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 nohz_balance_kick 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 threadgroup_fork_lock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idx 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 dummy has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_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 parent 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 attached_by 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 root_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 list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field parent 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 name_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field md5_add 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 termios_locked 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 minor_num has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter 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 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 | 1st middle parameter task 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 ioc of type struct io_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 gfp_flags 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 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 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 | 1st middle parameter tsk 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 off 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 | Type of 1st parameter all has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Type of 3rd parameter mask has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | Type of 2nd parameter one has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 (2 bytes) to int (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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 (2 bytes) to int (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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 (2 bytes) to int (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. |
| 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 | 2nd middle parameter sizet 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 field_obj of type union acpi_operand_object* 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 sdata of type struct ieee80211_sub_if_data* 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 4th parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter last_pfx has been changed from insn_byte_t (1 byte) to int (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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter last_pfx has been changed from insn_byte_t (1 byte) to int (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. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter path of type struct path* 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 mnt has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter start has been changed from u64 (8 bytes) to phys_addr_t (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 | Type of 2nd parameter end has been changed from u64 (8 bytes) to phys_addr_t (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| 3 | Type of 3rd parameter size has been changed from u64 (8 bytes) to phys_addr_t (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| 4 | Type of 4th parameter align has been changed from u64 (8 bytes) to phys_addr_t (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. |
| 5 | The parameter align became passed at the different offset on the stack (0 instead of 16). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter task 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 dont_wait_for_ack of type bool has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sig_mbm 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 bss of type struct cfg80211_bss* 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 return value has been changed from int (4 bytes) to struct ctl_path[2] (8 bytes). | 1) The return value became passed in memory as the hidden first argument (address of the space on the stack provided by the caller) instead of the register and therefore the layout of parameter's stack has been shifted by 4 bytes. All the parameters will be incorrectly initialized by applications. 2) Applications will read the wrong memory block instead of the return value. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 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 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter neigh 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 client of type struct rpc_clnt* 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 client of type struct rpc_clnt* 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 sig_dbm 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 | Type of 4th parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter value has been changed from u32 (4 bytes) to u64 (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter min_level of type s16 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 anycast has been changed from int (4 bytes) to bool (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter 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 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 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter bss of type struct cfg80211_bss* 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 channel 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. |
| 3 | 3rd middle parameter bssid 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 2nd parameter idx 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 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 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 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 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 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 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 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 set of type struct ctl_table_set* 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 root 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. |
| 3 | 2nd middle parameter namespaces has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter da of type u8 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 name of type char 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 | The parameter key became passed at the different offset on the stack (12 instead of 0). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter lock_name became passed at the different offset on the stack (16 instead of 4). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field connection_node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field resource_buffer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field resource_length has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 ACPI_MADT_TYPE_RESERVED has been changed from 11 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_id_valid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member AUDIT_BUILD_CONTEXT has been changed from 2 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member AUDIT_RECORD_CONTEXT has been changed from 3 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field preallocated_names has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 names_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 principal has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pipe_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field deferred_probe has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex 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 interfaces 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 class_interfaces has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field class_mutex has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field icq_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 | 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 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field connect has been changed from 92 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field ibss has been changed from 36 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel_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 max_reg_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshHWMPperrMinInterval has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field ap_sme_capa 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 features 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 ht_capa_mod_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. |
| 5 | Field probe_resp_offload 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 ap_unexpected_nlpid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wext has been changed from 188 bytes to 252 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id_lock has been changed from struct rwlock_t (4 bytes) to spinlock_t (2 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_dentry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 ap_beacons_nlpid 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 sysdev 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 governor_data 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 states has been changed from 544 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. |
| 2 | Type of field name has been changed from char[16] (16 bytes) to char const* (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The pointer level of field name 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 disable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_root has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_name has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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 mmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 kdev has been changed from 216 bytes to 220 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 encoder_ids has been changed from uint32_t[2] (8 bytes) to uint32_t[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 | Size of field mode has been changed from 204 bytes to 200 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field hwmode has been changed from 204 bytes to 200 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field offsets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pitches has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pixel_format has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_plane has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field plane_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 mode_config has been changed from 300 bytes to 320 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_import has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 prime_fd_to_handle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gem_prime_export has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 prime_handle_to_fd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field fops has been changed from struct file_operations (104 bytes) to struct file_operations const* (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | The pointer level of field fops has been increased from 0 to 1. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kdev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed0 has been changed from 19 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field expires has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field hw has been changed from 256 bytes to 260 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ce4100_gbe_mdio_base_virt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 field boottime 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 query_variable_store 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 elevator_exit_icq_fn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field elevator_init_icq_fn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field trim 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 icq_align has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 icq_cache has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 icq_cache_name has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 icq_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field ops has been changed from 72 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | The relative position of field elevator_attrs has been changed from 2 to 1. | 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 elevator_name has been changed from 3 to 2. | 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 elevator_owner has been changed from 4 to 3. | 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 list has been changed from 0 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_rxfh_indir_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field open_fds_init has been changed from struct embedded_fd_set to unsigned long[1] of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field close_on_exec_init has been changed from struct embedded_fd_set to unsigned long[1] of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field daddr has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field saddr has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field bd_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fs_supers has been changed from struct list_head (8 bytes) to struct hlist_head (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_max_links 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 s_mounts 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 | Type of field s_instances has been changed from struct list_head to struct hlist_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field part0 has been changed from 288 bytes to 292 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field __dev has been changed from 216 bytes to 220 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 irq0_irqs has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field single_adc_amp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 config_collision_dist has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 reload has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 aliasing_ppgtt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_sprite_wm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cpu_ring_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cpu_ring_tail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 done_reg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field faddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field fault_reg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field ring has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 semaphore_mboxes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field tail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field acthd has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Type of field instdone has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 12 | Type of field instpm has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 13 | Type of field instps has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 14 | Type of field ipehr has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 15 | Type of field ipeir has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 16 | Type of field seqno has been changed from u32 (4 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 84 bytes to 92 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 tail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gmbus_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sprite_scaling_enabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field display has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field fence_regs has been changed from 256 bytes to 320 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field mm has been changed from 396 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Size of field ring has been changed from 648 bytes to 660 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 adapter has been changed from 352 bytes to 356 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 force_bit has been changed from struct i2c_adapter* (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_wq has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field idmap_im has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field idmap_lock has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | Field idmap_group_hash has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Field idmap_user_hash 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. |
| 6 | Field idmap_im_lock has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member IEEE80211_WORK_OFFCHANNEL_TX has been changed from 6 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member IEEE80211_WORK_REMAIN_ON_CHANNEL has been changed from 5 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_period 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 num_sta_authorized has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 probe_resp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel_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. |
| 2 | Field control_port has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 incomplete_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field incomplete_stations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 assoc_data has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field auth_data has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field uapsd_max_sp_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field uapsd_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_perr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mshcfg 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 | Field ack_status_frames has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ack_status_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field tim_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Size of field napi_dev has been changed from 960 bytes to 1088 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 noack_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 rc_rateidx_mcs_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. |
| 3 | Size of field u has been changed from 392 bytes to 460 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field wdev has been changed from 368 bytes to 404 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field vif has been changed from 128 bytes to 132 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 skbs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 data_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field unnamed0 has been changed from 68 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 3 | Field ie 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 assoc 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. |
| 2 | Field probe_auth has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ap has been changed from 292 bytes to 300 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field ibss has been changed from 148 bytes to 168 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 348 bytes to 356 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field mgd has been changed from 392 bytes to 460 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 icsk_inet has been changed from 536 bytes to 560 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 uc_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 | Size of field sk has been changed from 396 bytes to 416 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 760 bytes to 756 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 484 bytes to 476 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 helper has been changed from 124 bytes to 120 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 ifb has been changed from 64 bytes to 96 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 60 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pending has been changed from struct atomic_t to int of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_retired_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from int (4 bytes) to umode_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icq_hint has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field icq_tree has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ioc_data 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 sysctl_tcp_mem has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ucast_oif has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Field timer_rand_state 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 | Value of member KMSG_DUMP_EMERG has been changed from 6 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member KMSG_DUMP_OOPS has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member KMSG_DUMP_PANIC has been changed from 1 to 0. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field done_seq has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field queue_seq 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 tdev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field device has been changed from 2696 bytes to 2704 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field link has been changed from 3268 bytes to 3280 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field tdev has been changed from 216 bytes to 220 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field u has been changed from 48 bytes to 8 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field lsm_post_audit has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field lsm_pre_audit 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 | The pointer level of field net 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 | The pointer level of field selinux_audit_data 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 finish_tx_sync has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field tx_sync has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_idx_mcs_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field merge_check_needed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 memory has been changed from 12 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field total_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dirty_balance_reserve 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 lruvec 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 lru 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 mnt_devname has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field mnt_expire has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field mnt_fsnotify_marks has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | Field mnt_fsnotify_mask has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Field 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. |
| 6 | Field mnt_group_id 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. |
| 7 | Field mnt_id 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. |
| 8 | Field mnt_ns 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. |
| 9 | Field mnt_pinned 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. |
| 10 | Field mnt_slave_list 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. |
| 11 | Field mnt_expiry_mark 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. |
| 12 | Field mnt_list 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. |
| 13 | Field mnt_master 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. |
| 14 | Field mnt_share 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. |
| 15 | Field mnt_slave 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 hash_rnd has been changed from __u32 (4 bytes) to __u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_queue_len_bytes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sysctls has been changed from 16 bytes to 48 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field ipv4 has been changed from 156 bytes to 168 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field neigh_priv_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field pm_qos_req has been changed from 24 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Type of field hw_features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Type of field vlan_features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Type of field wanted_features has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field trans_timeout has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | The relative position of field _xmit_lock has been changed from 5 to 4. | 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 kobj has been changed from 4 to 3. | 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 xmit_lock_owner has been changed from 6 to 5. | 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 qdisc_sleeping has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field trans_start has been changed from 7 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field state has been changed from 2 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field module has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_timeouts has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ls_seqid has been changed from 12 bytes to 148 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 ls_stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field open_stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_expires 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 so_lru 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 so_sequence has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field so_owner_id 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 create_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field owner_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 commit_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 fc_slot_table has been changed from 168 bytes to 184 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 bc_slot_table has been changed from 168 bytes to 184 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field used_slots has been changed from unsigned long[4] (16 bytes) to unsigned long[8] (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 | Field state_owners_lru has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fh_expire_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. |
| 3 | Type of field openowner_id has been changed from struct rb_root (4 bytes) to struct ida (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. |
| 4 | Type of field lockowner_id has been changed from struct rb_root (4 bytes) to struct ida (24 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sa_slotid has been changed from u8 (1 byte) to u32 (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_owner has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field owner has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Type of field delegation has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| 4 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field args 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. |
| 2 | Size of field fattr has been changed from 144 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_args has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename_rpc_prepare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 write_rpc_prepare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 read_rpc_prepare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 unlink_rpc_prepare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 args has been changed from 48 bytes to 52 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 fattr has been changed from 144 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_args has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 block_cfg_access has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 msi_kset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field res_attr has been changed from struct bin_attribute*[12] (48 bytes) to struct bin_attribute*[11] (44 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 5 | Type of field res_attr_wc has been changed from struct bin_attribute*[12] (48 bytes) to struct bin_attribute*[11] (44 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 6 | Type of field resource has been changed from struct resource[12] (336 bytes) to struct resource[11] (308 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 216 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 latency_pm_qos_req has been changed from 24 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field event_constraints has been changed from 1792 bytes to 2048 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 br_sel has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lbr_sel has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 interrupts_seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field unnamed0 has been changed from 64 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field regs has been changed from struct er_account[2] (48 bytes) to struct er_account[3] (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 ctx has been changed from 136 bytes to 144 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 hw has been changed from 128 bytes to 144 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 attr has been changed from 72 bytes to 80 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_branch_stack has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field nr_freq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr_groups has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr_rdpmc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 events_mask_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field flush_branch_stack has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 format_attrs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lbr_sel_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. |
| 6 | Field lbr_sel_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. |
| 7 | Field unnamed0 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 ops has been changed from 68 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 | Field poweroff_late has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 restore_early has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field resume_early has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 suspend_late has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 thaw_early has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 freeze_late has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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_SUPPLY_PROP_MANUFACTURER has been changed from 41 to 42. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 40 to 41. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 42 to 43. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_SUPPLY_TYPE_BATTERY has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_TYPE_MAINS has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_TYPE_UPS has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member POWER_SUPPLY_TYPE_USB has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member POWER_SUPPLY_TYPE_USB_ACA has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member POWER_SUPPLY_TYPE_USB_CDP has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member POWER_SUPPLY_TYPE_USB_DCP has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field power has been changed from 868 bytes to 864 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 272 bytes to 268 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 has_fpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_cpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fpu has been changed from 4 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref 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 resched_ipi has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dynticks_nesting has been changed from int (4 bytes) to long long (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_region has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 nohz_flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cfs_tasks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field cfs has been changed from 148 bytes to 132 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rpc_count_stats has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tk_pid 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 is_child_subreaper has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 group_rwsem has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 128 bytes to 132 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field irqaction 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 skip_vpd_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 | Size of field sdev_dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field sdev_gendev has been changed from 216 bytes to 220 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 pdt_1f_for_no_lun has been changed from 4 bytes to 1 bit. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field shost_dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field shost_gendev has been changed from 216 bytes to 220 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 netlink_recv has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field l4_rxhash has been changed from 35 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field ndisc_nodetype has been changed from 33 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field ooo_okay has been changed from 34 to 35. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field queue_mapping has been changed from 32 to 33. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field rxhash has been changed from 31 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field secmark has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field tc_index has been changed from 29 to 31. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field tc_verd has been changed from 30 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field unnamed1 has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field vlan_tci has been changed from 38 to 30. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field params has been changed from 92 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[83] (332 bytes) to unsigned long[84] (336 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_peek_off has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sk_cgrp_prioidx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sk_cgrp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Type of field sk_route_nocaps has been changed from int (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Type of field sk_route_caps has been changed from int (4 bytes) to netdev_features_t (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_addba_req_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_loss_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. |
| 2 | Field sta_state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field ampdu_mlme has been changed from 256 bytes to 320 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field session_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field failed_resume_early has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 failed_suspend_late has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 unnamed0 has been changed from 20 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field parent has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field default_set has been changed from 16 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_hash has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 s_flags has been changed from unsigned int (4 bytes) to unsigned short (2 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field unnamed0 has been changed from 16 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field name_tree 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 s_dir has been changed from 16 bytes to 12 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 alloced4 has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field alloced6 has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field entries4 has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | Field entries6 has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Field keys6 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 addr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 family has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Type of field key has been changed from u8* (4 bytes) to u8[80] (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. |
| 5 | The relative position of field key has been changed from 0 to 1. | 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 800 bytes to 824 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 216 bytes to 220 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 sig_on_uaccess_error 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 field has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 buffer_disabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 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 children has been changed from struct usb_device*[31] (124 bytes) to struct usb_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. |
| 3 | The pointer level of field children has been increased from 1 to 2. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 bytes to 220 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 216 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[49] (196 bytes) to unsigned long[52] (208 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_slots has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 servername has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 stat has been changed from 44 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field servername has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 parameter iir 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 port 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 140 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] (4 bytes) to char const*[34] (136 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] (4 bytes) to char const*[14] (56 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] (4 bytes) to char const*[29] (116 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] (4 bytes) to char const*[10] (40 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] (4 bytes) to char const*[6] (24 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_opcode_info[127] const (2032 bytes) to struct acpi_opcode_info[129] const (2064 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2032 bytes to 2064 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32 (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[8] (32 bytes) to char const*[10] (40 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 244 bytes to 268 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u8[17] const (17 bytes) to u8[] const (4 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 17 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_rsconvert_info*[28] (112 bytes) to struct acpi_rsconvert_info*[31] (124 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u8[28] const (28 bytes) to u8[] const (4 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 28 bytes to 30 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_rsconvert_info*[17] (68 bytes) to struct acpi_rsconvert_info*[20] (80 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 31 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sllao of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fops 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 name 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 priv 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 188 bytes to 192 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 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 320 bytes to 316 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter service_name of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter node has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from struct io_context* (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ioc became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter max_hw_sectors 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 q became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bdev 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 260 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 140 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 140 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 140 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 140 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter hd became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter partno became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flavor of type rpc_authflavor_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clp became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 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 governor 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 became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry 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 name became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type fmode_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Base type of parameter dst has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | This parameter may be incorrectly initialized by applications. |
| 3 | 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 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | This parameter may be incorrectly initialized by 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 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Applications will obtain a different return value and execution may change. |
| 2 | The parameter mask 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 one 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 | Type of return value has been changed from u32 (4 bytes) to netdev_features_t (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dst 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 in_dev 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 local 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drv became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| 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 group 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 2nd parameter mode_cmd has been changed from struct drm_mode_fb_cmd (28 bytes) to struct drm_mode_fb_cmd2 (68 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter n 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 panic_str 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 ununsed 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 master became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 212 bytes to 164 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ctx 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 fmt 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 insert became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter frag_offp of type __be16* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter func became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter 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 | 2nd parameter sig_only has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gov 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 gm 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter host 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 net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter kt 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 flags of type u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u8 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 672 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter obj 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 do_retire of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter do_retire of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id 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 idp 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 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dentry has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter mode_cmd has been changed from struct drm_mode_fb_cmd (28 bytes) to struct drm_mode_fb_cmd2 (68 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct intel_quirk[16] (256 bytes) to struct intel_quirk[11] (176 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 256 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 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 pipe 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 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nr 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 port 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 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter address has been changed from struct sockaddr (16 bytes) to struct __kernel_sockaddr_storage (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 124 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter k 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 host 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 host 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 mesg 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 | Type of this global data has been changed from unsigned int to struct atomic_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pre_audit of type void(*)(struct audit_buffer*, void*) has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter post_audit of type void(*)(struct audit_buffer*, void*) has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter pfn 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 vector 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 end 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 size became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from u64 (8 bytes) to phys_addr_t (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pool became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter assoc_flags of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter ht_capa of type struct ieee80211_ht_cap* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter ht_capa_mask of type struct ieee80211_ht_cap* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 13th parameter local_state_change has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter assoc_flags of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter ht_capa of type struct ieee80211_ht_cap* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter ht_capa_mask of type struct ieee80211_ht_cap* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 13th parameter local_state_change has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gfp became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rssi_event 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 vif 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 cookie has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cookie has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mm 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 address 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 vma 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 | 1st parameter name has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 3rd parameter path has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dir became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mode became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of return value has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mnt has been changed from struct vfsmount (132 bytes) to struct dentry (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mnt became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mnt became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter child_mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 320 bytes to 316 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter adapter has been changed from struct e1000_adapter (1972 bytes) to struct e1000_ring (80 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter adapter has been changed from struct e1000_adapter (1972 bytes) to struct e1000_ring (80 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter adapter has been changed from struct e1000_adapter (1972 bytes) to struct e1000_ring (80 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter adapter has been changed from struct e1000_adapter (1972 bytes) to struct e1000_ring (80 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 40 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 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 48 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 16 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | 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 | The parameter l3proto 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 l4proto 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 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter status 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 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter lsp has been changed from struct nfs4_lock_state const* to struct nfs4_lock_state* (became non-const). | This function may change parameter lsp, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_flags of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter enable_beaconing has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter value has been changed from unsigned int (4 bytes) to unsigned long long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter width became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nid 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 range_end_pfn 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 range_start_pfn 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 req 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 max_level of type s16 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter attrs of type struct dma_attrs* 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 68 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 2056 bytes to 2312 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 3044 bytes to 3056 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct jump_label_key to struct static_key_deferred of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 68 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dest_mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 3rd parameter source_mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mnt has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 272 bytes to 276 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 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 129 bytes to 130 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter node became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter old became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter root 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 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 576 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter calling_module 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 first_index became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter results 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 root 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 first_index became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter results 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 root 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 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter counter 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 val 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 page became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter addr has been changed from struct in6_addr (16 bytes) to struct flowi6 (60 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter inode has been changed from struct inode (332 bytes) to struct rpc_pipe (120 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ops 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 | 2nd parameter out has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nr of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter cls has been changed from struct sysdev_class (68 bytes) to struct device (220 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter cred has been changed from struct cred (112 bytes) to struct user_namespace (536 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter ns has been changed from struct user_namespace (536 bytes) to struct cred (112 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter realloc_head has been changed from struct resource_list_x (32 bytes) to struct list_head (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter flags 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 tsk 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 truesize 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 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 | Parameter use_effective of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter kaddr has been changed from struct sockaddr (16 bytes) to struct __kernel_sockaddr_storage (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sock 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 stats of type struct rpc_iostats* 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 140 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter page 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 | Base type of 2nd parameter parent has been changed from struct ctl_table_set (16 bytes) to struct ctl_table_root (56 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sysdev has been changed from struct sys_device (44 bytes) to struct device (220 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sysdev has been changed from struct sys_device (44 bytes) to struct device (220 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 76 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 52 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 844 bytes to 868 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 168 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 488 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 624 bytes to 628 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 88 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 248 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 76 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 188 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 44 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 12 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 12 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 212 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 412 bytes to 444 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 396 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 856 bytes to 908 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 204 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 1388 bytes to 1376 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 388 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 288 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 436 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 1116 bytes to 1128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 148 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 76 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1616 bytes to 644 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 128 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 528 bytes to 552 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 52 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 132 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter entry 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 s became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter first_ok 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 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 68 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter rate 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 bss_notify 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 196 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[78] const (312 bytes) to char const*[81] const (324 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 312 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter flags became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter max_active 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 name became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xid 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 xprt 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 type has been changed from 76 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field active has been changed from int volatile to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field needcheck has been changed from int volatile 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 32 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field access_length 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 access_length 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 access_length 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 access_length 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 access_length 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 resource_buffer 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field access_length has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field resource_length 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 field field has been changed from 36 bytes to 40 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus has been renamed to resources. | 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 772 bytes to 776 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field common_serial_bus has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field fixed_dma has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field gpio has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field i2c_serial_bus 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. |
| 5 | Field spi_serial_bus 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. |
| 6 | Field uart_serial_bus 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 sleep_control 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 sleep_status 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 244 bytes to 268 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from unsigned long to __kernel_ulong_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field common_serial_bus has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field fixed_dma has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field gpio has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field i2c_serial_bus 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. |
| 5 | Field spi_serial_bus 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. |
| 6 | Field uart_serial_bus has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 188 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The member AUDIT_SETUP_CONTEXT has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field perm_mode has been changed from mode_t to umode_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field mode has been changed from mode_t to umode_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_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 1616 bytes to 644 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 pipes_create 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 pipes_destroy has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 28 bytes to 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 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 104 bytes to 124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 296 bytes to 300 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 76 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcomm 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 200 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 | Size of this type has been changed from 1116 bytes to 1128 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 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 field hdr has been changed from 103 bytes to 115 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field init_size has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field pref_address 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 103 bytes to 115 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net 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 116 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net 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. |
| 3 | Type of field slotid has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field keeplocked 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 188 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 | Field flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field ht_capa 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 ht_capa_mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 72 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 bg_scan_period 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 flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field ht_capa_mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field ht_capa 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 92 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 | Field bss has been renamed to bssid. | 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field control_port 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 get_channel 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 probe_client 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 set_noack_map 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 260 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field deauth has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_deauth_request*, void*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_deauth_request*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field disassoc has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_disassoc_request*, void*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_disassoc_request*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, u64*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, bool, u64*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Field add_beacon has been renamed to start_ap. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 9 | Field del_beacon has been renamed to stop_ap. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 10 | Field set_beacon has been renamed to change_beacon. | 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field parse_error 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 dot11MeshForwarding has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field rssi_threshold 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 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcast_rate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 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 beacon_loss_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 404 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_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 140 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field bind has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field can_attach has been changed from int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*) to int(*)(struct cgroup*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field cancel_attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field create has been changed from struct cgroup_subsys_state*(*)(struct cgroup_subsys*, struct cgroup*) to struct cgroup_subsys_state*(*)(struct cgroup*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field destroy has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field exit has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field fork has been changed from void(*)(struct cgroup_subsys*, struct task_struct*) to void(*)(struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 10 | Base type of field post_clone has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 11 | Base type of field pre_destroy has been changed from int(*)(struct cgroup_subsys*, struct cgroup*) to int(*)(struct cgroup*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cl_protname became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Field cl_program became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Type of field cl_program has been changed from struct rpc_program* to struct rpc_program const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field cl_protname has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field program became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field servername became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Type of field program has been changed from struct rpc_program* to struct rpc_program const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field servername has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field p_name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field p_name has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field version became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Field pipe_dir_name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Type of field version has been changed from struct rpc_version** to struct rpc_version const**. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field pipe_dir_name has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field name has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field name has been changed from unsigned char* to unsigned char 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 392 bytes to 396 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev 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 52 bytes to 228 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 268 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 576 bytes to 628 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field en_core_tk_irqen 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 name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field enter_dead 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 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field power_usage 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. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(struct dm_target*, status_type_t, char*, unsigned int) to int(*)(struct dm_target*, status_type_t, char*, unsigned int). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 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 | Base type of field devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field alloc_coherent has been renamed to alloc. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field free_coherent has been renamed to free. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 760 bytes to 756 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 484 bytes to 476 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 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field type 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 60 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 | Field preferred_depth 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 prefer_shadow 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 300 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field fb_create has been changed from struct drm_framebuffer*(*)(struct drm_device*, struct drm_file*, struct drm_mode_fb_cmd*) to struct drm_framebuffer*(*)(struct drm_device*, struct drm_file*, struct drm_mode_fb_cmd2*). | 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 24 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field data has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | Type of field data has been changed from void* to unsigned char[]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 44 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unplugged 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 912 bytes to 936 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 324 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field fops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prime 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 108 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 export_dma_buf 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 import_attach has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 84 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 316 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 336 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 rt6_next has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 2 | Field dn_next has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 3 | Field rt_next has been renamed to from. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field next has been renamed to expires. | 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 1972 bytes to 1976 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field dump_buffers 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 256 bytes to 260 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field boottime has been changed from unsigned long to efi_boot_services_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 16 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 76 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ops has been renamed to type. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 228 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 164 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_rxfh_indir has been changed from int(*)(struct net_device*, struct ethtool_rxfh_indir*) to int(*)(struct net_device*, u32*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field set_rxfh_indir has been changed from int(*)(struct net_device*, struct ethtool_rxfh_indir const*) to int(*)(struct net_device*, u32 const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field capabilities 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 colorspace has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field open_fds has been changed from struct __kernel_fd_set (128 bytes) to unsigned long (4 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Base type of field close_on_exec has been changed from struct __kernel_fd_set (128 bytes) to unsigned long (4 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field mknod has been changed from int(*)(struct inode*, struct dentry*, int, dev_t) to int(*)(struct inode*, struct dentry*, umode_t, dev_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, int, struct nameidata*) to int(*)(struct inode*, struct dentry*, umode_t, struct nameidata*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field mkdir has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_readonly_remount 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 s_remove_count has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show_stats has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field show_options has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field show_devname has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field show_path has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field reg has been changed from int(*)(struct ftrace_event_call*, enum trace_reg) to int(*)(struct ftrace_event_call*, enum trace_reg, void*). | 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 388 bytes to 392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field devnode has been changed from char*(*)(struct gendisk*, mode_t*) to char*(*)(struct gendisk*, umode_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 292 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icr_read_retry_count has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field irq 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 | Field jacktbl 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 688 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 3756 bytes to 3760 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 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 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 352 bytes to 356 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 260 bytes to 264 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 396 bytes to 400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 428 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 208 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field has_aliasing_ppgtt_mapping has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 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 5108 bytes to 5212 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_llc 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 bit_algo 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 gpio_reg 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 dev_priv 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. |
| 4 | Size of this type has been changed from 360 bytes to 408 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field has_gpio has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | The pointer level of field force_bit has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_key_cons 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 idmap_mutex has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 212 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field idmap_dentry has been renamed to idmap_pipe. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_WORK_ASSOC has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 2 | The member IEEE80211_WORK_ASSOC_BEACON_WAIT has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 3 | The member IEEE80211_WORK_AUTH has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 4 | The member IEEE80211_WORK_DIRECT_PROBE has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 3 has been changed from SCAN_LEAVE_OPER_CHANNEL to SCAN_SUSPEND. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 4 has been changed from SCAN_ENTER_OPER_CHANNEL to SCAN_RESUME. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field corrupt_data 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 valid_data 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 292 bytes to 300 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 148 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 ht_capa 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 ht_capa_mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 392 bytes to 460 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 348 bytes to 356 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 3392 bytes to 3520 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 1268 bytes to 1400 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 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 120 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ie_len has been renamed to 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 68 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 392 bytes to 460 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 800 bytes to 824 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 536 bytes to 560 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcv_tos has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_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 672 bytes to 676 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt 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 scratch_page_dma 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 16 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 764 bytes to 760 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1364 bytes to 1356 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 228 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 1 has been changed from RING_RENDER to VCS. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 2 has been changed from RING_BSD to BCS. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | The member RING_BLT has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 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 net 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 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net 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 380 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field release_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 44 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field cic_list has been renamed to icq_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field init_netns has been changed from void(*)(struct net*, struct ip_vs_proto_data*) to int(*)(struct net*, struct ip_vs_proto_data*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_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 156 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcv_tclass 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 336 bytes to 316 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field bufferram has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field freehigh has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field freeram has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field freeswap has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field loads has been changed from unsigned long[3] to __kernel_ulong_t[3]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field mem_unit has been changed from unsigned int to __u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field procs has been changed from unsigned short to __u16. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field sharedram has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field totalhigh has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field totalram has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 11 | Type of field totalswap has been changed from unsigned long to __kernel_ulong_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 12 | Type of field uptime has been changed from long to __kernel_long_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_class 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 | Type of field wait has been changed from enum umh_wait to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_KEXEC has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field flushing has been renamed to worker. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_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 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 1348 bytes to 1352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3268 bytes to 3280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net 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 396 bytes to 400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 100 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 36 bytes to 4 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 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 timestamp has been renamed to last_tsf. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sta_state 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 tx_frags 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 | Reserved field pad has been replaced by ack_frame_id. | This field will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 128 bytes to 132 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 attr has been changed from struct sysdev_attribute to struct device_attribute. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hot_remove_disk has been changed from int(*)(struct mddev*, int) to int(*)(struct mddev*, struct md_rdev*). | 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 688 bytes to 692 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field reserved has been changed from 12 bytes to 16 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field nid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Base type of field icmpmsg_statistics has been changed from struct icmpmsg_mib* (4 bytes) to struct icmpmsg_mib (2048 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Base type of field icmpv6msg_statistics has been changed from struct icmpv6msg_mib* (4 bytes) to struct icmpv6msg_mib (2048 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | The pointer level of field icmpv6msg_statistics 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 icmpmsg_statistics 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 | Type of field mode has been changed from mode_t to umode_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 436 bytes to 432 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 root has been changed from struct vfsmount (132 bytes) to struct mount (140 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field incs has been changed from unsigned int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field decs has been changed from unsigned int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been renamed to level. | 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 132 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj 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 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 20 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 queue_len has been renamed to queue_len_bytes. | 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 320 bytes to 316 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field hash has been changed from __u32(*)(void const*, struct net_device const*, __u32) to __u32(*)(void const*, struct net_device const*, __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 276 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_peek_off 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 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 960 bytes to 1088 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_neigh_construct 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_neigh_destroy 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 140 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Base type of field ndo_fix_features has been changed from u32(*)(struct net_device*, u32) to netdev_features_t(*)(struct net_device*, netdev_features_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field ndo_set_features has been changed from int(*)(struct net_device*, u32) to int(*)(struct net_device*, netdev_features_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field ndo_vlan_rx_add_vid has been changed from void(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, unsigned short). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field ndo_vlan_rx_kill_vid has been changed from void(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, unsigned short). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dql 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 128 bytes to 256 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 52 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 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field new has been changed from bool(*)(struct nf_conn*, struct sk_buff const*, unsigned int) to bool(*)(struct nf_conn*, struct sk_buff const*, unsigned int, unsigned int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field packet has been changed from int(*)(struct nf_conn*, struct sk_buff const*, unsigned int, enum ip_conntrack_info, u_int8_t, unsigned int) to int(*)(struct nf_conn*, struct sk_buff const*, unsigned int, enum ip_conntrack_info, u_int8_t, unsigned int, unsigned int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 0 has been changed from IP_NAT_MANIP_SRC to NF_NAT_MANIP_SRC. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 1 has been changed from IP_NAT_MANIP_DST to NF_NAT_MANIP_DST. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field nlattr_to_range has been changed from int(*)(struct nlattr**, struct nf_nat_range*) to int(*)(struct nlattr**, struct nf_nat_ipv4_range*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field unique_tuple has been changed from void(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*) to void(*)(struct nf_conntrack_tuple*, struct nf_nat_ipv4_range const*, enum nf_nat_manip_type, struct nf_conn const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 204 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field validate_stateid has been renamed to match_stateid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field so_seqid has been changed from 12 bytes to 148 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field task has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| 2 | Field lock has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field wait has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 12 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 628 bytes to 624 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 412 bytes to 444 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 168 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field max_slots has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field target_max_slots has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field highest_used_slotid has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field net 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 impl_id 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 488 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 856 bytes to 908 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been renamed to wb_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 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_name 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 owner_name 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 144 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 256 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 436 bytes to 448 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 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 464 bytes to 476 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 372 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 900 bytes to 824 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 232 bytes to 236 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 332 bytes to 336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field list became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field list has been changed from unsigned int* to unsigned int 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 240 bytes to 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2056 bytes to 2312 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field branch_reg 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 52 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 3044 bytes to 3056 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field overlap 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 128 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 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 predicted 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 flags has been renamed to mispred. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 176 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 552 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field branch_sample_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 72 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 136 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field br_stack has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_idx 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 flush_branch_stack has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 76 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field quirks has been changed from void(*)() (4 bytes) to struct x86_pmu_quirk (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 52 bytes to 72 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 420 bytes to 424 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 412 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hide_pid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field reboot 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 pid_gid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 40 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 240 bytes to 244 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 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 68 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 | Field 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 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field name has been changed from char* to char 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 316 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 376 bytes to 380 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 276 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 long to __kernel_long_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from unsigned long to __kernel_ulong_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_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 1104 bytes to 1100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field need_hotplug_init 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 868 bytes to 864 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 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field trap_no has been renamed to trap_nr. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field write has been changed from int(*)(enum pstore_type_id, u64*, unsigned int, size_t, struct pstore_info*) to int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, size_t, struct pstore_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head 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 16 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field qlen_lazy 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 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field signaled has been renamed to fqs_state. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_region has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field create_buf_file has been changed from struct dentry*(*)(char const*, struct dentry*, int, struct rchan_buf*, int*) to struct dentry*(*)(char const*, struct dentry*, umode_t, struct rchan_buf*, 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 548 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 148 bytes to 132 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 1388 bytes to 1376 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_update 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 nr_busy_cpus 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 624 bytes to 628 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field has_child_subreaper 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 irq_thread 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 dirty_paused_when 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 try_rc_10_first 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 656 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 | 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 field dev has been changed from 216 bytes to 220 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field no_report_luns 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 eh_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 | Size of this type has been changed from 68 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 692 bytes to 700 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field eh_noresume 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 task_free has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Base type of field capable has been changed from int(*)(struct task_struct*, struct cred const*, struct user_namespace*, int, int) to int(*)(struct cred const*, struct user_namespace*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field inode_create has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field inode_mkdir has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field inode_mknod has been changed from int(*)(struct inode*, struct dentry*, int, dev_t) to int(*)(struct inode*, struct dentry*, umode_t, dev_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 372 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_fcs 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 wifi_acked 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 wifi_acked_valid has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 180 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 332 bytes to 336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 396 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 552 bytes to 556 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 696 bytes to 764 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field program became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field program has been changed from struct rpc_program* to struct rpc_program const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member SUSPEND_RESUME has been changed from 6 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member SUSPEND_RESUME_NOIRQ has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member SUSPEND_SUSPEND_NOIRQ has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 140 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 | Base type of field sv_shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field nreg 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 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 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field mode has been changed from mode_t to umode_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 48 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field parent has been changed from struct ctl_table_header (48 bytes) to struct ctl_dir (44 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field attached_to has been renamed to node. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 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 20 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 20 bytes to 16 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from mode_t to umode_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field is_visible has been changed from mode_t(*)(struct kobject*, struct attribute*, int) to umode_t(*)(struct kobject*, struct attribute*, 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 80 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field s_ino has been changed from ino_t to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field s_mode has been changed from unsigned short to umode_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field inode_node has been renamed to s_rb. | 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 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field inode_tree has been renamed to children. | 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 12 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 24 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field keys4 has been renamed to head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 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 8 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | The pointer level of field key 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 1236 bytes to 1260 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 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 260 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 404 bytes to 408 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 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field key has been changed from struct jump_label_key to struct static_key. | 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 188 bytes to 180 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 devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field removable 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 672 bytes to 560 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | The pointer level of field children 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 268 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 228 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 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 88 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field name has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | Type of field name has been changed from char const* to char[]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_percpu_clock_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 fixup_cpu_id 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 4 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore_msi_irqs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore_sched_clock_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 save_sched_clock_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 | Size of this type has been changed from 36 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sending_u 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 pending_u 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 44 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 844 bytes to 868 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter umode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter program has been changed from struct rpc_program* to struct rpc_program const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t* to umode_t*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter seq has been renamed to seqp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter name has been changed from struct qstr* to struct qstr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 1st parameter parent has been changed from struct dentry* to struct dentry 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 int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from struct drm_display_mode* to struct drm_display_mode const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter startt has been renamed to size. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter region_space has been renamed to space_id. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter amode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 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 uid has been renamed to gid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter uid has been renamed to gid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter last_pfx has been renamed to lpfx_id. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter last_pfx has been renamed to lpfx_id. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32 to __be32. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter wait has been changed from enum umh_wait to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter res has been renamed to p. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Replacement of data type may indicate a change in 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 this global data has been changed from char const*[4] to char const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[9] to char const*[9] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[2] to char const*[2] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter memory_limit has been renamed to limit. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mnt has been renamed to root. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to rx_ring. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to tx_ring. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to rx_ring. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to tx_ring. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from union nfs4_stateid to struct nfs_stateid4. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter lsp has been changed from struct nfs4_lock_state const* to struct nfs4_lock_state*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 5th parameter maxlen has been renamed to maxout. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter maxlen has been renamed to maxout. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 5th parameter maxlen has been renamed to maxout. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mem has been renamed to memcg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter list has been changed from unsigned int* to unsigned int const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct jump_label_key[9] to struct static_key[9]. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter pdevinfo has been changed from struct platform_device_info* to struct platform_device_info const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mem_cont has been renamed to memcg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter addr has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter umode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been renamed to pipe. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter timestamp has been renamed to tsf. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cls has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ns has been renamed to cred. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter cred has been renamed to ns. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter timeout_msecs has been changed from long to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter esc has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter p has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter esc has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter esc has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter esc has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 3rd parameter root has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter idx has been renamed to bss. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter idx has been changed from int to struct cfg80211_internal_bss*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr 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 task has been changed from struct rpc_task* to struct rpc_task const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to set. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter parent has been renamed to root. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sysdev has been renamed to cpu_dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sysdev has been renamed to cpu_dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter real has been renamed to offs_real. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter boot has been renamed to offs_boot. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from mode_t to umode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to fmt. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field active became non-volatile. | No effect. |
| 2 | Field needcheck became non-volatile. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR with value 12 has been added. | No effect. |
| 2 | The member ACPI_MADT_TYPE_GENERIC_INTERRUPT with value 11 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member TRACE_REG_PERF_ADD with value 6 has been added. | No effect. |
| 2 | The member TRACE_REG_PERF_CLOSE with value 5 has been added. | No effect. |
| 3 | The member TRACE_REG_PERF_DEL with value 7 has been added. | No effect. |
| 4 | The member TRACE_REG_PERF_OPEN with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member RCS with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_SCOPE with value 40 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_TYPE_UNKNOWN with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SUSPEND_RESUME_EARLY with value 7 has been added. | No effect. |
| 2 | The member SUSPEND_SUSPEND_LATE with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.2.52 |
| Version #2 | 3.4.69 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 748 |
|---|---|
| Total Source Files | 1374 |
| Total Objects | 1 |
| Total Symbols / Types | 15054 / 8467 |
| Verdict | Incompatible (50.1%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 729 |
| Removed Symbols | High | 317 |
| Problems with Data Types | High | 194 |
| Medium | 55 | |
| Low | 392 | |
| Problems with Symbols | High | 42 |
| Medium | 105 | |
| Low | 93 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 73 |
| Other Changes in Symbols | - | 48 |
| Change | Effect | |
|---|---|---|
| 1 | Field timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bsd_acct_struct' has no member named 'timer'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus has been renamed to resources. | Recompilation of a client program may be broken with the error message: struct pci_root_info has no member named bus. |
| Change | Effect | |
|---|---|---|
| 1 | The member AUDIT_SETUP_CONTEXT has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field names has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_context' has no member named 'names'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_magic has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_cred' has no member named 'cr_magic'. |
| Change | Effect | |
|---|---|---|
| 1 | Field class_interfaces has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct subsys_private' has no member named 'class_interfaces'. |
| 2 | Field class_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct subsys_private' has no member named 'class_mutex'. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_auth_request' has no member named 'local_state_change'. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_deauth_request' has no member named 'local_state_change'. |
| 2 | Field bss has been renamed to bssid. | Recompilation of a client program may be broken with the error message: struct cfg80211_deauth_request has no member named bss. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_beacon has been renamed to start_ap. | Recompilation of a client program may be broken with the error message: struct cfg80211_ops has no member named add_beacon. |
| 2 | Field del_beacon has been renamed to stop_ap. | Recompilation of a client program may be broken with the error message: struct cfg80211_ops has no member named del_beacon. |
| 3 | Field set_beacon has been renamed to change_beacon. | Recompilation of a client program may be broken with the error message: struct cfg80211_ops has no member named set_beacon. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_bsses has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'auth_bsses'. |
| 2 | Field authtry_bsses has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'authtry_bsses'. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_task 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 'attach_task'. |
| 2 | Field can_attach_task 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 'can_attach_task'. |
| 3 | Field pre_attach 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 'pre_attach'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_server has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_clnt' has no member named 'cl_server'. |
| 2 | Field cl_inline_name has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_clnt' has no member named 'cl_inline_name'. |
| 3 | Field cl_path has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_clnt' has no member named 'cl_path'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysdev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpu' has no member named 'sysdev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field governor_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_device' has no member named 'governor_data'. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_coherent has been renamed to alloc. | Recompilation of a client program may be broken with the error message: struct dma_map_ops has no member named alloc_coherent. |
| 2 | Field free_coherent has been renamed to free. | Recompilation of a client program may be broken with the error message: struct dma_map_ops has no member named free_coherent. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_encoder_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'force_encoder_id'. |
| 2 | Field initial_x has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'initial_x'. |
| 3 | Field initial_y has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'initial_y'. |
| Change | Effect | |
|---|---|---|
| 1 | Field connector_count 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 'connector_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pitch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_framebuffer' has no member named 'pitch'. |
| Change | Effect | |
|---|---|---|
| 1 | Field conn_limit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_fb_helper' has no member named 'conn_limit'. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_fb_helper_crtc' has no member named 'crtc_id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field expires has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dst_entry' has no member named 'expires'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt6_next has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field dn_next has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field next has been renamed to expires. | Recompilation of a client program may be broken with the error message: anon-union-dst.h-84 has no member named next. |
| 4 | Field rt_next has been renamed to from. | Recompilation of a client program may be broken with the error message: anon-union-dst.h-84 has no member named rt_next. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_variable_store has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct efivar_operations' has no member named 'query_variable_store'. |
| Change | Effect | |
|---|---|---|
| 1 | Field trim has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct elevator_ops' has no member named 'trim'. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct elevator_queue' has no member named 'elevator_type'. |
| 2 | Field ops has been renamed to type. | Recompilation of a client program may be broken with the error message: struct elevator_queue has no member named ops. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_rx_csum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_rx_csum'. |
| 2 | Field set_flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_flags'. |
| 3 | Field get_ufo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_ufo'. |
| 4 | Field get_tx_csum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_tx_csum'. |
| 5 | Field set_tx_csum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_tx_csum'. |
| 6 | Field set_sg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_sg'. |
| 7 | Field set_ufo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_ufo'. |
| 8 | Field get_flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_flags'. |
| 9 | Field set_rx_ntuple has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_rx_ntuple'. |
| 10 | Field get_sg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_sg'. |
| 11 | Field set_tso has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'set_tso'. |
| 12 | Field get_tso has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_tso'. |
| 13 | Field get_rx_csum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ethtool_ops' has no member named 'get_rx_csum'. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq0_irqs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_cpustat_t' has no member named 'irq0_irqs'. |
| Change | Effect | |
|---|---|---|
| 1 | Field batchbuffer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'batchbuffer'. |
| 2 | Field bcs_acthd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bcs_acthd'. |
| 3 | Field bcs_instdone has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bcs_instdone'. |
| 4 | Field bcs_ipehr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bcs_ipehr'. |
| 5 | Field bcs_ipeir has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bcs_ipeir'. |
| 6 | Field bcs_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'bcs_seqno'. |
| 7 | Field ringbuffer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'ringbuffer'. |
| 8 | Field vcs_acthd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'vcs_acthd'. |
| 9 | Field vcs_instdone has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'vcs_instdone'. |
| 10 | Field vcs_ipehr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'vcs_ipehr'. |
| 11 | Field vcs_ipeir has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'vcs_ipeir'. |
| 12 | Field vcs_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'vcs_seqno'. |
| Change | Effect | |
|---|---|---|
| 1 | Field agp_heap 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 'agp_heap'. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_group_hash has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_group_hash'. |
| 2 | Field idmap_im has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_im'. |
| 3 | Field idmap_im_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_im_lock'. |
| 4 | Field idmap_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_lock'. |
| 5 | Field idmap_user_hash has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_user_hash'. |
| 6 | Field idmap_wq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idmap' has no member named 'idmap_wq'. |
| 7 | Field idmap_dentry has been renamed to idmap_pipe. | Recompilation of a client program may be broken with the error message: struct idmap has no member named idmap_dentry. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_WORK_ASSOC has been removed. | Recompilation of a client program may be broken. |
| 2 | The member IEEE80211_WORK_ASSOC_BEACON_WAIT has been removed. | Recompilation of a client program may be broken. |
| 3 | The member IEEE80211_WORK_AUTH has been removed. | Recompilation of a client program may be broken. |
| 4 | The member IEEE80211_WORK_DIRECT_PROBE has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 3 has been changed from SCAN_LEAVE_OPER_CHANNEL to SCAN_SUSPEND. | Recompilation of a client program may be broken with the error message: 'SCAN_LEAVE_OPER_CHANNEL' was not declared in this scope. |
| 2 | Name of member with value 4 has been changed from SCAN_ENTER_OPER_CHANNEL to SCAN_RESUME. | Recompilation of a client program may be broken with the error message: 'SCAN_ENTER_OPER_CHANNEL' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_period has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct beacon_data' has no member named 'dtim_period'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sta_finish_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'sta_finish_work'. |
| 2 | Field sta_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'sta_lock'. |
| 3 | Field sta_pending_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'sta_pending_list'. |
| 4 | Field uapsd_max_sp_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'uapsd_max_sp_len'. |
| 5 | Field uapsd_queues has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'uapsd_queues'. |
| 6 | Field wifi_wme_noack_test has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'wifi_wme_noack_test'. |
| 7 | Field work_skb_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'work_skb_queue'. |
| Change | Effect | |
|---|---|---|
| 1 | Field filter_ta has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_work' has no member named 'filter_ta'. |
| 2 | Field ie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_work' has no member named 'ie'. |
| 3 | Field ie_len has been renamed to data. | Recompilation of a client program may be broken with the error message: struct ieee80211_work has no member named ie_len. |
| Change | Effect | |
|---|---|---|
| 1 | Field assoc has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field probe_auth has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field redirect_genid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'redirect_genid'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 1 has been changed from RING_RENDER to VCS. | Recompilation of a client program may be broken with the error message: 'RING_RENDER' was not declared in this scope. |
| 2 | Name of member with value 2 has been changed from RING_BSD to BCS. | Recompilation of a client program may be broken with the error message: 'RING_BSD' was not declared in this scope. |
| 3 | The member RING_BLT has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioprio_changed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct io_context' has no member named 'ioprio_changed'. |
| 2 | Field ioc_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct io_context' has no member named 'ioc_data'. |
| 3 | Field radix_root has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct io_context' has no member named 'radix_root'. |
| 4 | Field cic_list has been renamed to icq_list. | Recompilation of a client program may be broken with the error message: struct io_context has no member named cic_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field timer_rand_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'timer_rand_state'. |
| Change | Effect | |
|---|---|---|
| 1 | Field j_barrier has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct journal_s' has no member named 'j_barrier'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpustat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kernel_stat' has no member named 'cpustat'. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_KEXEC has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field done_seq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kthread_work' has no member named 'done_seq'. |
| 2 | Field queue_seq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kthread_work' has no member named 'queue_seq'. |
| 3 | Field flushing has been renamed to worker. | Recompilation of a client program may be broken with the error message: struct kthread_work has no member named flushing. |
| Change | Effect | |
|---|---|---|
| 1 | Field lsm_post_audit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct common_audit_data' has no member named 'lsm_post_audit'. |
| 2 | Field lsm_pre_audit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct common_audit_data' has no member named 'lsm_pre_audit'. |
| Change | Effect | |
|---|---|---|
| 1 | Field timestamp has been renamed to last_tsf. | Recompilation of a client program may be broken with the error message: struct ieee80211_bss_conf has no member named timestamp. |
| Change | Effect | |
|---|---|---|
| 1 | Field finish_tx_sync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_ops' has no member named 'finish_tx_sync'. |
| 2 | Field tx_sync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_ops' has no member named 'tx_sync'. |
| Change | Effect | |
|---|---|---|
| 1 | Field memory_size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct memblock' has no member named 'memory_size'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_legacy_base has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'mmap_legacy_base'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zone' has no member named 'lru'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been renamed to level. | Recompilation of a client program may be broken with the error message: struct kernel_param has no member named flags. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_parent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_parent'. |
| 2 | Field mnt_pinned has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_pinned'. |
| 3 | Field mnt_slave has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_slave'. |
| 4 | Field mnt_mounts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_mounts'. |
| 5 | Field mnt_devname has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_devname'. |
| 6 | Field mnt_expire has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_expire'. |
| 7 | Field mnt_hash has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_hash'. |
| 8 | Field mnt_mountpoint has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_mountpoint'. |
| 9 | Field mnt_child has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_child'. |
| 10 | Field mnt_expiry_mark has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_expiry_mark'. |
| 11 | Field mnt_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_id'. |
| 12 | Field mnt_longterm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_longterm'. |
| 13 | Field mnt_master has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_master'. |
| 14 | Field mnt_fsnotify_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_fsnotify_mask'. |
| 15 | Field mnt_group_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_group_id'. |
| 16 | Field mnt_pcp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_pcp'. |
| 17 | Field mnt_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_list'. |
| 18 | Field mnt_fsnotify_marks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_fsnotify_marks'. |
| 19 | Field mnt_ghosts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_ghosts'. |
| 20 | Field mnt_ns has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_ns'. |
| 21 | Field mnt_share has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_share'. |
| 22 | Field mnt_slave_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_slave_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field queue_len has been renamed to queue_len_bytes. | Recompilation of a client program may be broken with the error message: struct neigh_parms has no member named queue_len. |
| Change | Effect | |
|---|---|---|
| 1 | Field kmem_cachep has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct neigh_table' has no member named 'kmem_cachep'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 0 has been changed from IP_NAT_MANIP_SRC to NF_NAT_MANIP_SRC. | Recompilation of a client program may be broken with the error message: 'IP_NAT_MANIP_SRC' was not declared in this scope. |
| 2 | Name of member with value 1 has been changed from IP_NAT_MANIP_DST to NF_NAT_MANIP_DST. | Recompilation of a client program may be broken with the error message: 'IP_NAT_MANIP_DST' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field me has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_nat_protocol' has no member named 'me'. |
| 2 | Field range_to_nlattr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_nat_protocol' has no member named 'range_to_nlattr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ls_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_lock_state' has no member named 'ls_id'. |
| 2 | Field ls_sequence has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_lock_state' has no member named 'ls_sequence'. |
| Change | Effect | |
|---|---|---|
| 1 | Field validate_stateid has been renamed to match_stateid. | Recompilation of a client program may be broken with the error message: struct nfs4_minor_version_ops has no member named validate_stateid. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_owner_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_owner' has no member named 'so_owner_id'. |
| 2 | Field so_sequence has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_owner' has no member named 'so_sequence'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sequence has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_seqid_counter' has no member named 'sequence'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nfs_page_tree has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_inode' has no member named 'nfs_page_tree'. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been renamed to wb_list. | Recompilation of a client program may be broken with the error message: struct nfs_page has no member named unnamed0. |
| Change | Effect | |
|---|---|---|
| 1 | Field block_ucfg_access 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 'block_ucfg_access'. |
| 2 | Field fw_addr 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 'fw_addr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been renamed to mispred. | Recompilation of a client program may be broken with the error message: struct perf_branch_entry has no member named flags. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_fpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thread_struct' has no member named 'has_fpu'. |
| 2 | Field trap_no has been renamed to trap_nr. | Recompilation of a client program may be broken with the error message: struct thread_struct has no member named trap_no. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct radix_tree_node has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rate_control_ref' has no member named 'kref'. |
| Change | Effect | |
|---|---|---|
| 1 | Field resched_ipi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_data' has no member named 'resched_ipi'. |
| Change | Effect | |
|---|---|---|
| 1 | Field signaled has been renamed to fqs_state. | Recompilation of a client program may be broken with the error message: struct rcu_state has no member named signaled. |
| Change | Effect | |
|---|---|---|
| 1 | Field balance_iterator has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfs_rq' has no member named 'balance_iterator'. |
| 2 | Field tasks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfs_rq' has no member named 'tasks'. |
| 3 | Field task_weight has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfs_rq' has no member named 'task_weight'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sched_switch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'sched_switch'. |
| 2 | Field nohz_balance_kick has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'nohz_balance_kick'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tk_pid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_task' has no member named 'tk_pid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field threadgroup_fork_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct signal_struct' has no member named 'threadgroup_fork_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field irqaction 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 'irqaction'. |
| Change | Effect | |
|---|---|---|
| 1 | Field idx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct scsi_device_handler' has no member named 'idx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field netlink_recv has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'netlink_recv'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dummy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_info' has no member named 'dummy'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_entry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-sysctl.h-1064' has no member named 'ctl_entry'. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table' has no member named 'parent'. |
| Change | Effect | |
|---|---|---|
| 1 | Field attached_by has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_header' has no member named 'attached_by'. |
| 2 | Field attached_to has been renamed to node. | Recompilation of a client program may be broken with the error message: struct ctl_table_header has no member named attached_to. |
| Change | Effect | |
|---|---|---|
| 1 | Field root_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_root' has no member named 'root_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_set' has no member named 'parent'. |
| 2 | Field list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_set' has no member named 'list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysfs_dirent' has no member named 'name_node'. |
| 2 | Field inode_node has been renamed to s_rb. | Recompilation of a client program may be broken with the error message: struct sysfs_dirent has no member named inode_node. |
| Change | Effect | |
|---|---|---|
| 1 | Field name_tree has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysfs_elem_dir' has no member named 'name_tree'. |
| 2 | Field inode_tree has been renamed to children. | Recompilation of a client program may be broken with the error message: struct sysfs_elem_dir has no member named inode_tree. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloced4 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_md5sig_info' has no member named 'alloced4'. |
| 2 | Field alloced6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_md5sig_info' has no member named 'alloced6'. |
| 3 | Field entries4 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_md5sig_info' has no member named 'entries4'. |
| 4 | Field entries6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_md5sig_info' has no member named 'entries6'. |
| 5 | Field keys6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_md5sig_info' has no member named 'keys6'. |
| 6 | Field keys4 has been renamed to head. | Recompilation of a client program may be broken with the error message: struct tcp_md5sig_info has no member named keys4. |
| Change | Effect | |
|---|---|---|
| 1 | Field md5_add has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock_af_ops' has no member named 'md5_add'. |
| Change | Effect | |
|---|---|---|
| 1 | Field termios_locked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_driver' has no member named 'termios_locked'. |
| 2 | Field minor_num has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_driver' has no member named 'minor_num'. |
| 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 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 | 1st middle parameter task has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ioc of type struct io_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter gfp_flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack 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 | 1st middle parameter tsk has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter off 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 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 | 2nd middle parameter sizet has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter field_obj of type union acpi_operand_object* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sdata of type struct ieee80211_sub_if_data* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter cred has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter path of type struct path* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter mnt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter task has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dont_wait_for_ack of type bool has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sig_mbm 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 bss of type struct cfg80211_bss* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter neigh has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter client of type struct rpc_clnt* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter client of type struct rpc_clnt* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sig_dbm 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 min_level of type s16 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 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 bss of type struct cfg80211_bss* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter channel has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter bssid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack 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 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 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 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 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 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 set of type struct ctl_table_set* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter root has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd middle parameter namespaces has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter da of type u8 const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter name of type char const* 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 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id_lock has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_protname became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_clnt::cl_protname'. |
| 2 | Field cl_program became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_clnt::cl_program'. |
| Change | Effect | |
|---|---|---|
| 1 | Field program became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_create_args::program'. |
| 2 | Field servername became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_create_args::servername'. |
| Change | Effect | |
|---|---|---|
| 1 | Field p_name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_procinfo::p_name'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_program::name'. |
| 2 | Field pipe_dir_name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_program::pipe_dir_name'. |
| 3 | Field version became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_program::version'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct snd_kcontrol_new::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct cpuidle_driver::name'. |
| 2 | The pointer level of field name has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field data has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct drm_driver::fops'. |
| 2 | The pointer level of field fops has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field boottime has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field close_on_exec has been changed from struct __kernel_fd_set to unsigned long of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of field open_fds has been changed from struct __kernel_fd_set to unsigned long of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field open_fds_init has been changed from struct embedded_fd_set to unsigned long[1] of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field close_on_exec_init has been changed from struct embedded_fd_set to unsigned long[1] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fs_supers has been changed from struct list_head to struct hlist_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field s_instances has been changed from struct list_head to struct hlist_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field acthd has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field instdone has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 3 | Type of field instpm has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 4 | Type of field instps has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 5 | Type of field ipehr has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 6 | Type of field ipeir has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| 7 | Type of field seqno has been changed from u32 to u32[3] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field force_bit has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pending has been changed from struct atomic_t to int of different format. | 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 net has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field selinux_audit_data has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field icmpmsg_statistics has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | The pointer level of field icmpv6msg_statistics has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field root has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash_rnd has been changed from __u32 to __u32[4] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ls_stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field open_stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lockowner_id has been changed from struct rb_root to struct ida of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field openowner_id has been changed from struct rb_root to struct ida of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field delegation has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field stateid has been changed from union nfs4_stateid to nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field list became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct snd_pcm_hw_constraint_list::list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct wakeup_source::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Field program became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rpc_stat::program'. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field parent has been changed from struct ctl_table_header to struct ctl_dir of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field key has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field children has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sllao of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter service_name of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter node has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from struct io_context* (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flavor of type rpc_authflavor_t 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 | 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 flags of type fmode_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter dst has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mode_cmd has been changed from struct drm_mode_fb_cmd to struct drm_mode_fb_cmd2 of different format. | 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 frag_offp of type __be16* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sig_only has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter do_retire of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter do_retire of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mode_cmd has been changed from struct drm_mode_fb_cmd to struct drm_mode_fb_cmd2 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter address has been changed from struct sockaddr to struct __kernel_sockaddr_storage of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pre_audit of type void(*)(struct audit_buffer*, void*) has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter post_audit of type void(*)(struct audit_buffer*, void*) 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 | Type of return value has been changed from unsigned long (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter assoc_flags of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter ht_capa of type struct ieee80211_ht_cap* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter ht_capa_mask of type struct ieee80211_ht_cap* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 13th parameter local_state_change has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter assoc_flags of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter ht_capa of type struct ieee80211_ht_cap* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter ht_capa_mask of type struct ieee80211_ht_cap* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 13th parameter local_state_change has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cookie has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cookie has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct ctl_path[2] of different format. | Recompilation of a client program may be broken. |
| 2 | 1st parameter name has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 3rd parameter path has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of return value has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct dentry of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter child_mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter adapter has been changed from struct e1000_adapter to struct e1000_ring of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter adapter has been changed from struct e1000_adapter to struct e1000_ring of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter adapter has been changed from struct e1000_adapter to struct e1000_ring of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter adapter has been changed from struct e1000_adapter to struct e1000_ring of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter lsp has been changed from struct nfs4_lock_state const* to struct nfs4_lock_state* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_flags of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from union nfs4_stateid to struct nfs_stateid4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter enable_beaconing has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max_level of type s16 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter attrs of type struct dma_attrs* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct jump_label_key to struct static_key_deferred of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dest_mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter source_mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mnt has been changed from struct vfsmount to struct mount of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter addr has been changed from struct in6_addr to struct flowi6 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter inode has been changed from struct inode to struct rpc_pipe of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter out has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nr 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 cls has been changed from struct sysdev_class to struct device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter cred has been changed from struct cred to struct user_namespace of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter ns has been changed from struct user_namespace to struct cred of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter realloc_head has been changed from struct resource_list_x to struct list_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter truesize 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 2nd parameter idx has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter use_effective of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter kaddr has been changed from struct sockaddr to struct __kernel_sockaddr_storage of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter stats of type struct rpc_iostats* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter parent has been changed from struct ctl_table_set to struct ctl_table_root of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sysdev has been changed from struct sys_device to struct device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sysdev has been changed from struct sys_device to struct device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter first_ok has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter bss_notify of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field needcheck has been changed from int volatile to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field connection_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field resource_buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field resource_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_length has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field resource_buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field resource_length has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sleep_control has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sleep_status 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 long to __kernel_ulong_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_id_valid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field names_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field preallocated_names has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field principal has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipes_create has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pipes_destroy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipe_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field deferred_probe has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field interfaces has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcomm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icq_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field id has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | 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 init_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pref_address has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field slotid has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field keeplocked has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bg_scan_period has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field control_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field channel_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field probe_client has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_noack_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Base type of field deauth has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_deauth_request*, void*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_deauth_request*). | Recompilation of a client program may be broken. |
| 5 | Base type of field disassoc has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_disassoc_request*, void*) to int(*)(struct wiphy*, struct net_device*, struct cfg80211_disassoc_request*). | Recompilation of a client program may be broken. |
| 6 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, u64*) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, bool, u64*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_reg_power has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field parse_error has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshForwarding has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dot11MeshHWMPperrMinInterval has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rssi_threshold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcast_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_loss_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_sme_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field probe_resp_offload has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field features has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ht_capa_mod_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_unexpected_nlpid 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 attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup_taskset*). | Recompilation of a client program may be broken. |
| 2 | Base type of field bind has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Recompilation of a client program may be broken. |
| 3 | Base type of field can_attach has been changed from int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*) to int(*)(struct cgroup*, struct cgroup_taskset*). | Recompilation of a client program may be broken. |
| 4 | Base type of field cancel_attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup_taskset*). | Recompilation of a client program may be broken. |
| 5 | Base type of field create has been changed from struct cgroup_subsys_state*(*)(struct cgroup_subsys*, struct cgroup*) to struct cgroup_subsys_state*(*)(struct cgroup*). | Recompilation of a client program may be broken. |
| 6 | Base type of field destroy has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Recompilation of a client program may be broken. |
| 7 | Base type of field exit has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup*, struct cgroup*, struct task_struct*). | Recompilation of a client program may be broken. |
| 8 | Base type of field fork has been changed from void(*)(struct cgroup_subsys*, struct task_struct*) to void(*)(struct task_struct*). | Recompilation of a client program may be broken. |
| 9 | Base type of field post_clone has been changed from void(*)(struct cgroup_subsys*, struct cgroup*) to void(*)(struct cgroup*). | Recompilation of a client program may be broken. |
| 10 | Base type of field pre_destroy has been changed from int(*)(struct cgroup_subsys*, struct cgroup*) to int(*)(struct cgroup*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_dentry has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_beacons_nlpid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field en_core_tk_irqen has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field name has been changed from char[16] to char const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field enter_dead has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field power_usage has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void(*)(struct dm_target*, status_type_t, char*, unsigned int) to int(*)(struct dm_target*, status_type_t, char*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_root has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dev_name 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 devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field encoder_ids has been changed from uint32_t[2] to uint32_t[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field type has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field offsets has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pitches has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pixel_format has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_plane has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prefer_shadow has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field plane_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field preferred_depth 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 fb_create has been changed from struct drm_framebuffer*(*)(struct drm_device*, struct drm_file*, struct drm_mode_fb_cmd*) to struct drm_framebuffer*(*)(struct drm_device*, struct drm_file*, struct drm_mode_fb_cmd2*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from void* to unsigned char[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field unplugged has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_import has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prime_fd_to_handle has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gem_prime_export has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field prime_handle_to_fd has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field fops has been changed from struct file_operations to struct file_operations const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field prime has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field export_dma_buf has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field import_attach has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dump_buffers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ce4100_gbe_mdio_base_virt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field boottime has been changed from unsigned long to efi_boot_services_t*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_exit_icq_fn has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field elevator_init_icq_fn has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icq_align has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field icq_cache has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field icq_cache_name has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field icq_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_rxfh_indir_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field get_rxfh_indir has been changed from int(*)(struct net_device*, struct ethtool_rxfh_indir*) to int(*)(struct net_device*, u32*). | Recompilation of a client program may be broken. |
| 3 | Base type of field set_rxfh_indir has been changed from int(*)(struct net_device*, struct ethtool_rxfh_indir const*) to int(*)(struct net_device*, u32 const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field capabilities has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field colorspace has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bd_queue 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 create has been changed from int(*)(struct inode*, struct dentry*, int, struct nameidata*) to int(*)(struct inode*, struct dentry*, umode_t, struct nameidata*). | Recompilation of a client program may be broken. |
| 2 | Base type of field mkdir has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Recompilation of a client program may be broken. |
| 3 | Base type of field mknod has been changed from int(*)(struct inode*, struct dentry*, int, dev_t) to int(*)(struct inode*, struct dentry*, umode_t, dev_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_max_links has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field s_mounts has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field s_readonly_remount has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field s_remove_count 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 show_options has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Recompilation of a client program may be broken. |
| 2 | Base type of field show_devname has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Recompilation of a client program may be broken. |
| 3 | Base type of field show_path has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Recompilation of a client program may be broken. |
| 4 | Base type of field show_stats has been changed from int(*)(struct seq_file*, struct vfsmount*) to int(*)(struct seq_file*, struct dentry*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field reg has been changed from int(*)(struct ftrace_event_call*, enum trace_reg) to int(*)(struct ftrace_event_call*, enum trace_reg, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field devnode has been changed from char*(*)(struct gendisk*, mode_t*) to char*(*)(struct gendisk*, umode_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field icr_read_retry_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field irq has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field jacktbl has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field single_adc_amp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field config_collision_dist has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reload has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aliasing_ppgtt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_sprite_wm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_ring_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cpu_ring_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field done_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field faddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field fault_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field head has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field semaphore_mboxes has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field tail has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_aliasing_ppgtt_mapping has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tail has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gmbus_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sprite_scaling_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_llc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bit_algo has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gpio_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field has_gpio has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field force_bit has been changed from struct i2c_adapter* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_key_cons has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field idmap_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field corrupt_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field valid_data has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_sta_authorized has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field probe_resp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field control_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field incomplete_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field incomplete_stations has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field assoc_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field auth_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field uapsd_max_sp_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field uapsd_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_perr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ack_status_frames has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ack_status_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tim_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field noack_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rc_rateidx_mcs_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skbs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field data_len has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcv_tos has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field uc_index has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field scratch_page_dma has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_retired_head has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field icq_hint has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field icq_tree has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field release_work 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 init_netns has been changed from void(*)(struct net*, struct ip_vs_proto_data*) to int(*)(struct net*, struct ip_vs_proto_data*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_tcp_mem has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcv_tclass has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ucast_oif has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_class has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wait has been changed from enum umh_wait to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sta_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tx_frags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_idx_mcs_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field attr has been changed from struct sysdev_attribute to struct device_attribute. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hot_remove_disk has been changed from int(*)(struct mddev*, int) to int(*)(struct mddev*, struct md_rdev*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field merge_check_needed has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field total_size 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 icmpmsg_statistics has been changed from struct icmpmsg_mib* to struct icmpmsg_mib. | Recompilation of a client program may be broken. |
| 2 | Base type of field icmpv6msg_statistics has been changed from struct icmpv6msg_mib* to struct icmpv6msg_mib. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dirty_balance_reserve has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lruvec has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field incs has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of field decs has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hash has been changed from __u32(*)(void const*, struct net_device const*, __u32) to __u32(*)(void const*, struct net_device const*, __u32*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_queue_len_bytes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_peek_off has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wanted_features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 2 | Type of field hw_features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 3 | Type of field features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 4 | Type of field vlan_features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_neigh_destroy has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_neigh_construct has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field ndo_vlan_rx_kill_vid has been changed from void(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, unsigned short). | Recompilation of a client program may be broken. |
| 4 | Base type of field ndo_fix_features has been changed from u32(*)(struct net_device*, u32) to netdev_features_t(*)(struct net_device*, netdev_features_t). | Recompilation of a client program may be broken. |
| 5 | Base type of field ndo_vlan_rx_add_vid has been changed from void(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, unsigned short). | Recompilation of a client program may be broken. |
| 6 | Base type of field ndo_set_features has been changed from int(*)(struct net_device*, u32) to int(*)(struct net_device*, netdev_features_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dql has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field trans_timeout 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 gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field module has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_timeouts has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field new has been changed from bool(*)(struct nf_conn*, struct sk_buff const*, unsigned int) to bool(*)(struct nf_conn*, struct sk_buff const*, unsigned int, unsigned int*). | Recompilation of a client program may be broken. |
| 3 | Base type of field packet has been changed from int(*)(struct nf_conn*, struct sk_buff const*, unsigned int, enum ip_conntrack_info, u_int8_t, unsigned int) to int(*)(struct nf_conn*, struct sk_buff const*, unsigned int, enum ip_conntrack_info, u_int8_t, unsigned int, unsigned int*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field nlattr_to_range has been changed from int(*)(struct nlattr**, struct nf_nat_range*) to int(*)(struct nlattr**, struct nf_nat_ipv4_range*). | Recompilation of a client program may be broken. |
| 2 | Base type of field unique_tuple has been changed from void(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*) to void(*)(struct nf_conntrack_tuple*, struct nf_nat_ipv4_range const*, enum nf_nat_manip_type, struct nf_conn const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_expires has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field so_lru has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field task has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field create_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field owner_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field wait has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field commit_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field highest_used_slotid has been changed from int to u32. | Recompilation of a client program may be broken. |
| 2 | Type of field max_slots has been changed from int to u32. | Recompilation of a client program may be broken. |
| 3 | Type of field target_max_slots has been changed from int to u32. | Recompilation of a client program may be broken. |
| 4 | Type of field used_slots has been changed from unsigned long[4] to unsigned long[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field impl_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fh_expire_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field state_owners_lru has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sa_slotid has been changed from u8 to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_name has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field owner_name has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_owner has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field owner has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field read_rpc_prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rename_rpc_prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field unlink_rpc_prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field write_rpc_prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field block_cfg_access has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field msi_kset has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field res_attr has been changed from struct bin_attribute*[12] to struct bin_attribute*[11]. | Recompilation of a client program may be broken. |
| 4 | Type of field res_attr_wc has been changed from struct bin_attribute*[12] to struct bin_attribute*[11]. | Recompilation of a client program may be broken. |
| 5 | Type of field resource has been changed from struct resource[12] to struct resource[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field branch_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field br_sel has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lbr_sel has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field overlap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field interrupts_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field regs has been changed from struct er_account[2] to struct er_account[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field predicted has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field branch_sample_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_branch_stack has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_freq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field br_stack has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field attr_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field flush_branch_stack has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr_rdpmc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field events_mask_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field flush_branch_stack has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field format_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field lbr_sel_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field lbr_sel_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Base type of field quirks has been changed from void(*)() to struct x86_pmu_quirk. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hide_pid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pid_gid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field reboot has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field poweroff_late has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field thaw_early has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field restore_early has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field resume_early has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field freeze_late has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field suspend_late has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field work 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 long to __kernel_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from unsigned long to __kernel_ulong_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from long to __kernel_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field need_hotplug_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field has_fpu 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 gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, u32) to struct sk_buff*(*)(struct sk_buff*, netdev_features_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field write has been changed from int(*)(enum pstore_type_id, u64*, unsigned int, size_t, struct pstore_info*) to int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, size_t, struct pstore_info*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field qlen_lazy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dynticks_nesting has been changed from int to long long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_region has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_region 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 create_buf_file has been changed from struct dentry*(*)(char const*, struct dentry*, int, struct rchan_buf*, int*) to struct dentry*(*)(char const*, struct dentry*, umode_t, struct rchan_buf*, int*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfs_tasks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nohz_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rpc_count_stats has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_update has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_busy_cpus has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_child_subreaper has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_child_subreaper has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field group_rwsem has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dirty_paused_when has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field irq_thread has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field try_rc_10_first has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field skip_vpd_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_report_luns has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eh_action has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eh_noresume has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field task_free has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field capable has been changed from int(*)(struct task_struct*, struct cred const*, struct user_namespace*, int, int) to int(*)(struct cred const*, struct user_namespace*, int, int). | Recompilation of a client program may be broken. |
| 3 | Base type of field inode_create has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Recompilation of a client program may be broken. |
| 4 | Base type of field inode_mkdir has been changed from int(*)(struct inode*, struct dentry*, int) to int(*)(struct inode*, struct dentry*, umode_t). | Recompilation of a client program may be broken. |
| 5 | Base type of field inode_mknod has been changed from int(*)(struct inode*, struct dentry*, int, dev_t) to int(*)(struct inode*, struct dentry*, umode_t, dev_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_fcs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field wifi_acked_valid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field wifi_acked has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[83] to unsigned long[84]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_cgrp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_cgrp_prioidx has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sk_peek_off has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field sk_route_nocaps has been changed from int to netdev_features_t. | Recompilation of a client program may be broken. |
| 5 | Type of field sk_route_caps has been changed from int to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_addba_req_time has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_loss_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sta_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field session_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field failed_resume_early has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field failed_suspend_late 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 sv_shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nreg has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field is_visible has been changed from mode_t(*)(struct kobject*, struct attribute*, int) to umode_t(*)(struct kobject*, struct attribute*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field s_ino has been changed from ino_t to unsigned int. | Recompilation of a client program may be broken. |
| 3 | Type of field s_flags has been changed from unsigned int to unsigned short. | Recompilation of a client program may be broken. |
| 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 addr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field family has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field key has been changed from u8* to u8[80]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sig_on_uaccess_error has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field field has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buffer_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field key has been changed from struct jump_label_key to struct static_key. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field devnode has been changed from char*(*)(struct device*, mode_t*) to char*(*)(struct device*, umode_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field removable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field children has been changed from struct usb_device*[31] to struct usb_device**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[49] to unsigned long[52]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field name has been changed from char const* to char[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_percpu_clock_init has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fixup_cpu_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore_msi_irqs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore_sched_clock_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field save_sched_clock_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pending_u has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sending_u has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field max_slots has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field servername has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field servername has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] to char const*[34]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] to char const*[14]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] to char const*[29]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] to char const*[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[] to char const*[6]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_opcode_info[127] const to struct acpi_opcode_info[129] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32 to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[8] to char const*[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u8[17] const to u8[] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_rsconvert_info*[28] to struct acpi_rsconvert_info*[31]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u8[28] const to u8[] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_rsconvert_info*[17] to struct acpi_rsconvert_info*[20]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter all has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter mask has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 3 | Type of 2nd parameter one has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| 4 | Type of return value has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from u16 to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter last_pfx has been changed from insn_byte_t to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter last_pfx has been changed from insn_byte_t to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct intel_quirk[16] to struct intel_quirk[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32 to __be32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter wait has been changed from enum umh_wait to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[9] to char const*[9] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[2] to char const*[2] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[4] to char const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter align has been changed from u64 to phys_addr_t. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter end has been changed from u64 to phys_addr_t. | Recompilation of a client program may be broken. |
| 3 | Type of 3rd parameter size has been changed from u64 to phys_addr_t. | Recompilation of a client program may be broken. |
| 4 | Type of 1st parameter start has been changed from u64 to phys_addr_t. | Recompilation of a client program may be broken. |
| 5 | Type of return value has been changed from u64 to phys_addr_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter range has been changed from struct nf_nat_range to struct nf_nat_ipv4_range. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from union nfs4_stateid to struct nfs_stateid4. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_program to struct rpc_program const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter value has been changed from unsigned int to unsigned long long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter value has been changed from u32 to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct jump_label_key[9] to struct static_key[9]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter anycast has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from int to umode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter timeout_msecs has been changed from long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter idx has been changed from int to struct cfg80211_internal_bss*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter shutdown has been changed from void(*)(struct svc_serv*) to void(*)(struct svc_serv*, struct net*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from u32 to netdev_features_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[78] const to char const*[81] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_version to struct rpc_version const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field active became non-volatile. | No effect. |
| 2 | Field needcheck became non-volatile. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field common_serial_bus has been added to this type. | No effect. |
| 2 | Field fixed_dma has been added to this type. | No effect. |
| 3 | Field gpio has been added to this type. | No effect. |
| 4 | Field i2c_serial_bus has been added to this type. | No effect. |
| 5 | Field spi_serial_bus has been added to this type. | No effect. |
| 6 | Field uart_serial_bus has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR with value 12 has been added. | No effect. |
| 2 | The member ACPI_MADT_TYPE_GENERIC_INTERRUPT with value 11 has been added. | No effect. |
| 3 | Value of member ACPI_MADT_TYPE_RESERVED has been changed from 11 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field common_serial_bus has been added to this type. | No effect. |
| 2 | Field fixed_dma has been added to this type. | No effect. |
| 3 | Field gpio has been added to this type. | No effect. |
| 4 | Field i2c_serial_bus has been added to this type. | No effect. |
| 5 | Field spi_serial_bus has been added to this type. | No effect. |
| 6 | Field uart_serial_bus has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member AUDIT_BUILD_CONTEXT has been changed from 2 to 1. | No effect. |
| 2 | Value of member AUDIT_RECORD_CONTEXT has been changed from 3 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed0 has been changed from 19 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field elevator_attrs has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field elevator_name has been changed from 3 to 2. | No effect. |
| 3 | The relative position of field elevator_owner has been changed from 4 to 3. | No effect. |
| 4 | The relative position of field list has been changed from 0 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field daddr has been changed from 1 to 2. | No effect. |
| 2 | The relative position of field saddr has been changed from 2 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member TRACE_REG_PERF_ADD with value 6 has been added. | No effect. |
| 2 | The member TRACE_REG_PERF_CLOSE with value 5 has been added. | No effect. |
| 3 | The member TRACE_REG_PERF_DEL with value 7 has been added. | No effect. |
| 4 | The member TRACE_REG_PERF_OPEN with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member IEEE80211_WORK_OFFCHANNEL_TX has been changed from 6 to 2. | No effect. |
| 2 | Value of member IEEE80211_WORK_REMAIN_ON_CHANNEL has been changed from 5 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member RCS with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member KMSG_DUMP_EMERG has been changed from 6 to 2. | No effect. |
| 2 | Value of member KMSG_DUMP_OOPS has been changed from 0 to 1. | No effect. |
| 3 | Value of member KMSG_DUMP_PANIC has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field pad has been replaced by ack_frame_id. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field state has been changed from 2 to 7. | No effect. |
| 2 | The relative position of field trans_start has been changed from 7 to 6. | No effect. |
| 3 | The relative position of field qdisc_sleeping has been changed from 3 to 2. | No effect. |
| 4 | The relative position of field kobj has been changed from 4 to 3. | No effect. |
| 5 | The relative position of field xmit_lock_owner has been changed from 6 to 5. | No effect. |
| 6 | The relative position of field _xmit_lock has been changed from 5 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_SCOPE with value 40 has been added. | No effect. |
| 2 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 41 to 42. | No effect. |
| 3 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 40 to 41. | No effect. |
| 4 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 42 to 43. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_TYPE_UNKNOWN with value 0 has been added. | No effect. |
| 2 | Value of member POWER_SUPPLY_TYPE_BATTERY has been changed from 0 to 1. | No effect. |
| 3 | Value of member POWER_SUPPLY_TYPE_MAINS has been changed from 2 to 3. | No effect. |
| 4 | Value of member POWER_SUPPLY_TYPE_UPS has been changed from 1 to 2. | No effect. |
| 5 | Value of member POWER_SUPPLY_TYPE_USB has been changed from 3 to 4. | No effect. |
| 6 | Value of member POWER_SUPPLY_TYPE_USB_ACA has been changed from 6 to 7. | No effect. |
| 7 | Value of member POWER_SUPPLY_TYPE_USB_CDP has been changed from 5 to 6. | No effect. |
| 8 | Value of member POWER_SUPPLY_TYPE_USB_DCP has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tc_verd has been changed from 30 to 32. | No effect. |
| 2 | The relative position of field l4_rxhash has been changed from 35 to 36. | No effect. |
| 3 | The relative position of field ooo_okay has been changed from 34 to 35. | No effect. |
| 4 | The relative position of field ndisc_nodetype has been changed from 33 to 34. | No effect. |
| 5 | The relative position of field vlan_tci has been changed from 38 to 30. | No effect. |
| 6 | The relative position of field secmark has been changed from 36 to 37. | No effect. |
| 7 | The relative position of field tc_index has been changed from 29 to 31. | No effect. |
| 8 | The relative position of field unnamed1 has been changed from 37 to 38. | No effect. |
| 9 | The relative position of field rxhash has been changed from 31 to 29. | No effect. |
| 10 | The relative position of field queue_mapping has been changed from 32 to 33. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SUSPEND_RESUME_EARLY with value 7 has been added. | No effect. |
| 2 | The member SUSPEND_SUSPEND_LATE with value 4 has been added. | No effect. |
| 3 | Value of member SUSPEND_RESUME has been changed from 6 to 8. | No effect. |
| 4 | Value of member SUSPEND_RESUME_NOIRQ has been changed from 5 to 6. | No effect. |
| 5 | Value of member SUSPEND_SUSPEND_NOIRQ has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field parent has been changed from 6 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field key has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter seq has been renamed to seqp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter startt has been renamed to size. | 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 | 3rd parameter region_space has been renamed to space_id. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter uid has been renamed to gid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter uid has been renamed to gid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter last_pfx has been renamed to lpfx_id. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter last_pfx has been renamed to lpfx_id. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter res has been renamed to p. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter memory_limit has been renamed to limit. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mnt has been renamed to root. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mnt has been renamed to m. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to rx_ring. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to tx_ring. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to rx_ring. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter adapter has been renamed to tx_ring. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | No effect. |
| 2 | 5th parameter maxlen has been renamed to maxout. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter maxlen has been renamed to maxout. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter len has been renamed to inlen. | No effect. |
| 2 | 5th parameter maxlen has been renamed to maxout. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mem has been renamed to memcg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter mem_cont has been renamed to memcg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter addr has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been renamed to pipe. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter timestamp has been renamed to tsf. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cls has been renamed to dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ns has been renamed to cred. | No effect. |
| 2 | 2nd parameter cred has been renamed to ns. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter idx has been renamed to bss. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to set. | No effect. |
| 2 | 2nd parameter parent has been renamed to root. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sysdev has been renamed to cpu_dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sysdev has been renamed to cpu_dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter real has been renamed to offs_real. | No effect. |
| 2 | 2nd parameter boot has been renamed to offs_boot. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to fmt. | No effect. |