| Module Name | vmlinux |
|---|---|
| Version #1 | 3.11.8 |
| Version #2 | 3.12 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 801 |
|---|---|
| Total Source Files | 1477 |
| Total Objects | 1 |
| Total Symbols / Types | 17082 / 9499 |
| Verdict | Incompatible (41%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 410 |
| Removed Symbols | High | 131 |
| Problems with Data Types | High | 85 |
| Medium | 283 | |
| Low | 252 | |
| Problems with Symbols | High | 22 |
| Medium | 475 | |
| Low | 51 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 10 |
| Change | Effect | |
|---|---|---|
| 1 | Field power_dependent has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ki_buf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_cur_seg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_dtor has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_inline_vec has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_iovec has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_left has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_nr_segs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_opcode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ki_users has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipes_create has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pipes_destroy has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field css_kill_cnt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cgroup_ida has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_dentry has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field getavg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dithering_mode_property has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_unused has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 unused_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 unused_nodes has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf_readers has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 buf_writers has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ctx_start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field dma_flag has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 last_checked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 lck_start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field context_wait has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field interrupt_flag has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 buf_async has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 last_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_version has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field map_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 proc_nodes has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field proc_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 i_unrsv_conversion_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 i_unrsv_conversion_work has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field iocb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 result has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_nr_dentry_unused has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field s_nr_inodes_unused has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field s_inode_lru_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 active_info_valid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_offset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gtt_space has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfb_fb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cfb_plane has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field cfb_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. |
| 4 | Field cfb_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. |
| 5 | Field compressed_fb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 compressed_llb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 fbc_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. |
| 8 | Field forcewake_count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field gt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gt_fifo_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. |
| 11 | Field gt_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. |
| 12 | Field lfp_lvds_vbt_mode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field no_fbc_reason has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field sdvo_lvds_vbt_mode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_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 gtt_mtrr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gtt_space has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 inactive_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. |
| 5 | Field suspended has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scratch_page has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 scratch_page_dma has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field total has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clear_range has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field insert_entries has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pte_encode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 scratch_page_dma_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 rx_led_counter has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 scan_channel has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field tx_led_counter has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_clid_cred has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_load_throttle has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_resused has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field highest_alloc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 lowest_alloc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field char_buf_ptr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 flag_buf_ptr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field iflags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ldisc_mutex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of 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 1st parameter pseudoflavor 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 | Type of 3rd parameter block_group has been changed from unsigned int (4 bytes) to ext4_group_t (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter ss 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 nr_to_scan of type unsigned long has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter status has been changed from unsigned long long (8 bytes) to unsigned 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 vm of type struct i915_address_space* 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 vm of type struct i915_address_space* 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 plane of type struct drm_plane* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Parameter crtc of type struct drm_crtc* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 1st middle parameter dev has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 4 | 2nd middle parameter pipe 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 9th parameter df has been changed from __be16 (2 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. |
| 2 | Type of 5th parameter dst has been changed from __be32 (4 bytes) to __u8 (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. |
| 3 | Type of 8th parameter ttl has been changed from __u8 (1 byte) to __be16 (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 flags of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dst of type __be32 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 oldsize 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 8th parameter channel has been changed from u8 (1 byte) to struct cfg80211_chan_def* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 8th parameter channel 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 | Type of 2nd parameter max_length has been changed from u8 (1 byte) to u16 (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 | Field eject_pending 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 fixup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 users has been changed from struct atomic_t (4 bytes) to struct percpu_ref (24 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 cpu 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 free_work 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 req_batch 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 list has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field rcu_work 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 | The relative position of field ki_obj has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field ki_pos has been changed from 5 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field ki_user_data has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ac_flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_css has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_css has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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 added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dput_work has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field cgroup_idr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 top_cgroup has been changed from 172 bytes to 240 bytes. | 1) Size of the inclusive type has been 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_pipedir_objects has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_principal 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 cl_protname 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 port has been changed from 176 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field pub 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 may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field coalesce 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 policy_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field transition_ongoing 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 kobj_dev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field kobj 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 kobj_unregister 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 dev_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. |
| 2 | Field bus_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. |
| 3 | Field drv_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 bridge has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bridge_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field num_bridge has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_bridges has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field render has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field mode_config has been changed from 368 bytes to 380 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field object_name_lock has been changed from spinlock_t (2 bytes) to struct mutex (24 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vma_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 | Type of field handle_count has been changed from struct atomic_t to unsigned int of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mode_group has been changed from 16 bytes to 20 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member EHCI_HRTIMER_ASYNC_UNLINKS has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member EHCI_HRTIMER_DISABLE_ASYNC has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member EHCI_HRTIMER_DISABLE_PERIODIC has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member EHCI_HRTIMER_IAA_WATCHDOG has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member EHCI_HRTIMER_IO_WATCHDOG has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member EHCI_HRTIMER_NUM_EVENTS has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_tdi_phy_lpm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 intr_unlink_wait has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 intr_unlink_wait_cycle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Type of field hr_timeouts has been changed from ktime_t[10] (80 bytes) to ktime_t[11] (88 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field s_es_shrinker has been changed from 24 bytes to 32 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field unrsv_conversion_wq 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 suppress_ifgroup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 suppress_prefixlen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | The relative position of field action has been changed from 9 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field ctarget has been changed from 11 to 9. | 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 oifname has been changed from 13 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field pref has been changed from 6 to 12. | 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 rcu has been changed from 14 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field flags has been changed from 7 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field fr_net has been changed from 15 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field iifindex has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field iifname has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field mark has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field mark_mask has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field oifindex has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field refcnt has been changed from 1 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field table has been changed from 8 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field target has been changed from 10 to 8. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field suppress has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rcu 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. |
| 2 | The relative position of field bpf_func has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field insns 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 s_dio_done_wq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 s_shrink has been changed from 24 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The relative position of field s_dentry_lru has been changed from 22 to 42. | 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 s_max_links has been changed from 33 to 31. | 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 s_shrink has been changed from 41 to 39. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field s_uuid has been changed from 31 to 29. | 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 s_bdi has been changed from 25 to 23. | 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 s_options has been changed from 38 to 36. | 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 s_bdev has been changed from 24 to 22. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field s_id has been changed from 30 to 28. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field s_fs_info has been changed from 32 to 30. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field s_inode_lru has been changed from 23 to 43. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field s_instances has been changed from 27 to 25. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field s_vfs_rename_mutex has been changed from 36 to 34. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field s_writers has been changed from 29 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field s_readonly_remount has been changed from 43 to 41. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field s_dquot has been changed from 28 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | Type of field s_dentry_lru has been changed from struct list_head to struct list_lru of different format. | This field may be incorrectly initialized or accessed by applications. |
| 19 | Type of field s_inode_lru has been changed from struct list_head to struct list_lru of different format. | This field may be incorrectly initialized or accessed by applications. |
| 20 | The relative position of field cleancache_poolid has been changed from 40 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field s_d_op has been changed from 39 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field s_mode has been changed from 34 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field s_time_gran has been changed from 35 to 33. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field s_remove_count has been changed from 42 to 40. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field s_mtd has been changed from 26 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field s_subtype has been changed from 37 to 35. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field high_prio_bh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 low_prio_bh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_multi_io 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 horizontal_bar_valid has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field vertical_bar_valid has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 led_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_clock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field active_bo 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. |
| 2 | The pointer level of field active_bo_count 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. |
| 3 | The pointer level of field pinned_bo 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. |
| 4 | The pointer level of field pinned_bo_count 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 vma_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field pin_display has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 base has been changed from 92 bytes to 108 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field cache_level has been changed from 2 bits to 3 bits. | 1) Size of the inclusive type has been 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 ellc_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fbc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 no_psr_reason has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field pc8 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pm_irq_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field uncore has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vm_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. |
| 8 | Field 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. |
| 9 | Size of field display has been changed from 80 bytes to 84 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 10 | Size of field gtt has been changed from 60 bytes to 180 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Size of field mm has been changed from 392 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. |
| 12 | Size of field ring has been changed from 944 bytes to 960 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 13 | Size of field shared_dplls has been changed from 88 bytes to 104 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field object_stat_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field inactive_shrinker has been changed from 24 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field stolen has been changed from 100 bytes to 88 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mtrr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gtt_clear_range 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 gtt_insert_entries 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 gtt_remove 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 pte_encode has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cleanup 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 dpll_md has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pm_iir has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field vlv_work has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field lock 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 mode_set has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 hw_state 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 and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_pdo has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_beacon has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_capa has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ht_capa_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 scan_chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_counter_offset_beacon has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 csa_counter_offset_presp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 csa_finalize_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field csa_radar_required has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vif has been changed from 232 bytes to 236 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 mc_qri has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mc_qi has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cnf has been changed from 84 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 cnf has been changed from 112 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from int[26] (104 bytes) to int[28] (112 bytes). | 1) Size of the inclusive type has been 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 config has been changed from 544 bytes to 552 bytes. | 1) Size of the inclusive type has been 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 dpll_hw_state 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 and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field pch_pfit has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field timings_set has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 108 bytes to 112 bytes. | 1) Size of the inclusive type has been 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tunnels has been changed from struct hlist_head* (4 bytes) to struct hlist_head[128] (512 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field fb_tunnel_dev has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field tunnels has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mldv1_unsolicited_report_interval has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field suppress_frag_ndisc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mldv2_unsolicited_report_interval has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ledmode has been changed from 2 bits to 1 bit. | 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 current_may_mount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ncq_send_recv_cmds has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 2736 bytes to 2768 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 3324 bytes to 3356 bytes. | 1) Size of the inclusive type has been 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 qcmd has been changed from 4992 bytes to 5248 bytes. | 1) Size of the inclusive type has been 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 result_tf has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field tf has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field lock has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_active has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 NR_ACTIVE_ANON has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member NR_ACTIVE_FILE has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member NR_ANON_PAGES has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member NR_ANON_TRANSPARENT_HUGEPAGES has been changed from 26 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member NR_BOUNCE has been changed from 17 to 18. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member NR_DIRTIED has been changed from 24 to 25. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member NR_FILE_DIRTY has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member NR_FILE_MAPPED has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 9 | Value of member NR_FILE_PAGES has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 10 | Value of member NR_FREE_CMA_PAGES has been changed from 27 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 11 | Value of member NR_INACTIVE_ANON has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 12 | Value of member NR_INACTIVE_FILE has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 13 | Value of member NR_ISOLATED_ANON has been changed from 21 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 14 | Value of member NR_ISOLATED_FILE has been changed from 22 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 15 | Value of member NR_KERNEL_STACK has been changed from 15 to 16. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 16 | Value of member NR_LRU_BASE has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 17 | Value of member NR_MLOCK has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 18 | Value of member NR_PAGETABLE has been changed from 14 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 19 | Value of member NR_SHMEM has been changed from 23 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 20 | Value of member NR_SLAB_RECLAIMABLE has been changed from 12 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 21 | Value of member NR_SLAB_UNRECLAIMABLE has been changed from 13 to 14. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 22 | Value of member NR_UNEVICTABLE has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 23 | Value of member NR_UNSTABLE_NFS has been changed from 16 to 17. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 24 | Value of member NR_VMSCAN_IMMEDIATE has been changed from 19 to 20. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 25 | Value of member NR_VMSCAN_WRITE has been changed from 18 to 19. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 26 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 28 to 29. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 27 | Value of member NR_WRITEBACK has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 28 | Value of member NR_WRITEBACK_TEMP has been changed from 20 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 29 | Value of member NR_WRITTEN has been changed from 25 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[28] (28 bytes) to s8[29] (29 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat has been changed from atomic_long_t[28] (112 bytes) to atomic_long_t[29] (116 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 all_unreclaimable 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 | Size of field mkobj 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_unreg_count 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 rt_genid has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field lower_dev_list has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 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 | Value of member NF_CT_EXT_ACCT has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member NF_CT_EXT_NUM has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[3] (3 bytes) to u8[4] (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 shutdown_client has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 call_sync_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_sp4_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 cl_slot_tbl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_ds_clients has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field msi has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field migrate_entry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | The relative position of field event_entry has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field group_entry has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field changed_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_h_load_update has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 h_load_next has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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 added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cfs has been changed from 128 bytes to 136 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field css has been changed from 52 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_wakee has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wakee_flip_decay_ts has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wakee_flips has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pending_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 port has been changed from 176 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_objects has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 list has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from u64[32] (256 bytes) to u64[36] (288 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field stream_memory_free has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cluster_info has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field free_cluster_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. |
| 3 | Field free_cluster_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. |
| 4 | Field percpu_cluster has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notsent_lowat has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field binding_limits has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_hwmon has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tracing_cpumask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field priority has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sentinel has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lock has been changed from spinlock_t (2 bytes) to struct mutex (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 | The relative position of field lock has been changed from 1 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field work 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. |
| 6 | The relative position of field head has been changed from 2 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | Type of field memory_used has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 8 | The relative position of field memory_used has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field free has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field tail has been changed from 3 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field buf has been changed from 36 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 winsize_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 ldisc_sem has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 termios_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 | Field wq_idle 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 receive_buf2 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field may_mount_sysfs 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 may_mount_proc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[59] (236 bytes) to unsigned long[63] (252 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 184 bytes to 196 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 340 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 84 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 260 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 404 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1408 bytes to 1416 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 36 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 20 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 176 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 420 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1284 bytes to 1296 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 584 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 48 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 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 340 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 84 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 260 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 404 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1408 bytes to 1416 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 36 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 20 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 176 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 420 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1284 bytes to 1296 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 584 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 48 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter block_group 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 desc 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 sb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter authflavour 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different 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 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 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 340 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1408 bytes to 1416 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 584 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 32 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 512 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 404 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 20 bytes to 24 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 84 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 420 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 1284 bytes to 1296 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 208 bytes to 212 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 260 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 20 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 176 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 36 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 48 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 36 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 640 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 360 bytes to 312 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nid of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 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. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter frame 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 mode 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 dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter obj 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 size 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 | 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 flags of type enum drm_mm_search_flags has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type enum drm_mm_search_flags has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm 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 file_priv of type struct drm_file* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fmt 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 insert 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 bprm 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 flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter iocb 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 iov 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 nr_segs 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 adapter 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 adapter became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter force of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter ring has been changed from struct intel_ring_buffer (236 bytes) to struct drm_device (956 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cache_level 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 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 | The parameter dev_priv 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 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 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 | The parameter dev_priv 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 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 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 | Parameter nid of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scaled of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter val 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 ops of type struct rtnl_link_ops* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter skb has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Base type of 1st parameter net has been changed from struct net (2560 bytes) to struct rtable (112 bytes). | This parameter may be incorrectly initialized by applications. |
| 3 | Base type of 2nd parameter rt has been changed from struct rtable (112 bytes) to struct sk_buff (192 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter q has been removed from the calling stack. | This parameter will be ignored by the function. |
| 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 | 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 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 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 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 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 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 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 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 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 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 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 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 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nvec 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 type 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 | The parameter dentry 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 flag 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 mnt became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter portid of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter report of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter authflavour has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter auth_probe of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter auth_probe of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter flag 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 lockdep_ok became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[12] (432 bytes) to struct event_constraint[13] (468 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 432 bytes to 468 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct static_key[9] (36 bytes) to struct static_key[10] (40 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 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 enable 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 sleep_state 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 | 2nd parameter mpss has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dentry has been changed from struct dentry (128 bytes) to struct rpc_clnt (212 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[34] const (136 bytes) to struct nla_policy[35] const (140 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scan_width of type enum nl80211_bss_scan_width has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 84 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 260 bytes to 292 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 404 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 1408 bytes to 1416 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 36 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 28 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 176 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 420 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1284 bytes to 1296 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 584 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4400 bytes to 4464 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 172 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 52 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 108 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 1408 bytes to 1416 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 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter xnet of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max_page_order of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 bytes to 52 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 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty 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 tty became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 200 bytes to 204 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 84 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 48 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 220 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shift of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scan_width of type enum nl80211_bss_scan_width has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter local has been changed from struct ieee80211_local (2628 bytes) to struct ieee80211_sub_if_data (1780 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 236 bytes to 252 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[28] (112 bytes) to atomic_long_t[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*[89] const (356 bytes) to char const*[94] const (376 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 356 bytes to 376 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 596 bytes to 588 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reqs_active has been renamed to reqs_available. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field aio_ring_file 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 id has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 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 | Base type has been changed from int()(struct kiocb*, struct io_event*) to int()(struct kiocb*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field auxiliary has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 | 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 key_timeout has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 48 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field create has been changed from struct rpc_auth*(*)(struct rpc_clnt*, rpc_authflavor_t) to struct rpc_auth*(*)(struct rpc_auth_create_args*, struct rpc_clnt*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field crkey_to_expire has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 crkey_timeout has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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 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 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 52 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel_switch has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 set_coalesce has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 328 bytes to 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 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field patterns has been changed from struct cfg80211_wowlan_trig_pkt_pattern to struct cfg80211_pkt_pattern. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field coalesce 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 cg has been renamed to cset. | 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 136 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field read has been changed from ssize_t(*)(struct cgroup*, struct cftype*, struct file*, char*, size_t, loff_t*) to ssize_t(*)(struct cgroup_subsys_state*, struct cftype*, struct file*, char*, size_t, loff_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field read_map has been changed from int(*)(struct cgroup*, struct cftype*, struct cgroup_map_cb*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct cgroup_map_cb*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field read_s64 has been changed from s64(*)(struct cgroup*, struct cftype*) to s64(*)(struct cgroup_subsys_state*, struct cftype*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field read_seq_string has been changed from int(*)(struct cgroup*, struct cftype*, struct seq_file*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct seq_file*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field read_u64 has been changed from u64(*)(struct cgroup*, struct cftype*) to u64(*)(struct cgroup_subsys_state*, struct cftype*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field register_event has been changed from int(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct eventfd_ctx*, char const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field trigger has been changed from int(*)(struct cgroup*, unsigned int) to int(*)(struct cgroup_subsys_state*, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field unregister_event has been changed from void(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*) to void(*)(struct cgroup_subsys_state*, struct cftype*, struct eventfd_ctx*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 10 | Base type of field write has been changed from ssize_t(*)(struct cgroup*, struct cftype*, struct file*, char const*, size_t, loff_t*) to ssize_t(*)(struct cgroup_subsys_state*, struct cftype*, struct file*, char const*, size_t, loff_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 11 | Base type of field write_s64 has been changed from int(*)(struct cgroup*, struct cftype*, s64) to int(*)(struct cgroup_subsys_state*, struct cftype*, s64). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 12 | Base type of field write_string has been changed from int(*)(struct cgroup*, struct cftype*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, char const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 13 | Base type of field write_u64 has been changed from int(*)(struct cgroup*, struct cftype*, u64) to int(*)(struct cgroup_subsys_state*, struct cftype*, u64). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 172 bytes to 240 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 attach has been changed from void(*)(struct cgroup*, struct cgroup_taskset*) to void(*)(struct cgroup_subsys_state*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field bind has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field can_attach has been changed from int(*)(struct cgroup*, struct cgroup_taskset*) to int(*)(struct cgroup_subsys_state*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field cancel_attach has been changed from void(*)(struct cgroup*, struct cgroup_taskset*) to void(*)(struct cgroup_subsys_state*, struct cgroup_taskset*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field css_alloc has been changed from struct cgroup_subsys_state*(*)(struct cgroup*) to struct cgroup_subsys_state*(*)(struct cgroup_subsys_state*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field css_free has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field css_offline has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field css_online has been changed from int(*)(struct cgroup*) to int(*)(struct cgroup_subsys_state*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field exit has been changed from void(*)(struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup_subsys_state*, struct cgroup_subsys_state*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_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 | Field destroy_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. |
| 3 | Size of this type has been changed from 52 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 4400 bytes to 4464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_clid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 208 bytes to 212 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 516 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 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 68 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 148 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 360 bytes to 312 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 age_limit has been changed from int to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field dummy has been changed from int[2] to long[2]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field nr_dentry has been changed from int to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field nr_unused has been changed from int to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field want_pages has been changed from int to 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 72 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field stats has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 432 bytes to 480 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 page_flip has been changed from int(*)(struct drm_crtc*, struct drm_framebuffer*, struct drm_pending_vblank_event*) to int(*)(struct drm_crtc*, struct drm_framebuffer*, struct drm_pending_vblank_event*, uint32_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 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 | Field async_page_flip has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 368 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 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 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 100 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 | Field agp_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. |
| 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 992 bytes to 956 bytes. | The fields or parameters of 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 252 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ioctls 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 ioctls has been changed from struct drm_ioctl_desc* to struct drm_ioctl_desc 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 92 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field export_dma_buf has been renamed to dma_buf. | 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 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 | Size of this type has been changed from 480 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 640 bytes to 616 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 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 | Type of field dummy has been changed from int[5] to long[5]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field nr_inodes has been changed from int to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field nr_unused has been changed from int to 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 640 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field free_cached_objects has been changed from void(*)(struct super_block*, int) to long(*)(struct super_block*, long, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field nr_cached_objects has been changed from int(*)(struct super_block*) to long(*)(struct super_block*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(struct kiocb*, loff_t, ssize_t, void*, int, bool) to void()(struct kiocb*, loff_t, ssize_t, void*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 240 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dp_mst 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 72 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field oui has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 s3d_ext_data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field s3d_struct has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 vic has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 36 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 3804 bytes to 3820 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 2 has been changed from I915_CACHE_LLC_MLC to I915_CACHE_L3_LLC. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field queue_flip has been changed from int(*)(struct drm_device*, struct drm_crtc*, struct drm_framebuffer*, struct drm_i915_gem_object*) to int(*)(struct drm_device*, struct drm_crtc*, struct drm_framebuffer*, struct drm_i915_gem_object*, uint32_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field update_sprite_wm has been changed from void(*)(struct drm_device*, int, uint32_t, int, bool) to void(*)(struct drm_plane*, struct drm_crtc*, uint32_t, int, bool, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field active_bo has been changed from struct drm_i915_error_buffer* to struct drm_i915_error_buffer**. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field active_bo_count has been changed from u32 to u32*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field pinned_bo has been changed from struct drm_i915_error_buffer* to struct drm_i915_error_buffer**. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field pinned_bo_count has been changed from u32 to u32*. | 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 212 bytes to 228 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mm_list has been renamed to obj_exec_link. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ums has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 8932 bytes to 9140 bytes. | The fields or parameters of 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 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 60 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 44 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 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 44 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 300 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 148 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2628 bytes to 2632 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1748 bytes to 1780 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 ap has been changed from 300 bytes to 304 bytes. | 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 200 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 404 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 280 bytes to 288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 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 2168 bytes to 2176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 544 bytes to 552 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 708 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field psr_dpcd 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 psr_setup_done has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 bytes to 112 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 write_infoframe has been changed from void(*)(struct drm_encoder*, struct dip_infoframe*) to void(*)(struct drm_encoder*, enum hdmi_infoframe_type, uint8_t const*, ssize_t). | 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 wait to HANGCHECK_WAIT. | 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 active to HANGCHECK_ACTIVE. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Name of member with value 2 has been changed from kick to HANGCHECK_KICK. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Name of member with value 3 has been changed from hung to HANGCHECK_HUNG. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field scratch has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 236 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field private has been removed from this type. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 516 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 tunnels 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 msg_ctlmnb 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. |
| 2 | Type of field msg_ctlmni 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. |
| 3 | Type of field msg_ctlmax 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 rt_genid 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 84 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_genid 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 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1368 bytes to 1384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3324 bytes to 3356 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 9600 bytes to 9856 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 156 bytes to 164 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 | 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 channel_switch_beacon has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 284 bytes to 288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Base type of field rate_init has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*) to void(*)(void*, struct ieee80211_supported_band*, struct cfg80211_chan_def*, struct ieee80211_sta*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field rate_update has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32) to void(*)(void*, struct ieee80211_supported_band*, struct cfg80211_chan_def*, struct ieee80211_sta*, void*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field control has been changed from 24 bytes to 28 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctx_list has been renamed to ioctx_table. | 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 340 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj_completion has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 48 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 ndo_add_vxlan_port has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_del_vxlan_port has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field ndo_get_phys_port_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. |
| 4 | Size of this type has been changed from 184 bytes to 196 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_expect has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 seq_adjust has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field call_sync has been renamed to init_client. | 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 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 512 bytes to 528 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 open_context has been changed from struct inode*(*)(struct inode*, struct nfs_open_context*, int, struct iattr*) to struct inode*(*)(struct inode*, struct nfs_open_context*, int, struct iattr*, int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field write_rpc_prepare has been changed from void(*)(struct rpc_task*, struct nfs_write_data*) to int(*)(struct rpc_task*, struct nfs_write_data*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field read_rpc_prepare has been changed from void(*)(struct rpc_task*, struct nfs_read_data*) to int(*)(struct rpc_task*, struct nfs_read_data*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field init_client has been changed from struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t) to struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char 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 408 bytes to 412 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset_slot has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 | Size of this type has been changed from 584 bytes to 592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap2 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 size 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 time_zero 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 cap_____res has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 2 | Field cap_usr_rdpmc has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 3 | Field cap_usr_time 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 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 changed 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_xstatev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1408 bytes to 1416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 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 1284 bytes to 1296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member SDEV_EVT_LAST has been changed from 1 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member SDEV_EVT_MAXBITS has been changed from 2 to 7. | 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 696 bytes to 700 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field expecting_lun_change 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 inode_init_security has been changed from int(*)(struct inode*, struct inode*, struct qstr const*, char**, void**, size_t*) to int(*)(struct inode*, struct inode*, struct qstr const*, char const**, void**, size_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 196 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 | 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 | Field nodes_to_scan has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_deferred has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field nr_in_batch has been renamed to flags. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field shrink has been renamed to count_objects. | 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 260 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 | Size of this type has been changed from 200 bytes to 204 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3628 bytes to 3624 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field discard_cluster_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 | Field discard_cluster_tail has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 discard_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. |
| 4 | Size of this type has been changed from 92 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 1292 bytes to 1296 bytes. | The fields or parameters of 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 | 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 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field next has been renamed to 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 36 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field free 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 free has been changed from struct tty_buffer* to struct llist_head. | 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 176 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 420 bytes to 464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field termios_mutex has been renamed to throttle_mutex. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field users has been renamed to tty. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_sg_constraint 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 220 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 236 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 | 1st parameter iocb has been renamed to req. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pseudoflavor has been renamed to args. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter pseudoflavor has been changed from rpc_authflavor_t to struct rpc_auth_create_args*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to policy. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter root has been renamed to parent. | 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 long (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mask has been changed from struct cpumask* to struct cpumask const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter offset has been renamed to nextoff. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter flag has been renamed to gb_flags. | 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 drm_ioctl_desc[] to struct drm_ioctl_desc[] 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 bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ring has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | 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 long (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter nr_to_scan has been changed from int to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st 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 1st parameter fixed_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 | 5th parameter enable has been renamed to enabled. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been renamed to rt. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter rt has been renamed to skb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter skb has been renamed to src. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | 4th parameter src has been renamed to dst. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 5 | 5th parameter dst has been renamed to proto. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 6 | 6th parameter proto has been renamed to tos. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 7 | 7th parameter tos has been renamed to ttl. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 8 | 8th parameter ttl has been renamed to df. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 9 | 9th parameter df has been renamed to xnet. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 10 | Type of 3rd parameter skb has been changed from struct sk_buff* to __be32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter dest has been changed from char to unsigned char. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter src has been changed from char to unsigned char. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter dest has been changed from char to unsigned char. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter src has been changed from char to unsigned char. | 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 void(*)(struct sk_buff*, struct sk_buff*) to void(*)(struct sk_buff*, struct sk_buff const*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter pre_order_visit has been renamed to descending_callback. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 6th parameter post_order_visit has been renamed to ascending_callback. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter pre_order_visit has been renamed to descending_callback. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 5th parameter post_order_visit has been renamed to ascending_callback. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sta has been renamed to pubsta. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter rcutorturename has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter res has been renamed to resp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dentry has been renamed to rpc_client. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ops has been changed from struct Qdisc_ops* to struct Qdisc_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ops has been changed from struct Qdisc_ops* to struct Qdisc_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter name has been changed from char** to char const**. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter addr has been renamed to src. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter channel has been renamed to chandef. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter shrink has been renamed to shrinkctl. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mark has been changed from struct xfrm_mark* to struct xfrm_mark const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member EHCI_HRTIMER_START_UNLINK_INTR with value 5 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_CACHE_WT with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_ALLOC_BATCH with value 1 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NF_CT_EXT_SEQADJ with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SDEV_EVT_CAPACITY_CHANGE_REPORTED with value 3 has been added. | No effect. |
| 2 | The member SDEV_EVT_FIRST with value 1 has been added. | No effect. |
| 3 | The member SDEV_EVT_INQUIRY_CHANGE_REPORTED with value 2 has been added. | No effect. |
| 4 | The member SDEV_EVT_LUN_CHANGE_REPORTED with value 6 has been added. | No effect. |
| 5 | The member SDEV_EVT_MODE_PARAMETER_CHANGE_REPORTED with value 5 has been added. | No effect. |
| 6 | The member SDEV_EVT_SOFT_THRESHOLD_REACHED_REPORTED with value 4 has been added. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.11.8 |
| Version #2 | 3.12 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 801 |
|---|---|
| Total Source Files | 1477 |
| Total Objects | 1 |
| Total Symbols / Types | 17097 / 9499 |
| Verdict | Incompatible (38.5%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 412 |
| Removed Symbols | High | 131 |
| Problems with Data Types | High | 132 |
| Medium | 16 | |
| Low | 219 | |
| Problems with Symbols | High | 13 |
| Medium | 42 | |
| Low | 21 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 104 |
| Other Changes in Symbols | - | 32 |
| Change | Effect | |
|---|---|---|
| 1 | Field power_dependent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device' has no member named 'power_dependent'. |
| Change | Effect | |
|---|---|---|
| 1 | Field eject_pending has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_flags' has no member named 'eject_pending'. |
| Change | Effect | |
|---|---|---|
| 1 | Field reqs_active has been renamed to reqs_available. | Recompilation of a client program may be broken with the error message: anon-struct-aio.c-93 has no member named reqs_active. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'list'. |
| 2 | Field rcu_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'rcu_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ki_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_buf'. |
| 2 | Field ki_cur_seg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_cur_seg'. |
| 3 | Field ki_dtor has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_dtor'. |
| 4 | Field ki_inline_vec has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_inline_vec'. |
| 5 | Field ki_iovec has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_iovec'. |
| 6 | Field ki_left has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_left'. |
| 7 | Field ki_nr_segs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_nr_segs'. |
| 8 | Field ki_opcode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_opcode'. |
| 9 | Field ki_users has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_users'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipes_destroy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_authops' has no member named 'pipes_destroy'. |
| 2 | Field pipes_create has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_authops' has no member named 'pipes_create'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cg has been renamed to cset. | Recompilation of a client program may be broken with the error message: struct task_and_cgroup has no member named cg. |
| Change | Effect | |
|---|---|---|
| 1 | Field css_kill_cnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'css_kill_cnt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dput_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys_state' has no member named 'dput_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cgroup_ida has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroupfs_root' has no member named 'cgroup_ida'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_principal 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_principal'. |
| 2 | Field cl_protname 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_protname'. |
| 3 | Field cl_dentry 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_dentry'. |
| Change | Effect | |
|---|---|---|
| 1 | Field getavg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpufreq_driver' has no member named 'getavg'. |
| 2 | Field owner has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpufreq_driver' has no member named 'owner'. |
| Change | Effect | |
|---|---|---|
| 1 | Field transition_ongoing has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpufreq_policy' has no member named 'transition_ongoing'. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj 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 'kobj'. |
| 2 | Field kobj_unregister 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 'kobj_unregister'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dithering_mode_property has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mode_config' has no member named 'dithering_mode_property'. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_unused has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mm' has no member named 'num_unused'. |
| 2 | Field unused_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mm' has no member named 'unused_lock'. |
| 3 | Field unused_nodes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mm' has no member named 'unused_nodes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf_writers has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'buf_writers'. |
| 2 | Field ctx_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'ctx_start'. |
| 3 | Field last_checked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'last_checked'. |
| 4 | Field lck_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'lck_start'. |
| 5 | Field context_wait has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'context_wait'. |
| 6 | Field interrupt_flag has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'interrupt_flag'. |
| 7 | Field buf_async has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'buf_async'. |
| 8 | Field dma_flag has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'dma_flag'. |
| 9 | Field buf_readers has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'buf_readers'. |
| 10 | Field last_switch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'last_switch'. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_version has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'set_version'. |
| Change | Effect | |
|---|---|---|
| 1 | Field map_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_gem_object' has no member named 'map_list'. |
| 2 | Field export_dma_buf has been renamed to dma_buf. | Recompilation of a client program may be broken with the error message: struct drm_gem_object has no member named export_dma_buf. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_root has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_minor' has no member named 'proc_root'. |
| 2 | Field proc_nodes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_minor' has no member named 'proc_nodes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_unrsv_conversion_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_inode_info' has no member named 'i_unrsv_conversion_list'. |
| 2 | Field i_unrsv_conversion_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_inode_info' has no member named 'i_unrsv_conversion_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field iocb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_io_end' has no member named 'iocb'. |
| 2 | Field result has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_io_end' has no member named 'result'. |
| Change | Effect | |
|---|---|---|
| 1 | Field unrsv_conversion_wq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_sb_info' has no member named 'unrsv_conversion_wq'. |
| Change | Effect | |
|---|---|---|
| 1 | Field insns has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sk_filter' has no member named 'insns'. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_nr_inodes_unused has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_nr_inodes_unused'. |
| 2 | Field s_nr_dentry_unused has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_nr_dentry_unused'. |
| 3 | Field s_inode_lru_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_inode_lru_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_info_valid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_avi_infoframe' has no member named 'active_info_valid'. |
| 2 | Field horizontal_bar_valid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_avi_infoframe' has no member named 'horizontal_bar_valid'. |
| 3 | Field vertical_bar_valid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_avi_infoframe' has no member named 'vertical_bar_valid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_vendor_infoframe' has no member named 'data'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 2 has been changed from I915_CACHE_LLC_MLC to I915_CACHE_L3_LLC. | Recompilation of a client program may be broken with the error message: 'I915_CACHE_LLC_MLC' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_offset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'gtt_offset'. |
| 2 | Field gtt_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'gtt_space'. |
| 3 | Field mm_list has been renamed to obj_exec_link. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named mm_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field cfb_fb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'cfb_fb'. |
| 2 | Field cfb_plane has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'cfb_plane'. |
| 3 | Field cfb_size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'cfb_size'. |
| 4 | Field cfb_y has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'cfb_y'. |
| 5 | Field compressed_fb 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 'compressed_fb'. |
| 6 | Field compressed_llb 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 'compressed_llb'. |
| 7 | Field fbc_work 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 'fbc_work'. |
| 8 | Field forcewake_count 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 'forcewake_count'. |
| 9 | Field gt 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 'gt'. |
| 10 | Field gt_fifo_count 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 'gt_fifo_count'. |
| 11 | Field gt_lock 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 'gt_lock'. |
| 12 | Field lfp_lvds_vbt_mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'lfp_lvds_vbt_mode'. |
| 13 | Field no_fbc_reason has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'no_fbc_reason'. |
| 14 | Field sdvo_lvds_vbt_mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'sdvo_lvds_vbt_mode'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gem_mm' has no member named 'active_list'. |
| 2 | Field gtt_mtrr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gem_mm' has no member named 'gtt_mtrr'. |
| 3 | Field gtt_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gem_mm' has no member named 'gtt_space'. |
| 4 | Field inactive_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gem_mm' has no member named 'inactive_list'. |
| 5 | Field suspended has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gem_mm' has no member named 'suspended'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_clear_range has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'gtt_clear_range'. |
| 2 | Field gtt_insert_entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'gtt_insert_entries'. |
| 3 | Field gtt_remove has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'gtt_remove'. |
| 4 | Field pte_encode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'pte_encode'. |
| 5 | Field scratch_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'scratch_page'. |
| 6 | Field scratch_page_dma has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'scratch_page_dma'. |
| 7 | Field start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'start'. |
| 8 | Field total has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gtt' has no member named 'total'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'cleanup'. |
| 2 | Field clear_range has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'clear_range'. |
| 3 | Field dev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'dev'. |
| 4 | Field insert_entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'insert_entries'. |
| 5 | Field pte_encode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'pte_encode'. |
| 6 | Field scratch_page_dma_addr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_hw_ppgtt' has no member named 'scratch_page_dma_addr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_gen6_power_mgmt' has no member named 'lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_led_counter 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 'rx_led_counter'. |
| 2 | Field scan_channel 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 'scan_channel'. |
| 3 | Field tx_led_counter 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 'tx_led_counter'. |
| Change | Effect | |
|---|---|---|
| 1 | Field timings_set has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc_config' has no member named 'timings_set'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 0 has been changed from wait to HANGCHECK_WAIT. | Recompilation of a client program may be broken with the error message: 'wait' was not declared in this scope. |
| 2 | Name of member with value 1 has been changed from active to HANGCHECK_ACTIVE. | Recompilation of a client program may be broken with the error message: 'active' was not declared in this scope. |
| 3 | Name of member with value 2 has been changed from kick to HANGCHECK_KICK. | Recompilation of a client program may be broken with the error message: 'kick' was not declared in this scope. |
| 4 | Name of member with value 3 has been changed from hung to HANGCHECK_HUNG. | Recompilation of a client program may be broken with the error message: 'hung' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct lockref' has no member named 'lock'. |
| 2 | Field count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct lockref' has no member named 'count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctx_list has been renamed to ioctx_table. | Recompilation of a client program may be broken with the error message: struct mm_struct has no member named ioctx_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field all_unreclaimable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zone' has no member named 'all_unreclaimable'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_genid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net' has no member named 'rt_genid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field call_sync has been renamed to init_client. | Recompilation of a client program may be broken with the error message: struct nfs4_minor_version_ops has no member named call_sync. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_clid_cred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_recovery_ops' has no member named 'get_clid_cred'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cap_____res has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field cap_usr_rdpmc has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field cap_usr_time has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: anon-union-perf_event.h-376 has no member named cap_usr_time. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_load_throttle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'h_load_throttle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field shrink has been renamed to count_objects. | Recompilation of a client program may be broken with the error message: struct shrinker has no member named shrink. |
| 2 | Field nr_in_batch has been renamed to flags. | Recompilation of a client program may be broken with the error message: struct shrinker has no member named nr_in_batch. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_resused has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct svc_rqst' has no member named 'rq_resused'. |
| Change | Effect | |
|---|---|---|
| 1 | Field highest_alloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct swap_info_struct' has no member named 'highest_alloc'. |
| 2 | Field lowest_alloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct swap_info_struct' has no member named 'lowest_alloc'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flag_buf_ptr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_buffer' has no member named 'flag_buf_ptr'. |
| 2 | Field char_buf_ptr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_buffer' has no member named 'char_buf_ptr'. |
| 3 | Field next has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct tty_buffer has no member named next. |
| Change | Effect | |
|---|---|---|
| 1 | Field iflags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_port' has no member named 'iflags'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ldisc_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'ldisc_mutex'. |
| 2 | Field termios_mutex has been renamed to throttle_mutex. | Recompilation of a client program may be broken with the error message: struct tty_struct has no member named termios_mutex. |
| Change | Effect | |
|---|---|---|
| 1 | Field wq_idle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_ldisc' has no member named 'wq_idle'. |
| 2 | Field users has been renamed to tty. | Recompilation of a client program may be broken with the error message: struct tty_ldisc has no member named users. |
| Change | Effect | |
|---|---|---|
| 1 | Field may_mount_proc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'may_mount_proc'. |
| 2 | Field may_mount_sysfs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'may_mount_sysfs'. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter ss has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nr_to_scan of type unsigned long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vm of type struct i915_address_space* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vm of type struct i915_address_space* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter plane of type struct drm_plane* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter crtc of type struct drm_crtc* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 3 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 2nd middle parameter pipe has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dst of type __be32 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 oldsize has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field users has been changed from struct atomic_t to struct percpu_ref of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field object_name_lock has been changed from spinlock_t to struct mutex of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctls became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct drm_driver::ioctls'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field handle_count has been changed from struct atomic_t to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field s_dentry_lru has been changed from struct list_head to struct list_lru of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field s_inode_lru has been changed from struct list_head to struct list_lru of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field active_bo has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 2 | The pointer level of field active_bo_count has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 3 | The pointer level of field pinned_bo has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 4 | The pointer level of field pinned_bo_count has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field tunnels has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This type became opaque. | The internal structure of this type is hidden in the new library version and recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct rcu_state::name'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field free has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | Type of field lock has been changed from spinlock_t to struct mutex of different format. | Recompilation of a client program may be broken. |
| 3 | Type of field memory_used has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter pseudoflavor has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter authflavour has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nid 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 int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type enum drm_mm_search_flags has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type enum drm_mm_search_flags has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter file_priv of type struct drm_file* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter trace 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 | Parameter force 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 ring has been changed from struct intel_ring_buffer to struct drm_device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nid of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scaled of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ops of type struct rtnl_link_ops* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter net has been changed from struct net to struct rtable of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter rt has been changed from struct rtable to struct sk_buff of different format. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 3rd parameter skb has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter q has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter portid of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter report of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter authflavour has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter auth_probe of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter auth_probe of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mpss has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dentry has been changed from struct dentry to struct rpc_clnt of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scan_width of type enum nl80211_bss_scan_width has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter xnet of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max_page_order 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 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 | The pointer level of 8th parameter channel has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shift of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter scan_width of type enum nl80211_bss_scan_width has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter local has been changed from struct ieee80211_local to struct ieee80211_sub_if_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fixup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aio_ring_file has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field free_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field id has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field req_batch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct kiocb*, struct io_event*) to int()(struct kiocb*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field auxiliary has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ac_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field key_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field create has been changed from struct rpc_auth*(*)(struct rpc_clnt*, rpc_authflavor_t) to struct rpc_auth*(*)(struct rpc_auth_create_args*, struct rpc_clnt*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field crkey_to_expire has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field crkey_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | 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 channel_switch has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_coalesce has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_width 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 patterns has been changed from struct cfg80211_wowlan_trig_pkt_pattern to struct cfg80211_pkt_pattern. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field coalesce has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ss has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field read has been changed from ssize_t(*)(struct cgroup*, struct cftype*, struct file*, char*, size_t, loff_t*) to ssize_t(*)(struct cgroup_subsys_state*, struct cftype*, struct file*, char*, size_t, loff_t*). | Recompilation of a client program may be broken. |
| 3 | Base type of field read_map has been changed from int(*)(struct cgroup*, struct cftype*, struct cgroup_map_cb*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct cgroup_map_cb*). | Recompilation of a client program may be broken. |
| 4 | Base type of field read_s64 has been changed from s64(*)(struct cgroup*, struct cftype*) to s64(*)(struct cgroup_subsys_state*, struct cftype*). | Recompilation of a client program may be broken. |
| 5 | Base type of field read_seq_string has been changed from int(*)(struct cgroup*, struct cftype*, struct seq_file*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct seq_file*). | Recompilation of a client program may be broken. |
| 6 | Base type of field read_u64 has been changed from u64(*)(struct cgroup*, struct cftype*) to u64(*)(struct cgroup_subsys_state*, struct cftype*). | Recompilation of a client program may be broken. |
| 7 | Base type of field register_event has been changed from int(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, struct eventfd_ctx*, char const*). | Recompilation of a client program may be broken. |
| 8 | Base type of field trigger has been changed from int(*)(struct cgroup*, unsigned int) to int(*)(struct cgroup_subsys_state*, unsigned int). | Recompilation of a client program may be broken. |
| 9 | Base type of field unregister_event has been changed from void(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*) to void(*)(struct cgroup_subsys_state*, struct cftype*, struct eventfd_ctx*). | Recompilation of a client program may be broken. |
| 10 | Base type of field write has been changed from ssize_t(*)(struct cgroup*, struct cftype*, struct file*, char const*, size_t, loff_t*) to ssize_t(*)(struct cgroup_subsys_state*, struct cftype*, struct file*, char const*, size_t, loff_t*). | Recompilation of a client program may be broken. |
| 11 | Base type of field write_s64 has been changed from int(*)(struct cgroup*, struct cftype*, s64) to int(*)(struct cgroup_subsys_state*, struct cftype*, s64). | Recompilation of a client program may be broken. |
| 12 | Base type of field write_string has been changed from int(*)(struct cgroup*, struct cftype*, char const*) to int(*)(struct cgroup_subsys_state*, struct cftype*, char const*). | Recompilation of a client program may be broken. |
| 13 | Base type of field write_u64 has been changed from int(*)(struct cgroup*, struct cftype*, u64) to int(*)(struct cgroup_subsys_state*, struct cftype*, u64). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_css has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dummy_css 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*, struct cgroup_taskset*) to void(*)(struct cgroup_subsys_state*, struct cgroup_taskset*). | Recompilation of a client program may be broken. |
| 2 | Base type of field bind has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Recompilation of a client program may be broken. |
| 3 | Base type of field can_attach has been changed from int(*)(struct cgroup*, struct cgroup_taskset*) to int(*)(struct cgroup_subsys_state*, 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*, struct cgroup_taskset*) to void(*)(struct cgroup_subsys_state*, struct cgroup_taskset*). | Recompilation of a client program may be broken. |
| 5 | Base type of field css_alloc has been changed from struct cgroup_subsys_state*(*)(struct cgroup*) to struct cgroup_subsys_state*(*)(struct cgroup_subsys_state*). | Recompilation of a client program may be broken. |
| 6 | Base type of field css_free has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Recompilation of a client program may be broken. |
| 7 | Base type of field css_offline has been changed from void(*)(struct cgroup*) to void(*)(struct cgroup_subsys_state*). | Recompilation of a client program may be broken. |
| 8 | Base type of field css_online has been changed from int(*)(struct cgroup*) to int(*)(struct cgroup_subsys_state*). | Recompilation of a client program may be broken. |
| 9 | Base type of field exit has been changed from void(*)(struct cgroup*, struct cgroup*, struct task_struct*) to void(*)(struct cgroup_subsys_state*, struct cgroup_subsys_state*, struct task_struct*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ss has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field destroy_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field parent has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cgroup_idr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_clid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cl_pipedir_objects has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field coalesce has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field policy_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj_dev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field age_limit has been changed from int to long. | Recompilation of a client program may be broken. |
| 2 | Type of field dummy has been changed from int[2] to long[2]. | Recompilation of a client program may be broken. |
| 3 | Type of field nr_dentry has been changed from int to long. | Recompilation of a client program may be broken. |
| 4 | Type of field nr_unused has been changed from int to long. | Recompilation of a client program may be broken. |
| 5 | Type of field want_pages has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bus_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field drv_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field stats 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 page_flip has been changed from int(*)(struct drm_crtc*, struct drm_framebuffer*, struct drm_pending_vblank_event*) to int(*)(struct drm_crtc*, struct drm_framebuffer*, struct drm_pending_vblank_event*, uint32_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bridge has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field async_page_flip has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field num_bridge has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field bridge_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_bridges has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field agp_destroy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field render has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vma_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_tdi_phy_lpm has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field intr_unlink_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field intr_unlink_wait_cycle has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field hr_timeouts has been changed from ktime_t[10] to ktime_t[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field suppress_ifgroup has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field suppress_prefixlen has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field suppress has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dummy has been changed from int[5] to long[5]. | Recompilation of a client program may be broken. |
| 2 | Type of field nr_inodes has been changed from int to long. | Recompilation of a client program may be broken. |
| 3 | Type of field nr_unused has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_dio_done_wq 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 free_cached_objects has been changed from void(*)(struct super_block*, int) to long(*)(struct super_block*, long, int). | Recompilation of a client program may be broken. |
| 2 | Base type of field nr_cached_objects has been changed from int(*)(struct super_block*) to long(*)(struct super_block*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(struct kiocb*, loff_t, ssize_t, void*, int, bool) to void()(struct kiocb*, loff_t, ssize_t, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field high_prio_bh has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field low_prio_bh has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dp_mst has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_multi_io has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field oui has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field s3d_ext_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field s3d_struct has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vic has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field led_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_clock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field queue_flip has been changed from int(*)(struct drm_device*, struct drm_crtc*, struct drm_framebuffer*, struct drm_i915_gem_object*) to int(*)(struct drm_device*, struct drm_crtc*, struct drm_framebuffer*, struct drm_i915_gem_object*, uint32_t). | Recompilation of a client program may be broken. |
| 3 | Base type of field update_sprite_wm has been changed from void(*)(struct drm_device*, int, uint32_t, int, bool) to void(*)(struct drm_plane*, struct drm_crtc*, uint32_t, int, bool, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field active_bo has been changed from struct drm_i915_error_buffer* to struct drm_i915_error_buffer**. | Recompilation of a client program may be broken. |
| 2 | Type of field active_bo_count has been changed from u32 to u32*. | Recompilation of a client program may be broken. |
| 3 | Type of field pinned_bo has been changed from struct drm_i915_error_buffer* to struct drm_i915_error_buffer**. | Recompilation of a client program may be broken. |
| 4 | Type of field pinned_bo_count has been changed from u32 to u32*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vma_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pin_display has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ellc_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fbc has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field no_psr_reason has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pc8 has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field pm_irq_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ums has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field uncore has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field vm_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field wm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field object_stat_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mtrr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dpll_md has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mode_set has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_pdo has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | 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 scan_chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_counter_offset_beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field csa_counter_offset_presp has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field csa_finalize_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field csa_radar_required has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mc_qi has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mc_qri has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from int[26] to int[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field psr_dpcd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field psr_setup_done 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 write_infoframe has been changed from void(*)(struct drm_encoder*, struct dip_infoframe*) to void(*)(struct drm_encoder*, enum hdmi_infoframe_type, uint8_t const*, ssize_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field scratch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tunnels has been changed from struct hlist_head* to struct hlist_head[128]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field msg_ctlmax has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| 2 | Type of field msg_ctlmni has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| 3 | Type of field msg_ctlmnb has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mldv2_unsolicited_report_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mldv1_unsolicited_report_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field suppress_frag_ndisc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_may_mount has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ncq_send_recv_cmds has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel_switch_beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_active 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 rate_init has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*) to void(*)(void*, struct ieee80211_supported_band*, struct cfg80211_chan_def*, struct ieee80211_sta*, void*). | Recompilation of a client program may be broken. |
| 2 | Base type of field rate_update has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32) to void(*)(void*, struct ieee80211_supported_band*, struct cfg80211_chan_def*, struct ieee80211_sta*, void*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[28] to s8[29]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat has been changed from atomic_long_t[28] to atomic_long_t[29]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj_completion has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_unreg_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lower_dev_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_add_vxlan_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_del_vxlan_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ndo_get_phys_port_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_expect has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field seq_adjust has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[3] to u8[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field call_sync_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field shutdown_client has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_ds_clients has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cl_sp4_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cl_slot_tbl 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 read_rpc_prepare has been changed from void(*)(struct rpc_task*, struct nfs_read_data*) to int(*)(struct rpc_task*, struct nfs_read_data*). | Recompilation of a client program may be broken. |
| 2 | Base type of field init_client has been changed from struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t) to struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char const*). | Recompilation of a client program may be broken. |
| 3 | Base type of field open_context has been changed from struct inode*(*)(struct inode*, struct nfs_open_context*, int, struct iattr*) to struct inode*(*)(struct inode*, struct nfs_open_context*, int, struct iattr*, int*). | Recompilation of a client program may be broken. |
| 4 | Base type of field write_rpc_prepare has been changed from void(*)(struct rpc_task*, struct nfs_write_data*) to int(*)(struct rpc_task*, struct nfs_write_data*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field msi has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset_slot has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field migrate_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap2 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field time_zero has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field changed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field changed_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_xstatev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_load_next has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field last_h_load_update has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tk_pid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakee_flip_decay_ts has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field last_wakee has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field wakee_flips has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pending_events has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field expecting_lun_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field inode_init_security has been changed from int(*)(struct inode*, struct inode*, struct qstr const*, char**, void**, size_t*) to int(*)(struct inode*, struct inode*, struct qstr const*, char const**, void**, size_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nodes_to_scan has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_objects has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_deferred 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 u64[32] to u64[36]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field stream_memory_free has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cluster_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field discard_cluster_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field discard_cluster_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field discard_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field free_cluster_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field free_cluster_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field percpu_cluster has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notsent_lowat has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field binding_limits has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_hwmon has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tracing_cpumask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field priority has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sentinel has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field free has been changed from struct tty_buffer* to struct llist_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field winsize_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ldisc_sem has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field termios_rwsem has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field receive_buf2 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_sg_constraint has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[59] to unsigned long[63]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter pseudoflavor has been changed from rpc_authflavor_t to struct rpc_auth_create_args*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter status has been changed from unsigned long long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct drm_ioctl_desc[] to struct drm_ioctl_desc[] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nr_to_scan has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 9th parameter df has been changed from __be16 to bool. | Recompilation of a client program may be broken. |
| 2 | Type of 5th parameter dst has been changed from __be32 to __u8. | Recompilation of a client program may be broken. |
| 3 | Type of 3rd parameter skb has been changed from struct sk_buff* to __be32. | Recompilation of a client program may be broken. |
| 4 | Type of 8th parameter ttl has been changed from __u8 to __be16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter dest has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter src has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter dest has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter src has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from void(*)(struct sk_buff*, struct sk_buff*) to void(*)(struct sk_buff*, struct sk_buff const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[12] to struct event_constraint[13]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct static_key[9] to struct static_key[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[34] const to struct nla_policy[35] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 8th parameter channel has been changed from u8 to struct cfg80211_chan_def*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter max_length has been changed from u8 to u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[28] to atomic_long_t[29]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[89] const to char const*[94] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ki_obj has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field ki_pos has been changed from 5 to 6. | No effect. |
| 3 | The relative position of field ki_user_data has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member EHCI_HRTIMER_START_UNLINK_INTR with value 5 has been added. | No effect. |
| 2 | Value of member EHCI_HRTIMER_ASYNC_UNLINKS has been changed from 5 to 6. | No effect. |
| 3 | Value of member EHCI_HRTIMER_DISABLE_ASYNC has been changed from 8 to 9. | No effect. |
| 4 | Value of member EHCI_HRTIMER_DISABLE_PERIODIC has been changed from 7 to 8. | No effect. |
| 5 | Value of member EHCI_HRTIMER_IAA_WATCHDOG has been changed from 6 to 7. | No effect. |
| 6 | Value of member EHCI_HRTIMER_IO_WATCHDOG has been changed from 9 to 10. | No effect. |
| 7 | Value of member EHCI_HRTIMER_NUM_EVENTS has been changed from 10 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field action has been changed from 9 to 7. | No effect. |
| 2 | The relative position of field ctarget has been changed from 11 to 9. | No effect. |
| 3 | The relative position of field flags has been changed from 7 to 5. | No effect. |
| 4 | The relative position of field fr_net has been changed from 15 to 10. | No effect. |
| 5 | The relative position of field iifindex has been changed from 2 to 1. | No effect. |
| 6 | The relative position of field iifname has been changed from 12 to 13. | No effect. |
| 7 | The relative position of field mark has been changed from 4 to 3. | No effect. |
| 8 | The relative position of field mark_mask has been changed from 5 to 4. | No effect. |
| 9 | The relative position of field oifindex has been changed from 3 to 2. | No effect. |
| 10 | The relative position of field oifname has been changed from 13 to 14. | No effect. |
| 11 | The relative position of field pref has been changed from 6 to 12. | No effect. |
| 12 | The relative position of field rcu has been changed from 14 to 15. | No effect. |
| 13 | The relative position of field refcnt has been changed from 1 to 11. | No effect. |
| 14 | The relative position of field table has been changed from 8 to 6. | No effect. |
| 15 | The relative position of field target has been changed from 10 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rcu has been changed from 3 to 2. | No effect. |
| 2 | The relative position of field bpf_func has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field s_dentry_lru has been changed from 22 to 42. | No effect. |
| 2 | The relative position of field s_shrink has been changed from 41 to 39. | No effect. |
| 3 | The relative position of field s_uuid has been changed from 31 to 29. | No effect. |
| 4 | The relative position of field s_fs_info has been changed from 32 to 30. | No effect. |
| 5 | The relative position of field s_mode has been changed from 34 to 32. | No effect. |
| 6 | The relative position of field s_mtd has been changed from 26 to 24. | No effect. |
| 7 | The relative position of field s_options has been changed from 38 to 36. | No effect. |
| 8 | The relative position of field s_remove_count has been changed from 42 to 40. | No effect. |
| 9 | The relative position of field s_readonly_remount has been changed from 43 to 41. | No effect. |
| 10 | The relative position of field cleancache_poolid has been changed from 40 to 38. | No effect. |
| 11 | The relative position of field s_instances has been changed from 27 to 25. | No effect. |
| 12 | The relative position of field s_subtype has been changed from 37 to 35. | No effect. |
| 13 | The relative position of field s_bdev has been changed from 24 to 22. | No effect. |
| 14 | The relative position of field s_time_gran has been changed from 35 to 33. | No effect. |
| 15 | The relative position of field s_vfs_rename_mutex has been changed from 36 to 34. | No effect. |
| 16 | The relative position of field s_id has been changed from 30 to 28. | No effect. |
| 17 | The relative position of field s_max_links has been changed from 33 to 31. | No effect. |
| 18 | The relative position of field s_d_op has been changed from 39 to 37. | No effect. |
| 19 | The relative position of field s_writers has been changed from 29 to 27. | No effect. |
| 20 | The relative position of field s_bdi has been changed from 25 to 23. | No effect. |
| 21 | The relative position of field s_dquot has been changed from 28 to 26. | No effect. |
| 22 | The relative position of field s_inode_lru has been changed from 23 to 43. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_CACHE_WT with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pm_iir has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field vlv_work has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fb_tunnel_dev has been changed from 1 to 0. | No effect. |
| 2 | The relative position of field tunnels has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_ALLOC_BATCH with value 1 has been added. | No effect. |
| 2 | Value of member NR_ACTIVE_ANON has been changed from 2 to 3. | No effect. |
| 3 | Value of member NR_ACTIVE_FILE has been changed from 4 to 5. | No effect. |
| 4 | Value of member NR_ANON_PAGES has been changed from 7 to 8. | No effect. |
| 5 | Value of member NR_ANON_TRANSPARENT_HUGEPAGES has been changed from 26 to 27. | No effect. |
| 6 | Value of member NR_BOUNCE has been changed from 17 to 18. | No effect. |
| 7 | Value of member NR_DIRTIED has been changed from 24 to 25. | No effect. |
| 8 | Value of member NR_FILE_DIRTY has been changed from 10 to 11. | No effect. |
| 9 | Value of member NR_FILE_MAPPED has been changed from 8 to 9. | No effect. |
| 10 | Value of member NR_FILE_PAGES has been changed from 9 to 10. | No effect. |
| 11 | Value of member NR_FREE_CMA_PAGES has been changed from 27 to 28. | No effect. |
| 12 | Value of member NR_INACTIVE_ANON has been changed from 1 to 2. | No effect. |
| 13 | Value of member NR_INACTIVE_FILE has been changed from 3 to 4. | No effect. |
| 14 | Value of member NR_ISOLATED_ANON has been changed from 21 to 22. | No effect. |
| 15 | Value of member NR_ISOLATED_FILE has been changed from 22 to 23. | No effect. |
| 16 | Value of member NR_KERNEL_STACK has been changed from 15 to 16. | No effect. |
| 17 | Value of member NR_LRU_BASE has been changed from 1 to 2. | No effect. |
| 18 | Value of member NR_MLOCK has been changed from 6 to 7. | No effect. |
| 19 | Value of member NR_PAGETABLE has been changed from 14 to 15. | No effect. |
| 20 | Value of member NR_SHMEM has been changed from 23 to 24. | No effect. |
| 21 | Value of member NR_SLAB_RECLAIMABLE has been changed from 12 to 13. | No effect. |
| 22 | Value of member NR_SLAB_UNRECLAIMABLE has been changed from 13 to 14. | No effect. |
| 23 | Value of member NR_UNEVICTABLE has been changed from 5 to 6. | No effect. |
| 24 | Value of member NR_UNSTABLE_NFS has been changed from 16 to 17. | No effect. |
| 25 | Value of member NR_VMSCAN_IMMEDIATE has been changed from 19 to 20. | No effect. |
| 26 | Value of member NR_VMSCAN_WRITE has been changed from 18 to 19. | No effect. |
| 27 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 28 to 29. | No effect. |
| 28 | Value of member NR_WRITEBACK has been changed from 11 to 12. | No effect. |
| 29 | Value of member NR_WRITEBACK_TEMP has been changed from 20 to 21. | No effect. |
| 30 | Value of member NR_WRITTEN has been changed from 25 to 26. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NF_CT_EXT_SEQADJ with value 2 has been added. | No effect. |
| 2 | Value of member NF_CT_EXT_ACCT has been changed from 2 to 3. | No effect. |
| 3 | Value of member NF_CT_EXT_NUM has been changed from 3 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field event_entry has been changed from 1 to 0. | No effect. |
| 2 | The relative position of field group_entry has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SDEV_EVT_CAPACITY_CHANGE_REPORTED with value 3 has been added. | No effect. |
| 2 | The member SDEV_EVT_FIRST with value 1 has been added. | No effect. |
| 3 | The member SDEV_EVT_INQUIRY_CHANGE_REPORTED with value 2 has been added. | No effect. |
| 4 | The member SDEV_EVT_LUN_CHANGE_REPORTED with value 6 has been added. | No effect. |
| 5 | The member SDEV_EVT_MODE_PARAMETER_CHANGE_REPORTED with value 5 has been added. | No effect. |
| 6 | The member SDEV_EVT_SOFT_THRESHOLD_REACHED_REPORTED with value 4 has been added. | No effect. |
| 7 | Value of member SDEV_EVT_LAST has been changed from 1 to 6. | No effect. |
| 8 | Value of member SDEV_EVT_MAXBITS has been changed from 2 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field list has been changed from 3 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tail has been changed from 3 to 5. | No effect. |
| 2 | The relative position of field lock has been changed from 1 to 2. | No effect. |
| 3 | The relative position of field free has been changed from 4 to 3. | No effect. |
| 4 | The relative position of field memory_used has been changed from 5 to 4. | No effect. |
| 5 | The relative position of field work has been changed from 0 to 1. | No effect. |
| 6 | The relative position of field head has been changed from 2 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter iocb has been renamed to req. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pseudoflavor has been renamed to args. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to policy. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter root has been renamed to parent. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to long. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter offset has been renamed to nextoff. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter flag has been renamed to gb_flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ring has been renamed to dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to long. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter enable has been renamed to enabled. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been renamed to rt. | No effect. |
| 2 | 2nd parameter rt has been renamed to skb. | No effect. |
| 3 | 3rd parameter skb has been renamed to src. | No effect. |
| 4 | 4th parameter src has been renamed to dst. | No effect. |
| 5 | 5th parameter dst has been renamed to proto. | No effect. |
| 6 | 6th parameter proto has been renamed to tos. | No effect. |
| 7 | 7th parameter tos has been renamed to ttl. | No effect. |
| 8 | 8th parameter ttl has been renamed to df. | No effect. |
| 9 | 9th parameter df has been renamed to xnet. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter pre_order_visit has been renamed to descending_callback. | No effect. |
| 2 | 6th parameter post_order_visit has been renamed to ascending_callback. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter pre_order_visit has been renamed to descending_callback. | No effect. |
| 2 | 5th parameter post_order_visit has been renamed to ascending_callback. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sta has been renamed to pubsta. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter res has been renamed to resp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dentry has been renamed to rpc_client. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter addr has been renamed to src. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter channel has been renamed to chandef. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter shrink has been renamed to shrinkctl. | No effect. |