| Module Name | vmlinux |
|---|---|
| Version #1 | 3.10.19 |
| Version #2 | 3.11.8 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 795 |
|---|---|
| Total Source Files | 1460 |
| Total Objects | 1 |
| Total Symbols / Types | 16865 / 9390 |
| Verdict | Incompatible (43.3%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 325 |
| Removed Symbols | High | 108 |
| Problems with Data Types | High | 64 |
| Medium | 344 | |
| Low | 290 | |
| Problems with Symbols | High | 35 |
| Medium | 373 | |
| Low | 56 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 7 |
| Change | Effect | |
|---|---|---|
| 1 | Field physical_node_id_bitmap has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field removal_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field resolved_node has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup_work has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sme_state has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cft_q_node has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field free_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. |
| 3 | Field allcg_node has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allcg_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 actual_subsys_mask has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field devlist_mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sched_scan_mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wowlan has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_lock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field map_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 enabled has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gamma_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. |
| 3 | Field gamma_store has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_completed_io_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_unwritten_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 s_max_writeback_mb_bump has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bios_lvds_val has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 child_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 child_dev_num has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field crt_ddc_pin has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 edp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 int_tv_support has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 lvds_border_bits has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field lvds_ssc_freq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 num_pch_pll has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pch_pf_pos has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pch_pf_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. |
| 12 | Field pch_plls has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hangcheck_count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field last_acthd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field prev_instdone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_frame_registrations has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field channel has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 channel_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_beacon has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field conf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pch_pll has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pixel_target_clock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fnhe_rth has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field j_wait_checkpoint has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 j_wait_logspace has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field t_iobuf_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 t_log_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 unmap_area has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_area_cache has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 cached_hole_size has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field jiffies_interval has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_weight has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scoreboard_skb_hint has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_cpu has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field waiter has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_cpu has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 3rd middle parameter filldir has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter offset has been changed from unsigned long (4 bytes) to unsigned int (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 | 2nd middle parameter d has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter nowtime has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter handle of type handle_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 3rd middle parameter dirent 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 hub of type struct usb_hub* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 3rd middle parameter filldir 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 intel_crtc of type struct intel_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. |
| 2 | Parameter pipe_config of type struct intel_crtc_config* 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 | 3rd middle parameter mode has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter filp has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter end 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. |
| 2 | The pointer level of 1st parameter start has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter offset of type int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter log_bufs of type struct list_head* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter nowtime has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rsv_blocks of type int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sband of type struct ieee80211_supported_band* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter local has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter name 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 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field physical_node_count has been changed from u8 (1 byte) to unsigned int (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field performance_manageable 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. |
| 2 | Field suprise_removal_ok 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 full_pathname has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field node_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. |
| 4 | Field parent_package has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 predefined has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 return_btype has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 return_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. |
| 8 | Type of field param_count has been changed from u8 (1 byte) to u16 (2 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | The relative position of field obj_desc has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field parameters has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tcfc_rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (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 compare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 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 minorversion has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notified 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 auth_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 chain_signal_avg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field wowlan has been changed from struct wiphy_wowlan_support (24 bytes) to struct wiphy_wowlan_support const* (4 bytes). | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field wowlan_config 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 | The pointer level of field wowlan 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 destroy_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field css_kill_cnt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field serial_nr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 refcnt has been changed from struct atomic_t (4 bytes) to struct percpu_ref (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 | Size of field top_cgroup has been changed from 180 bytes to 172 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 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 governor_enabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field d_lock has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field online has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 offline has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_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 counts 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 depth 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 devices 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 event_context 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 event_fn has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | Field highs has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | Field holders has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | Field immutable_target_type has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | Field index has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | Field integrity_supported has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | Field mempools has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | Field mode has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | Field num_allocated has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | Field num_targets has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | Field singleton 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. |
| 16 | Field target_callbacks 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. |
| 17 | Field targets has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | Field type 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 io_barrier has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 map has been changed from 17 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kdev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field old_fb has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor_set2 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field helper_private has been removed from the middle position of this structural type. | 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_unpin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gem_prime_mmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kdev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field napi has been changed from 52 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field convert_pointer 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. |
| 2 | The pointer level of field get_next_high_mono_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 get_next_variable 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. |
| 4 | The pointer level of field get_time 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. |
| 5 | The pointer level of field get_variable 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. |
| 6 | The pointer level of field get_wakeup_time 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. |
| 7 | The pointer level of field query_capsule_caps 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. |
| 8 | The pointer level of field query_variable_info 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. |
| 9 | The pointer level of field reset_system 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. |
| 10 | The pointer level of field set_time 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. |
| 11 | The pointer level of field set_variable 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. |
| 12 | The pointer level of field set_virtual_address_map 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. |
| 13 | The pointer level of field set_wakeup_time 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. |
| 14 | The pointer level of field update_capsule has been increased from 0 to 1. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 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 i_rsv_conversion_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 i_rsv_conversion_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. |
| 3 | Field i_touch_when has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 i_unrsv_conversion_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. |
| 5 | Field i_unrsv_conversion_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 bio has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 handle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_es_last_sorted has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vol_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_dirty_writeback has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_link_cpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field fl_link has been changed from struct list_head to struct hlist_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lm_owner_key has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field part0 has been changed from 304 bytes to 308 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field __dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field creds 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 | Type of field pcm_dev_bits has been changed from unsigned long[8] (32 bytes) to unsigned long[1] (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field auto_mute_via_amp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mute_bits has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_linetime_wm has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field waiting has been changed from bool[3] (3 bytes) to bool[4] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field acthd has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field cpu_ring_head has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field cpu_ring_tail has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Type of field ctl has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Type of field faddr has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Type of field fault_reg has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Type of field head has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Type of field instdone has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 10 | Type of field instpm has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Type of field instps has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 12 | Type of field ipehr has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 13 | Type of field ipeir has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 14 | Type of field rc_psmi has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 15 | Type of field ring has been changed from struct drm_i915_error_ring[3] (60 bytes) to struct drm_i915_error_ring[4] (80 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 16 | Type of field semaphore_mboxes has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 17 | Type of field semaphore_seqno has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 18 | Type of field seqno has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 19 | Type of field tail has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hpd_event_bits has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_shared_dpll has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field power_well has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 shared_dplls has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vbt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vlv_pctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Size of field gmbus has been changed from 2544 bytes to 2568 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Size of field gpu_error has been changed from 132 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field gtt has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 10 | Size of field rps has been changed from 128 bytes to 204 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Type of field ring has been changed from struct intel_ring_buffer[3] (588 bytes) to struct intel_ring_buffer[4] (944 bytes). | 1) Size of the inclusive type has been 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 | Field display_clock_mode has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 13 | Field fdi_rx_polarity_inverted has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 14 | Field int_crt_support has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 15 | Field lvds_dither has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 16 | Field lvds_use_ssc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 17 | Field lvds_vbt has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ref has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pte_encode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_vebox_ring has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | The relative position of field has_force_wake has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field is_haswell has been changed from 16 to 15. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rpe_delay has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vlv_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field adapter has been changed from 372 bytes to 376 bytes. | 1) Size of the inclusive type has been 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 beacon_rate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_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 mbss_changed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field mshcfg has been changed from 68 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field u has been changed from 716 bytes to 700 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field wdev has been changed from 192 bytes to 172 bytes. | 1) Size of the inclusive type has been 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 vif has been changed from 228 bytes to 232 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 ibss has been changed from 168 bytes to 148 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field mgd has been changed from 500 bytes to 476 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field mesh has been changed from 716 bytes to 700 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 rs_timer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mc_dad_timer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field valid_ll_addr_cnt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field rs_probes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_hash has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field icsk_inet has been changed from 560 bytes to 568 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sk has been changed from 424 bytes to 432 bytes. | 1) Size of the inclusive type has been 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 mc_hash has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field metrics has been changed from u32[14] (56 bytes) to u32[15] (60 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_transcoders has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power_well_driver has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pipe has been changed from 96 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hblank 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 hsync 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 htotal 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 vblank 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 vsync 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 vtotal 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 860 bytes to 864 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 792 bytes to 796 bytes. | 1) Size of the inclusive type has been 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 config has been changed from 456 bytes to 544 bytes. | 1) Size of the inclusive type has been 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 fdi_lanes 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_hw_state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field port_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. |
| 3 | Field quirks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sdvo_tv_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. |
| 5 | Field shared_dpll has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Size of field dpll has been changed from 20 bytes to 36 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 104 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_pch_edp has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field needs_tv_clock has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field semaphore_register has been changed from u32[3] (12 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field sync_seqno has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field signal_mbox has been changed from u32[2] (8 bytes) to u32[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Field last_context_obj 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 fnhe_genid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fnhe_rth_input has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fnhe_rth_output has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_calc_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 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 | Size of field irq_data has been changed from 40 bytes to 44 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_rsv_handle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field h_reserved has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field j_reserved_credits has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 j_wait_reserved has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field device has been changed from 2728 bytes to 2736 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 3312 bytes to 3324 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field tdev has been changed from 228 bytes to 232 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field local_port_no 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 transmit_led_message has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 a_args has been changed from 320 bytes to 324 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field a_res has been changed from 300 bytes to 304 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_rate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 chains has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field bss_conf has been changed from 204 bytes to 208 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_sync_action has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field slot has been changed from 1 byte to 7 bits. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field grp 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 nvec_used has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ipvs 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 mpls_features has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_busy_poll has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ndo_set_vf_link_state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field type_def has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_target_max_rqst_sz 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 fc_target_max_resp_sz 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 attr_bitmask_nl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cache_consistency_bitmask has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field label has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_label has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 grp 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 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 228 bytes to 232 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 unnamed0 has been changed from 80 bytes to 84 bytes. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hrtimer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 hrtimer_interval has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hrtimer_interval_ms has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field late_ack has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 pmu has been changed from 88 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member PHY_INTERFACE_MODE_RGMII has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member PHY_INTERFACE_MODE_RGMII_ID has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member PHY_INTERFACE_MODE_RGMII_RXID has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member PHY_INTERFACE_MODE_RGMII_TXID has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member PHY_INTERFACE_MODE_RMII has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member PHY_INTERFACE_MODE_RTBI has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member PHY_INTERFACE_MODE_SMII has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field expires has been changed from union cpu_time_count to unsigned long long of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field incr has been changed from union cpu_time_count to unsigned long long of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field of_node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hard_math has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (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 | The relative position of field bstats has been changed from 19 to 18. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field rate_est has been changed from 10 to 13. | 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 refcnt has been changed from 9 to 23. | 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 callback_head has been changed from 22 to 21. | 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 q has been changed from 18 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field __state has been changed from 20 to 19. | 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 busylock has been changed from 23 to 24. | 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 padded has been changed from 3 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 qstats has been changed from 21 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field u32_node has been changed from 12 to 10. | 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 limit has been changed from 24 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field next_sched has been changed from 15 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field gso_skb has been changed from 16 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field reshape_fail has been changed from 11 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field state has been changed from 17 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field __parent has been changed from 13 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field dev_queue has been changed from 14 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field removed_load has been changed from struct atomic64_t (8 bytes) to atomic_long_t (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field runnable_load_avg has been changed from u64 (8 bytes) to unsigned long (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field blocked_load_avg has been changed from u64 (8 bytes) to unsigned long (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 4 | Type of field tg_load_contrib has been changed from u64 (8 bytes) to unsigned long (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. |
| 5 | The relative position of field last_decay has been changed from 16 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field removed_load has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cfs has been changed from 144 bytes to 128 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field css has been changed from 32 bytes to 52 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field load_avg has been changed from struct atomic64_t (8 bytes) to atomic_long_t (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 ptrace_bp_refcnt 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 eh_timeout has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field sdev_dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field sdev_gendev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field shost_dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field shost_gendev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry_init_security has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ismaclabel has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field inner_network_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field inner_transport_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field inner_mac_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 4 | Type of field transport_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 5 | Type of field network_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 6 | Type of field mac_header has been changed from sk_buff_data_t (4 bytes) to __u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 7 | Field inner_protocol 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. |
| 8 | Field unnamed2 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. |
| 9 | The relative position of field secmark has been changed from 44 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field unnamed1 has been changed from 45 to 44. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member CFG80211_CONN_AUTHENTICATE_NEXT has been changed from 3 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member CFG80211_CONN_AUTHENTICATING has been changed from 4 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member CFG80211_CONN_SCANNING has been changed from 1 to 0. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member CFG80211_CONN_SCAN_AGAIN has been changed from 2 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[95] (380 bytes) to unsigned long[96] (384 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_napi_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sk_ll_usec has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal_avg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 chain_signal_last has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field chains has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 rq_cred 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 | Size of field inet_conn has been changed from 828 bytes to 836 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tclass has been changed from 76 bytes to 80 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field class has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field minimum_to_wake has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fasync has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field usb2_hw_lpm_besl_capable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 l1_params has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 228 bytes to 232 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 260 bytes to 264 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fl has been changed from 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 may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 260 bytes to 264 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 this global data has been changed from 176 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter idev 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 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter filldir 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 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter length of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter offset 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 page became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter wiphy_idx 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 rq 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 68 bytes to 72 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 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct snd_card*[32] (128 bytes) to struct snd_card*[8] (32 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 128 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter inode 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 | Parameter label of type struct nfs4_label* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter srcu_idx of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter md 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 228 bytes to 232 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter 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 flags became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter obj became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[15] const (60 bytes) to u32[16] const (64 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter now of type struct timespec* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Type of return value has been changed from unsigned long (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rsv_blocks of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter chunk has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sb has been changed from struct super_block (640 bytes) to struct ext4_sb_info (832 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sb has been changed from struct super_block (640 bytes) to struct ext4_sb_info (832 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mapping 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 offset 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 page became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter k became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter size became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter skb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter curr 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 pi 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 uaddr became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter r has been changed from struct gnet_stats_rate_est (8 bytes) to struct gnet_stats_rate_est64 (16 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter b 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 d became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter r 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 | 3rd parameter filldir has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter filldir 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter codec 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 direct became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter nid became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mm became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sz 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 addr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mm became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter chunk has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter file has been changed from struct file (144 bytes) to struct inode (336 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter label of type struct nfs4_label* 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clock has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter m has been changed from struct seq_file (76 bytes) to struct drm_i915_error_state_buf (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ring of type struct intel_ring_buffer* 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 bool (1 byte) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter m has been changed from struct seq_file (76 bytes) to struct drm_i915_error_state_buf (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter adjusted_mode has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter enable of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 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 | Parameter protocol of type u8 const 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 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct journal_head (60 bytes) to struct buffer_head (56 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter jh_out has been changed from struct journal_head (60 bytes) to struct buffer_head (56 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter filldir 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. |
| 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 | Type of this global data has been changed from struct ucode_cpu_info[8] (160 bytes) to struct ucode_cpu_info[] (4 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct netlbl_domaddr4_map (28 bytes) to struct netlbl_dommap_def (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct netlbl_domaddr6_map (48 bytes) to struct netlbl_dommap_def (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const (8 bytes) to u32[3] const (12 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const (8 bytes) to u32[3] const (12 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const (8 bytes) to u32[3] const (12 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter minorversion of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct acpi_predefined_data (28 bytes) to struct acpi_evaluate_info (52 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 288 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter constraints has been changed from struct event_constraint (36 bytes) to struct perf_event (584 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 244 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter phydev 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 228 bytes to 232 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 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 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 284 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 131 bytes to 130 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 404 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 1100 bytes to 1104 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 424 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 380 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 120 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 296 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 4420 bytes to 4400 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 180 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1424 bytes to 1408 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 144 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 32 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 96 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 1288 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 180 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 784 bytes to 788 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter name has been changed from struct qstr (12 bytes) to char (1 byte). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter name has been changed from struct qstr (12 bytes) to char (1 byte). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter now of type struct timespec* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Type of return value has been changed from unsigned long (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter now 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 miter became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed 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 1100 bytes to 1104 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 404 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 1100 bytes to 1104 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 424 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 380 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 120 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4420 bytes to 4400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 180 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1424 bytes to 1408 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 144 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 32 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 96 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 1288 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 180 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 1100 bytes to 1104 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 148 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 404 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 1100 bytes to 1104 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 424 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 380 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 120 bytes to 124 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 296 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 4420 bytes to 4400 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 180 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 32 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 96 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 4420 bytes to 4400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 1424 bytes to 1408 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 144 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 180 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 32 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 96 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 64 bytes to 72 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 1288 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 232 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 12 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 228 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 180 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4420 bytes to 4400 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 180 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 32 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 96 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 424 bytes to 412 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1424 bytes to 1408 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 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 | Parameter kern_flags of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter set_kern_flags of type unsigned long* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prev_bssid of type u8 const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bss has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct net_device (1088 bytes) to struct wireless_dev (172 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mntroot 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 mount_info 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 s became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter lru has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter lru 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sk has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The pointer level of return value has been decreased from 1 to 0. | Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash. |
| 3 | Type of return value has been changed from struct tcp_md5sig_pool* (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter journal 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 length of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter length of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lstart 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 mapping became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 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 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter band 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 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 600 bytes to 596 bytes. | The fields or parameters of 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 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 28 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field pathname has been renamed to relative_pathname. | 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 100 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field plat_data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 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 irq_desc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 596 bytes to 600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden 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 316 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field plink_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 68 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field basic_rates has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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 116 bytes to 124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field chains 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 wowlan became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 172 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 180 bytes to 172 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field css_sets has been renamed to cset_links. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cg_link has been renamed to cset_link. | 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 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 4420 bytes to 4400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cg_links has been renamed to cgrp_links. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner 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 owner 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 412 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 832 bytes to 736 bytes. | The fields or parameters of 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 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field index has been renamed to driver_data. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field transition_ongoing has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 140 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpumask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 784 bytes to 788 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_lockref 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 d_compare has been changed from int(*)(struct dentry const*, struct inode const*, struct dentry const*, struct inode const*, unsigned int, char const*, struct qstr const*) to int(*)(struct dentry const*, struct dentry const*, unsigned int, char const*, struct qstr const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field d_hash has been changed from int(*)(struct dentry const*, struct inode const*, struct qstr*) to int(*)(struct dentry const*, struct qstr*). | 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 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field offline has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 offline_disabled has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 228 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 200 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field md has been renamed to undefined__. | 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 332 bytes to 432 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 860 bytes to 864 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 792 bytes to 796 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 356 bytes to 340 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 256 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 332 bytes to 336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 348 bytes to 352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2004 bytes to 2016 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 convert_pointer has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field get_next_high_mono_count has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field get_next_variable has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field get_time has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field get_variable has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field get_wakeup_time has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field query_capsule_caps has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field query_variable_info has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field reset_system has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field set_time has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 11 | Type of field set_variable has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 12 | Type of field set_virtual_address_map has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 13 | Type of field set_wakeup_time has been changed from unsigned long to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 14 | Type of field update_capsule has been changed from unsigned long to void*. | 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 236 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 612 bytes to 640 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 36 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unrsv_conversion_wq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 768 bytes to 832 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field dio_unwritten_wq has been renamed to rsv_conversion_wq. | 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 2280 bytes to 2284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 76 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field invalidatepage has been changed from void(*)(struct page*, unsigned long) to void(*)(struct page*, unsigned int, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Field readdir has been renamed to iterate. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field tmpfile 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 | Field fu_llist has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 404 bytes to 408 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 304 bytes to 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field napi has been changed from 52 bytes to 64 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 104 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 228 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field no_response_fallback 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 2668 bytes to 2676 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3800 bytes to 3804 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 244 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 372 bytes to 376 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 276 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock 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 find_dpll has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Base type of field update_sprite_wm has been changed from void(*)(struct drm_device*, int, uint32_t, int) to void(*)(struct drm_device*, int, uint32_t, int, bool). | 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 656 bytes to 784 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_list has been renamed to global_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8448 bytes to 8932 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pte_encode has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hang_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 20 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 has_ddi 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 has_fpga_dbg 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 128 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 424 bytes to 428 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 168 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 500 bytes to 476 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 716 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 | Size of this type has been changed from 84 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1780 bytes to 1748 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 716 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 | Size of this type has been changed from 296 bytes to 404 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mc_dad_count has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field peer_addr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 140 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field probes has been renamed to dad_probes. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field timer has been renamed to dad_timer. | 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 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 | Size of this type has been changed from 828 bytes to 836 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 560 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 276 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 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 692 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field transcoder has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 228 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 m has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 p has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field vco has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Size of this type has been changed from 20 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Type of field m1 has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field m2 has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field n has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field p1 has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field p2 has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 888 bytes to 892 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_fifo_underrun_disabled has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 2080 bytes to 2168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field pch_fifo_underrun_disabled 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 fdi_lanes has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 fdi_m_n has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 gmch_pfit has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ips_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. |
| 5 | Field pch_pfit has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Size of this type has been changed from 456 bytes to 544 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Field bw_constrained 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 704 bytes to 708 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field adapter has been changed from 372 bytes to 376 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 104 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hangcheck has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 last_context has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 196 bytes to 236 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field fbc_dirty 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 lookup_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 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 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 28 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field h_transaction 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 736 bytes to 728 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 140 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1364 bytes to 1368 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3312 bytes to 3324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 240 bytes to 244 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 716 bytes to 724 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 204 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 228 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 712 bytes to 720 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 424 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 exact_match 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 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 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fnhe_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 | Field napi_hash_node has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field napi_id has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 52 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 1088 bytes to 1152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 176 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field backlog has been changed from 52 bytes to 64 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field flow_limit 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 def 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 compare has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 | Base type of field reclaim_complete has been changed from int(*)(struct nfs_client*) to int(*)(struct nfs_client*, struct rpc_cred*). | 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 700 bytes to 692 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 936 bytes to 952 bytes. | The fields or parameters of 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 268 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field getattr has been changed from int(*)(struct nfs_server*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct nfs_server*, struct nfs_fh*, struct nfs_fattr*, struct nfs4_label*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field lookup has been changed from int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*, struct nfs4_label*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid_ns has been renamed to pid_ns_for_children. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 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 404 bytes to 408 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 844 bytes to 848 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 252 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 244 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field ops has been changed from struct snd_pcm_ops* to struct snd_pcm_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field constraint has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field full_width_write 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 abort 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 in_tx 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 180 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 88 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | 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. |
| 3 | 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 244 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 80 bytes to 84 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 436 bytes to 440 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 476 bytes to 480 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field is_internal has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 260 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 328 bytes to 332 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 388 bytes to 392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 124 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 672 bytes to 676 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 564 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_bps has been renamed to rate_bytes_ps. | 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 148 bytes to 256 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 __parent 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 __state has been changed from unsigned int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field __parent has been changed from struct Qdisc* 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 144 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1424 bytes to 1408 bytes. | The fields or parameters of 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 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1288 bytes to 1284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 684 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 308 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 | Size of this type has been changed from 720 bytes to 728 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 688 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field sb_set_mnt_opts has been changed from int(*)(struct super_block*, struct security_mnt_opts*) to int(*)(struct super_block*, struct security_mnt_opts*, unsigned long, unsigned long*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 384 bytes to 388 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field inner_network_header 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. |
| 2 | The pointer level of field inner_transport_header has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | The pointer level of field inner_mac_header has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 4 | The pointer level of field transport_header has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 5 | The pointer level of field network_header has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 6 | The pointer level of field mac_header has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved_tailroom has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 2 | Field mark has been renamed to napi_id. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field dropcount has been renamed to dma_cookie. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 7 has been changed from CFG80211_CONN_DEAUTH_ASSOC_FAIL to CFG80211_CONN_ASSOC_FAILED. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | The member CFG80211_CONN_IDLE has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 380 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 424 bytes to 432 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 572 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 880 bytes to 936 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3624 bytes to 3628 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_gss_mech has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bin_attrs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1288 bytes to 1292 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 304 bytes to 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 456 bytes to 460 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 88 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 596 bytes to 608 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 280 bytes to 284 bytes. | The fields or parameters of 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 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Field for_sync 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 get_wallclock has been changed from unsigned long(*)() to void(*)(struct timespec*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field set_wallclock has been changed from int(*)(unsigned long) to int(*)(struct timespec const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ulog_warn_deprecated 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 320 bytes to 324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 260 bytes to 264 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Field local_error has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1100 bytes to 1104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter parent has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd 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 | Type of 1st parameter connector has been changed from struct drm_connector* to struct drm_connector const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter encoder has been changed from struct drm_encoder* to struct drm_encoder const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nowtime has been renamed to now. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter nowtime has been changed from unsigned long to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nblocks has been renamed to blocks. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nrblocks has been renamed to extents. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sb has been renamed to sbi. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sb has been renamed to sbi. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st 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 filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter file has been renamed to inode. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter jh_out has been renamed to bh_out. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter blocknr has been changed from unsigned long long to sector_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter end has been changed from unsigned long to void*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter start has been changed from unsigned long to void*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter ops has been changed from struct snd_pcm_ops* to struct snd_pcm_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter constraints has been renamed to events. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter ppos has been changed from loff_t* to loff_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nowtime has been renamed to now. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter nowtime has been changed from unsigned long to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 0 to 1. | Applications will treat the return value as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 2 | Type of return value has been changed from int to int(*)(). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter offset has been changed from unsigned long to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter offset has been changed from unsigned long to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter name has been changed from u32 to char*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member CFG80211_CONN_AUTH_FAILED with value 4 has been added. | No effect. |
| 2 | The member CFG80211_CONN_CONNECTED with value 9 has been added. | No effect. |
| 3 | The member CFG80211_CONN_DEAUTH with value 8 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member VECS with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_CHAN_WIDTH_10 with value 7 has been added. | No effect. |
| 2 | The member NL80211_CHAN_WIDTH_5 with value 6 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_REVMII with value 5 has been added. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.10.19 |
| Version #2 | 3.11.8 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 795 |
|---|---|
| Total Source Files | 1460 |
| Total Objects | 1 |
| Total Symbols / Types | 16882 / 9390 |
| Verdict | Incompatible (50.1%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 326 |
| Removed Symbols | High | 111 |
| Problems with Data Types | High | 130 |
| Medium | 29 | |
| Low | 240 | |
| Problems with Symbols | High | 29 |
| Medium | 76 | |
| Low | 22 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 45 |
| Other Changes in Symbols | - | 32 |
| Change | Effect | |
|---|---|---|
| 1 | Field physical_node_id_bitmap 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 'physical_node_id_bitmap'. |
| 2 | Field removal_type 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 'removal_type'. |
| Change | Effect | |
|---|---|---|
| 1 | Field performance_manageable 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 'performance_manageable'. |
| 2 | Field suprise_removal_ok 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 'suprise_removal_ok'. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_pci_root' has no member named 'node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field resolved_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_evaluate_info' has no member named 'resolved_node'. |
| 2 | Field pathname has been renamed to relative_pathname. | Recompilation of a client program may be broken with the error message: struct acpi_evaluate_info has no member named pathname. |
| Change | Effect | |
|---|---|---|
| 1 | Field sme_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'sme_state'. |
| 2 | Field cleanup_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'cleanup_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'free_work'. |
| 2 | Field allcg_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'allcg_node'. |
| 3 | Field count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'count'. |
| 4 | Field cft_q_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'cft_q_node'. |
| 5 | Field css_sets has been renamed to cset_links. | Recompilation of a client program may be broken with the error message: struct cgroup has no member named css_sets. |
| Change | Effect | |
|---|---|---|
| 1 | Field cg_link has been renamed to cset_link. | Recompilation of a client program may be broken with the error message: struct cgroup_iter has no member named cg_link. |
| Change | Effect | |
|---|---|---|
| 1 | Field allcg_list 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 'allcg_list'. |
| 2 | Field actual_subsys_mask 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 'actual_subsys_mask'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cg_links has been renamed to cgrp_links. | Recompilation of a client program may be broken with the error message: struct css_set has no member named cg_links. |
| Change | Effect | |
|---|---|---|
| 1 | Field devlist_mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_registered_device' has no member named 'devlist_mtx'. |
| 2 | Field mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_registered_device' has no member named 'mtx'. |
| 3 | Field sched_scan_mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_registered_device' has no member named 'sched_scan_mtx'. |
| 4 | Field wowlan has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_registered_device' has no member named 'wowlan'. |
| Change | Effect | |
|---|---|---|
| 1 | Field index has been renamed to driver_data. | Recompilation of a client program may be broken with the error message: struct cpufreq_frequency_table has no member named index. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dentry' has no member named 'd_count'. |
| 2 | Field d_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dentry' has no member named 'd_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field counts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'counts'. |
| 2 | Field depth has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'depth'. |
| 3 | Field devices has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'devices'. |
| 4 | Field event_context has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'event_context'. |
| 5 | Field event_fn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'event_fn'. |
| 6 | Field highs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'highs'. |
| 7 | Field holders has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'holders'. |
| 8 | Field immutable_target_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'immutable_target_type'. |
| 9 | Field index has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'index'. |
| 10 | Field integrity_supported has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'integrity_supported'. |
| 11 | Field mempools has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'mempools'. |
| 12 | Field mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'mode'. |
| 13 | Field num_allocated has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'num_allocated'. |
| 14 | Field num_targets has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'num_targets'. |
| 15 | Field singleton has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'singleton'. |
| 16 | Field target_callbacks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'target_callbacks'. |
| 17 | Field targets has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'targets'. |
| 18 | Field type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_table' has no member named 'type'. |
| 19 | Field md has been renamed to undefined__. | Recompilation of a client program may be broken with the error message: struct dm_table has no member named md. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mapped_device' has no member named 'io_lock'. |
| 2 | Field map_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mapped_device' has no member named 'map_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_plane' has no member named 'enabled'. |
| 2 | Field gamma_size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_plane' has no member named 'gamma_size'. |
| 3 | Field gamma_store has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_plane' has no member named 'gamma_store'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_completed_io_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_completed_io_list'. |
| 2 | Field i_unwritten_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_unwritten_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_max_writeback_mb_bump 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 's_max_writeback_mb_bump'. |
| 2 | Field dio_unwritten_wq has been renamed to rsv_conversion_wq. | Recompilation of a client program may be broken with the error message: struct ext4_sb_info has no member named dio_unwritten_wq. |
| Change | Effect | |
|---|---|---|
| 1 | Field readdir has been renamed to iterate. | Recompilation of a client program may be broken with the error message: struct file_operations has no member named readdir. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_linetime_wm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'update_linetime_wm'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_list has been renamed to global_list. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named gtt_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field bios_lvds_val 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 'bios_lvds_val'. |
| 2 | Field child_dev 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 'child_dev'. |
| 3 | Field child_dev_num 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 'child_dev_num'. |
| 4 | Field crt_ddc_pin 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 'crt_ddc_pin'. |
| 5 | Field display_clock_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 'display_clock_mode'. |
| 6 | Field edp 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 'edp'. |
| 7 | Field fdi_rx_polarity_inverted 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 'fdi_rx_polarity_inverted'. |
| 8 | Field int_crt_support 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 'int_crt_support'. |
| 9 | Field int_tv_support 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 'int_tv_support'. |
| 10 | Field lvds_border_bits 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 'lvds_border_bits'. |
| 11 | Field lvds_dither 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 'lvds_dither'. |
| 12 | Field lvds_ssc_freq 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 'lvds_ssc_freq'. |
| 13 | Field lvds_use_ssc 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 'lvds_use_ssc'. |
| 14 | Field lvds_vbt 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 'lvds_vbt'. |
| 15 | Field num_pch_pll has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'num_pch_pll'. |
| 16 | Field pch_pf_pos 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 'pch_pf_pos'. |
| 17 | Field pch_pf_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 'pch_pf_size'. |
| 18 | Field pch_plls 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 'pch_plls'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hangcheck_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gpu_error' has no member named 'hangcheck_count'. |
| 2 | Field last_acthd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gpu_error' has no member named 'last_acthd'. |
| 3 | Field prev_instdone has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i915_gpu_error' has no member named 'prev_instdone'. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_frame_registrations has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'auth_frame_registrations'. |
| 2 | Field channel has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'channel'. |
| 3 | Field channel_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'channel_type'. |
| 4 | Field mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'mtx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_managed' has no member named 'mtx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_mesh' has no member named 'mtx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_beacon has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_mgd_assoc_data' has no member named 'have_beacon'. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_dev' has no member named 'next'. |
| Change | Effect | |
|---|---|---|
| 1 | Field probes has been renamed to dad_probes. | Recompilation of a client program may be broken with the error message: struct inet6_ifaddr has no member named probes. |
| 2 | Field timer has been renamed to dad_timer. | Recompilation of a client program may be broken with the error message: struct inet6_ifaddr has no member named timer. |
| Change | Effect | |
|---|---|---|
| 1 | Field conf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'conf'. |
| 2 | Field hblank has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'hblank'. |
| 3 | Field hsync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'hsync'. |
| 4 | Field htotal has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'htotal'. |
| 5 | Field vblank has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'vblank'. |
| 6 | Field vsync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'vsync'. |
| 7 | Field vtotal has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_pipe_error_state' has no member named 'vtotal'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fdi_lanes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'fdi_lanes'. |
| 2 | Field pch_pll has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'pch_pll'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pixel_target_clock 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 'pixel_target_clock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_pch_edp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dp' has no member named 'is_pch_edp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field needs_tv_clock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_encoder' has no member named 'needs_tv_clock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_context_obj has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'last_context_obj'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fnhe_rth has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fib_nh_exception' has no member named 'fnhe_rth'. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_transaction has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct jbd2_journal_handle has no member named h_transaction. |
| Change | Effect | |
|---|---|---|
| 1 | Field j_wait_checkpoint has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct journal_s' has no member named 'j_wait_checkpoint'. |
| 2 | Field j_wait_logspace has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct journal_s' has no member named 'j_wait_logspace'. |
| Change | Effect | |
|---|---|---|
| 1 | Field t_iobuf_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct transaction_s' has no member named 't_iobuf_list'. |
| 2 | Field t_log_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct transaction_s' has no member named 't_log_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_area_cache has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'free_area_cache'. |
| 2 | Field unmap_area has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'unmap_area'. |
| 3 | Field cached_hole_size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'cached_hole_size'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ipvs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net' has no member named 'ipvs'. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlbl_dom_map' has no member named 'type'. |
| 2 | Field type_def has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlbl_dom_map' has no member named 'type_def'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_target_max_resp_sz has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_session' has no member named 'fc_target_max_resp_sz'. |
| 2 | Field fc_target_max_rqst_sz has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_session' has no member named 'fc_target_max_rqst_sz'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid_ns has been renamed to pid_ns_for_children. | Recompilation of a client program may be broken with the error message: struct nsproxy has no member named pid_ns. |
| Change | Effect | |
|---|---|---|
| 1 | Field jiffies_interval has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_cpu_context' has no member named 'jiffies_interval'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hard_math has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuinfo_x86' has no member named 'hard_math'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_bps has been renamed to rate_bytes_ps. | Recompilation of a client program may be broken with the error message: struct psched_ratecfg has no member named rate_bps. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_weight has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_group' has no member named 'load_weight'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ptrace_bp_refcnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_struct' has no member named 'ptrace_bp_refcnt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved_tailroom has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field mark has been renamed to napi_id. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-506 has no member named mark. |
| 3 | Field dropcount has been renamed to dma_cookie. | Recompilation of a client program may be broken with the error message: anon-union-skbuff.h-506 has no member named dropcount. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 7 has been changed from CFG80211_CONN_DEAUTH_ASSOC_FAIL to CFG80211_CONN_ASSOC_FAILED. | Recompilation of a client program may be broken with the error message: 'CFG80211_CONN_DEAUTH_ASSOC_FAIL' was not declared in this scope. |
| 2 | The member CFG80211_CONN_IDLE has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field scoreboard_skb_hint has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'scoreboard_skb_hint'. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'trace_cpu'. |
| 2 | Field waiter has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'waiter'. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array_cpu' has no member named 'trace_cpu'. |
| Change | Effect | |
|---|---|---|
| 1 | Field minimum_to_wake 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 'minimum_to_wake'. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter d has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter handle of type handle_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hub of type struct usb_hub* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter intel_crtc of type struct intel_crtc* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter pipe_config of type struct intel_crtc_config* 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 | 3rd middle parameter mode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type struct dir_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dirent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter filp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter offset of type int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter log_bufs of type struct list_head* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rsv_blocks of type int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sband of type struct ieee80211_supported_band* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter local has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field wowlan became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct wiphy::wowlan'. |
| 2 | The pointer level of field wowlan has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field refcnt 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 | The pointer level of field convert_pointer has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 2 | The pointer level of field get_next_high_mono_count has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 3 | The pointer level of field get_next_variable has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 4 | The pointer level of field get_time has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 5 | The pointer level of field get_variable has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 6 | The pointer level of field get_wakeup_time has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 7 | The pointer level of field query_capsule_caps has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 8 | The pointer level of field query_variable_info has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 9 | The pointer level of field reset_system has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 10 | The pointer level of field set_time has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 11 | The pointer level of field set_variable has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 12 | The pointer level of field set_virtual_address_map has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 13 | The pointer level of field set_wakeup_time has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 14 | The pointer level of field update_capsule has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fl_link has been changed from struct list_head to struct hlist_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct snd_pcm_substream::ops'. |
| 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 pmu::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field expires has been changed from union cpu_time_count to unsigned long long of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field incr has been changed from union cpu_time_count to unsigned long long of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field __parent has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field transport_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | The pointer level of field inner_transport_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 3 | The pointer level of field inner_network_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 4 | The pointer level of field mac_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 5 | The pointer level of field network_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 6 | The pointer level of field inner_mac_header has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter length of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter inode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter label of type struct nfs4_label* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter srcu_idx 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 became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value became const (has been changed from char* to char const*). | 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 now of type struct timespec* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from unsigned long (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter nowtime has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rsv_blocks of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter chunk has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sb has been changed from struct super_block to struct ext4_sb_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sb has been changed from struct super_block to struct ext4_sb_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter chunk has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter file has been changed from struct file to struct inode of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter label of type struct nfs4_label* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clock has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter m has been changed from struct seq_file to struct drm_i915_error_state_buf of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ring of type struct intel_ring_buffer* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter m has been changed from struct seq_file to struct drm_i915_error_state_buf of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter max of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter adjusted_mode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter enable of type bool has been added to the calling stack. | 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 | Parameter protocol of type u8 const has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct journal_head to struct buffer_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter jh_out has been changed from struct journal_head to struct buffer_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter filldir has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct netlbl_domaddr4_map to struct netlbl_dommap_def of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct netlbl_domaddr6_map to struct netlbl_dommap_def of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter minorversion of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct acpi_predefined_data to struct acpi_evaluate_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter end has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 1st parameter start has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter constraints has been changed from struct event_constraint to struct perf_event of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from struct qstr to char of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from struct qstr to char of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter now of type struct timespec* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from unsigned long (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter nowtime has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter kern_flags of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter set_kern_flags of type unsigned long* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prev_bssid of type u8 const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bss has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter lru has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter lru has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sk has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | The pointer level of return value has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter length of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter length of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter band has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter name has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field physical_node_count has been changed from u8 to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field full_pathname has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field node_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field parent_package has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field predefined has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field return_btype has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field return_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Type of field param_count has been changed from u8 to u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tcfc_rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field compare has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field plat_data has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_desc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field minorversion has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notified has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field plink_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field basic_rates has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chain_signal_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field chains has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wowlan_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field wowlan has been changed from struct wiphy_wowlan_support to struct wiphy_wowlan_support const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field destroy_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field serial_nr has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field css_kill_cnt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field governor_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field transition_ongoing has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpumask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_lockref 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 d_hash has been changed from int(*)(struct dentry const*, struct inode const*, struct qstr*) to int(*)(struct dentry const*, struct qstr*). | Recompilation of a client program may be broken. |
| 2 | Base type of field d_compare has been changed from int(*)(struct dentry const*, struct inode const*, struct dentry const*, struct inode const*, unsigned int, char const*, struct qstr const*) to int(*)(struct dentry const*, struct dentry const*, unsigned int, char const*, struct qstr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field offline has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field online has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field offline has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field offline_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_barrier has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field old_fb has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor_set2 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_unpin has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gem_prime_mmap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field convert_pointer has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 2 | Type of field get_next_high_mono_count has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 3 | Type of field get_next_variable has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 4 | Type of field get_time has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 5 | Type of field get_variable has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 6 | Type of field get_wakeup_time has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 7 | Type of field query_capsule_caps has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 8 | Type of field query_variable_info has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 9 | Type of field reset_system has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 10 | Type of field set_time has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 11 | Type of field set_variable has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 12 | Type of field set_virtual_address_map has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 13 | Type of field set_wakeup_time has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 14 | Type of field update_capsule has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_rsv_conversion_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field i_rsv_conversion_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field i_touch_when has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field i_unrsv_conversion_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field i_unrsv_conversion_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bio has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field handle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_es_last_sorted has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unrsv_conversion_wq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vol_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_dirty_writeback has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field invalidatepage has been changed from void(*)(struct page*, unsigned long) to void(*)(struct page*, unsigned int, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_link_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tmpfile has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lm_owner_key has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_response_fallback has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field pcm_dev_bits has been changed from unsigned long[8] to unsigned long[1]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field auto_mute_via_amp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mute_bits has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field find_dpll has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field update_sprite_wm has been changed from void(*)(struct drm_device*, int, uint32_t, int) to void(*)(struct drm_device*, int, uint32_t, int, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field acthd has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 2 | Type of field cpu_ring_head has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 3 | Type of field cpu_ring_tail has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 4 | Type of field ctl has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 5 | Type of field faddr has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 6 | Type of field fault_reg has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 7 | Type of field head has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 8 | Type of field instdone has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 9 | Type of field instpm has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 10 | Type of field instps has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 11 | Type of field ipehr has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 12 | Type of field ipeir has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 13 | Type of field rc_psmi has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 14 | Type of field ring has been changed from struct drm_i915_error_ring[3] to struct drm_i915_error_ring[4]. | Recompilation of a client program may be broken. |
| 15 | Type of field semaphore_mboxes has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| 16 | Type of field semaphore_seqno has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| 17 | Type of field seqno has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 18 | Type of field tail has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 19 | Type of field waiting has been changed from bool[3] to bool[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hpd_event_bits has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field num_shared_dpll has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field power_well has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field shared_dplls has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field vbt has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field vlv_pctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Type of field ring has been changed from struct intel_ring_buffer[3] to struct intel_ring_buffer[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pte_encode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hang_stats has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ref has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pte_encode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_ddi has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field has_fpga_dbg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field has_vebox_ring has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rpe_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vlv_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mbss_changed has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rs_probes has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rs_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mc_dad_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field valid_ll_addr_cnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mc_dad_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field peer_addr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mc_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field metrics has been changed from u32[14] to u32[15]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_transcoders has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field power_well_driver has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field transcoder has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field m has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field p has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vco has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field m1 has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| 6 | Type of field m2 has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| 7 | Type of field n has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| 8 | Type of field p1 has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| 9 | Type of field p2 has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_fifo_underrun_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pch_fifo_underrun_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bw_constrained has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dpll_hw_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fdi_lanes has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field fdi_m_n has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field gmch_pfit has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ips_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field pch_pfit has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field port_clock has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field quirks has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field sdvo_tv_clock has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field shared_dpll has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_config has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_context has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hangcheck has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fbc_dirty has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field semaphore_register has been changed from u32[3] to u32[4]. | Recompilation of a client program may be broken. |
| 5 | Type of field sync_seqno has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| 6 | Type of field signal_mbox has been changed from u32[2] to u32[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lookup_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fnhe_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fnhe_rth_input has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fnhe_rth_output has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_calc_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_rsv_handle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_port_no has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field transmit_led_message has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chains has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_sync_action has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field exact_match has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nvec_used has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fnhe_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field napi_hash_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field napi_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mpls_features has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_busy_poll has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_set_vf_link_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flow_limit has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field def has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compare 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 reclaim_complete has been changed from int(*)(struct nfs_client*) to int(*)(struct nfs_client*, struct rpc_cred*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field attr_bitmask_nl has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field cache_consistency_bitmask has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field label has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_label 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 getattr has been changed from int(*)(struct nfs_server*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct nfs_server*, struct nfs_fh*, struct nfs_fattr*, struct nfs4_label*). | Recompilation of a client program may be broken. |
| 2 | Base type of field lookup has been changed from int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*, struct nfs4_label*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field constraint has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field full_width_write has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field abort has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field in_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hrtimer_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hrtimer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hrtimer_interval_ms has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field late_ack has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_internal has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field of_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field __parent has been changed from struct Qdisc* to u32. | Recompilation of a client program may be broken. |
| 2 | Type of field rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| 3 | Type of field __state has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tg_load_contrib has been changed from u64 to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of field runnable_load_avg has been changed from u64 to unsigned long. | Recompilation of a client program may be broken. |
| 3 | Type of field removed_load has been changed from struct atomic64_t to atomic_long_t. | Recompilation of a client program may be broken. |
| 4 | Type of field blocked_load_avg has been changed from u64 to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field load_avg has been changed from struct atomic64_t to atomic_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field eh_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry_init_security has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ismaclabel has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field sb_set_mnt_opts has been changed from int(*)(struct super_block*, struct security_mnt_opts*) to int(*)(struct super_block*, struct security_mnt_opts*, unsigned long, unsigned long*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field inner_protocol has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field inner_network_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| 3 | Type of field network_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| 4 | Type of field inner_transport_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| 5 | Type of field transport_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| 6 | Type of field mac_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| 7 | Type of field inner_mac_header has been changed from sk_buff_data_t to __u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[95] to unsigned long[96]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_ll_usec has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_napi_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chain_signal_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chain_signal_last has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field chains has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_gss_mech has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bin_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fasync has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field usb2_hw_lpm_besl_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field l1_params has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field for_sync 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 get_wallclock has been changed from unsigned long(*)() to void(*)(struct timespec*). | Recompilation of a client program may be broken. |
| 2 | Base type of field set_wallclock has been changed from int(*)(unsigned long) to int(*)(struct timespec const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ulog_warn_deprecated has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_error has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter offset has been changed from unsigned 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 snd_card*[32] to struct snd_card*[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[15] const to u32[16] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter nowtime has been changed from unsigned long to struct timespec const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rate_est has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter r has been changed from struct gnet_stats_rate_est to struct gnet_stats_rate_est64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct ucode_cpu_info[8] to struct ucode_cpu_info[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const to u32[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const to u32[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const to u32[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter end has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| 2 | Type of 1st parameter start has been changed from unsigned long to void*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter nowtime has been changed from unsigned long to struct timespec const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to int(*)(). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct tcp_md5sig_pool* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter offset has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter offset has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter name has been changed from u32 to char*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The member CFG80211_CONN_CONNECTED with value 9 has been added. | No effect. |
| 2 | The member CFG80211_CONN_AUTH_FAILED with value 4 has been added. | No effect. |
| 3 | The member CFG80211_CONN_DEAUTH with value 8 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field obj_desc has been changed from 2 to 3. | No effect. |
| 2 | The relative position of field parameters has been changed from 3 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field map has been changed from 17 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field fu_llist has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field has_force_wake has been changed from 15 to 16. | No effect. |
| 2 | The relative position of field is_haswell has been changed from 16 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member VECS with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_CHAN_WIDTH_5 with value 6 has been added. | No effect. |
| 2 | The member NL80211_CHAN_WIDTH_10 with value 7 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PHY_INTERFACE_MODE_REVMII with value 5 has been added. | No effect. |
| 2 | Value of member PHY_INTERFACE_MODE_RTBI has been changed from 10 to 11. | No effect. |
| 3 | Value of member PHY_INTERFACE_MODE_RGMII_TXID has been changed from 9 to 10. | No effect. |
| 4 | Value of member PHY_INTERFACE_MODE_RGMII has been changed from 6 to 7. | No effect. |
| 5 | Value of member PHY_INTERFACE_MODE_SMII has been changed from 11 to 12. | No effect. |
| 6 | Value of member PHY_INTERFACE_MODE_RGMII_RXID has been changed from 8 to 9. | No effect. |
| 7 | Value of member PHY_INTERFACE_MODE_RMII has been changed from 5 to 6. | No effect. |
| 8 | Value of member PHY_INTERFACE_MODE_RGMII_ID has been changed from 7 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field busylock has been changed from 23 to 24. | No effect. |
| 2 | The relative position of field bstats has been changed from 19 to 18. | No effect. |
| 3 | The relative position of field state has been changed from 17 to 16. | No effect. |
| 4 | The relative position of field qstats has been changed from 21 to 20. | No effect. |
| 5 | The relative position of field gso_skb has been changed from 16 to 15. | No effect. |
| 6 | The relative position of field __state has been changed from 20 to 19. | No effect. |
| 7 | The relative position of field callback_head has been changed from 22 to 21. | No effect. |
| 8 | The relative position of field rate_est has been changed from 10 to 13. | No effect. |
| 9 | The relative position of field limit has been changed from 24 to 3. | No effect. |
| 10 | The relative position of field dev_queue has been changed from 14 to 12. | No effect. |
| 11 | The relative position of field refcnt has been changed from 9 to 23. | No effect. |
| 12 | The relative position of field u32_node has been changed from 12 to 10. | No effect. |
| 13 | The relative position of field next_sched has been changed from 15 to 14. | No effect. |
| 14 | The relative position of field __parent has been changed from 13 to 11. | No effect. |
| 15 | The relative position of field reshape_fail has been changed from 11 to 9. | No effect. |
| 16 | The relative position of field q has been changed from 18 to 17. | No effect. |
| 17 | The relative position of field padded has been changed from 3 to 22. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field last_decay has been changed from 16 to 15. | No effect. |
| 2 | The relative position of field removed_load has been changed from 15 to 16. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed1 has been changed from 45 to 44. | No effect. |
| 2 | The relative position of field secmark has been changed from 44 to 45. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member CFG80211_CONN_AUTHENTICATE_NEXT has been changed from 3 to 2. | No effect. |
| 2 | Value of member CFG80211_CONN_SCANNING has been changed from 1 to 0. | No effect. |
| 3 | Value of member CFG80211_CONN_AUTHENTICATING has been changed from 4 to 3. | No effect. |
| 4 | Value of member CFG80211_CONN_SCAN_AGAIN has been changed from 2 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter parent has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nowtime has been renamed to now. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nblocks has been renamed to blocks. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nrblocks has been renamed to extents. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sb has been renamed to sbi. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sb has been renamed to sbi. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter direct has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter file has been renamed to inode. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter jh_out has been renamed to bh_out. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter filp has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to info. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter constraints has been renamed to events. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nowtime has been renamed to now. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |