| Module Name | vmlinux |
|---|---|
| Version #1 | 2.6.34.14 |
| Version #2 | 3.0.101 |
| CPU Type | x86_64 |
| Subject | Binary Compatibility |
| Total Header Files | 705 |
|---|---|
| Total Source Files | 1314 |
| Total Objects | 1 |
| Total Symbols / Types | 13974 / 7665 |
| Verdict | Incompatible (57.1%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 1860 |
| Removed Symbols | High | 863 |
| Problems with Data Types | High | 333 |
| Medium | 1561 | |
| Low | 1140 | |
| Problems with Symbols | High | 198 |
| Medium | 4407 | |
| Low | 415 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 35 |
| Change | Effect | |
|---|---|---|
| 1 | Field apicid_to_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 cpu_to_logical_apicid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field watch has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ilist has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hits has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_cnt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field rcu_head has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 unplug_io_fn has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 unplug_io_data has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field wb_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. |
| 6 | Field wb_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 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 prepare_flush_fn has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 post_flush_rq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field bar_rq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field unplug_timer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field pre_flush_rq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field unplug_thresh has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 unplug_work has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field ordseq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ordcolor has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 orig_bar_rq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field unplug_delay has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field action has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mesh_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mesh_id_len has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cn_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field wq_created has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wq_creation has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wq_requested has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vc_tty has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field Attributes has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 CardValues has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ConfigBase has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ExtStatus has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 IntType has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 Status has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_io has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 add_mem has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 adjust_io_region has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sem has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 nr_pages has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_error_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 barrier_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 flush_request has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_single_range_for_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 sync_single_range_for_device has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field waitq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field desired_mode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field desired_x has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_off_supported has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 blank_to_black has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 bluex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 display_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. |
| 5 | Field gamma has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 greenx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 redx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 serration_vsync has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 whitex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wpgamma1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wpgamma2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wpx1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field wpx2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field wpy1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field wpy2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fbdev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pseudo_palette has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_kernel_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 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. |
| 2 | Field fill has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ml_entry has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field object_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 object_memory has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field timer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field context_ctor has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 dma_ready has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field gem_free_object_unlocked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field get_map_ofs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field get_reg_ofs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 kernel_context_switch has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field kernel_context_switch_unlock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pci_driver has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field proc_init has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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. |
| 2 | Field dev_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 rate_last has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 save has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field blink_timer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field led_status has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_scope has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_mmap_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 i_fsnotify_mark_entries has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field i_list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field i_dentry has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field inotify_watches has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 inotify_mutex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_copy_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 fl_mylease has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_need_sync has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clear_inode has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_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 group_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. |
| 3 | Field mark_entries has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mask has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field on_group_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 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 fields has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 filter_active has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field raw_init has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 regfunc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 system has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 unregfunc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field async_notify has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field function_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field input_pins has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_list_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 gpu_write_list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field irq_gem_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field next_gem_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field request_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. |
| 6 | Field waiting_gem_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipeastat has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pipebstat has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_offset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field agp_mem has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 obj has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight_duty_cycle has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 crt_ddc_bus has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 de_irq_enable_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field dma_status_page has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field edp_bpp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field gt_irq_enable_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gt_irq_mask_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 hw_status_page has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field hws_obj has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 irq_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. |
| 11 | Field irq_mask_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 irq_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field pch_irq_enable_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field pch_irq_mask_reg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field seqno_gfx_addr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field seqno_obj has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | Field seqno_page has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 18 | Field trace_irq_seqno has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Field user_irq_refcount has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 20 | Field vram has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_rc6 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_gen6 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_i8xx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_i965g has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_i965gm has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_i9xx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 is_ironlake has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field request has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 skb_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_loss_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 skb_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field work has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_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 key_lock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field mc_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. |
| 4 | Field 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. |
| 5 | Field work_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 default_key has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dst has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 flags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field fragsize has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 length has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 opt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inet_daddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field inet_rcv_saddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field opt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mc_list_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 v4daddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field abs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 absflat has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 absfuzz has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 absmax has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 absmin has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 absres has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ddc_bus has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 enc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 i2c_bus has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 load_detect_temp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nat_vmalloced has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 rt_secret_timer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field todo has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_policy has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_task has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field port_task_data has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field prd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 prd_dma has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_ack_map has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field barriers_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 biolist has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field write_behind has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vm_truncate_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 set has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field get has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_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 hash_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 wait has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field br_port has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 macvlan_port has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 mc_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. |
| 4 | Field mc_list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field refcnt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 rx_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_client_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 so_client has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 so_delegations has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Field lockowner has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_state_owners has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cl_openowner_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field cl_delegations has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 cl_lockowner_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_slotid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_id has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field remaining has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 filp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field enable has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prio_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 type_attr_map has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf_offset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field offset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field prev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field demotion has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 promotion has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field orphan_cbs_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 orphan_cbs_tail has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 orphan_qlen has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field country_ie_checksum has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 u has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 idev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_set_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. |
| 2 | Field irq_set_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 nr_spread_over has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 shares has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field in_nohz_recently has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 migration_queue has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field migration_thread has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tk_rtt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 tk_magic has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field tk_bytes_sent has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg_overlap has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 avg_wakeup has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 block_max has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 block_start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field exec_max has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 iowait_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. |
| 7 | Field iowait_sum has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 last_wakeup has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 nr_failed_migrations_affine has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 nr_failed_migrations_hot has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 nr_failed_migrations_running has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 nr_forced_migrations has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field nr_migrations_cold has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field nr_wakeups has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field nr_wakeups_affine has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field nr_wakeups_affine_attempts has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | Field nr_wakeups_idle has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 18 | Field nr_wakeups_local has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Field nr_wakeups_migrate has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 20 | Field nr_wakeups_passive has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 21 | Field nr_wakeups_remote has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 22 | Field nr_wakeups_sync has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 23 | Field sleep_max has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 24 | Field sleep_start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 25 | Field slice_max has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 26 | Field start_runtime has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 27 | Field sum_sleep_runtime has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 28 | Field wait_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. |
| 29 | Field wait_max has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 30 | Field wait_start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 31 | Field wait_sum has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bts has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 cred_guard_mutex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field lock_depth has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acct has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 cred_commit has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 inode_delete has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 key_session_to_parent has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field sb_check_sb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb_post_addmount has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb_post_pivotroot has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb_post_remount has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb_umount_busy has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb_umount_close has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sysctl has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 task_setgid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field task_setgroups has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field task_setuid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field child has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_peercred has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_rmem_alloc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tid_state_rx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 tid_state_tx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field key has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field last_noise has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ssn has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field warning has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 warning_symbol has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field xpt_pool has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field resume has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 shutdown has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 suspend has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_dma has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field scanning_done has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field autosuspend_delay has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_busy has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nents has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field singlethread has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bdi has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bundles has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of 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 root of type struct acpi_pci_root* 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 device 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 5th parameter flags has been changed from int (4 bytes) to unsigned long (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_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 | 2nd middle parameter dentry 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 file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter targ_ns of type struct user_namespace* 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 fl6 of type struct flowi6* 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 fl 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 name has been changed from char const* (8 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter features has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter all has been changed from unsigned long (8 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Type of 3rd parameter mask has been changed from unsigned long (8 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | Type of 2nd parameter one has been changed from unsigned long (8 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gfp_mask has been changed from gfp_t (4 bytes) to struct shrink_control* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Type of 1st parameter nr_to_scan has been changed from int (4 bytes) to struct shrinker* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | The pointer level of 2nd parameter gfp_mask 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. |
| 4 | The pointer level of 1st parameter nr_to_scan 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 ns of type void const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type void const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_ns of type void const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter submit_io of type dio_submit_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq 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 fb_helper of type struct drm_fb_helper* 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 spd of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gpe_device of type struct acpi_namespace_node* 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 gpe_xrupt_info of type struct acpi_gpe_xrupt_info* 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 gpe_device 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 | 3rd middle parameter flags has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter personality has been changed from u_long (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter personality has been changed from u_long (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter net 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 5th parameter dev has been changed from struct net_device* (8 bytes) to int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Type of 4th parameter oif has been changed from int (4 bytes) to u8 (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | Type of 1st parameter src has been changed from __be32 (4 bytes) to struct sk_buff* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 4 | Type of 3rd parameter tos has been changed from u8 (1 byte) to __be32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 5 | Type of 8th parameter mark has been changed from u32 (4 bytes) to u32* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 6 | The pointer level of 8th parameter mark 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. |
| 7 | The pointer level of 1st parameter src 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 | 7th middle parameter scope 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 flp has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry 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 inode 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 fentry of type struct sock_filter const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter filter 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 uevent has been changed from int (4 bytes) to bool (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter sb 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 path of type struct path* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct hpet_dev* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct hpet_dev* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter acctflag has been changed from int (4 bytes) to vm_flags_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter action has been changed from u8 (1 byte) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter i has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter flush_domains has been changed from uint32_t (4 bytes) to struct drm_i915_gem_request* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 3rd parameter flush_domains 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 mappable_end of type unsigned long has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter write has been changed from int (4 bytes) to bool (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter server of type struct nfs_server const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter clp 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 server of type struct nfs_server const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter clp 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 ipfragok has been changed from int (4 bytes) to struct flowi* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 2nd parameter ipfragok 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 fl4 of type struct flowi4* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter daddr has been changed from __be32 (4 bytes) to struct inetpeer_addr* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter daddr has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter inf has been changed from struct autofs_info* (8 bytes) to mode_t (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter fs_dir_inode_ops has been changed from struct inode_operations const* (8 bytes) to int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Type of 5th parameter isvfat has been changed from int (4 bytes) to void(*)(struct super_block*) (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | The pointer level of 5th parameter isvfat has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter acctflag has been changed from int (4 bytes) to vm_flags_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter ino 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 dir of type struct inode const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type void const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type struct fsnotify_mark* 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 entry 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 ke of type struct input_keymap_entry* 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 scancode 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 ke of type struct input_keymap_entry const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter scancode 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 connector of type struct drm_connector* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter connector of type struct drm_connector* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter connector of type struct drm_connector* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter prot became passed at the different offset on the stack (-72 instead of -56). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl6 of type struct flowi6* 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 | 9th middle parameter fl 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 fl6 of type struct flowi6* 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 fl 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 fl4 of type struct flowi4* 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 fl4 of type struct flowi4* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ipfragok has been changed from int (4 bytes) to struct flowi* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 2nd parameter ipfragok 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 daddr of type __be32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter saddr of type __be32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Parameter daddr of type __be32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local of type struct ieee80211_local* 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 ap of type struct ata_port* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter done has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter cache_op has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter index has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter index 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 4th parameter keys has been changed from unsigned int* (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter thread has been increased from 1 to 2. | 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 rdev of type mdk_rdev_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. |
| 2 | 1st middle parameter bdev has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter regnum has been changed from u16 (2 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter regnum has been changed from u16 (2 bytes) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vma of type struct vm_area_struct* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter offlining has been changed from int (4 bytes) to bool (1 byte). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type struct zone* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter vm_flags has been changed from unsigned int (4 bytes) to vm_flags_t (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int (4 bytes) to struct irq_data* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter irq 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 op of type struct open_flags const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 3rd middle parameter open_flag 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 flags of type unsigned int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter buflen has been changed from ssize_t (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter base has been increased from 1 to 2. | 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 | 2nd middle parameter vmalloced has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter vmalloced 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 mnt_parent 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 clnt of type struct rpc_clnt* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_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 arg of type struct nfs4_setclientid_res* 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 endian of type enum utf16_endian has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* (8 bytes) to struct kernel_param const* (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter change_bridge has been changed from bool (1 byte) to u32 (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type u32* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter req has been changed from memreq_t* (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 2nd parameter wh has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter wh has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter wh has been changed from window_handle_t* (8 bytes) to unsigned int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter pid has been changed from pid_t (4 bytes) to struct task_struct* (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 3rd parameter pid 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 head of type struct hlist_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. |
| 2 | 1st middle parameter event_id has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter task of type struct task_struct* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter of type struct ring_buffer_iter* 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 buffer 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 flp4 of type struct flowi4* 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 rp 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 flp4 of type struct flowi4* 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 rp 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 flp 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 skb of type struct sk_buff* 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 daddr of type __be32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 ns of type struct user_namespace* 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 qstr of type struct qstr const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct user_namespace* 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 ns of type struct user_namespace* 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 p of type struct task_struct* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter objname of type char const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* 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 channel of type struct ieee80211_channel* 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 tx_flags of type __u8* 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 msg has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter tty has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter len 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 begin has been increased from 1 to 2. | 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 3rd parameter end has been increased from 1 to 2. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| 3 | The pointer level of 1st parameter tracepoint has been increased from 2 to 3. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter begin has been increased from 1 to 2. | 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 2nd parameter end has been increased from 1 to 2. | 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 regs of type struct pt_regs* 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 pairwise of type bool has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct ipc_namespace* 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 ns of type struct ipc_namespace* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gfp_mask has been changed from gfp_t (4 bytes) to unsigned long (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | The pointer level of 1st parameter scanned 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 | 2nd middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter file has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter delta has been changed from short (2 bytes) to int (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dst_p has been changed from struct dst_entry** (8 bytes) to struct dst_entry* (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| 2 | Type of 3rd parameter fl has been changed from struct flowi* (8 bytes) to struct flowi const* (8 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 | Field gpe_count has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dispatch has been changed from 8 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field wakeup_count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field device has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field scope_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 access_bit_width has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field wakeup has been changed from 128 bytes to 120 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field power has been changed from 424 bytes to 528 bytes. | 1) Size of the inclusive type has been 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 force_power_state has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field wake_capable has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field states has been changed from struct acpi_device_power_state[4] (416 bytes) to struct acpi_device_power_state[5] (520 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 run_wake_count 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 state has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field always_enabled has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field drv has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field secondary has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 osc_control_qry 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 osc_queried 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 bus_nr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field arguments has been changed from 224 bytes to 280 bytes. | 1) Size of the inclusive type has been 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 local_variables has been changed from 256 bytes to 320 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field agp_map_memory 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 agp_map_page 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 agp_unmap_memory 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 agp_unmap_page 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 chipset_flush 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 vmalloc_flag has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cpuid has been changed from u8 (1 byte) to u16 (2 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 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 | Field cache_cfg 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 reset_in_progress has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from 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 wdata 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 hashbits has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 hashtable has been changed from struct hlist_head[16] (128 bytes) to struct hlist_head* (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The pointer level of field hashtable 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 free 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 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. |
| 3 | Field size 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 u 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 laptop_mode_wb_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 | Size of field wb has been changed from 96 bytes to 168 bytes. | 1) Size of the inclusive type has been 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 wakeup_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 last_active has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field props 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 may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hasvdso 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 counter_bits 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 syncchunk has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member REQ_TYPE_ATA_PC has been changed from 10 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member REQ_TYPE_ATA_TASKFILE has been changed from 9 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field swap_slot_free_notify has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 locked_ioctl 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 max_integrity_segments has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field part has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unnamed1 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field elevator_private2 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. |
| 4 | Field elevator_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 flush_not_queueable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 flush_pending_idx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field delay_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field flush_queue_delayed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 flush_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. |
| 6 | Field flush_pending_since has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 flush_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field flush_rq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 flush_data_in_flight has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Size of field limits has been changed from 64 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Size of field backing_dev_info has been changed from 432 bytes to 520 bytes. | 1) Size of the inclusive type has been 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 queue_lock has been changed from spinlock_t* (8 bytes) to spinlock_t (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 13 | Field next_ordered has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 14 | Field orderr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash has been changed from struct list_head to struct hlist_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field req has been changed from 8 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctl_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field vfs_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field check_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ibss has been changed from 40 bytes to 56 bytes. | 1) Size of the inclusive type has been 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 crypto has been changed from 48 bytes to 52 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field basic_rates has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field join_mesh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 leave_mesh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mgmt_tx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mgmt_tx_cancel_wait has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bss_param has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 connected_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field rx_dropped_misc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rxrate has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 6 | Field tx_failed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tx_retries has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field available_antennas_tx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 iface_combinations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 max_remain_on_channel_duration has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mgmt_stypes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 n_iface_combinations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 software_iftypes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wowlan has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | The relative position of field addresses has been changed from 3 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field n_addresses has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_interval has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field channel has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wext has been changed from 240 bytes to 256 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 attach_task has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field can_attach_task has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field pre_attach has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 parts has been changed from 6144 bytes to 26624 bytes. | 1) Size of the inclusive type has been 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 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 max_delta_ticks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 min_delta_ticks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The relative position of field features has been changed from 1 to 8. | 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 list has been changed from 13 to 16. | 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 min_delta_ns has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field rating has been changed from 6 to 13. | 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 set_next_event has been changed from 9 to 1. | 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 broadcast has been changed from 12 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field cpumask has been changed from 8 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field event_handler has been changed from 11 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field irq has been changed from 7 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field max_delta_ns has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field mode has been changed from 14 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field mult has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field name has been changed from 0 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field next_event has been changed from 15 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field retries has been changed from 16 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field set_mode has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field shift has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cycle_last has been changed from 14 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field disable has been changed from 5 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field enable has been changed from 4 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field flags has been changed from 10 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field list has been changed from 1 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field mask has been changed from 6 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field max_idle_ns has been changed from 9 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field mult has been changed from 7 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field name has been changed from 0 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field rating has been changed from 2 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field read has been changed from 3 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field resume has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field shift has been changed from 8 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field suspend has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field vread has been changed from 11 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_tstamp has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tstamp_sysctl_header has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field expect_vmalloc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field hash_vmalloc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field port has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sched_scan_mtx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sched_scan_req has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field sched_scan_results_wk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field wiphy has been changed from 544 bytes to 640 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 refcount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 attr has been changed from 24 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 user_ns has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 io has been changed from io_req_t (28 bytes) to struct resource[2] (112 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 2 | Field irq 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 Copy has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field Option has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field Pin has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_resume has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field remove has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 d_count has been changed from struct atomic_t to unsigned int of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field d_lru has been changed from 7 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field d_time has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field d_alias has been changed from 10 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field d_flags has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field d_subdirs has been changed from 9 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field d_parent has been changed from 5 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field d_sb has been changed from 13 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field d_fsdata has been changed from 14 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field d_lock has been changed from 2 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field d_name has been changed from 6 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field d_hash has been changed from 4 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field d_op has been changed from 12 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field d_inode has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field d_count has been changed from 0 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field d_iname has been changed from 15 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field d_u has been changed from 8 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 18 | Field d_mounted has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 dev_bin_attrs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field namespace has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ns_type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | Field pwr_domain has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Size of field power has been changed from 64 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 of_match_table has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 attr has been changed from 24 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 nr_reserved_pages has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field type_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field barrier_bio 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 barrier_error has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field polled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 display_info has been changed from 136 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. |
| 3 | Size of field kdev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hwmode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 desired_y has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 bluey has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field composite_sync has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field digital has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field greeny has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 6 | Field gtf_supported has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field redy has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 8 | Field separate_syncs has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 9 | Field standard_color has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 10 | Field standby_supported has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 11 | Field suspend_supported has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 12 | Field sync_on_green has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 13 | Field video_level has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 14 | Field whitey has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_poll_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 poll_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 | Type of field timings has been changed from struct std_timing[5] (10 bytes) to struct std_timing[6] (12 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field order has been changed from unsigned int (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field table has been changed from 1 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field use_vmalloc 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 head_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 | Size of field owner_hash_tab has been changed from 32 bytes to 16 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field user_hash_tab has been changed from 32 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 _vblank_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field platformdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 usbdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vblank_time_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Size of field map_hash has been changed from 32 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. |
| 7 | Size of field mode_config has been changed from 432 bytes to 536 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 8 | Field drw_idr 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 drw_lock has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | Field flush_domains 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 gtt_count 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 gtt_memory 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 gtt_total 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 invalidate_domains 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 pin_memory 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 bus has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dumb_destroy has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dumb_map_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field get_scanout_position has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field get_vblank_timestamp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 kdriver has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | The relative position of field debugfs_cleanup has been changed from 30 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field debugfs_init has been changed from 29 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field gem_free_object has been changed from 32 to 31. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field gem_init_object has been changed from 31 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field vgaarb_irq has been changed from 33 to 32. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field magiclist has been changed from 32 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 kdev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 40 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field card_addr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field config_base has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field config_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 config_index has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field config_regs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 io_lines has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 resource has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vpp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 10 | Type of field irq has been changed from irq_req_t (16 bytes) to unsigned int (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | The relative position of field _io has been changed from 12 to 9. | 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 _irq has been changed from 11 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field dev has been changed from 25 to 22. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field dma_mask has been changed from 24 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field func_id has been changed from 20 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field irq has been changed from 8 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field open has been changed from 6 to 24. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field prod_id has been changed from 23 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field suspended has been changed from 10 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field _locked has been changed from 14 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field _win has been changed from 13 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field allow_func_id_match has been changed from 15 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field card_id has been changed from 22 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field has_card_id has been changed from 17 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field has_func_id has been changed from 18 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field has_manf_id has been changed from 16 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field manf_id has been changed from 21 to 18. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field drv has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field metrics has been changed from u32[14] (56 bytes) to unsigned long (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field __pad_to_align_refcnt 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. |
| 3 | The relative position of field lastuse 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. |
| 4 | The relative position of field expires has been changed from 6 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field __refcnt 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. |
| 6 | The relative position of field error has been changed from 3 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field trailer_len has been changed from 8 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field header_len has been changed from 7 to 14. | 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 flags has been changed from 5 to 21. | 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 hh has been changed from 11 to 8. | 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 obsolete has been changed from 4 to 13. | 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 ops has been changed from 15 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field path has been changed from 9 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field __use has been changed from 20 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field input has been changed from 13 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field output has been changed from 14 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field xfrm has been changed from 12 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 18 | Field rate_tokens has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_mtu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 default_advmss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cow_metrics has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bytecount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 segs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member e1000_82541 has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member e1000_82541_rev_2 has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member e1000_82546_rev_3 has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member e1000_82547 has been changed from 12 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member e1000_82547_rev_2 has been changed from 13 to 14. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member e1000_num_macs has been changed from 14 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_queue_empty_fn has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field vfs_inode has been changed from 616 bytes to 592 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 ratelimit has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field aperture_base 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 save_graphics has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpf_func has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field iif has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field mark has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field nl_u has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field oif has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 6 | Field proto has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field secid has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 8 | Field uli_u has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_mmap_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unmap_mutex has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | Field truncate_count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_page has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bd_openers has been changed from 3 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field bd_inode has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field bd_super has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field bd_holder_list has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_tfile_llink has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctl 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 | Type of field nr_files has been changed from int (4 bytes) to unsigned long (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field nr_free_files has been changed from int (4 bytes) to unsigned long (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field max_files has been changed from int (4 bytes) to unsigned long (8 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 i_fsnotify_marks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_lru has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field i_wb_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. |
| 4 | Field unnamed1 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field i_data has been changed from 176 bytes to 168 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 6 | The relative position of field i_gid has been changed from 6 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field i_mode has been changed from 16 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field i_dquot has been changed from 26 to 31. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field i_fop has been changed from 21 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field i_alloc_sem has been changed from 19 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field unnamed0 has been changed from 28 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field i_mtime has been changed from 12 to 22. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field i_ctime has been changed from 13 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field i_mapping has been changed from 24 to 29. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field i_security has been changed from 35 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field i_nlink has been changed from 4 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field i_blkbits has been changed from 8 to 18. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field i_state has been changed from 31 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field i_devices has been changed from 27 to 32. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field i_sb has been changed from 22 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 21 | The relative position of field i_version has been changed from 9 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 22 | The relative position of field i_atime has been changed from 11 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 23 | The relative position of field i_data has been changed from 25 to 30. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 24 | The relative position of field i_bytes has been changed from 15 to 25. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 25 | The relative position of field i_count has been changed from 3 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 26 | The relative position of field i_mutex has been changed from 18 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 27 | The relative position of field i_op has been changed from 20 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 28 | The relative position of field i_uid has been changed from 5 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 29 | Size of field unnamed0 has been changed from 8 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 30 | The relative position of field i_rdev has been changed from 7 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field i_generation has been changed from 29 to 33. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field i_hash has been changed from 0 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field dirtied_when has been changed from 32 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field i_blocks has been changed from 14 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field i_fsnotify_mask has been changed from 30 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field i_ino has been changed from 2 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field i_lock has been changed from 17 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field i_size has been changed from 10 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field i_sb_list has been changed from 1 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field i_flock has been changed from 23 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field i_flags has been changed from 33 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field create has been changed from 0 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field link has been changed from 2 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field mkdir has been changed from 5 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field readlink has been changed from 9 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field unlink has been changed from 3 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field put_link has been changed from 11 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field truncate has been changed from 12 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field permission has been changed from 13 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field follow_link has been changed from 10 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field check_acl has been changed from 14 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field lookup has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field symlink has been changed from 4 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field mknod has been changed from 7 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field rmdir has been changed from 6 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field rename has been changed from 8 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 16 | Field fallocate 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 | Type of field s_files has been changed from struct list_head (16 bytes) to struct list_head* (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | The pointer level of field s_files 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 show_devname has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 show_path has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_dentry has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field i_rcu has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field i_cdev has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 4 | Field i_pipe has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 5 | Field i_bdev has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field lock has been changed from struct rwlock_t to spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field marks_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 priority has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field class has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 3 | Type of field event has been changed from struct trace_event* (8 bytes) to struct trace_event (48 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | The relative position of field perf_refcount has been changed from 9 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Field perf_event_disable 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 perf_event_enable 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 | The relative position of field data has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field filter has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field mod has been changed from 7 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field binary 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 hex 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 raw 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 lost_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tmp_seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The relative position of field cpu has been changed from 10 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field ent has been changed from 8 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field seq has been changed from 7 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field started has been changed from 14 to 7. | 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 idx has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field leftover has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field pos has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field ts has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field pi_mutex has been changed from 48 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field post_doit has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field pre_doit has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 part0 has been changed from 456 bytes to 504 bytes. | 1) Size of the inclusive type has been 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 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. |
| 2 | Field info has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field __dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_streams has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_streams has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 map_urb_for_dma has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 unmap_urb_for_dma has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 bandwidth_mutex has been changed from struct mutex (32 bytes) to struct mutex* (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field speed has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The pointer level of field bandwidth_mutex 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 relative position of field uses_new_polling has been changed from 9 to 11. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field prepare_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field afg_function_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 conn_lists has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cvt_setups has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 no_sticky_stream has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inputs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_inputs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 items has been changed from 256 bytes to 576 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field label has been changed from char const* (8 bytes) to char[32] (32 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hid_get_raw_report has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field feature_mapping has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 reset_resume has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field resume has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field suspend has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field driver has been changed from 104 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 | Type of field field has been changed from struct hid_field*[64] (512 bytes) to struct hid_field*[128] (1024 bytes). | 1) Size of the inclusive type has been 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 node has been changed from struct rb_node (24 bytes) to struct timerqueue_node (32 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field _expires has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field active has been changed from struct rb_root (8 bytes) to struct timerqueue_head (16 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field first has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_bases has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 clock_base has been changed from struct hrtimer_clock_base[2] (128 bytes) to struct hrtimer_clock_base[3] (192 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The relative position of field clock_base has been changed from 1 to 9. | 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 userspace_clients_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field bus_lock has been changed from 48 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 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 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field driver has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Field unmask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member FBC_BAD_PLANE has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member FBC_MODE_TOO_LARGE has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member FBC_NOT_TILED has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member FBC_STOLEN_TOO_SMALL has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member FBC_UNSUPPORTED_MODE has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field deferred_free_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 gtt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field gtt_end has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gtt_mappable_end has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gtt_start has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 inactive_shrinker has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 interruptible has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pinned_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. |
| 9 | Field stolen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Size of field gtt_space has been changed from 56 bytes to 160 bytes. | 1) Size of the inclusive type has been 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 | The relative position of field gtt_mapping has been changed from 1 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field gtt_mtrr has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field size has been changed from size_t (8 bytes) to u32 (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bcs_acthd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field bcs_instdone has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field bcs_ipehr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field bcs_ipeir has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field bcs_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field error has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fence has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pinned_bo has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pipestat has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field vcs_acthd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field vcs_instdone has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 12 | Field vcs_ipehr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field vcs_ipeir has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field vcs_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Type of field batchbuffer has been changed from struct drm_i915_error_object*[2] (16 bytes) to struct drm_i915_error_object*[3] (24 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ring has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field base has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field exec_entry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field exec_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. |
| 5 | Field last_fenced_ring has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field last_fenced_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field ring_list has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field tiling_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. |
| 9 | Field exec_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. |
| 10 | Field exec_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. |
| 11 | Field fault_mappable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 map_and_fenceable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field pin_mappable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field sg_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. |
| 15 | Size of field fence_reg has been changed from 4 bytes to 5 bits. | Previous accesses of applications and library functions to this field may be broken. |
| 16 | The relative position of field bit_17 has been changed from 14 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field gtt_offset has been changed from 8 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field stride has been changed from 13 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field pages has been changed from 6 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field phys_obj has been changed from 19 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 21 | The relative position of field pin_filp has been changed from 18 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 22 | The relative position of field user_pin_count has been changed from 17 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 23 | The relative position of field gpu_write_list has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field page_cpu_valid has been changed from 16 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field fence_reg has been changed from 9 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field last_rendering_seqno has been changed from 11 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field madv has been changed from 21 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field tiling_mode has been changed from 12 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight_level has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 c_m has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field cfb_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field cfb_y has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 chipset_power has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field corr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 edp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 error_completion has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fstart has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gfx_power has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field gmbus has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gt_irq_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field irq_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field irq_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field is_ddr3 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field last_acthd_bsd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | Field last_count1 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 18 | Field last_count2 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Field last_instdone has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 20 | Field last_time1 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 21 | Field last_time2 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 22 | Field mchdev_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 23 | Field next_seqno has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 24 | Field panel_t12 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 25 | Field pch_pf_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 26 | Field pch_type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 27 | Field pm_iir has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 28 | 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. |
| 29 | Field r_t has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 30 | Field renderctx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 31 | Field rps_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 32 | Field rps_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. |
| 33 | Size of field display has been changed from 56 bytes to 96 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 34 | Size of field fence_regs has been changed from 128 bytes to 512 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 35 | Size of field mm has been changed from 360 bytes to 712 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 36 | Size of field opregion has been changed from 40 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 37 | Size of field sdvo_mappings has been changed from 8 bytes to 14 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 38 | Type of field ring has been changed from drm_i915_ring_buffer_t (80 bytes) to struct intel_ring_buffer[3] (960 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 39 | The relative position of field lid_notifier has been changed from 50 to 49. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 40 | The relative position of field pipestat 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. |
| 41 | The relative position of field lvds_ssc_freq has been changed from 49 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 42 | Field lvds_edid_good has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 43 | Field panel_wants_dither has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 44 | Field status_gfx_addr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field gen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field is_broadwater has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 is_crestline has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 is_ivybridge has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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 this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dvo_port has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field dvo_wiring has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field initialized has been changed from 3 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field slave_addr has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member IEEE80211_WORK_ASSOC has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member IEEE80211_WORK_REMAIN_ON_CHANNEL has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field basic_rates has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_connection_loss_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 beacon_crc_valid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field beacon_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. |
| 4 | Field driver_smps_mode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field request_smps_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 agg_queue_stop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 disable_dynamic_ps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field dynamic_ps_forced_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. |
| 4 | Field dynamic_ps_user_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. |
| 5 | Field ifa_notifier has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 key_mtx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 leave_oper_channel_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field mtx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 running_rx_handler has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rx_skb_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field sched_scan_ies has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sched_scan_stopped_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. |
| 13 | Field sched_scanning has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field tpt_led_trigger has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Size of field hw has been changed from 96 bytes to 104 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 16 | Type of field mc_list has been changed from struct dev_addr_list* (8 bytes) to struct netdev_hw_addr_list (24 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_filter_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 default_multicast_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. |
| 3 | Field default_unicast_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. |
| 4 | Field skb_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field 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. |
| 7 | Size of field u has been changed from 576 bytes to 584 bytes. | 1) Size of the inclusive type has been 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 wdev has been changed from 528 bytes to 560 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field vif has been changed from 56 bytes to 96 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 mesh has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of field ap has been changed from 312 bytes to 320 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field ibss has been changed from 248 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field mgd has been changed from 576 bytes to 584 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 stats has been changed from 56 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field addr_list has been changed from struct inet6_ifaddr* (8 bytes) to struct list_head (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 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 state_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field dead 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 if_next 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 lst_next 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 icmpv6msg 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 icmpv6 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 killall has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field sfmode has been changed from 4 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field tomb has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field sources has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field icsk_inet has been changed from 744 bytes to 776 bytes. | 1) Size of the inclusive type has been 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 fragments_tail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inet_opt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field sk has been changed from 584 bytes to 600 bytes. | 1) Size of the inclusive type has been 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 nexthop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_daddr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field tw_rcv_saddr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 | Field daddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tcp_ts 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 ip_id_count 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 rid 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 tcp_ts_stamp has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field absinfo has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 hint_events_per_packet has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mtsize has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 propbit has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 trkid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Type of field sync has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 9 | The relative position of field key has been changed from 23 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 led has been changed from 24 to 23. | 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 sync has been changed from 21 to 35. | 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 snd has been changed from 25 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field sw has been changed from 26 to 25. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_id has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field active has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fdi_lanes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Size of field base has been changed from 328 bytes to 560 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Field cursor_visble has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field base has been changed from struct drm_connector (880 bytes) to struct drm_encoder (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. |
| 2 | Field dev_priv 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 hw_wedged has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field virt_addr 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 thread_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | The relative position of field irq has been changed from 5 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field thread_fn has been changed from 7 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field dev_id has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field dir has been changed from 6 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field name has been changed from 2 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field next has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field thread has been changed from 8 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field thread_flags has been changed from 9 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field events has been changed from unsigned long[25] (200 bytes) to unsigned long[27] (216 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_prefsrc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dst has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt6i_prefsrc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt6i_peer_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. |
| 4 | Field rt6i_peer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | The relative position of field rt6i_metric has been changed from 4 to 7. | 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 rt6i_nfheader_len has been changed from 6 to 10. | 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 rt6i_protocol has been changed from 7 to 11. | 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 rt6i_flow_cache_genid has been changed from 10 to 9. | 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 rt6i_dst has been changed from 9 to 4. | 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 rt6i_src has been changed from 11 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field rt6i_flags has been changed from 3 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field rt6i_ref has been changed from 5 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field rt6i_idev has been changed from 0 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field rt6i_table has been changed from 8 to 0. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field fib_dead has been changed from int (4 bytes) to unsigned char (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field fib_protocol has been changed from int (4 bytes) to unsigned char (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 4 | Type of field fib_metrics has been changed from u32[14] (56 bytes) to u32* (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | The pointer level of field fib_metrics 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 relative position of field fib_dead has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field fib_flags has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field table has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tb_num_default has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 shm_tot has been changed from int (4 bytes) to unsigned long (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field shm_ctlmni has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field shm_tot has been changed from 13 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_addr_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 sysctl_ping_group_range has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cache_resolve_queue_len 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 maxvif 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 mfc_cache_array 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 mroute_do_assert 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 mroute_do_pim 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 mroute_reg_vif_num 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 vif_table 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 nhoff has been changed from __u32 (4 bytes) 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field dontfrag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 min_hopcount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rxpmtu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 ip6_dst_ops has been changed from 88 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field affinity_hint has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field affinity_notify has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field core_internal_state__do_not_mess_with_it has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field irq_data has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field status_use_accessors 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. |
| 6 | The relative position of field pending_mask has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field chip 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. |
| 8 | Field chip_data 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. |
| 9 | Field handler_data 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. |
| 10 | Field irq 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. |
| 11 | Field msi_desc 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. |
| 12 | Field node 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. |
| 13 | Field status has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member T_COMMIT has been changed from 4 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member T_FLUSH has been changed from 3 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kbdmode has been changed from 2 bits to 3 bits. | 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 DIE_CALL has been changed from 11 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member DIE_GPF has been changed from 10 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member DIE_KERNELDEBUG has been changed from 8 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member DIE_NMIUNKNOWN has been changed from 14 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member DIE_PAGE_FAULT has been changed from 13 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member DIE_TRAP has been changed from 9 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field irqs_sum has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vet_description has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field init has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cred 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. |
| 3 | Field stdin 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 blink_brightness has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 blink_delay_off has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field blink_delay_on has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 blink_timer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eh_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field eh_owner has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 device has been changed from 2384 bytes to 3184 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 bmdma_prd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 bmdma_prd_dma has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 scsi_scan_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field sff_pio_task has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field sff_pio_task_link has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 target_lpm_policy has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field link has been changed from 2752 bytes to 3960 bytes. | 1) Size of the inclusive type has been 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 qcmd has been changed from 7168 bytes to 6912 bytes. | 1) Size of the inclusive type has been 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 drain_fifo has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field disable_pm has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cursg has been changed from 15 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field cursg_ofs has been changed from 16 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 sg has been changed from 18 to 16. | 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 sgent has been changed from 17 to 15. | 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 h_srcaddrlen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field auditdeny has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed0 has been changed from 40 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field selinux_audit_data has been changed from 40 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcast_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 max_report_rates has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field napi_weight has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field change_interface has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field get_survey has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field resume has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sched_scan_start has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sched_scan_stop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 set_frag_threshold has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 suspend has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field noise has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field bss_conf has been changed from 40 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 status has been changed from 32 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_op 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 e_indexes 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 attr has been changed from 40 bytes to 32 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field log has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_set has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field can_decrease_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field plug_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 ready has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field bitmap_info has been changed from 88 bytes to 96 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Field max_write_behind has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field meta_bdev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 new_raid_disk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from 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 om_rtt has been changed from unsigned long long to ktime_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field om_execute has been changed from unsigned long long to ktime_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field om_queue has been changed from unsigned long long to ktime_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_mmap_lock has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field truncate_count has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field mmap_sem has been changed from 13 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field page_table_lock has been changed from 14 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 29 to 32. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member NUMA_FOREIGN has been changed from 25 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member NUMA_HIT has been changed from 23 to 25. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member NUMA_INTERLEAVE_HIT has been changed from 26 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member NUMA_LOCAL has been changed from 27 to 29. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member NUMA_MISS has been changed from 24 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member NUMA_OTHER has been changed from 28 to 30. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[29] (29 bytes) to s8[32] (32 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field reclaim_stat has been changed from 72 bytes to 32 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field vm_stat has been changed from atomic_long_t[29] (232 bytes) to atomic_long_t[32] (256 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 prev_priority 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 nr_saved_scan 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 mattr has been changed from 64 bytes to 56 bytes. | 1) Size of the inclusive type has been 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 target_list has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tracepoints_ptrs has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field core_ro_size has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field init_ro_size has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field source_list has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | The pointer level of field trace_events has been increased from 1 to 2. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| 7 | The relative position of field num_trace_bprintk_fmt has been changed from 46 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field trace_bprintk_fmt_start has been changed from 45 to 46. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field percpu has been changed from 41 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field percpu_size has been changed from 42 to 43. | Applications will access incorrect memory when attempting to access this field. |
| 11 | Field num_ctors has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 12 | Field tracepoints has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 13 | Field ctors has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 14 | Field modules_which_use_me has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field elemsize has been changed from 3 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field num has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_pcp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mnt_fsnotify_marks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field mnt_longterm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mnt_writers 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 mask has been changed from unsigned long[4] (32 bytes) to unsigned long[512] (4096 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 inode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash_rnd has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ha_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The relative position of field used has been changed from 4 to 9. | 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 type has been changed from 9 to 13. | 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 output has been changed from 16 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field flags has been changed from 7 to 11. | 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 refcnt has been changed from 15 to 6. | 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 timer has been changed from 18 to 8. | 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 ha has been changed from 13 to 15. | 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 dead has been changed from 10 to 14. | 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 lock has been changed from 12 to 5. | 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 arp_queue has been changed from 17 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field nud_state has been changed from 8 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field probes has been changed from 11 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field confirmed has been changed from 5 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field dev has been changed from 3 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field updated has been changed from 6 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field hh has been changed from 14 to 16. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field passive has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ipv4 has been changed from 360 bytes to 248 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field ipv6 has been changed from 392 bytes to 512 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field xfrm has been changed from 592 bytes to 832 bytes. | 1) Size of the inclusive type has been 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 dev_base_head has been changed from 8 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field dev_index_head has been changed from 10 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field dev_name_head has been changed from 9 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field exit_list has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field proc_net_stat has been changed from 5 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field rtnl has been changed from 13 to 8. | 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 rules_mod_lock has been changed from 12 to 1. | 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 rules_ops has been changed from 11 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field sysctls has been changed from 6 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field xfrm has been changed from 25 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field cleanup_list has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field genl_sock has been changed from 14 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field list has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field loopback_dev has been changed from 7 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field proc_net has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field _rx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 addr_assign_type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field dismantle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 hw_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. |
| 5 | Field ingress_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field mc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 num_rx_queues has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field pcpu_refcnt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pm_qos_req has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field prio_tc_map has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field queues_kset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 12 | Field rx_cpu_rmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 13 | Field rx_dropped has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 14 | Field rx_handler has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 15 | Field rx_handler_data has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field tc_to_txq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 17 | Field wanted_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. |
| 18 | Field unnamed0 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 20 | Size of field reg_state has been changed from 2 bytes to 1 byte. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 21 | Type of field features has been changed from unsigned long (8 bytes) to u32 (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 22 | Type of field vlan_features has been changed from unsigned long (8 bytes) to u32 (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 23 | The relative position of field _tx has been changed from 51 to 52. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 24 | The relative position of field addr_list_lock has been changed from 37 to 35. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 25 | The relative position of field broadcast has been changed from 50 to 51. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 26 | The relative position of field dev has been changed from 70 to 71. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 27 | The relative position of field dev_addr has been changed from 48 to 49. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 28 | The relative position of field dev_addrs has been changed from 49 to 50. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 29 | The relative position of field dev_list has been changed from 10 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 30 | The relative position of field dma has been changed from 8 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 31 | The relative position of field features has been changed from 13 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 32 | The relative position of field flags 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. |
| 33 | The relative position of field garp_port has been changed from 69 to 70. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 34 | The relative position of field ifindex has been changed from 14 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 35 | The relative position of field index_hlist has been changed from 61 to 63. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 36 | The relative position of field link_watch_list has been changed from 62 to 64. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 37 | The relative position of field mtu has been changed from 26 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 38 | The relative position of field napi_list has been changed from 11 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 39 | The relative position of field needed_tailroom has been changed from 30 to 31. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 40 | The relative position of field netdev_ops has been changed from 17 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 41 | The relative position of field operstate has been changed from 24 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 42 | The relative position of field real_num_tx_queues has been changed from 53 to 54. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 43 | The relative position of field reg_state has been changed from 63 to 65. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 44 | The relative position of field rtnl_link_state has been changed from 64 to 66. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 45 | The relative position of field state has been changed from 9 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 46 | The relative position of field stats has been changed from 16 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 47 | The relative position of field sysfs_groups has been changed from 71 to 72. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 48 | The relative position of field trans_start has been changed from 57 to 59. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 49 | The relative position of field tx_global_lock has been changed from 56 to 57. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 50 | The relative position of field tx_queue_len has been changed from 55 to 56. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 51 | The relative position of field uc has been changed from 35 to 36. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 52 | The relative position of field vlan_features has been changed from 73 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 53 | The relative position of field watchdog_timeo has been changed from 58 to 60. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 54 | The relative position of field watchdog_timer has been changed from 59 to 61. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 55 | Type of field priv_flags has been changed from unsigned short (2 bytes) to unsigned int (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 56 | The relative position of field destructor has been changed from 65 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 57 | The relative position of field ethtool_ops has been changed from 18 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 58 | The relative position of field hard_header_len has been changed from 28 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 59 | The relative position of field header_ops has been changed from 19 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 60 | The relative position of field if_port has been changed from 7 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 61 | The relative position of field iflink has been changed from 15 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 62 | The relative position of field link_mode has been changed from 25 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 63 | The relative position of field master has been changed from 31 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 64 | The relative position of field nd_net has been changed from 67 to 69. | Applications will access incorrect memory when attempting to access this field. |
| 65 | The relative position of field needed_headroom has been changed from 29 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 66 | The relative position of field npinfo has been changed from 66 to 68. | Applications will access incorrect memory when attempting to access this field. |
| 67 | The relative position of field num_tx_queues has been changed from 52 to 53. | Applications will access incorrect memory when attempting to access this field. |
| 68 | The relative position of field padded has been changed from 23 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 69 | The relative position of field qdisc has been changed from 54 to 55. | Applications will access incorrect memory when attempting to access this field. |
| 70 | The relative position of field rtnl_link_ops has been changed from 72 to 73. | Applications will access incorrect memory when attempting to access this field. |
| 71 | The relative position of field todo_list has been changed from 60 to 62. | Applications will access incorrect memory when attempting to access this field. |
| 72 | The relative position of field type has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 73 | The relative position of field uc_promisc has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 74 | The relative position of field unreg_list has been changed from 12 to 10. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_get_stats64 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_netpoll_cleanup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ndo_netpoll_setup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field numa_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 tx_bytes 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 tx_dropped 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 tx_packets 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 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 | Field cpu_collision has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 csd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 input_queue_tail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field output_queue_tailp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 process_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field processed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rps_ipi_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. |
| 9 | Field rps_ipi_next has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | The relative position of field input_pkt_queue has been changed from 1 to 3. | 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 family has been changed from int (4 bytes) to u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eff_cap 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 loginuid 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 sessionid 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 sid has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ct_net has been changed from 9 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field ext has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field proto has been changed from 7 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field help has been changed from 32 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ct_h323_info has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 2 | Field ct_pptp_info has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 3 | Field ct_sane_info has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NF_CT_EXT_NUM has been changed from 5 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[5] (5 bytes) to u8[3] (3 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 | Type of this type has been changed from struct to union. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ls_owner has been changed from fl_owner_t (8 bytes) to struct nfs4_lock_owner (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 ls_seqid has been changed from 4 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field ls_flags has been changed from 3 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field ls_count has been changed from 8 to 7. | 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 ls_id has been changed from 6 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field ls_sequence has been changed from 5 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field ls_owner has been changed from 2 to 8. | 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 ls_stateid has been changed from 7 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | Type of field ls_stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field open_stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_server_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 commits_outstanding has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 layout has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vfs_inode has been changed from 616 bytes to 592 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 lock_context has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dir_cookie 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 cl_seqid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cl_mvops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lockowner_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 openowner_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. |
| 3 | Field delegations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 roc_rpcwaitq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pnfs_curr_ld has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 state_owners has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 time_delta has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field backing_dev_info has been changed from 432 bytes to 520 bytes. | 1) Size of the inclusive type has been 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 wb_lock_context has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fattr has been changed from 184 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_slot has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mounted_on_fileid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 seq_res has been changed from 32 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | Type of field delegation has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ds_clp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lseg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mds_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mds_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field pnfs_error has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 read_done_cb has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Size of field args has been changed from 56 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. |
| 8 | Size of field fattr has been changed from 184 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field res has been changed from 48 bytes to 56 bytes. | 1) Size of the inclusive type has been 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 task has been changed from 264 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_context has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_res has been changed from 32 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rename_done has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rename_setup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 file_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ds_clp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ds_commit_index has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field lseg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mds_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field mds_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field pnfs_error has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 write_done_cb has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field args has been changed from 72 bytes to 80 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field fattr has been changed from 184 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 10 | Size of field res has been changed from 64 bytes to 72 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 11 | Size of field task has been changed from 264 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_context has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_res has been changed from 32 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mattr has been changed from 64 bytes to 56 bytes. | 1) Size of the inclusive type has been 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field __aer_firmware_first_valid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fw_addr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field 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. |
| 4 | Field mmio_always_on has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Type of field res_attr has been changed from struct bin_attribute*[12] (96 bytes) to struct bin_attribute*[18] (144 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Type of field res_attr_wc has been changed from struct bin_attribute*[12] (96 bytes) to struct bin_attribute*[18] (144 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Type of field resource has been changed from struct resource[12] (672 bytes) to struct resource[18] (1008 bytes). | 1) Size of the inclusive type has been 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 driver has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 368 bytes to 400 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 driver has been changed from 104 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 | Field hw_ptr_buffer_jiffies has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field no_period_wakeup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_pm_qos_req has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field period_left has been changed from struct atomic64_t to struct local64_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field prev_count has been changed from struct atomic64_t to struct local64_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buffer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field child_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field header_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field hlist_entry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field refcount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 shadow_ctx_time has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field tp_event has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 count has been changed from struct atomic64_t to struct local64_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bp_addr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field bp_len has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rotate_disable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field page has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field locked 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 add has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 del has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 entry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field event_init has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field name has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field pmu_disable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field pmu_disable_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field pmu_enable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 task_ctx_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. |
| 10 | Field type has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | The relative position of field read has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field start has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field stop has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed2 has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field info has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hwtstamp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rxtstamp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 txtstamp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Size of field driver has been changed from 104 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 | Field buffers has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 bufs has been changed from struct pipe_buffer[16] (640 bytes) to struct pipe_buffer* (8 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field tmp_page has been changed from 3 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The pointer level of field bufs 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 mfd_cell has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field driver has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field plist has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field should_wakeup 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 status 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 dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field link has been changed from 168 bytes to 176 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field driver has been changed from 104 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 | Field can_wakeup has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field filename_trans has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 filename_trans_ttypes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field type_attr_map_array has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_offset has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 30 to 31. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_PROP_CAPACITY_LEVEL has been changed from 31 to 32. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_PROP_CHARGE_AVG has been changed from 22 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY has been changed from 20 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY_DESIGN has been changed from 18 to 19. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL has been changed from 19 to 20. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN has been changed from 17 to 18. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member POWER_SUPPLY_PROP_CHARGE_NOW has been changed from 21 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 9 | Value of member POWER_SUPPLY_PROP_CURRENT_AVG has been changed from 14 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 10 | Value of member POWER_SUPPLY_PROP_CURRENT_NOW has been changed from 13 to 14. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 11 | Value of member POWER_SUPPLY_PROP_ENERGY_AVG has been changed from 29 to 30. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 12 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY has been changed from 27 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 13 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY_DESIGN has been changed from 25 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 14 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL has been changed from 26 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 15 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL_DESIGN has been changed from 24 to 25. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 16 | Value of member POWER_SUPPLY_PROP_ENERGY_NOW has been changed from 28 to 29. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 17 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 39 to 41. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 18 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 38 to 40. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 19 | Value of member POWER_SUPPLY_PROP_POWER_AVG has been changed from 16 to 17. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 20 | Value of member POWER_SUPPLY_PROP_POWER_NOW has been changed from 15 to 16. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 21 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 40 to 42. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 22 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 32 to 33. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 23 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 33 to 34. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 24 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG has been changed from 35 to 36. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 25 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW has been changed from 34 to 35. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 26 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 37 to 38. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 27 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 36 to 37. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field property_is_writeable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field set_property has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 namelen has been changed from unsigned short (2 bytes) to unsigned int (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field power has been changed from 2168 bytes to 1664 bytes. | 1) Size of the inclusive type has been 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 984 bytes to 992 bytes. | 1) Size of the inclusive type has been 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 states has been changed from 1152 bytes to 640 bytes. | 1) Size of the inclusive type has been 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 x86_capability has been changed from __u32[9] (36 bytes) to __u32[10] (40 bytes). | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field compute_unit_id has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field x86_hyper_vendor has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field llc_shared_map 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 fpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field debugctlmsr 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 ds_ctx 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 allocated_dquots 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 cache_hits 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 drops 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 free_dquots 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 lookups 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 reads 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 syncs 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 writes 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 quota_on_meta has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field set_xquota 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 get_xquota 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 n_cbs_adopted has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field n_cbs_invoked has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field n_cbs_orphaned has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field n_rp_report_qs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dynticks_nmi_snap has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dynticks_nmi_nesting 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 | Type of field dynticks has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 3 | Field dynticks_nmi has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakemask has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field blocked_tasks has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field levelspread has been changed from u8[1] (1 byte) to u8[2] (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field level has been changed from struct rcu_node*[1] (8 bytes) to struct rcu_node*[2] (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 node has been changed from struct rcu_node[1] (256 bytes) to struct rcu_node[5] (1280 bytes). | 1) Size of the inclusive type has been 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 real_end has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_overrun has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 lost_events has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The relative position of field buffer has been changed from 1 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field lock has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field lock_key has been changed from 4 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field read_stamp has been changed from 17 to 18. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field record_disabled has been changed from 18 to 1. | 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 commit_overrun has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field commit_page has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field commits has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field committing has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field entries has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field head_page has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field overrun has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field pages has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field read has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field reader_lock has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field reader_page has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field tail_page has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field write_stamp has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field refcount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 root has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dst has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt_key_dst has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt_route_iif has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt_mark has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt_key_src has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rt_oif has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_irq_enable 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 dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field wait_list has been changed from 32 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 | The relative position of field qstats has been changed from 20 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field on_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 skip has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nohz_stamp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field stop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 active_balance_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field clock_task has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field last_load_update_tick has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 nohz_balance_kick has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cfs has been changed from 176 bytes to 216 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Size of field rq_sched_info has been changed from 40 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field rt has been changed from 1720 bytes to 1704 bytes. | 1) Size of the inclusive type has been 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 | Field bkl_count 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 pushable_tasks has been changed from 32 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 load_weight has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tk_owner has been changed from 21 to 15. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field tk_callback has been changed from 9 to 5. | 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 u has been changed from 18 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 tk_calldata has been changed from 12 to 8. | 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 tk_status has been changed from 4 to 16. | 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 tk_start has been changed from 20 to 14. | 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 tk_msg has been changed from 5 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field tk_priority has been changed from 22 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field tk_timeouts 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. |
| 10 | The relative position of field tk_flags has been changed from 14 to 17. | 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 tk_rebind_retry has been changed from 8 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field tk_garb_retry has been changed from 6 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field tk_ops has been changed from 11 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field tk_action has been changed from 10 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | Type of field tk_start has been changed from unsigned long to ktime_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 16 | The relative position of field tk_pid has been changed from 23 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field tk_waitqueue has been changed from 17 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field tk_runstate has been changed from 15 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field tk_cred_retry has been changed from 7 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field tk_timeout has been changed from 13 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field tk_workqueue has been changed from 16 to 11. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field yield_to_task has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field statistics has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sgp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bkl_count 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 nr_threads has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 threadgroup_fork_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpuset_slab_spread_rotor has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field group_stop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mems_allowed_seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field on_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. |
| 5 | Field on_rq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 plug has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sched_task_group has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wake_entry has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Size of field sched_info has been changed from 40 bytes to 32 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 10 | Size of field se has been changed from 376 bytes to 344 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 11 | Size of field pi_waiters has been changed from 32 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. |
| 12 | Size of field thread has been changed from 192 bytes to 184 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | The relative position of field creds has been changed from 0 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field fp has been changed from 1 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field requeue_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 | Size of field sdev_dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field sdev_gendev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field idx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field gendrv has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field shost_dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field shost_gendev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sg_prot_tablesize has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 unlock_native_capacity has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sb_remount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 secmark_refcount_dec has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 secmark_refcount_inc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 secmark_relabel_packet has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field set_termios has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field child_node has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field children has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field private has been removed from 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 cache has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rxhash 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 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. |
| 2 | The relative position of field offset has been changed from 4 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field ctor has been changed from 10 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field align has been changed from 12 to 13. | 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 refcount has been changed from 9 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field min_partial has been changed from 13 to 2. | 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 min has been changed from 7 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field allocflags has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field oo has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field max has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field inuse has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field objsize has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field size has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field tid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 mibs has been changed from unsigned long[28] (224 bytes) to unsigned long[27] (216 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[4] (32 bytes) to unsigned long[5] (40 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[77] (616 bytes) to unsigned long[81] (648 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 rmem_alloc 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 head has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field tail has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field len has been changed from 2 to 0. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field compat_ioctl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 clear_sk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_gso_max_segs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_rxhash has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field sk_route_nocaps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sk_peer_cred has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sk_peer_pid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 __sk_common has been changed from 72 bytes to 80 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | The relative position of field sk_filter has been changed from 38 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field sk_error_queue has been changed from 27 to 29. | 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 sk_gso_type has been changed from 22 to 25. | 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 sk_backlog has been changed from 8 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field sk_priority has been changed from 35 to 36. | 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 sk_receive_queue has been changed from 16 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field sk_shutdown has been changed from 1 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field sk_lock has been changed from 7 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field sk_err_soft has been changed from 31 to 33. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field sk_max_ack_backlog has been changed from 34 to 35. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field sk_dst_cache has been changed from 10 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field sk_gso_max_size has been changed from 23 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field sk_policy has been changed from 11 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field sk_prot_creator has been changed from 28 to 30. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 21 | The relative position of field sk_rcvlowat has been changed from 24 to 27. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 22 | Type of field sk_dst_lock has been changed from struct rwlock_t to spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 23 | The relative position of field sk_callback_lock has been changed from 29 to 31. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field sk_flags has been changed from 25 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field sk_forward_alloc has been changed from 19 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field sk_no_check has been changed from 2 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field sk_wmem_queued has been changed from 18 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field sk_drops has been changed from 32 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 29 | The relative position of field sk_route_caps has been changed from 21 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 30 | The relative position of field sk_userlocks has been changed from 3 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field sk_protocol has been changed from 4 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field sk_type has been changed from 5 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field sk_ack_backlog has been changed from 33 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field sk_sndtimeo has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field sk_allocation has been changed from 20 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field sk_lingertime has been changed from 26 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field sk_err has been changed from 30 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field sk_rcvtimeo has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field sk_write_queue has been changed from 17 to 16. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_dontcopy_begin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field skc_rcv_saddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field skc_daddr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | The relative position of field skc_reuse has been changed from 6 to 3. | 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 skc_tx_queue_mapping has been changed from 2 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field unnamed1 has been changed from 3 to 5. | 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 skc_bound_dev_if has been changed from 7 to 4. | 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 skc_family has been changed from 4 to 1. | 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 skc_prot has been changed from 9 to 6. | 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 skc_state has been changed from 5 to 2. | 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 skc_net has been changed from 10 to 7. | 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 skc_refcnt has been changed from 1 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | Size of field unnamed1 has been changed from 4 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 14 | Size of field unnamed0 has been changed from 16 bytes to 4 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_hash has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field skc_u16hashes has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field skc_nulls_node has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 4 | Field skc_node has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_portaddr_node has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field skc_bind_node has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field skc_hash has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| 4 | Field skc_u16hashes has been removed from this union. | 1) Applications may access incorrect memory when attempting to access this field. 2) Size of the union has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_pages_max has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tur_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 cdi has been changed from 112 bytes to 120 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcmcia_irq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field pcmcia_state has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field resource_setup_new has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field resource_setup_old has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tid_rx_timer_expired has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tid_start_tx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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 avg_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 gtk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 last_connected has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 last_rx_rate_flag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field last_rx_rate_idx has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field lost_packets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ptk has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Size of field ampdu_mlme has been changed from 312 bytes to 480 bytes. | 1) Size of the inclusive type has been 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 rcu_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field reorder_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field reorder_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. |
| 4 | Field shutdown has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_dropme has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rq_chandle has been changed from 8 bytes to 16 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_table has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field used has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field ctl_entry has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field attr has been changed from 24 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 attr has been changed from 24 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 resume 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 shutdown 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 suspend 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 attr has been changed from 24 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 s_ns has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 inet_conn has been changed from 1096 bytes to 1136 bytes. | 1) Size of the inclusive type has been 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 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field slack 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 start_site has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field base has been changed from 4 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field start_comm has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field data has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field function has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field start_pid has been changed from 7 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field active has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field local has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 need_flush has been changed from 4 bytes to 1 bit. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Type of field pages has been changed from struct page*[506] (4048 bytes) to struct page*[8] (64 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 root has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field print_max has been changed from 16 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field tracepoint has been increased from 1 to 2. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tclass has been changed from 128 bytes to 152 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field class has been changed from 104 bytes to 128 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field work has been changed from struct delayed_work (112 bytes) to struct work_struct (32 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field buf has been changed from 152 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 | Field scan_dwork has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 current_sg has been changed from 104 bytes to 88 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ep0 has been changed from 72 bytes to 64 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Field autosuspend_disabled has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field drvwrap has been changed from 112 bytes to 120 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field drvwrap has been changed from 112 bytes to 120 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ss_ep_comp has been changed from struct usb_host_ss_ep_comp* (8 bytes) to struct usb_ss_ep_comp_descriptor (6 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field ss_ep_comp has been changed from 4 to 1. | 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 urb_list has been changed from 1 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field ep_dev has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 368 bytes to 400 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field driver has been changed from 104 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field uidhash_table has been changed from struct hlist_head[256] (2048 bytes) to struct hlist_head[128] (1024 bytes). | 1) Size of the inclusive type has been 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 368 bytes to 400 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 flush_mutex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field rescuer has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mayday_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. |
| 4 | Field saved_max_active has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field flusher_queue has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field first_flusher has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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 | Field nr_cwqs_to_flush has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 flusher_overflow has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | The relative position of field name has been changed from 2 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field tagged_writepages has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field no_nrwrite_index_update has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mapping has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 timers has been changed from 24 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field jumpstack has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 stackptr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field family has been changed from 13 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field hooks has been changed from 11 to 12. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field revision has been changed from 14 to 2. | 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 table has been changed from 8 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field checkentry has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field compat_from_user has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field compat_to_user has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field compatsize has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field destroy has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field me has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field proto has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field target has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field targetsize has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field xfrm4_dst_ops has been changed from 88 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field xfrm6_dst_ops has been changed from 88 bytes to 192 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The relative position of field nlsk has been changed from 19 to 17. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field nlsk_stash has been changed from 20 to 18. | 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 sysctl_aevent_etime has been changed from 21 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field sysctl_aevent_rseqth has been changed from 22 to 20. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field sysctl_hdr has been changed from 25 to 23. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field xfrm4_dst_ops has been changed from 17 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 xfrm6_dst_ops has been changed from 18 to 25. | 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 sysctl_acq_expires has been changed from 24 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field sysctl_larval_drop has been changed from 23 to 21. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 flo has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field find_bundle 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 replay_esn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tfcpad has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 preplay_esn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 repl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_finish has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 init_temprop has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_rtt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field rq_xmit_bytes_sent has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Type of field rq_reply_bytes_recvd has been changed from int (4 bytes) to size_t (8 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field rq_reply_bytes_recvd has been changed from 6 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | Type of field rq_xtime has been changed from unsigned long to ktime_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field connect_timeout 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 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 | The parameter alg became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pos became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter val became passed in rdx 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 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 48 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 864 bytes to 984 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 32 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter domain has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 3rd parameter busnum has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter a became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter bind became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ref became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter act became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter align of type size_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter min_dump_alloc of type u16 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter initiator became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sta became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter tid became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter timeout of type u16 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter initiator has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter alg_name became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter frontend became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mask became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter type became passed on stack instead of rdx 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 352 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter len became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter string became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter list of type struct list_head** has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter watch became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter list has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter watch has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cred became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter lookupflags became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter task became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bdi became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sync became passed on stack instead of rsi 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed on stack instead of rdi 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter blocks has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter blocks has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter x became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter limits became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter min became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter max_hw_sectors became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter q became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lim became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter req became passed on stack instead of rdi 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter kill_dirty of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bdev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter holder of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter fsdata has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter file became passed in rdi 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 r8 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter len became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter mapping became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter pagep became passed in r9 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 6 | The parameter pos became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bh became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bh became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cache_request became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter detail became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter h became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cps of type struct cb_process_state* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cps of type struct cb_process_state* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cap became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 408 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 224 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 224 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 224 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 224 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter info of type struct partition_meta_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task_setup_data became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter c became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter i1 became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter i2 became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from __u32[9] (36 bytes) to __u32[10] (40 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter policy has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 3rd parameter lp has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 200 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 200 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter id became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter numid became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter wiphy_idx became passed on stack instead of rdi 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 152 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[288] const (2304 bytes) to char const*[320] const (2560 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2304 bytes to 2560 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dontfrag of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter p1 became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p2 became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter buflen became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter path became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter loops became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dst has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter validate_stateid has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter delegation became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ifindex became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi 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 rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter skb became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ifindex became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter storage of type struct rtnl_link_stats64* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter dev became passed in rdi 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 rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter inc became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter buffer has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 3rd parameter len has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 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 | The pointer level of 2nd parameter name has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Type of 2nd parameter name has been changed from char const* to u32 (became non-const). | This function may change parameter name, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from unsigned long (8 bytes) to u32 (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long (8 bytes) to u32 (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter master became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter slave became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter skb became passed in rdi 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 rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rootdev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter alen has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 4th parameter glbl has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter from became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter to became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter num_pages has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nr_pages has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 2nd parameter result has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | Type of return value has been changed from int (4 bytes) to struct dm_kcopyd_client* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter rh became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter index became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter t became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter integrity 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 md became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clone became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter error became passed in rsi 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 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fault_reason became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter fault_type became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter reserve has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter inode became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter number became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter warn became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter number became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter reserve became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dquot became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter type became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drv became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter size became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter connector became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter init_val became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter property became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter connector became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter property became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter value became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter encoder became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter connector became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter edid became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter edid became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter blank became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter info became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter fb has been changed from struct drm_framebuffer (168 bytes) to struct drm_fb_helper (184 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fb_create has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter kref has been changed from struct kref (4 bytes) to struct drm_gem_object (136 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ht became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter order became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dev of type struct net_device* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter initial_ref of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter initial_obsolete of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter flags became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter regs became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter signr became passed in rdx 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 112 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 112 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 112 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 112 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 112 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dplx of type u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pa_data has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bus became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter func became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter slot became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bus became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter func became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter slot became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter force_poll has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter regs has been changed from struct err_regs (20 bytes) to struct mce (88 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[16] (128 bytes) to char const*[9] (72 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 128 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter plug has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter plug has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter supported 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 376 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gpe_block_address became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter gpe_block_base_number became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_device became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter interrupt_number became passed in r8 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter register_count became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 6 | The parameter return_gpe_block became passed in r9 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ignored of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter address became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter context became passed on stack instead of r8 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_device became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter gpe_number became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter type became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter gpe_device became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_number became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter gpe_device became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_number became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ep became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter thread_id has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter info became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter state became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flp has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 5th parameter dev has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Base type of 6th parameter spec_dst has been changed from unsigned int (4 bytes) to struct net_device (1600 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter flp has been changed from struct flowi (64 bytes) to struct flowi4 (32 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter fib_flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter flp has been changed from struct flowi (64 bytes) to struct flowi4 (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to long (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter class_driver became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter intf became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to unsigned long (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter iocb became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter iov became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter nr_segs became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter pos became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter i became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fs became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flen has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter key became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pid became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sync became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 12 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter disk became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter flags became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter piter became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter devt became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter partno became passed on stack instead of rsi 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter devname of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter devname of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter group_info became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter new became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hcd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter irqflags became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter irqnum became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter spdif_ctls of type unsigned short has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tim became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lhs became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rhs became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter delta became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter expires became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mode became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter page became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter size became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter tsk has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drnum became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter len became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter probe of type int(*)(struct i2c_adapter*, unsigned short) has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 144 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 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 144 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 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 144 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi 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 16 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (1544 bytes) to struct intel_ring_buffer (320 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter align of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter obj became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by 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 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter map_and_fenceable of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter pipelined 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 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter obj became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter obj became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter resume has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buflen of type size_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter clp has been changed from struct nfs_client (712 bytes) to struct nfs_server (1144 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter clp has been changed from struct nfs_client (712 bytes) to struct nfs_server (1144 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buflen of type size_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter local became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter high became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter low became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tw became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tsk has been changed from struct task_struct (1936 bytes) to struct mm_struct (824 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter tsk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter task has been changed from struct task_struct (1936 bytes) to struct mm_struct (824 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 107 | 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 | The pointer level of 2nd parameter inf has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter fs_dir_inode_ops has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Type of 4th parameter fs_dir_inode_ops has been changed from struct inode_operations const* to int (became non-const). | This function may change parameter fs_dir_inode_ops, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ctx became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter kill_dirty of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fileid became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fattr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mnt of type struct vfsmount* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter allow_dups of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter entry has been changed from struct fsnotify_mark_entry (104 bytes) to struct fsnotify_mark (128 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter entry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter entry has been changed from struct fsnotify_mark_entry (104 bytes) to struct fsnotify_mark (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter entry has been changed from struct fsnotify_mark_entry (104 bytes) to struct fsnotify_mark (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter entry has been changed from struct fsnotify_mark_entry (104 bytes) to struct fsnotify_mark (128 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter keycode has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter keycode 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 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. |
| 2 | Parameter old of type struct intel_load_detect_pipe* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Type of return value has been changed from struct drm_crtc* (8 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter crtc became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter type became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter old of type struct intel_load_detect_pipe* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pipe of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter adapter of type struct i2c_adapter* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ddc_bus of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter response has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter enabled became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rtc became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter enabled became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rtc became passed in rdi 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 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 1960 bytes to 2072 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gsi became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cfg became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter arg became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter bdev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter cmd became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter mode became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fieinfo became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter fs_flags became passed on stack instead of rsi 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 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter aprio became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter bprio became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dontfrag of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter ipfragok 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 | Base type of 2nd parameter optp has been changed from struct ip_options (12 bytes) to struct ip_options_rcu (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter optp has been changed from struct ip_options (12 bytes) to struct ip_options_rcu (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 5th parameter opt has been changed from struct ip_options (12 bytes) to struct ip_options_rcu (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl4 of type struct flowi4* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 344 bytes to 360 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 40 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 40 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 144 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 144 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev 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 135 bytes to 133 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uni of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter multi of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter _prealloc of type unsigned long* 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 int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter no_state_check 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 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter led_cdev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter led_cdev became passed on stack instead of rdi 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xfer_mask became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mwdma_mask became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pio_mask became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter udma_mask became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ap became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tf became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tf became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xfer_mode became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mwdma_mask became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pio_mask became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter udma_mask became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter xfer_mask became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xfer_mode became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter link became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter command became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cmd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter cmd has been changed from struct scsi_cmnd (232 bytes) to struct Scsi_Host (1216 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter done has been changed from void(*)(struct scsi_cmnd*) (8 bytes) to struct scsi_cmnd (232 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter done has been removed from the calling stack. | This parameter will be ignored by the function. |
| 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 ap became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from u8 (1 byte) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dir became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter old_dentry became passed in rdi 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 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fl became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter new became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type struct cpumask* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter entry_size has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 4th parameter indexes_count has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter keys has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mddev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter metadata_op of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter task became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter tlbp has been decreased from 2 to 1. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter p became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter step of type enum mpol_rebind_step has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sc of type struct scan_control* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter nr_anon of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter nr_file of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Parameter page_list of type struct list_head* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 5 | 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 device became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter list became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter vendor became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter timestamp of type u64 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sock of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mm became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter npages became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter vm_flags became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter module became passed in rdi 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 40 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 40 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 40 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[255] (1020 bytes) to int[] (8 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1020 bytes to 131072 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 4096 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lock became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sig became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter acc_mode has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dfd became passed in rdi 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 rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter name became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter path became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter ns has been changed from struct ipc_namespace (344 bytes) to struct task_struct (1896 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mnt became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter buffer has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Base type of 3rd parameter dentry has been changed from struct dentry (192 bytes) to char (1 byte). | This parameter may be incorrectly initialized by applications. |
| 3 | Type of 1st parameter base has been changed from char const* to char** (became non-const). | This function may change parameter base, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| 4 | Type of 2nd parameter droot has been changed from struct dentry const* to struct dentry* (became non-const). | This function may change parameter droot, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ns became passed on stack instead of rdi 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 360 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 392 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 48 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 274 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 275 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 276 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 277 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 278 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 279 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 280 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 281 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 282 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 283 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 284 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 285 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 286 | Size of this global data has been changed from 376 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 287 | Size of this global data has been changed from 528 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 288 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 289 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 290 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 291 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 292 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 293 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 294 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 295 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 296 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 297 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 298 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 299 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 300 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 301 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 302 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 303 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 304 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 305 | Size of this global data has been changed from 544 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 306 | Size of this global data has been changed from 200 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 307 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 308 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 309 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 310 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 311 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 312 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 313 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 314 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 315 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 316 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 317 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 318 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 319 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 320 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 321 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 322 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 323 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 324 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 325 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 326 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 327 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 328 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 329 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 330 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 331 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 332 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 333 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 334 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 335 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 336 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 337 | Size of this global data has been changed from 1536 bytes to 1600 bytes. | Applications will obtain a different value and execution may change. |
| 338 | Size of this global data has been changed from 256 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 339 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 340 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 341 | Size of this global data has been changed from 616 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 342 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 343 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 344 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 345 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 346 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 347 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 348 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 349 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 350 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 351 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 352 | Size of this global data has been changed from 128 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 353 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 354 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 355 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 356 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 357 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 358 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 359 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 360 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 361 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 362 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 363 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 364 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 365 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 366 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 367 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 368 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 369 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 370 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 371 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 372 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 373 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 374 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 375 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 376 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 377 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 378 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 379 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 380 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 381 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 382 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 383 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 384 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 385 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 386 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 387 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 388 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 389 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 390 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 391 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 392 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 393 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 394 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 395 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 396 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 397 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 398 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 399 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 400 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 401 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 402 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 403 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 404 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 405 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 406 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 407 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 408 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 409 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 410 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 411 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 412 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 413 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 414 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 415 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 416 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 417 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 418 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 419 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 420 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 421 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 422 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 423 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 424 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 425 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 426 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 427 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 428 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 429 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 430 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 431 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 432 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 433 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 434 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 435 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 436 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 437 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 438 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 439 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 440 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 441 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 442 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 443 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 444 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 445 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 446 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 447 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 448 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 449 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 450 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 451 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 452 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 453 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 454 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 455 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 456 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 457 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 458 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 459 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 460 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 461 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 462 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 463 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 464 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 465 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 466 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 467 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 468 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 469 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 470 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 471 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 472 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 473 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 474 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 475 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 476 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 477 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 478 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 479 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 480 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 481 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 482 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 483 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 484 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 485 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 486 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 487 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 488 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 489 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 490 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 491 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 492 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 493 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 494 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 495 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 496 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 497 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 498 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 499 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 500 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 501 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 502 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 503 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 504 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 505 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 506 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 507 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 508 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 509 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 510 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 511 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 512 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 513 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 514 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 515 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 516 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 517 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 518 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 519 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 520 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 521 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 522 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 523 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 524 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 525 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 526 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 527 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 528 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 529 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 530 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 531 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 532 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 533 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 534 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 535 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 536 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 537 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 538 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 539 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 540 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 541 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 542 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 543 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 544 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 545 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 546 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 547 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 548 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 549 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 550 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 551 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 552 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 553 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 554 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 555 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 556 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 557 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 558 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 559 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 560 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 561 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 562 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 563 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 564 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 565 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 566 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 567 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 568 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 569 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 570 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 571 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 572 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 573 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 574 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 575 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 576 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 577 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 578 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 579 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 580 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 581 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 582 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 583 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 584 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 585 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 586 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 587 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 588 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 589 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 590 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 591 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 592 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 593 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 594 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 595 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 596 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 597 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 598 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 599 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 600 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 601 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 602 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 603 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 604 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 605 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 606 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 607 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 608 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 609 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 610 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 611 | Size of this global data has been changed from 2168 bytes to 2496 bytes. | Applications will obtain a different value and execution may change. |
| 612 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 613 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 614 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 615 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 616 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 617 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 618 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 619 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 620 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 621 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 622 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 623 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 624 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 625 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 626 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 627 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 628 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 629 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 630 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 631 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 632 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 633 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 634 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 635 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 636 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 637 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 638 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 639 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 640 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 641 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 642 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 643 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 644 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 645 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 646 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 647 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 648 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 649 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 650 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 651 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 652 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 653 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 654 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 655 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 656 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 657 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 658 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 659 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 660 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 661 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 662 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 663 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 664 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 665 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 666 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 667 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 668 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 669 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 670 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 671 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 672 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 673 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 674 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 675 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 676 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 677 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 678 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 679 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 680 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 681 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 682 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 683 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 684 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 685 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 686 | Size of this global data has been changed from 592 bytes to 832 bytes. | Applications will obtain a different value and execution may change. |
| 687 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 688 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 689 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 690 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 691 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 48 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 376 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 528 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 544 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 200 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1536 bytes to 1600 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 48 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 152 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter entry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter entry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter np became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter trap became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[37] (296 bytes) to struct nf_conntrack_l3proto*[39] (312 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 296 bytes to 312 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ct became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ctinfo became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter match_len became passed on stack instead of r8 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter match_offset became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter rep_buffer became passed on stack instead of r9 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 6 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ct became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ctinfo became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter match_len became passed on stack instead of r8 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter match_offset became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter rep_buffer became passed on stack instead of r9 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 6 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Base type of 1st parameter p has been changed from unsigned int (4 bytes) to struct xdr_stream (56 bytes). | This parameter may be incorrectly initialized by applications. |
| 3 | Type of return value has been changed from __be32* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter roc of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter res of type struct nfs4_setclientid_res* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl_pid of type pid_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Base type of parameter dst has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clp became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clp became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Base type of 1st parameter p has been changed from unsigned int (4 bytes) to struct xdr_stream (56 bytes). | This parameter may be incorrectly initialized by applications. |
| 3 | Type of return value has been changed from __be32* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Parameter root_device of type char** has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter root_data of type char** has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Type of return value has been changed from void* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter maxlen of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter merge of type struct fsnotify_event*(*)(struct list_head*, struct fsnotify_event*) 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 int (4 bytes) to struct fsnotify_event* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter group became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter child_node became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter parent_node became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter start_pfn has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 2nd parameter last_pfn has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 3rd parameter acpi has been removed from the calling stack. | This parameter will be ignored by the function. |
| 4 | 4th parameter k8 has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dentry has been changed from struct dentry (192 bytes) to struct path (16 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | The parameter buf became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter dentry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter value has been changed from unsigned int (4 bytes) to unsigned long long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter str became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mapping became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter page became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter info of type struct backing_dev_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter order became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter page became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter size became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter vaddr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter kp became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter val became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter state became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter req of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter format became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter format became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter format became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter plugin became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter p_dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter align became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter base became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter low became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter num became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter s became passed on stack instead of r8 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter req has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter req has been changed from struct irq_req_t (16 bytes) to irqreturn_t(*)(int, void*) (8 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter wh has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Base type of 2nd parameter req has been changed from struct win_req_t (24 bytes) to struct resource (56 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter curr has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rctx of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ptep became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter vma became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter mii_data has been changed from struct mii_ioctl_data (8 bytes) to struct ifreq (40 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter phydev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pid became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter task became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pid became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter type became passed on stack instead of rsi 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter num became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of rsi 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 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wowlan of type struct cfg80211_wowlan* 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 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 472 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter state of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from __u32[9] (36 bytes) to __u32[10] (40 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter handle became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter __pc became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nr_hits became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 352 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter disk became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter info became passed on stack instead of rdi 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 40 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 40 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 40 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 40 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter az became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter end became passed on stack instead of r8 register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter nr_range became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter range became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter start became passed on stack instead of rcx 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 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 232 bytes to 264 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of rdi 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 1024 bytes to 1536 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 232 bytes to 264 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of rdi 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 1024 bytes to 1536 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter alpha2 became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter initiator became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter wiphy became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pci_bus became passed in rdi 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 rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter counter became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter val became passed on stack instead of rsi 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter num became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lost_events of type unsigned long* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter iter became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lost_events of type unsigned long* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from struct ring_buffer_iter* (8 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter anon_vma became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flp has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from int (4 bytes) to struct rtable* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dst became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter iph became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter more became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dst became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter net became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from int (4 bytes) to struct rtable* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lock became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter name became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lock became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter detect_deadlock became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter lock became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ops became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter calcit of type rtnl_calcit_func has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter doit became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter dumpit became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter msgtype became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter protocol became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[23] const (92 bytes) to struct nla_policy[30] const (120 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 92 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter calcit of type rtnl_calcit_func has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 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. |
| 2 | The parameter device became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter chan of type struct ieee80211_channel* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sg became passed on stack instead of rdi 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 48 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cputime became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cputime became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ticks of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nice became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter owner has been changed from struct thread_info (104 bytes) to struct task_struct (1896 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter calldata became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ops became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clone_flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clone_flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 24 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 184 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 24 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 184 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 832 bytes to 824 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 184 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 832 bytes to 824 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 72 bytes to 64 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 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 48 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 80 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 24 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 184 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 832 bytes to 824 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 274 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 275 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 276 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 277 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 278 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 279 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 280 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 281 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 282 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 283 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 284 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 285 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 286 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 287 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 288 | Size of this global data has been changed from 56 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 289 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 290 | Size of this global data has been changed from 2176 bytes to 2192 bytes. | Applications will obtain a different value and execution may change. |
| 291 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 292 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 293 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 294 | Size of this global data has been changed from 4 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 295 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 296 | Size of this global data has been changed from 88 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 297 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 298 | Size of this global data has been changed from 360 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 299 | Size of this global data has been changed from 320 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 300 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 301 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 302 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 303 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 304 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 305 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 306 | Size of this global data has been changed from 712 bytes to 744 bytes. | Applications will obtain a different value and execution may change. |
| 307 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 308 | Size of this global data has been changed from 392 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 309 | Size of this global data has been changed from 424 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 310 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 311 | Size of this global data has been changed from 48 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 312 | Size of this global data has been changed from 192 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 313 | Size of this global data has been changed from 64 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 314 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 315 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 316 | Size of this global data has been changed from 376 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| 317 | Size of this global data has been changed from 528 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 318 | Size of this global data has been changed from 240 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 319 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 320 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 321 | Size of this global data has been changed from 544 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 322 | Size of this global data has been changed from 200 bytes to 288 bytes. | Applications will obtain a different value and execution may change. |
| 323 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 324 | Size of this global data has been changed from 1536 bytes to 1600 bytes. | Applications will obtain a different value and execution may change. |
| 325 | Size of this global data has been changed from 256 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 326 | Size of this global data has been changed from 64 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 327 | Size of this global data has been changed from 616 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 328 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 329 | Size of this global data has been changed from 128 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 330 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 331 | Size of this global data has been changed from 256 bytes to 248 bytes. | Applications will obtain a different value and execution may change. |
| 332 | Size of this global data has been changed from 328 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| 333 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 334 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 335 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 336 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 337 | Size of this global data has been changed from 72 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 338 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 339 | Size of this global data has been changed from 504 bytes to 496 bytes. | Applications will obtain a different value and execution may change. |
| 340 | Size of this global data has been changed from 216 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 341 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 342 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 343 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 344 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 345 | Size of this global data has been changed from 16 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 346 | Size of this global data has been changed from 728 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 347 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 348 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 349 | Size of this global data has been changed from 584 bytes to 600 bytes. | Applications will obtain a different value and execution may change. |
| 350 | Size of this global data has been changed from 2168 bytes to 2496 bytes. | Applications will obtain a different value and execution may change. |
| 351 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 352 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 353 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 354 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 355 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 356 | Size of this global data has been changed from 592 bytes to 832 bytes. | Applications will obtain a different value and execution may change. |
| 357 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 358 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 359 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 360 | Size of this global data has been changed from 396 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| 361 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 362 | Size of this global data has been changed from 32 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 363 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 364 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 365 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 366 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 367 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 368 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 369 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 370 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 371 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 372 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 373 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 374 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 375 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 376 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 377 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 378 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 379 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 380 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 381 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 382 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 383 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 384 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 385 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 386 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 387 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 388 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 389 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 390 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 391 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 392 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 393 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 394 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 395 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 396 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 397 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 398 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 399 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 400 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 401 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 402 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 403 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 404 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 405 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 406 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 407 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 408 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 409 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 410 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 411 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 412 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 413 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 414 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 415 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 416 | Size of this global data has been changed from 32 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 417 | Size of this global data has been changed from 104 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 418 | Size of this global data has been changed from 32 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 419 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 420 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 421 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 422 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 423 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 424 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 425 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 426 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 427 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 428 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 429 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 430 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 431 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 432 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 433 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 434 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 435 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 436 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 437 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 438 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 439 | Size of this global data has been changed from 96 bytes to 104 bytes. | Applications will obtain a different value and execution may change. |
| 440 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 441 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 442 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 443 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 444 | Size of this global data has been changed from 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| 445 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 446 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 447 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 448 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 449 | Size of this global data has been changed from 1944 bytes to 1960 bytes. | Applications will obtain a different value and execution may change. |
| 450 | Size of this global data has been changed from 1720 bytes to 1704 bytes. | Applications will obtain a different value and execution may change. |
| 451 | Size of this global data has been changed from 16 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 452 | Size of this global data has been changed from 176 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 453 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 454 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 455 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 456 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 457 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 458 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 459 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 460 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 461 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 462 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 463 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 464 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 465 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 466 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 467 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 468 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 469 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 470 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 471 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 472 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 473 | Size of this global data has been changed from 24 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 474 | Size of this global data has been changed from 184 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 475 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 476 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 477 | Size of this global data has been changed from 224 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 478 | Size of this global data has been changed from 192 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| 479 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 480 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 481 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 482 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 483 | Size of this global data has been changed from 832 bytes to 824 bytes. | Applications will obtain a different value and execution may change. |
| 484 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 485 | Size of this global data has been changed from 32 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 486 | Size of this global data has been changed from 264 bytes to 280 bytes. | Applications will obtain a different value and execution may change. |
| 487 | Size of this global data has been changed from 2416 bytes to 2480 bytes. | Applications will obtain a different value and execution may change. |
| 488 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 489 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 490 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 491 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 492 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 493 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 494 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 495 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 496 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 497 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 498 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 499 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 500 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 501 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 502 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 503 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 504 | Size of this global data has been changed from 376 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 505 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 506 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 507 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 508 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 509 | Size of this global data has been changed from 976 bytes to 1056 bytes. | Applications will obtain a different value and execution may change. |
| 510 | Size of this global data has been changed from 152 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 511 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 512 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 513 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 514 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 515 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 516 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 517 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 518 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 519 | Size of this global data has been changed from 1352 bytes to 1280 bytes. | Applications will obtain a different value and execution may change. |
| 520 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 521 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 522 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 523 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 524 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 525 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 526 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 527 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 528 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 529 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 530 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 531 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 532 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 533 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 534 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 535 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 536 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 537 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 538 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 539 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 540 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 541 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 542 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 543 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 544 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 545 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 546 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 547 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 548 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 549 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 550 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 551 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 552 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 553 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 554 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 555 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 556 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 557 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 558 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 559 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 560 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 561 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 562 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 563 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 564 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 565 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 566 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 567 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 568 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 569 | Size of this global data has been changed from 728 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 570 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 571 | Size of this global data has been changed from 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 572 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 573 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 574 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 575 | Size of this global data has been changed from 1936 bytes to 1896 bytes. | Applications will obtain a different value and execution may change. |
| 576 | Size of this global data has been changed from 184 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 577 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 578 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 579 | Size of this global data has been changed from 104 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 580 | Size of this global data has been changed from 40 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 581 | Size of this global data has been changed from 104 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 582 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 583 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 584 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 585 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 586 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 587 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 588 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 589 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 590 | Size of this global data has been changed from 664 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 591 | Size of this global data has been changed from 192 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bootmem has been removed from the calling stack. | This parameter will be ignored by the function. |
| 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 channel became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter id became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter lun became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter shost became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter lun became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter starget became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter done_q became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter scmd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter scmd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ses became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter channel became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter shost became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter scsilun became passed on stack instead of rdi 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 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter state became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter state became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter starget became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter t became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 296 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cred of type struct cred const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter from_file has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter policy has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 3rd parameter lp has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter other has been changed from struct socket (72 bytes) to struct sock (600 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 1st parameter sock has been changed from struct socket (72 bytes) to struct sock (600 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pwq became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter head became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pos became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter head became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pos became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter head became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pos became passed on stack instead of rsi 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 440 bytes to 472 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter desc became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter req became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inst became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter tmpl became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter 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 mask became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pending became passed on stack instead of rdi 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 40 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 40 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 40 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 40 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter skb became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter st became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter len became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct kmem_cache[28] (19488 bytes) to struct kmem_cache*[14] (112 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 19488 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter zone became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter count has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter count has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter expires became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter timer became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter shtx 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 rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter keycode became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter code became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter autorelease became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter code became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter value became passed on stack instead of rdx 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bytes became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter inode became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpus became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter data became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter fn became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter count became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter cs became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ct became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter str became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cs became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ct became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter option became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter xprt_list has been changed from struct list_head (16 bytes) to struct svc_serv (208 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xprt became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xprt became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter page became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mode became passed on stack instead of rdi 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter entry became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_addr became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter hwdev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter size became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter vaddr became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ecn_ok of type bool* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[300] const (2400 bytes) to sys_call_ptr_t[309] const (2472 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 2400 bytes to 2472 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter key became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter tty has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter data has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 5th parameter resident has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| 3 | Base type of 2nd parameter shared has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| 4 | Base type of 3rd parameter text has been changed from int (4 bytes) to unsigned long (8 bytes). | This parameter may be incorrectly initialized by applications. |
| 5 | Type of return value has been changed from int (4 bytes) to unsigned long (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter instance became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter out_table became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter signature became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter tbl_size became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter sock has been changed from struct socket (72 bytes) to struct sock (600 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sock has been changed from struct socket (72 bytes) to struct sock (600 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Type of return value has been changed from ssize_t (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mss became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pmtu became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nsec became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sec became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ts became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gran became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter boot of type ktime_t* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter timeri became passed on stack instead of rdi 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 40 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 40 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 40 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 40 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 40 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 40 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 40 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 40 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 40 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 40 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 40 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 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 192 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter oops_dump_mode of type enum ftrace_dump_mode 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 144 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 456 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 24 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 136 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 264 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 624 bytes to 648 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 296 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 712 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 176 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 336 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 496 bytes to 504 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 792 bytes to 1144 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 368 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 344 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 48 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 88 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 128 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 2216 bytes to 1696 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 616 bytes to 592 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 8 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 56 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 40 bytes to 32 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 432 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 552 bytes to 560 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 64 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 320 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 624 bytes to 656 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 128 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 104 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 368 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 96 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 712 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 176 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter irq_flags has been changed from unsigned long (8 bytes) to int (4 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 3rd parameter rctxp has been changed from int (4 bytes) to struct pt_regs (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter filter became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter rec became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[10] (80 bytes) to char const*[8] (64 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 80 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter type became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tsk of type struct task_struct* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter error_code of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter trapnr of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter offset became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter page became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter new became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter old became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter port became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter port became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter port became passed on stack instead of rdi 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 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 344 bytes to 360 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 696 bytes to 704 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter urb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 160 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 24 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 24 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 40 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 64 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 48 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 104 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 224 bytes to 232 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 7008 bytes to 7176 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter key became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter m became passed on stack instead of rsi 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 2096 bytes to 1072 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[9] (72 bytes) to char const*[8] (64 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter has_80211_header of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rate_mask of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter channel of type u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter band of type enum ieee80211_band has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter forsdata has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter old_ns has been changed from struct uts_namespace (396 bytes) to struct task_struct (1896 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 396 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter gfp_mask has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter classzone_idx of type enum zone_type has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[29] (232 bytes) to atomic_long_t[32] (256 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 232 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter csw became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter csw became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter deflt became passed on stack instead of rcx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter first became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter last became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter i became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter new became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter work became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter wq became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 24 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | The parameter match became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter target became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter af became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter name became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter revision became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter xdr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nbytes became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter xdr became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter dst_p has been decreased from 2 to 1. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | The parameter dst_p became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter fl became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter flags became passed in r8 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter net became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 6 | The parameter sk became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 7 | Type of return value has been changed from int (4 bytes) to struct dst_entry* (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Field initialized has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 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 thread_id 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 | Type of field thread_id has been changed from struct task_struct* to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field thread_id 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 | Type of field thread_id has been changed from struct task_struct* to u64. | 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 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field handler has been changed from struct acpi_handler_info (24 bytes) to struct acpi_gpe_handler_info (32 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Field extra has been renamed to dispatch. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field method_flags has been renamed to info_flags. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field thread_id 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 | Type of field thread_id has been changed from struct task_struct* to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field extra has been changed from 48 bytes to 56 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field node has been changed from 32 bytes to 40 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 1224 bytes to 1352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 424 bytes to 528 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 352 bytes to 360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 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 864 bytes to 984 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcfc_rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 104 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tlp has been changed from struct header_log_regs to struct aer_header_log_regs. | 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 224 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 | Field stored_addr_hi has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 stored_addr_lo has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 stored_l1 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 stored_l2 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 136 bytes to 1096 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 352 bytes to 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 128 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 104 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap 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 136 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field crbind has been changed from void(*)(struct rpc_task*, struct rpc_cred*, int) to struct rpc_cred*(*)(struct rpc_task*, struct rpc_cred*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field crunwrap_resp has been changed from int(*)(struct rpc_task*, kxdrproc_t, void*, __be32*, void*) to int(*)(struct rpc_task*, kxdrdproc_t, void*, __be32*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field crwrap_req has been changed from int(*)(struct rpc_task*, kxdrproc_t, void*, __be32*, void*) to int(*)(struct rpc_task*, kxdreproc_t, void*, __be32*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 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 24 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 432 bytes to 520 bytes. | The fields or parameters of 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 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 488 bytes to 520 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field filename became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field interp 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 filename 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. |
| 4 | Type of field interp has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field behind_writes_used 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 logattrs has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The member REQ_TYPE_LINUX_BLOCK 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 | Field check_events has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 88 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field set_capacity has been renamed to unlock_native_capacity. | 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 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field discard_zeroes_data has been changed from signed char to unsigned char. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 320 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 2216 bytes to 1696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field queue_lock has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | Field ordered has been renamed to flush_running_idx. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field unplug_fn has been renamed to unprep_rq_fn. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field olpc_ofw_header 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 thread_wait has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 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 112 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 240 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 | Field local_state_change has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field crypto has been changed from 48 bytes to 52 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field control_port_ethertype has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 control_port_no_encrypt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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 local_state_change has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcast_rate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 40 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_antenna has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 get_ringparam has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 mgmt_frame_register has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 sched_scan_start has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 sched_scan_stop has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field set_antenna has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field set_cqm_rssi_config has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field set_ringparam has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Size of this type has been changed from 408 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 10 | Base type of field add_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*, struct key_params*) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*, struct key_params*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 11 | Base type of field add_virtual_intf has been changed from int(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*) to struct net_device*(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 12 | Base type of field del_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 13 | Base type of field get_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*, void*, void(*)(void*, struct key_params*)) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*, void*, void(*)(void*, struct key_params*)). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 14 | Base type of field set_channel has been changed from int(*)(struct wiphy*, struct ieee80211_channel*, enum nl80211_channel_type) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, enum nl80211_channel_type). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 15 | Base type of field set_default_key has been changed from int(*)(struct wiphy*, struct net_device*, u8) to int(*)(struct wiphy*, struct net_device*, u8, bool, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 16 | Base type of field set_tx_power has been changed from int(*)(struct wiphy*, enum tx_power_setting, int) to int(*)(struct wiphy*, enum nl80211_tx_power_setting, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 17 | Base type of field set_wds_peer has been changed from int(*)(struct wiphy*, struct net_device*, u8*) to int(*)(struct wiphy*, struct net_device*, u8 const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 18 | Base type of field suspend has been changed from int(*)(struct wiphy*) to int(*)(struct wiphy*, struct cfg80211_wowlan*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 19 | Field get_mesh_params has been renamed to get_mesh_config. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 20 | Field set_mesh_params has been renamed to update_mesh_config. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field _next_bitmap has been changed from uint32_t* to __le32*. | 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 40 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 16 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 544 bytes to 640 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field available_antennas_rx 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 528 bytes to 560 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mesh_id_len has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field mesh_id_up_len has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field action_registrations has been renamed to mgmt_registrations. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 5 | Field action_registrations_lock has been renamed to mgmt_registrations_lock. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field unregister_event has been changed from int(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*) to void(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*). | 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 224 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*, bool) to void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field can_attach has been changed from int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*, bool) to int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field cancel_attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*, bool) to void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field exit has been changed from void(*)(struct cgroup_subsys*, struct task_struct*) to void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_info has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field info has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 24 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_beyond_eod has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 pp_buf has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 6184 bytes to 26688 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_kref has been renamed to cl_count. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field p_decode has been changed from int(*)(void*, __be32*, void*) to int(*)(void*, struct xdr_stream*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field p_encode has been changed from int(*)(void*, __be32*, void*) to void(*)(void*, struct xdr_stream*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field name has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 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 con_debug_enter has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 con_debug_leave has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 200 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vc_panic_force_write has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 432 bytes to 640 bytes. | The fields or parameters of 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 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 928 bytes to 1088 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 672 bytes to 680 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field suspend has been changed from int(*)(struct cpufreq_policy*, pm_message_t) to int(*)(struct cpufreq_policy*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prepare has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 984 bytes to 992 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field power_specified 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 144 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mem has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 64 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field find_io has been changed from struct resource*(*)(unsigned long, int, unsigned long, struct pcmcia_socket*) to int(*)(struct pcmcia_socket*, unsigned int, unsigned int*, unsigned int, unsigned int, struct resource**). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field event has been renamed to add. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from u_char to unsigned char. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_seq 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 | Type of field d_hash has been changed from struct hlist_node to struct hlist_bl_node. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_automount has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 d_manage has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 56 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Base type of field d_compare has been changed from int(*)(struct dentry*, struct qstr*, struct qstr*) to int(*)(struct dentry const*, struct inode const*, struct dentry const*, struct inode const*, unsigned int, char const*, struct qstr const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field d_delete has been changed from int(*)(struct dentry*) to int(*)(struct dentry const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field d_hash has been changed from int(*)(struct dentry*, struct qstr*) to int(*)(struct dentry const*, struct inode const*, struct qstr*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field discards_supported has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field num_discard_requests 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 flush_request has been renamed to target_request_nr. | 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field p has been changed from struct bus_type_private (248 bytes) to struct subsys_private (400 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field p has been changed from struct class_private (288 bytes) to struct subsys_private (400 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field type 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 type has been changed from struct device_type* to struct device_type 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_failure has been renamed to flush_failure. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field discards_supported has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 target_callbacks has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 288 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field integrity_supported 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 flush_bio has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 576 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 128 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 128 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field null_edid_counter has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 880 bytes to 856 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field fb_helper_private has been removed from this type. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field detect has been changed from enum drm_connector_status(*)(struct drm_connector*) to enum drm_connector_status(*)(struct drm_connector*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field framedur_ns has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 linedur_ns has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 pixeldur_ns has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 328 bytes to 560 bytes. | The fields or parameters of 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 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field gamma_set has been changed from void(*)(struct drm_crtc*, u16*, u16*, u16*, uint32_t) to void(*)(struct drm_crtc*, u16*, u16*, u16*, uint32_t, uint32_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 136 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field color_formats 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 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field dirty has been changed from int(*)(struct drm_framebuffer*, unsigned int, unsigned int, struct drm_clip_rect*, unsigned int) to int(*)(struct drm_framebuffer*, struct drm_file*, unsigned int, unsigned int, struct drm_clip_rect*, 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 432 bytes to 536 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_changed has been renamed to output_poll_changed. | 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 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_scanned_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 scan_alignment has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 scan_check_range has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 scan_end has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 scan_hit_size has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field scan_hit_start has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field scan_size has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field scan_start has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field scanned_blocks has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 10 | Size of this type has been changed from 56 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 11 | Field fl_entry has been renamed to hole_stack. | 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 72 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field private has been removed from this type. | Size of the inclusive type has been changed. |
| 3 | Field allocated has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field scanned_block 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. |
| 5 | Field scanned_next_free has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field scanned_preceeds_hole 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. |
| 7 | Field scanned_prev_free has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field fl_entry has been renamed to node_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 9 | Field free has been renamed to hole_follows. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 10 | Field ml_entry has been renamed to hole_stack. | 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 96 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 1544 bytes to 1512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field pin_count has been renamed to switch_power_state. | 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 856 bytes to 616 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field proc_cleanup has been renamed to dumb_create. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field handlecount has been renamed to handle_count. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_drv has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 176 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 536 bytes to 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 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 80 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 568 bytes to 600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The relative position of private field priv has been changed from 26 to 23. | Size of the inclusive type has been changed. |
| 3 | Type of field open has been changed from u_int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 200 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field id_table 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 id_table has been changed from struct pcmcia_device_id* to struct pcmcia_device_id 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 216 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The relative position of private field __pad2 has been changed from 17 to 16. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcpuc_entries has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 88 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Field fifo_stall_task has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field phy_info_task has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 1736 bytes to 1712 bytes. | The fields or parameters of 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 | Field elevator_bio_merged_fn 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 registered has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 384 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_channels has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field get_dump_data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field get_dump_flag has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 get_rxfh_indir has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 set_channels has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field set_dump has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field set_rxfh_indir has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Size of this type has been changed from 376 bytes to 432 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Field phys_id has been renamed to set_phys_id. | 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 832 bytes to 808 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2264 bytes to 2296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aperture_size has been renamed to apertures. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_debug_enter has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 fb_debug_leave has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 176 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 480 bytes to 488 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 32 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 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 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct net*, struct flowi*, u16, u8, void**, atomic_t**) to struct flow_cache_object*(*)(struct net*, struct flowi const*, u16, u8, struct flow_cache_object*, void*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 176 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field freepage 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 migratepage has been changed from int(*)(struct address_space*, struct page*, struct page*) to int(*)(struct address_space*, struct page*, struct page*, enum migrate_mode). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field bd_write_holder 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 bd_claiming has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field bd_holder_disks 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 fa_rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 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 192 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field f_sb_list_cpu 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 fallocate 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 fsync has been changed from int(*)(struct file*, struct dentry*, int) to int(*)(struct file*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_vfs_rename_key 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 get_sb has been renamed to mount. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 616 bytes to 592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field permission has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, int, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field check_acl has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, 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 64 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 s_uuid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field s_d_op has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 cleancache_poolid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 712 bytes to 728 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field s_xattr became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 6 | Type of field s_xattr has been changed from struct xattr_handler** to struct xattr_handler const**. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field s_anon has been changed from struct hlist_head to struct hlist_bl_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field dirty_inode has been changed from void(*)(struct inode*) to void(*)(struct inode*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field drop_inode has been changed from void(*)(struct inode*) to int(*)(struct inode*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Field delete_inode has been renamed to evict_inode. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(struct kiocb*, loff_t, ssize_t, void*) to void()(struct kiocb*, loff_t, ssize_t, void*, int, bool). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Field tgid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 104 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field file_name has been changed from char to unsigned char. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 bytes to 192 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 freeing_mark has been changed from void(*)(struct fsnotify_mark_entry*, struct fsnotify_group*) to void(*)(struct fsnotify_mark*, struct fsnotify_group*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field handle_event has been changed from int(*)(struct fsnotify_group*, struct fsnotify_event*) to int(*)(struct fsnotify_group*, struct fsnotify_mark*, struct fsnotify_mark*, struct fsnotify_event*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field should_send_event has been changed from bool(*)(struct fsnotify_group*, struct inode*, __u32) to bool(*)(struct fsnotify_group*, struct inode*, struct fsnotify_mark*, struct fsnotify_mark*, __u32, void*, 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 176 bytes to 136 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 event 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 | Field define_fields has been renamed to perf_events. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_depth has been renamed to padding. | 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 72 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field trace has been renamed to funcs. | 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 4744 bytes to 8864 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 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 user_ptr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 48 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal_flags 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 624 bytes to 656 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field async_events 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 456 bytes to 504 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field in_flight has been changed from int[2] to atomic_t[2]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field gm_upcall_enctypes has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 72 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gss_import_sec_context has been changed from int(*)(void const*, size_t, struct gss_ctx*) to int(*)(void const*, size_t, struct gss_ctx*, gfp_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_pending_irqs has been renamed to apic_irq_work_irqs. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_device has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 264 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field pci_suspend has been changed from int(*)(struct usb_hcd*) to int(*)(struct usb_hcd*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field primary_hcd 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 shared_hcd has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field poll_pending has been renamed to msix_enabled. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field poll_rh has been renamed to rh_pollable. | 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 328 bytes to 360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 800 bytes to 848 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field afg_unsol has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field mfg_function_id has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field mfg_unsol 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. |
| 5 | Field slave_dig_outs became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 6 | Type of field slave_dig_outs has been changed from hda_nid_t* to hda_nid_t 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 88 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 264 bytes to 580 bytes. | The fields or parameters of 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 36 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 label 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 dac_nids became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field slave_dig_outs 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 dac_nids has been changed from hda_nid_t* to hda_nid_t const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field slave_dig_outs has been changed from hda_nid_t* to hda_nid_t 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 7104 bytes to 7144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 216 bytes to 256 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field report_fixup has been changed from void(*)(struct hid_device*, __u8*, unsigned int) to __u8*(*)(struct hid_device*, __u8*, 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 552 bytes to 1064 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clockid 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 | Type of field index has been changed from clockid_t 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 192 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 560 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 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 432 bytes to 464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 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 gtt_total has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 mappable_gtt_total has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 object_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field object_memory has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 360 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Field shrink_list has been renamed to gtt_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_mode_set has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_link_train has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 init_clock_gating has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 init_pch_clock_gating has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 queue_flip has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Size of this type has been changed from 56 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Base type of field fbc_enabled has been changed from bool(*)(struct drm_crtc*) to bool(*)(struct drm_device*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field update_wm has been changed from void(*)(struct drm_device*, int, int, int, int) to void(*)(struct drm_device*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ring has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 40 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field cache_level 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 display has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 overlay has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 pinned_bo_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 112 bytes to 336 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field ringbuffer has been changed from struct drm_i915_error_object to struct drm_i915_error_object*. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field setup_seqno has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 376 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cache_level has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field fenced_gpu_access has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Base type of field bit_17 has been changed from long to unsigned long. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Field agp_type has been renamed to pending_fenced_gpu_access. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 6 | Field in_execbuffer has been renamed to num_sg. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 7 | Field pages_refcount has been renamed to pending_gpu_write. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field fence_list has been renamed to mm_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 9 | Field list has been renamed to gtt_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cur_obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Field broadcast_rgb_property has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 fbdev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 force_audio_property has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 forcewake_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. |
| 5 | Field last_gpu_reset has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 4592 bytes to 6432 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Base type of field pwrctx has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 8 | Field backlight_enabled has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field fmax 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. |
| 10 | Field last_acthd_blt 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. |
| 11 | Field last_instdone1 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. |
| 12 | Field no_aux_handshake has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 13 | Field num_pipe 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. |
| 14 | Field panel_t3 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. |
| 15 | Field pch_pf_pos 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. |
| 16 | Field relative_constants_mode has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 17 | Field savePCH_PORT_HOTPLUG 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. |
| 18 | Field edp_support has been renamed to crt_ddc_pin. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 19 | Field user_irq_lock has been renamed to pch_irq_mask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_bsd_ring has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 has_overlay has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 overlay_needs_physical has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 supports_tv has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 3 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Field has_blt_ring 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 lid_state has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field vbt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 40 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ddc_pin has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 i2c_pin has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 i2c_speed has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 4 bytes to 7 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The member WLAN_BACK_TIMER 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 | Field dtim_bc_mc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 312 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field work has been renamed to mtx. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ave_beacon_signal has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field count_beacon_signal has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field last_beacon_signal has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 576 bytes to 584 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field broken_ap has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field last_cqm_event_signal 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. |
| 7 | Field nullfunc_failed 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 fif_probe_req has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 hw_offchan_tx_cookie has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 hw_roc_channel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field hw_roc_channel_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field hw_roc_cookie has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field hw_roc_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. |
| 7 | Field hw_roc_done has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field hw_roc_duration has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field hw_roc_for_tx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 10 | Field hw_roc_skb has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 11 | Field hw_roc_skb_for_status has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 12 | Field hw_roc_start has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 13 | Field napi has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 14 | Field napi_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. |
| 15 | Field probe_req_reg has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 16 | Field wiphy_ciphers_allocated has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 17 | Size of this type has been changed from 3776 bytes to 5824 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 18 | Field wowlan 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. |
| 19 | Base type of field wep_rx_tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 20 | Base type of field wep_tx_tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 21 | The pointer level of field mc_list has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1592 bytes to 1752 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field control_port_no_encrypt has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field control_port_protocol has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field old_idle 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 offchan_tx 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 576 bytes to 584 bytes. | The fields or parameters of 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 416 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 addr_list has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr_lst has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 if_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 176 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 | Field icmpv6msgdev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 icmpv6dev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 56 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 48 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 168 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field next has been renamed to unnamed0. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been renamed to next_rcu. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field icsk_user_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 1096 bytes to 1136 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 queue_xmit has been changed from int(*)(struct sk_buff*, int) to int(*)(struct sk_buff*, struct flowi*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field send_check has been changed from void(*)(struct sock*, int, struct sk_buff*) to void(*)(struct sock*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Field remember_stamp has been renamed to get_peer. | 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 160 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 744 bytes to 776 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field nodefrag has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field __tw_common has been changed from 72 bytes to 80 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 392 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 72 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 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 | Base type of field read has been changed from long(*)(struct snd_info_entry*, void*, struct file*, char*, unsigned long, unsigned long) to ssize_t(*)(struct snd_info_entry*, void*, struct file*, char*, size_t, loff_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field write has been changed from long(*)(struct snd_info_entry*, void*, struct file*, char const*, unsigned long, unsigned long) to ssize_t(*)(struct snd_info_entry*, void*, struct file*, char const*, size_t, loff_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field llseek has been changed from long long(*)(struct snd_info_entry*, void*, struct file*, long long, int) to loff_t(*)(struct snd_info_entry*, void*, struct file*, loff_t, 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 2488 bytes to 1024 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field slot has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Base type of field getkeycode has been changed from int(*)(struct input_dev*, unsigned int, unsigned int*) to int(*)(struct input_dev*, struct input_keymap_entry*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field setkeycode has been changed from int(*)(struct input_dev*, unsigned int, unsigned int) to int(*)(struct input_dev*, struct input_keymap_entry const*, unsigned int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field iommu_superpage 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 i2c_speed 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 rsvd 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 old_fb_obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Base type of field pending_flip_obj has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field enable_stall_check 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 1240 bytes to 1480 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field cursor_bo has been changed from struct drm_gem_object (136 bytes) to struct drm_i915_gem_object (376 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field cursor_visible 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 1008 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flip_tail has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 128 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 map has been changed from int(*)(struct iommu_domain*, unsigned long, phys_addr_t, size_t, int) to int(*)(struct iommu_domain*, unsigned long, phys_addr_t, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field unmap has been changed from void(*)(struct iommu_domain*, unsigned long, size_t) to int(*)(struct iommu_domain*, unsigned long, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field destructor 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 | Base type of field opt has been changed from struct ip_options (12 bytes) to struct ip_options_rcu (32 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Field shtx has been renamed to tx_flags. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 320 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 | Base type has been changed from struct rt6_info*(*)(struct net*, struct fib6_table*, struct flowi*, int) to struct rt6_info*(*)(struct net*, struct fib6_table*, struct flowi6*, int). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 136 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field fib_scope 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 nh_saddr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field nh_saddr_genid has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field tb_data has been changed from unsigned char[] to unsigned long[]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 344 bytes to 360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 360 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mroute_sk has been renamed to mrt. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rxorigdstaddr 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 rxpmtu has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 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 160 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 392 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field irq_pm_shutdown has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 irq_print_chip has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 irq_resume has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 irq_suspend has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 144 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Field ack has been renamed to irq_ack. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field bus_lock has been renamed to irq_bus_sync_unlock. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 9 | Field bus_sync_unlock has been renamed to irq_cpu_online. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 10 | Field disable has been renamed to irq_disable. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 11 | Field enable has been renamed to irq_enable. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 12 | Field end has been renamed to irq_set_affinity. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 13 | Field eoi has been renamed to irq_eoi. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 14 | Field mask has been renamed to irq_mask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 15 | Field mask_ack has been renamed to irq_mask_ack. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 16 | Field retrigger has been renamed to irq_set_type. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 17 | Field set_affinity has been renamed to irq_retrigger. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 18 | Field set_type has been renamed to irq_set_wake. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 19 | Field set_wake has been renamed to irq_bus_lock. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 20 | Field shutdown has been renamed to irq_shutdown. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 21 | Field startup has been renamed to irq_startup. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 22 | Field typename has been renamed to irq_cpu_offline. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 23 | Field unmask has been renamed to irq_unmask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field affinity has been renamed to threads_oneshot. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | The member T_RUNDOWN 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 | Field b_cow_tid has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The member DIE_NMIWATCHDOG has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 2 | The member DIE_NMI_IPI 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 120 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 320 bytes to 328 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 440 bytes to 424 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reject_error has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcudata 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 field ccmp has been changed from 320 bytes to 328 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Base type of field cleanup has been changed from void(*)(char**, char**) to void(*)(struct subprocess_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field child_ns_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 24 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 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 1192 bytes to 1592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 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 2752 bytes to 3960 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field lpm_policy 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 11264 bytes to 12672 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sff_drain_fifo 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 sff_set_devctl has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Base type of field sff_irq_on has been changed from u8(*)(struct ata_port*) to void(*)(struct ata_port*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Field enable_pm has been renamed to set_lpm. | 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 224 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 496 bytes to 504 bytes. | The fields or parameters of 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 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field inode has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field path has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field fs has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 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 32 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 arp_addr_cnt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 arp_addr_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field arp_filter_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. |
| 4 | Field channel_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field cqm_rssi_hyst has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field cqm_rssi_thold has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field qos has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Size of this type has been changed from 40 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Field ibss_joined 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. |
| 10 | Field idle 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 max_rx_aggregation_subframes has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 96 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field max_tx_aggregation_subframes 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 alg has been renamed to cipher. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cancel_remain_on_channel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field channel_switch has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field get_antenna has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 get_ringparam has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 napi_poll has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field offchannel_tx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field offchannel_tx_cancel_wait has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field remain_on_channel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field set_antenna has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 10 | Field set_bitrate_mask has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 11 | Field set_ringparam has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 12 | Field tx_frames_pending has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 13 | Size of this type has been changed from 240 bytes to 392 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 14 | Base type of field ampdu_action has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_ampdu_mlme_action, struct ieee80211_sta*, u16, u16*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_ampdu_mlme_action, struct ieee80211_sta*, u16, u16*, u8). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 15 | Base type of field hw_scan has been changed from int(*)(struct ieee80211_hw*, struct cfg80211_scan_request*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct cfg80211_scan_request*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 16 | Base type of field prepare_multicast has been changed from u64(*)(struct ieee80211_hw*, int, struct dev_addr_list*) to u64(*)(struct ieee80211_hw*, struct netdev_hw_addr_list*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 17 | Base type of field tx has been changed from int(*)(struct ieee80211_hw*, struct sk_buff*) to void(*)(struct ieee80211_hw*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_flags 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 ap has been renamed to bss. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_max_entries has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field c_indexes_hash has been renamed to c_index_hash. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_index has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 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 88 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field sync_super has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 952 bytes to 1008 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field barrier has been renamed to flush_bio. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 5 | Field barrier_work has been renamed to flush_work. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field make_request has been changed from int(*)(struct request_queue*, struct bio*) to int(*)(mddev_t*, struct bio*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field shrink has been changed from int(*)(int, gfp_t) to int(*)(struct shrinker*, struct shrink_control*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 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 832 bytes to 824 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field oom_disable_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. |
| 3 | Field cpu_vm_mask has been renamed to cpu_vm_mask_var. | 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 184 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ia32_compat 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 96 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field classzone_idx has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 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 80 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field trace_events has been changed from struct ftrace_event_call* to struct ftrace_event_call**. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field get has been renamed to ops. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field mnt_fsnotify_mask has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 4096 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 owner has been changed from struct thread_info (104 bytes) to struct task_struct (1896 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 504 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field hash has been changed from __u32(*)(void const*, struct net_device const*) to __u32(*)(void const*, struct net_device const*, __u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Field hash_buckets has been renamed to nht. | 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 240 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 72 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field fasync_list has been renamed to wq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ipvs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 2168 bytes to 2496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field group has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 phydev has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1536 bytes to 1600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | The relative position of private field priv_flags has been changed from 22 to 20. | Size of the inclusive type has been changed. |
| 5 | Field gso_max_segs has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field num_tc 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. |
| 7 | Field real_num_rx_queues 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. |
| 8 | Type of field dn_ptr has been changed from void* to struct dn_dev*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field ip6_ptr has been changed from void* to struct inet6_dev*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field ip_ptr has been changed from void* to struct in_device*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_add_slave has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field ndo_del_slave has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field ndo_fix_features has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ndo_get_vf_port has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field ndo_rx_flow_steer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field ndo_set_features has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field ndo_set_vf_port has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field ndo_setup_tc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Size of this type has been changed from 200 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 128 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field dropped has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field input_queue_head has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field received_rps 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. |
| 5 | Field time_squeeze 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 route has been changed from int(*)(struct dst_entry**, struct flowi*) to int(*)(struct net*, struct dst_entry**, struct flowi*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field min_dump_alloc has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field netpoll has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 192 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 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 32 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 search_restart has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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 | The member NF_CT_EXT_ECACHE has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 2 | The member NF_CT_EXT_ZONE 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 | Base type of field unique_tuple has been changed from bool(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*) to void(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 336 bytes to 344 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 ls_owner has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 368 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1048 bytes to 1040 bytes. | The fields or parameters of 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 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_layouts has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 712 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field cl_exchange_flags has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field cl_cb_ident 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. |
| 5 | Field cl_call_sync has been renamed to cl_session. | 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 792 bytes to 1144 bytes. | The fields or parameters of 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 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field wb_list 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 | Field pg_lseg has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 pg_test has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 72 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field pg_moreio 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. |
| 5 | Base type of field pg_doio has been changed from int(*)(struct inode*, struct list_head*, unsigned int, size_t, int) to int(*)(struct nfs_pageio_descriptor*). | 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 92080 bytes to 92088 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field server has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 56 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 184 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 296 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 688 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Field secinfo has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 open_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 | Field init_client has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 296 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field lookup has been changed from int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct rpc_clnt*, struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, struct iattr*, int, struct nameidata*) to int(*)(struct inode*, struct dentry*, struct iattr*, int, struct nfs_open_context*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field decode_dirent has been changed from __be32*(*)(__be32*, struct nfs_entry*, int) to int(*)(struct xdr_stream*, struct nfs_entry*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field readdir has been changed from int(*)(struct dentry*, struct rpc_cred*, u64, struct page*, unsigned int, int) to int(*)(struct dentry*, struct rpc_cred*, u64, struct page**, unsigned int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 736 bytes to 768 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 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 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 | Value of member NL80211_IFTYPE_MAX has been changed from 7 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 8 has been changed from __NL80211_IFTYPE_AFTER_LAST to NL80211_IFTYPE_P2P_CLIENT. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field param 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 param has been changed from struct kernel_param* to struct kernel_param 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 616 bytes to 648 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ats has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field unnamed0 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 1504 bytes to 2136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 232 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 | Base type has been changed from int(*)(struct pci_dev*, bool, unsigned int, bool) to int(*)(struct pci_dev*, bool, unsigned int, u32). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 400 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 168 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 888 bytes to 896 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 400 bytes to 424 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field access has been changed from int to snd_pcm_access_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field format has been changed from int to snd_pcm_format_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field extra_alloc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 extra_config has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 extra_reg has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 40 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 104 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field state has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 664 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field id_header_size has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field read_size has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Type of field pending has been changed from struct perf_pending_entry to struct irq_work. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field pmu has been changed from struct pmu const* to struct pmu*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_data has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field precise_ip has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field sample_id_all 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 nr_cgroups has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 184 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field data has been renamed to buffer. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field head has been renamed to wakeup. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field offset has been renamed to size. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cancel_txn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field commit_txn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field start_txn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 48 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field start has been changed from int(*)(struct perf_event*) to void(*)(struct perf_event*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field stop has been changed from void(*)(struct perf_event*) to void(*)(struct perf_event*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Field disable has been renamed to dev. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field unthrottle has been renamed to pmu_cpu_context. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 96 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 40 bytes to 64 bytes. | Size of the inclusive type has been changed. |
| 3 | Size of field unnamed1 has been changed from 104 bytes to 96 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 752 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 | Size of this type has been changed from 664 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 216 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 728 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 408 bytes to 448 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 bytes to 160 bytes. | The fields or parameters of 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 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prio_list 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 node_list 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 lock has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field wakeup has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 64 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field is_prepared 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. |
| 5 | Field is_suspended 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 512 bytes to 544 bytes. | The fields or parameters of 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 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 608 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 | Size of this type has been changed from 168 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 472 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 440 bytes to 472 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 sym_val_to_name has been decreased from 2 to 1. | 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 sym_val_to_name has been changed from char**[8] to struct flex_array*[8]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field type_val_to_struct has been renamed to type_val_to_struct_array. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field tclass has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alarmtimer has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field rcu 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 40 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 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 23 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field charging_blink_full_solid_trig has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 charging_blink_full_solid_trig_name has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 184 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2440 bytes to 1936 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 bytes to 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 2168 bytes to 1664 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 192 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field xstate has been renamed to has_fpu. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field stat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 32 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 88 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 quota_off has been changed from int(*)(struct super_block*, int, int) to int(*)(struct super_block*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field set_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct if_dqblk*) to int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field get_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct if_dqblk*) to int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field quota_on has been changed from int(*)(struct super_block*, int, int, char*, int) to int(*)(struct super_block*, int, int, struct path*). | 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 552 bytes to 560 bytes. | The fields or parameters of 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 264 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field preemptable has been renamed to preemptible. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field blkd_tasks 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 exp_tasks has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field gp_tasks has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field node_kthread_status 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. |
| 5 | Field node_kthread_task 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 gp_max has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 gp_start has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 jiffies_stall has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 name has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Size of this type has been changed from 1024 bytes to 1536 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Base type of field rda has been changed from struct rcu_data* (8 bytes) to struct rcu_data (264 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 7 | Field boost 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. |
| 8 | The pointer level of field rda has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field processed 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 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 136 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 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 fi has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 328 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field rt_peer_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. |
| 4 | Field rt_key_tos has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aie_timer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 irqwork has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 pie_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. |
| 4 | Field pie_timer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 timerqueue has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field uie_rtctimer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Size of this type has been changed from 624 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 48 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 | Type of field count has been changed from rwsem_count_t to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field busylock has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 rcu_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 192 bytes to 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field 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 | Size of this type has been changed from 48 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_contribution has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 load_last has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 load_stamp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 load_period has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field load_unacc_exec_time has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 176 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Field rq_weight has been renamed to load_avg. | 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 1944 bytes to 1960 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 2416 bytes to 2480 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field skip_clock_update 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 1720 bytes to 1704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 264 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 184 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field enqueue_task has been changed from void(*)(struct rq*, struct task_struct*, int, bool) to void(*)(struct rq*, struct task_struct*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field prio_changed has been changed from void(*)(struct rq*, struct task_struct*, int, int) to void(*)(struct rq*, struct task_struct*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field select_task_rq has been changed from int(*)(struct rq*, struct task_struct*, int, int) to int(*)(struct task_struct*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field switched_from has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field switched_to has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field task_waking has been changed from void(*)(struct rq*, struct task_struct*) to void(*)(struct task_struct*). | 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 264 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field level has been changed from enum sched_domain_level 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 376 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field group_weight has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field cpu_power has been renamed to ref. | 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred_guard_mutex has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field oom_score_adj has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 oom_score_adj_min has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 976 bytes to 1056 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field count has been renamed to sigcnt. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ptrace_bp_refcnt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1936 bytes to 1896 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field perf_event_ctxp has been changed from struct perf_event_context (184 bytes) to struct perf_event_context* (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 4 | Field pref_node_fork 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. |
| 5 | Field sched_contributes_to_load has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_read_capacity_16 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field no_read_disc_info has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 1096 bytes to 1192 bytes. | The fields or parameters of 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 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 496 bytes to 528 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sg_prot_tablesize has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1152 bytes to 1216 bytes. | The fields or parameters of 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 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field queuecommand has been changed from int(*)(struct scsi_cmnd*, void(*)(struct scsi_cmnd*)) to int(*)(struct Scsi_Host*, struct scsi_cmnd*). | 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 1400 bytes to 1320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field capable has been changed from int(*)(struct task_struct*, struct cred const*, int, int) to int(*)(struct task_struct*, struct cred const*, struct user_namespace*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field inode_init_security has been changed from int(*)(struct inode*, struct inode*, char**, void**, size_t*) to int(*)(struct inode*, struct inode*, struct qstr const*, char**, void**, size_t*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field inode_permission has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, int, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field settime has been changed from int(*)(struct timespec*, struct timezone*) to int(*)(struct timespec const*, struct timezone const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field syslog has been changed from int(*)(int, bool) to int(*)(int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field task_setrlimit has been changed from int(*)(unsigned int, struct rlimit*) to int(*)(struct task_struct*, unsigned int, struct rlimit*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field task_setscheduler has been changed from int(*)(struct task_struct*, int, struct sched_param*) to int(*)(struct task_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field unix_stream_connect has been changed from int(*)(struct socket*, struct socket*, struct sock*) to int(*)(struct sock*, struct sock*, struct sock*). | 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 120 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field set_ldisc has been changed from void(*)(struct uart_port*) to void(*)(struct uart_port*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_wake has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 216 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 576 bytes to 632 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field driver has been changed from 104 bytes to 112 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field description became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Field id_table became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Type of field description 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. |
| 5 | Type of field id_table has been changed from struct serio_device_id* to struct serio_device_id 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 24 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ooo_okay 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 _skb_dst has been renamed to _skb_refdst. | 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 696 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field func has been changed from void(*)(void*) to smp_call_func_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field syncp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 256 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field mibs has been changed from unsigned long[31] to u64[31]. | 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 616 bytes to 648 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 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 344 bytes to 360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field no_autobind 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 584 bytes to 600 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field sk_classid has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field sk_sleep has been renamed to sk_wq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_dontcopy_end has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 72 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_portaddr_node has been renamed to skc_nulls_node. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field skc_bind_node has been renamed to skc_node. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 176 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field get_event_changed has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field ignore_get_event has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field tur_mismatch 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. |
| 5 | Field previous_state has been renamed to media_present. | 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 944 bytes to 976 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field resource_setup_done has been changed from 1 bit to 1 byte. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Field pcmcia_pfc 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 312 bytes to 480 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 728 bytes to 992 bytes. | The fields or parameters of 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 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field stop_initiator has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 tx_stop has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 112 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field buf_size has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 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 f_flags 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 f_flags 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 f_flags 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 f_flags 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 6768 bytes to 6784 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field xpt_users has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 xpt_bc_xprt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 xpt_net has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 624 bytes to 648 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 xpo_create has been changed from struct svc_xprt*(*)(struct svc_serv*, struct sockaddr*, int, int) to struct svc_xprt*(*)(struct svc_serv*, struct net*, struct sockaddr*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 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 40 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 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 24 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 64 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field write has been changed from ssize_t(*)(struct kobject*, struct bin_attribute*, char*, loff_t, size_t) to ssize_t(*)(struct file*, struct kobject*, struct bin_attribute*, char*, loff_t, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field read has been changed from ssize_t(*)(struct kobject*, struct bin_attribute*, char*, loff_t, size_t) to ssize_t(*)(struct file*, struct kobject*, struct bin_attribute*, char*, loff_t, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field mmap has been changed from int(*)(struct kobject*, struct bin_attribute*, struct vm_area_struct*) to int(*)(struct file*, struct kobject*, struct bin_attribute*, struct vm_area_struct*). | 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 72 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field handler has been changed from void(*)(int, struct tty_struct*) to void(*)(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 1584 bytes to 1624 bytes. | The fields or parameters of 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 456 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Type of field ops has been changed from struct thermal_cooling_device_ops* to struct thermal_cooling_device_ops 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 648 bytes to 680 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Type of field ops has been changed from struct thermal_zone_device_ops* to struct thermal_zone_device_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field index has been renamed to clockid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle_lastupdate has been renamed to iowait_sleeptime. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field twsk_getpeer has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 40 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field batch_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 4072 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field fast_mode has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field a_preds has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | The pointer level of field preds has been decreased from 2 to 1. | 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 | Type of field preds has been changed from struct filter_pred** to struct filter_pred*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ref_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 enabled has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field flag_changed has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 use_max_tr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 144 bytes to 160 bytes. | The fields or parameters of 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 40 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 funcs has been decreased from 2 to 1. | 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 funcs has been changed from void** to struct tracepoint_func*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field state has been renamed to key. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field tracepoint 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 tracepoint has been changed from struct tracepoint* to struct tracepoint*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 224 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 128 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 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 1352 bytes to 1280 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 compat_ioctl has been changed from long(*)(struct tty_struct*, struct file*, unsigned int, unsigned long) to long(*)(struct tty_struct*, unsigned int, unsigned long). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field ioctl has been changed from int(*)(struct tty_struct*, struct file*, unsigned int, unsigned long) to int(*)(struct tty_struct*, unsigned int, unsigned long). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field tiocmget has been changed from int(*)(struct tty_struct*, struct file*) to int(*)(struct tty_struct*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field tiocmset has been changed from int(*)(struct tty_struct*, struct file*, unsigned int, unsigned int) to int(*)(struct tty_struct*, unsigned int, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field dcd_change has been changed from void(*)(struct tty_struct*, unsigned int, struct timespec*) to void(*)(struct tty_struct*, unsigned int, struct pps_event_time*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field counter has been changed from long volatile to long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field counter has been changed from int volatile to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sg has been changed from struct usb_sg_request (104 bytes) to struct scatterlist (32 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Field num_mapped_sgs has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field stream_id has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 504 bytes to 560 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field uses_pio_for_control 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 1200 bytes to 1208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ioctl has been renamed to unlocked_ioctl. | 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 72 bytes to 64 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 ss_ep_comp has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 464 bytes to 496 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 104 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2096 bytes to 1072 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 396 bytes to 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 384 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 | Type of field phys_addr has been changed from unsigned long to phys_addr_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 152 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 cpu_wq 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 | Field freezeable has been renamed to work_color. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field rt has been renamed to flush_color. | 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 80 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 208 bytes to 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wallclock_init has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field i8042_detect has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 128 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field checkentry has been changed from bool(*)(struct xt_mtchk_param const*) to int(*)(struct xt_mtchk_param const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field match has been changed from bool(*)(struct sk_buff const*, struct xt_match_param const*) to bool(*)(struct sk_buff const*, struct xt_action_param*). | 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 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field stacksize 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 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field checkentry has been changed from bool(*)(struct xt_tgchk_param const*) to int(*)(struct xt_tgchk_param const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field target has been changed from unsigned int(*)(struct sk_buff*, struct xt_target_param const*) to unsigned int(*)(struct sk_buff*, struct xt_action_param const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field prefix 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 prefix has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field page_ptr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field scratch has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 32 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 592 bytes to 832 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field migrate has been changed from int(*)(struct xfrm_selector*, u8, u8, struct xfrm_migrate*, int, struct xfrm_kmaddress*) to int(*)(struct xfrm_selector const*, u8, u8, struct xfrm_migrate const*, int, struct xfrm_kmaddress const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field notify has been changed from int(*)(struct xfrm_state*, struct km_event*) to int(*)(struct xfrm_state*, struct km_event const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field notify_policy has been changed from int(*)(struct xfrm_policy*, int, struct km_event*) to int(*)(struct xfrm_policy*, int, struct km_event const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 728 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 | Field blackhole_route 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 dst_lookup has been changed from struct dst_entry*(*)(struct net*, int, xfrm_address_t*, xfrm_address_t*) to struct dst_entry*(*)(struct net*, int, xfrm_address_t const*, xfrm_address_t const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field fill_dst has been changed from int(*)(struct xfrm_dst*, struct net_device*, struct flowi*) to int(*)(struct xfrm_dst*, struct net_device*, struct flowi const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field get_tos has been changed from int(*)(struct flowi*) to int(*)(struct flowi const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 712 bytes to 744 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2176 bytes to 2192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field init_tempsel has been changed from void(*)(struct xfrm_state*, struct flowi*, struct xfrm_tmpl*, xfrm_address_t*, xfrm_address_t*) to void(*)(struct xfrm_selector*, struct flowi const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field reject has been changed from int(*)(struct xfrm_state*, struct sk_buff*, struct flowi*) to int(*)(struct xfrm_state*, struct sk_buff*, struct flowi const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_cred has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 336 bytes to 360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field xprt_net 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 kref has been renamed to count. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Type of this global data has been changed from struct acpi_internal_rsdt to struct acpi_table_list. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter payload has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to struct rpc_cred* (8 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 | Base type of 2nd parameter decode has been changed from int(*)(void*, __be32*, void*) to int(*)(void*, struct xdr_stream*, void*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter encode has been changed from int(*)(void*, __be32*, void*) to void(*)(void*, struct xdr_stream*, void*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | 6th parameter in_avd has been renamed to avd. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter minsec has been renamed to maxsec. | Renaming of a parameter 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 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 ts has been changed from struct timespec* to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter tz has been changed from struct timezone* to struct timezone const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter envp has been renamed to __envp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter filename 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 5th parameter data has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter dev_name has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter dir_name has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 4 | Type of 3rd parameter type 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 2nd parameter filename 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 filename 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 filename has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter filename 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 2nd parameter filename 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 filename 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 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 2nd parameter new_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 3rd parameter pnpid has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter buffer has been renamed to buf. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter root has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | 7th parameter error_fn has been renamed to error. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct net_device_stats to struct rtnl_link_stats64. | Replacement of return base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 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 features has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter name has been renamed to features. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 1st parameter features has been changed from unsigned long to struct net_device*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from void* to unsigned char*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nr_to_scan has been renamed to shrink. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter gfp_mask has been renamed to sc. | Renaming of a parameter 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char* to char const*. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter warn has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter reserve has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter id has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fb has been renamed to fb_helper. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter kref has been renamed to obj. | 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 | 1st parameter node has been renamed to hole_node. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter node has been renamed to hole_node. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cur has been renamed to node. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter interlaced has been renamed to lace. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from struct drm_display_mode* to struct drm_display_mode const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter mode has been changed from struct drm_display_mode* to struct drm_display_mode const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter mode has been changed from struct drm_display_mode* to struct drm_display_mode const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been renamed to m. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter handle_errors has been renamed to nbcfg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 3rd parameter handle_errors has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct err_regs*) to void(*)(int, struct mce*, u32). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct err_regs*) to void(*)(int, struct mce*, u32). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter address has been changed from u32(*)(void*) to u32(*)(acpi_handle, u32, void*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter address has been changed from u32(*)(void*) to u32(*)(acpi_handle, u32, void*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter argv has been changed from char** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter envp has been renamed to __envp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter argv has been changed from char** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 4 | Type of 3rd parameter envp has been changed from char** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 5 | Type of 1st parameter filename has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter thread_id has been changed from struct task_struct* to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter src has been renamed to skb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter dst has been renamed to src. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter tos has been renamed to dst. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | 4th parameter oif has been renamed to tos. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 5 | 5th parameter dev has been renamed to oif. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 6 | 6th parameter spec_dst has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 7 | 7th parameter itag has been renamed to spec_dst. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 8 | 8th parameter mark has been renamed to itag. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 9 | Type of 7th parameter itag has been changed from u32* to __be32*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter tmpl has been changed from struct fib_rules_ops* to struct fib_rules_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter attr has been changed from struct attribute* to struct attribute const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter key has been changed from struct flowi* to struct flowi const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from void* to struct flow_cache_object*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Base type of 5th parameter file_name has been changed from char to unsigned char. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to enum ftrace_dump_mode. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter knew has been changed from struct snd_kcontrol_new* to struct snd_kcontrol_new const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter slaves has been changed from char const** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter models has been changed from char const** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter models has been changed from char const** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter ignore_nids has been changed from hda_nid_t* to hda_nid_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ops has been changed from struct platform_hibernation_ops* to struct platform_hibernation_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to hdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to hdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter acctflag has been renamed to vm_flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to nr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter client has been changed from struct i2c_client* to struct i2c_client const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter boxes has been renamed to box. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to ring. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter flush_domains has been renamed to request. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | Type of return value has been changed from uint32_t to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter obj has been renamed to gem_obj. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fl has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter clp has been renamed to server. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter clp has been renamed to server. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ipfragok has been renamed to fl_unused. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tsk has been renamed to mm. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter task has been renamed to mm. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter inf has been renamed to mode. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter fs_dir_inode_ops has been renamed to isvfat. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 5th parameter isvfat has been renamed to setup. | 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 | 2nd parameter iblock_s has been renamed to iblock. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 2nd parameter free_mark has been changed from void(*)(struct fsnotify_mark_entry*) to void(*)(struct fsnotify_mark*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to fsn_mark. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv 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 bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter bus_irq has been renamed to gsi. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter bus_irq has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq_want has been renamed to from. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter gsi has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gsi has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter phys_addr has been changed from unsigned long to phys_addr_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter daddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter saddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter daddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter saddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fl has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ipfragok has been renamed to fl. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from long(*)(long) to long(*)(int). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter alg has been renamed to cipher. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter alg has been changed from enum ieee80211_key_alg to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cmd has been renamed to shost. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter done has been renamed to cmd. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter src has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter src has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpumask has been renamed to mask. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter keys has been renamed to key. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter thread has been renamed to threadp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter thread has been changed from mdk_thread_t* to mdk_thread_t**. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tlbp has been renamed to tlb. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter tlbp has been changed from struct mmu_gather** to struct mmu_gather*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter no_context has been renamed to unused. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter no_context has been renamed to unused. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter mode has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ns has been renamed to tsk. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter base has been renamed to p. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter droot has been renamed to dentry. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter dentry has been renamed to buffer. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | 4th parameter buffer has been renamed to buflen. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 5 | 5th parameter buflen has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 6 | Type of 1st parameter base has been changed from char const* to char**. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 7 | Type of 4th parameter buffer has been changed from char* to ssize_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 8 | Type of 2nd parameter droot has been changed from struct dentry const* to struct dentry*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter module has been renamed to ops. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ssec has been renamed to sksec. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ssec has been renamed to sksec. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter stat has been renamed to status. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter stat has been changed from int to enum nfs_stat. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to xdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nfs4_stateid to union nfs4_stateid. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to xdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to int. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter head has been changed from struct nlattr* to struct nlattr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter head has been changed from struct nlattr* to struct nlattr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter head has been changed from struct nlattr* to struct nlattr 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. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 5th parameter name has been changed from char to unsigned char. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dentry has been renamed to path. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter doio has been changed from int(*)(struct inode*, struct list_head*, unsigned int, size_t, int) to int(*)(struct nfs_pageio_descriptor*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kparam has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter kp has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter params has been changed from struct kernel_param* to struct kernel_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter change_bridge has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter state has been changed from int to snd_pcm_state_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter format has been changed from int to snd_pcm_format_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter format has been changed from int to snd_pcm_format_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter format has been changed from int to snd_pcm_format_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from int to snd_pcm_format_t. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter conf_check has been changed from int(*)(struct pcmcia_device*, cistpl_cftable_entry_t*, cistpl_cftable_entry_t*, unsigned int, void*) to int(*)(struct pcmcia_device*, void*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wh has been renamed to res. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter req has been renamed to offset. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter wh has been changed from window_handle_t to struct resource*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wh has been renamed to res. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter wh has been changed from window_handle_t to struct resource*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been renamed to handler. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been renamed to res. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter wh has been renamed to speed. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dyn_size has been changed from ssize_t to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to task. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_t[9] to struct jump_label_key[9]. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mii_data has been renamed to ifr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter res has been changed from struct resource* to struct resource const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter argv has been changed from char** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter envp has been changed from char** to char const*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | 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 | Type of 3rd parameter addr has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter data has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter data has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from long to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | 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. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter sk has been changed from struct sock* to struct sock const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter iph has been changed from struct iphdr* to struct iphdr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter gwaddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter addr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter daddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter saddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter dest has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter saddr has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter src has been changed from struct in6_addr* to struct in6_addr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from char* to char const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter param has been changed from struct sched_param* to struct sched_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter param has been changed from struct sched_param* to struct sched_param const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long long to u64. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ts has been changed from struct timespec* to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter tz has been changed from struct timezone* to struct timezone const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | 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 2nd parameter features has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from 0 to 1. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter func has been changed from void(*)(void*) to smp_call_func_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter func has been changed from void(*)(void*) to smp_call_func_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter func has been changed from void(*)(void*) to smp_call_func_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter func has been changed from void(*)(void*) to smp_call_func_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter a has been renamed to from. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter b has been renamed to to. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter filename 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 2nd parameter filename 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 filename 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 filename 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 filename 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 2nd parameter filename 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 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 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 return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ops has been changed from struct platform_suspend_ops* to struct platform_suspend_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter xprt_list has been renamed to serv. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter info has been renamed to xpt. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter info has been changed from void* to struct svc_xprt*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter dir has been changed from int to enum dma_data_direction. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter dir has been changed from int to enum dma_data_direction. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter 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 2nd parameter filename 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 filename 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 2nd parameter ubuf 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 filename 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 filename has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sock has been renamed to sk. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sock has been renamed to sk. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | 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 thermal_cooling_device_ops* to struct thermal_cooling_device_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter ops has been changed from struct thermal_zone_device_ops* to struct thermal_zone_device_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter tv has been changed from struct timespec* to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter tz has been changed from struct timezone* to struct timezone const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter tv has been changed from struct timespec* to struct timespec const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter rctxp has been renamed to regs. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 4th parameter irq_flags has been renamed to rctxp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter begin has been changed from struct tracepoint* to struct tracepoint*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter end has been changed from struct tracepoint* to struct tracepoint*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 1st parameter tracepoint has been changed from struct tracepoint** to struct tracepoint*const**. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter begin has been changed from struct tracepoint* to struct tracepoint*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter end has been changed from struct tracepoint* to struct tracepoint*const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter filename 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 2nd parameter filename 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 2nd parameter filename has been changed from char* to char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter old_ns has been renamed to tsk. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int to isolate_mode_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter scanned has been renamed to shrink. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter gfp_mask has been renamed to nr_pages_scanned. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of 1st parameter scanned has been changed from unsigned long to struct shrink_control*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler* to struct xattr_handler const*. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Replacement of data type may indicate a change in 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 | 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 | 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 | 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 | 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 | 2nd parameter dst_p has been renamed to dst_orig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter fl has been changed from struct flowi* to struct flowi const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter sel has been changed from struct xfrm_selector* to struct xfrm_selector const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter c has been changed from struct km_event* to struct km_event const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter c has been changed from struct km_event* to struct km_event const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter daddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 7th parameter saddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter daddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter fl has been changed from struct flowi* to struct flowi const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 2nd parameter saddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter daddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter daddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter saddr has been changed from xfrm_address_t* to xfrm_address_t const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member e1000_ce4100 with value 9 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member e1000_phy_8201 with value 3 has been added. | No effect. |
| 2 | The member e1000_phy_8211 with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field label became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member FBC_MODULE_PARAM with value 7 has been added. | No effect. |
| 2 | The member FBC_MULTIPLE_PIPES with value 6 has been added. | No effect. |
| 3 | The member FBC_NO_OUTPUT with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_MAX_PIPES with value 3 has been added. | No effect. |
| 2 | The member PIPE_C with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PLANE_C with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_WORK_ASSOC_BEACON_WAIT with value 3 has been added. | No effect. |
| 2 | The member IEEE80211_WORK_OFFCHANNEL_TX with value 6 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member T_COMMIT_RECORD with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_EMERG with value 6 has been added. | No effect. |
| 2 | The member KMSG_DUMP_HALT with value 4 has been added. | No effect. |
| 3 | The member KMSG_DUMP_POWEROFF with value 5 has been added. | No effect. |
| 4 | The member KMSG_DUMP_RESTART with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_ANON_TRANSPARENT_HUGEPAGES with value 31 has been added. | No effect. |
| 2 | The member NR_DIRTIED with value 23 has been added. | No effect. |
| 3 | The member NR_WRITTEN with value 24 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IP_CT_ESTABLISHED_REPLY with value 3 has been added. | No effect. |
| 2 | The member IP_CT_NEW_REPLY with value 5 has been added. | No effect. |
| 3 | The member IP_CT_RELATED_REPLY with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SIP_HDR_CALL_ID with value 8 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_IFTYPE_P2P_GO with value 9 has been added. | No effect. |
| 2 | The member NUM_NL80211_IFTYPES with value 10 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NUM_NL80211_KEYTYPES with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmu became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_CURRENT_MAX with value 13 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_PROP_TYPE with value 39 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_TYPE_USB_ACA with value 6 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_TYPE_USB_CDP with value 5 has been added. | No effect. |
| 3 | The member POWER_SUPPLY_TYPE_USB_DCP with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter became non-volatile. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter became non-volatile. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 2.6.34.14 |
| Version #2 | 3.0.101 |
| CPU Type | x86_64 |
| Subject | Source Compatibility |
| Total Header Files | 705 |
|---|---|
| Total Source Files | 1314 |
| Total Objects | 1 |
| Total Symbols / Types | 13996 / 7667 |
| Verdict | Incompatible (56.6%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 1871 |
| Removed Symbols | High | 869 |
| Problems with Data Types | High | 646 |
| Medium | 80 | |
| Low | 1156 | |
| Problems with Symbols | High | 115 |
| Medium | 326 | |
| Low | 169 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 562 |
| Other Changes in Symbols | - | 170 |
| Change | Effect | |
|---|---|---|
| 1 | Field wakeup_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_gpe_event_info' has no member named 'wakeup_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_bank_field' has no member named 'access_bit_width'. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_buffer_field' has no member named 'access_bit_width'. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_field_common' has no member named 'access_bit_width'. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_index_field' has no member named 'access_bit_width'. |
| Change | Effect | |
|---|---|---|
| 1 | Field extra has been renamed to dispatch. | Recompilation of a client program may be broken with the error message: struct acpi_object_method has no member named extra. |
| 2 | Field method_flags has been renamed to info_flags. | Recompilation of a client program may be broken with the error message: struct acpi_object_method has no member named method_flags. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_bit_width has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_region_field' has no member named 'access_bit_width'. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_power_state 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 'force_power_state'. |
| 2 | Field wake_capable 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 'wake_capable'. |
| Change | Effect | |
|---|---|---|
| 1 | Field run_wake_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_wakeup' has no member named 'run_wake_count'. |
| 2 | Field state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_wakeup' has no member named 'state'. |
| Change | Effect | |
|---|---|---|
| 1 | Field always_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_wakeup_flags' has no member named 'always_enabled'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_nr 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 'bus_nr'. |
| 2 | Field osc_control_qry 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 'osc_control_qry'. |
| 3 | Field osc_queried 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 'osc_queried'. |
| Change | Effect | |
|---|---|---|
| 1 | Field agp_map_memory has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_bridge_driver' has no member named 'agp_map_memory'. |
| 2 | Field agp_map_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_bridge_driver' has no member named 'agp_map_page'. |
| 3 | Field agp_unmap_memory has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_bridge_driver' has no member named 'agp_unmap_memory'. |
| 4 | Field agp_unmap_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_bridge_driver' has no member named 'agp_unmap_page'. |
| 5 | Field chipset_flush has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_bridge_driver' has no member named 'chipset_flush'. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmalloc_flag has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct agp_memory' has no member named 'vmalloc_flag'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache_cfg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct amd_iommu' has no member named 'cache_cfg'. |
| 2 | Field reset_in_progress has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct amd_iommu' has no member named 'reset_in_progress'. |
| Change | Effect | |
|---|---|---|
| 1 | Field apicid_to_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct apic' has no member named 'apicid_to_node'. |
| 2 | Field cpu_to_logical_apicid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct apic' has no member named 'cpu_to_logical_apicid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field watch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_chunk' has no member named 'watch'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_parent' has no member named 'flags'. |
| 2 | Field ilist has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_parent' has no member named 'ilist'. |
| 3 | Field wdata has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_parent' has no member named 'wdata'. |
| Change | Effect | |
|---|---|---|
| 1 | Field free has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct autofs_info' has no member named 'free'. |
| 2 | Field mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct autofs_info' has no member named 'mode'. |
| 3 | Field size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct autofs_info' has no member named 'size'. |
| 4 | Field u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct autofs_info' has no member named 'u'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hits has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct avc_cache_stats' has no member named 'hits'. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'wb_list'. |
| 2 | Field rcu_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'rcu_head'. |
| 3 | Field unplug_io_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'unplug_io_data'. |
| 4 | Field unplug_io_fn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'unplug_io_fn'. |
| 5 | Field wb_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'wb_mask'. |
| 6 | Field wb_cnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct backing_dev_info' has no member named 'wb_cnt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bdi_writeback' has no member named 'list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hasvdso has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct linux_binfmt' has no member named 'hasvdso'. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter_bits has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'counter_bits'. |
| 2 | Field syncchunk has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'syncchunk'. |
| Change | Effect | |
|---|---|---|
| 1 | The member REQ_TYPE_LINUX_BLOCK has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field locked_ioctl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct block_device_operations' has no member named 'locked_ioctl'. |
| 2 | Field set_capacity has been renamed to unlock_native_capacity. | Recompilation of a client program may be broken with the error message: struct block_device_operations has no member named set_capacity. |
| Change | Effect | |
|---|---|---|
| 1 | Field orderr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'orderr'. |
| 2 | Field pre_flush_rq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'pre_flush_rq'. |
| 3 | Field unplug_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'unplug_timer'. |
| 4 | Field prepare_flush_fn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'prepare_flush_fn'. |
| 5 | Field unplug_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'unplug_work'. |
| 6 | Field ordcolor has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'ordcolor'. |
| 7 | Field unplug_delay has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'unplug_delay'. |
| 8 | Field next_ordered has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'next_ordered'. |
| 9 | Field ordseq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'ordseq'. |
| 10 | Field orig_bar_rq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'orig_bar_rq'. |
| 11 | Field post_flush_rq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'post_flush_rq'. |
| 12 | Field bar_rq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'bar_rq'. |
| 13 | Field unplug_thresh has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct request_queue' has no member named 'unplug_thresh'. |
| 14 | Field ordered has been renamed to flush_running_idx. | Recompilation of a client program may be broken with the error message: struct request_queue has no member named ordered. |
| 15 | Field unplug_fn has been renamed to unprep_rq_fn. | Recompilation of a client program may be broken with the error message: struct request_queue has no member named unplug_fn. |
| Change | Effect | |
|---|---|---|
| 1 | Field action has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_ops' has no member named 'action'. |
| 2 | Field get_mesh_params has been renamed to get_mesh_config. | Recompilation of a client program may be broken with the error message: struct cfg80211_ops has no member named get_mesh_params. |
| 3 | Field set_mesh_params has been renamed to update_mesh_config. | Recompilation of a client program may be broken with the error message: struct cfg80211_ops has no member named set_mesh_params. |
| Change | Effect | |
|---|---|---|
| 1 | Field mesh_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vif_params' has no member named 'mesh_id'. |
| 2 | Field mesh_id_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vif_params' has no member named 'mesh_id_len'. |
| Change | Effect | |
|---|---|---|
| 1 | Field action_registrations_lock has been renamed to mgmt_registrations_lock. | Recompilation of a client program may be broken with the error message: struct wireless_dev has no member named action_registrations_lock. |
| 2 | Field action_registrations has been renamed to mgmt_registrations. | Recompilation of a client program may be broken with the error message: struct wireless_dev has no member named action_registrations. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_kref has been renamed to cl_count. | Recompilation of a client program may be broken with the error message: struct rpc_clnt has no member named cl_kref. |
| Change | Effect | |
|---|---|---|
| 1 | Field cn_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cn_queue_dev' has no member named 'cn_queue'. |
| 2 | Field wq_created has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cn_queue_dev' has no member named 'wq_created'. |
| 3 | Field wq_creation has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cn_queue_dev' has no member named 'wq_creation'. |
| 4 | Field wq_requested has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cn_queue_dev' has no member named 'wq_requested'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash_vmalloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ct' has no member named 'hash_vmalloc'. |
| 2 | Field expect_vmalloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ct' has no member named 'expect_vmalloc'. |
| Change | Effect | |
|---|---|---|
| 1 | Field vc_tty has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vc_data' has no member named 'vc_tty'. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel 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 'channel'. |
| Change | Effect | |
|---|---|---|
| 1 | Field Attributes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'Attributes'. |
| 2 | Field CardValues has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'CardValues'. |
| 3 | Field ConfigBase has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'ConfigBase'. |
| 4 | Field Copy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'Copy'. |
| 5 | Field ExtStatus has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'ExtStatus'. |
| 6 | Field IntType has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'IntType'. |
| 7 | Field Option has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'Option'. |
| 8 | Field Pin has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'Pin'. |
| 9 | Field Status has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'Status'. |
| 10 | Field irq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct config_t' has no member named 'irq'. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_io has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pccard_resource_ops' has no member named 'add_io'. |
| 2 | Field add_mem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pccard_resource_ops' has no member named 'add_mem'. |
| 3 | Field adjust_io_region has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pccard_resource_ops' has no member named 'adjust_io_region'. |
| Change | Effect | |
|---|---|---|
| 1 | Field event has been renamed to add. | Recompilation of a client program may be broken with the error message: struct pcmcia_callback has no member named event. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_mounted 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_mounted'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_request has been renamed to target_request_nr. | Recompilation of a client program may be broken with the error message: union map_info has no member named flush_request. |
| Change | Effect | |
|---|---|---|
| 1 | Field sem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct device' has no member named 'sem'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_kcopyd_client' has no member named 'lock'. |
| 2 | Field nr_pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_kcopyd_client' has no member named 'nr_pages'. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_failure has been renamed to flush_failure. | Recompilation of a client program may be broken with the error message: struct dm_region_hash has no member named barrier_failure. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_bio 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 'barrier_bio'. |
| 2 | Field barrier_error 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 'barrier_error'. |
| 3 | Field barrier_error_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 'barrier_error_lock'. |
| 4 | Field barrier_work 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 'barrier_work'. |
| 5 | Field flush_request 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 'flush_request'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_single_range_for_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dma_map_ops' has no member named 'sync_single_range_for_cpu'. |
| 2 | Field sync_single_range_for_device has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dma_map_ops' has no member named 'sync_single_range_for_device'. |
| Change | Effect | |
|---|---|---|
| 1 | Field waitq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dma_pool' has no member named 'waitq'. |
| Change | Effect | |
|---|---|---|
| 1 | Field desired_mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_crtc' has no member named 'desired_mode'. |
| 2 | Field desired_x has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_crtc' has no member named 'desired_x'. |
| 3 | Field desired_y has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_crtc' has no member named 'desired_y'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_off_supported has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'active_off_supported'. |
| 2 | Field blank_to_black has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'blank_to_black'. |
| 3 | Field bluex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'bluex'. |
| 4 | Field bluey has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'bluey'. |
| 5 | Field composite_sync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'composite_sync'. |
| 6 | Field digital has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'digital'. |
| 7 | Field display_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'display_type'. |
| 8 | Field gamma has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'gamma'. |
| 9 | Field greenx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'greenx'. |
| 10 | Field greeny has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'greeny'. |
| 11 | Field gtf_supported has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'gtf_supported'. |
| 12 | Field redx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'redx'. |
| 13 | Field redy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'redy'. |
| 14 | Field separate_syncs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'separate_syncs'. |
| 15 | Field serration_vsync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'serration_vsync'. |
| 16 | Field standard_color has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'standard_color'. |
| 17 | Field standby_supported has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'standby_supported'. |
| 18 | Field suspend_supported has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'suspend_supported'. |
| 19 | Field sync_on_green has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'sync_on_green'. |
| 20 | Field video_level has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'video_level'. |
| 21 | Field whitex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'whitex'. |
| 22 | Field whitey has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'whitey'. |
| 23 | Field wpgamma1 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpgamma1'. |
| 24 | Field wpgamma2 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpgamma2'. |
| 25 | Field wpx1 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpx1'. |
| 26 | Field wpx2 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpx2'. |
| 27 | Field wpy1 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpy1'. |
| 28 | Field wpy2 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_info' has no member named 'wpy2'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fbdev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_framebuffer' has no member named 'fbdev'. |
| 2 | Field pseudo_palette has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_framebuffer' has no member named 'pseudo_palette'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_kernel_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mode_config' has no member named 'fb_kernel_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_changed has been renamed to output_poll_changed. | Recompilation of a client program may be broken with the error message: struct drm_mode_config_funcs has no member named fb_changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field use_vmalloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_open_hash' has no member named 'use_vmalloc'. |
| 2 | Field size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_open_hash' has no member named 'size'. |
| 3 | Field fill has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_open_hash' has no member named 'fill'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ml_entry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mm' has no member named 'ml_entry'. |
| 2 | Field fl_entry has been renamed to hole_stack. | Recompilation of a client program may be broken with the error message: struct drm_mm has no member named fl_entry. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_entry has been renamed to node_list. | Recompilation of a client program may be broken with the error message: struct drm_mm_node has no member named fl_entry. |
| 2 | Field free has been renamed to hole_follows. | Recompilation of a client program may be broken with the error message: struct drm_mm_node has no member named free. |
| 3 | Field ml_entry has been renamed to hole_stack. | Recompilation of a client program may be broken with the error message: struct drm_mm_node has no member named ml_entry. |
| Change | Effect | |
|---|---|---|
| 1 | Field drw_idr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'drw_idr'. |
| 2 | Field drw_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'drw_lock'. |
| 3 | Field flush_domains has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'flush_domains'. |
| 4 | Field gtt_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'gtt_count'. |
| 5 | Field gtt_memory has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'gtt_memory'. |
| 6 | Field gtt_total has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'gtt_total'. |
| 7 | Field invalidate_domains has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'invalidate_domains'. |
| 8 | Field object_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'object_count'. |
| 9 | Field object_memory has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'object_memory'. |
| 10 | Field pin_memory has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'pin_memory'. |
| 11 | Field timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_device' has no member named 'timer'. |
| 12 | Field pin_count has been renamed to switch_power_state. | Recompilation of a client program may be broken with the error message: struct drm_device has no member named pin_count. |
| Change | Effect | |
|---|---|---|
| 1 | Field context_ctor has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'context_ctor'. |
| 2 | Field dma_ready has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'dma_ready'. |
| 3 | Field gem_free_object_unlocked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'gem_free_object_unlocked'. |
| 4 | Field get_map_ofs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'get_map_ofs'. |
| 5 | Field get_reg_ofs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'get_reg_ofs'. |
| 6 | Field kernel_context_switch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'kernel_context_switch'. |
| 7 | Field kernel_context_switch_unlock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'kernel_context_switch_unlock'. |
| 8 | Field pci_driver has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'pci_driver'. |
| 9 | Field proc_init has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_driver' has no member named 'proc_init'. |
| 10 | Field proc_cleanup has been renamed to dumb_create. | Recompilation of a client program may be broken with the error message: struct drm_driver has no member named proc_cleanup. |
| Change | Effect | |
|---|---|---|
| 1 | Field handlecount has been renamed to handle_count. | Recompilation of a client program may be broken with the error message: struct drm_gem_object has no member named handlecount. |
| Change | Effect | |
|---|---|---|
| 1 | Field conf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_device' has no member named 'conf'. |
| 2 | Field dev_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_device' has no member named 'dev_node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_last has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dst_entry' has no member named 'rate_last'. |
| 2 | Field rate_tokens has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dst_entry' has no member named 'rate_tokens'. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dst_ops' has no member named 'entries'. |
| Change | Effect | |
|---|---|---|
| 1 | Field restore has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dvo_dev_ops' has no member named 'restore'. |
| 2 | Field save has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_dvo_dev_ops' has no member named 'save'. |
| Change | Effect | |
|---|---|---|
| 1 | Field blink_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'blink_timer'. |
| 2 | Field led_status has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'led_status'. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_queue_empty_fn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct elevator_ops' has no member named 'elevator_queue_empty_fn'. |
| Change | Effect | |
|---|---|---|
| 1 | Field phys_id has been renamed to set_phys_id. | Recompilation of a client program may be broken with the error message: struct ethtool_ops has no member named phys_id. |
| Change | Effect | |
|---|---|---|
| 1 | Field aperture_base has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fb_info' has no member named 'aperture_base'. |
| 2 | Field aperture_size has been renamed to apertures. | Recompilation of a client program may be broken with the error message: struct fb_info has no member named aperture_size. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_scope has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fib_alias' has no member named 'fa_scope'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'flags'. |
| 2 | Field iif has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'iif'. |
| 3 | Field mark has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'mark'. |
| 4 | Field nl_u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'nl_u'. |
| 5 | Field oif has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'oif'. |
| 6 | Field proto has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'proto'. |
| 7 | Field secid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'secid'. |
| 8 | Field uli_u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct flowi' has no member named 'uli_u'. |
| Change | Effect | |
|---|---|---|
| 1 | Field truncate_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct address_space' has no member named 'truncate_count'. |
| 2 | Field unmap_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct address_space' has no member named 'unmap_mutex'. |
| 3 | Field i_mmap_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct address_space' has no member named 'i_mmap_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sync_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct address_space_operations' has no member named 'sync_page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bd_holder_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct block_device' has no member named 'bd_holder_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct file_operations' has no member named 'ioctl'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_sb has been renamed to mount. | Recompilation of a client program may be broken with the error message: struct file_system_type has no member named get_sb. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dentry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'i_dentry'. |
| 2 | Field i_fsnotify_mark_entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'i_fsnotify_mark_entries'. |
| 3 | Field i_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'i_list'. |
| 4 | Field inotify_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'inotify_mutex'. |
| 5 | Field inotify_watches has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode' has no member named 'inotify_watches'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fallocate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inode_operations' has no member named 'fallocate'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fl_copy_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct lock_manager_operations' has no member named 'fl_copy_lock'. |
| 2 | Field fl_mylease has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct lock_manager_operations' has no member named 'fl_mylease'. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_need_sync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_need_sync'. |
| Change | Effect | |
|---|---|---|
| 1 | Field clear_inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_operations' has no member named 'clear_inode'. |
| 2 | Field delete_inode has been renamed to evict_inode. | Recompilation of a client program may be broken with the error message: struct super_operations has no member named delete_inode. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_bdev has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field i_cdev has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field i_pipe has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_group' has no member named 'group_list'. |
| 2 | Field group_num has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_group' has no member named 'group_num'. |
| 3 | Field mark_entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_group' has no member named 'mark_entries'. |
| 4 | Field mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_group' has no member named 'mask'. |
| 5 | Field on_group_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_group' has no member named 'on_group_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'enabled'. |
| 2 | Field fields has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'fields'. |
| 3 | Field filter_active has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'filter_active'. |
| 4 | Field id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'id'. |
| 5 | Field perf_event_disable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'perf_event_disable'. |
| 6 | Field perf_event_enable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'perf_event_enable'. |
| 7 | Field raw_init has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'raw_init'. |
| 8 | Field regfunc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'regfunc'. |
| 9 | Field system has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'system'. |
| 10 | Field unregfunc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'unregfunc'. |
| 11 | Field define_fields has been renamed to perf_events. | Recompilation of a client program may be broken with the error message: struct ftrace_event_call has no member named define_fields. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_depth has been renamed to padding. | Recompilation of a client program may be broken with the error message: struct trace_entry has no member named lock_depth. |
| Change | Effect | |
|---|---|---|
| 1 | Field binary has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_event' has no member named 'binary'. |
| 2 | Field hex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_event' has no member named 'hex'. |
| 3 | Field raw has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_event' has no member named 'raw'. |
| 4 | Field trace has been renamed to funcs. | Recompilation of a client program may be broken with the error message: struct trace_event has no member named trace. |
| Change | Effect | |
|---|---|---|
| 1 | Field async_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct gendisk' has no member named 'async_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_pending_irqs has been renamed to apic_irq_work_irqs. | Recompilation of a client program may be broken with the error message: struct irq_cpustat_t has no member named apic_pending_irqs. |
| Change | Effect | |
|---|---|---|
| 1 | Field poll_pending has been renamed to msix_enabled. | Recompilation of a client program may be broken with the error message: struct usb_hcd has no member named poll_pending. |
| 2 | Field poll_rh has been renamed to rh_pollable. | Recompilation of a client program may be broken with the error message: struct usb_hcd has no member named poll_rh. |
| Change | Effect | |
|---|---|---|
| 1 | Field function_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_codec' has no member named 'function_id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field input_pins has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct auto_pin_cfg' has no member named 'input_pins'. |
| Change | Effect | |
|---|---|---|
| 1 | Field _expires has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hrtimer' has no member named '_expires'. |
| Change | Effect | |
|---|---|---|
| 1 | Field first has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hrtimer_clock_base' has no member named 'first'. |
| Change | Effect | |
|---|---|---|
| 1 | Field id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i2c_adapter' has no member named 'id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_list_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'active_list_lock'. |
| 2 | Field gpu_write_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'gpu_write_list'. |
| 3 | Field irq_gem_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'irq_gem_seqno'. |
| 4 | Field next_gem_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'next_gem_seqno'. |
| 5 | Field request_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'request_list'. |
| 6 | Field waiting_gem_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-490' has no member named 'waiting_gem_seqno'. |
| 7 | Field shrink_list has been renamed to gtt_list. | Recompilation of a client program may be broken with the error message: anon-struct-i915_drv.h-490 has no member named shrink_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field pipeastat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'pipeastat'. |
| 2 | Field pipebstat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_error_state' has no member named 'pipebstat'. |
| Change | Effect | |
|---|---|---|
| 1 | Field obj has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'obj'. |
| 2 | Field agp_mem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'agp_mem'. |
| 3 | Field mmap_offset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'mmap_offset'. |
| 4 | Field pages_refcount has been renamed to pending_gpu_write. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named pages_refcount. |
| 5 | Field fence_list has been renamed to mm_list. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named fence_list. |
| 6 | Field agp_type has been renamed to pending_fenced_gpu_access. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named agp_type. |
| 7 | Field in_execbuffer has been renamed to num_sg. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named in_execbuffer. |
| 8 | Field list has been renamed to gtt_list. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named list. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight_duty_cycle 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 'backlight_duty_cycle'. |
| 2 | Field crt_ddc_bus 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_bus'. |
| 3 | Field de_irq_enable_reg 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 'de_irq_enable_reg'. |
| 4 | Field dma_status_page 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 'dma_status_page'. |
| 5 | Field edp_bpp 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_bpp'. |
| 6 | Field gt_irq_enable_reg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'gt_irq_enable_reg'. |
| 7 | Field gt_irq_mask_reg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'gt_irq_mask_reg'. |
| 8 | Field hw_status_page 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 'hw_status_page'. |
| 9 | Field hws_obj 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 'hws_obj'. |
| 10 | Field irq_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'irq_enabled'. |
| 11 | Field irq_mask_reg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'irq_mask_reg'. |
| 12 | Field irq_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'irq_queue'. |
| 13 | Field lvds_edid_good 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_edid_good'. |
| 14 | Field panel_wants_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 'panel_wants_dither'. |
| 15 | Field pch_irq_enable_reg 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_irq_enable_reg'. |
| 16 | Field pch_irq_mask_reg 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_irq_mask_reg'. |
| 17 | Field seqno_gfx_addr 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 'seqno_gfx_addr'. |
| 18 | Field seqno_obj 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 'seqno_obj'. |
| 19 | Field seqno_page 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 'seqno_page'. |
| 20 | Field status_gfx_addr 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 'status_gfx_addr'. |
| 21 | Field trace_irq_seqno 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 'trace_irq_seqno'. |
| 22 | Field user_irq_refcount 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 'user_irq_refcount'. |
| 23 | Field vram 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 'vram'. |
| 24 | Field edp_support has been renamed to crt_ddc_pin. | Recompilation of a client program may be broken with the error message: struct drm_i915_private has no member named edp_support. |
| 25 | Field user_irq_lock has been renamed to pch_irq_mask. | Recompilation of a client program may be broken with the error message: struct drm_i915_private has no member named user_irq_lock. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_rc6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'has_rc6'. |
| 2 | Field is_gen6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_gen6'. |
| 3 | Field is_i8xx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_i8xx'. |
| 4 | Field is_i965g has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_i965g'. |
| 5 | Field is_i965gm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_i965gm'. |
| 6 | Field is_i9xx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_i9xx'. |
| 7 | Field is_ironlake has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_device_info' has no member named 'is_ironlake'. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_opregion' has no member named 'enabled'. |
| Change | Effect | |
|---|---|---|
| 1 | The member WLAN_BACK_TIMER has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field request 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 'request'. |
| 2 | Field skb_queue 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 'skb_queue'. |
| 3 | Field work has been renamed to mtx. | Recompilation of a client program may be broken with the error message: struct ieee80211_if_ibss has no member named work. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_loss_work 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 'beacon_loss_work'. |
| 2 | Field skb_queue 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 'skb_queue'. |
| 3 | Field work 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 'work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'ampdu_lock'. |
| 2 | Field key_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'key_lock'. |
| 3 | Field mc_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'mc_count'. |
| 4 | Field scan_mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'scan_mtx'. |
| 5 | Field work_mtx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'work_mtx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_sub_if_data' has no member named 'default_key'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dead has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_ifaddr' has no member named 'dead'. |
| 2 | Field if_next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_ifaddr' has no member named 'if_next'. |
| 3 | Field lst_next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_ifaddr' has no member named 'lst_next'. |
| Change | Effect | |
|---|---|---|
| 1 | Field icmpv6msg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ipv6_devstat' has no member named 'icmpv6msg'. |
| 2 | Field icmpv6 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ipv6_devstat' has no member named 'icmpv6'. |
| Change | Effect | |
|---|---|---|
| 1 | Field killall has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vlan_group' has no member named 'killall'. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct ip_mc_list has no member named next. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been renamed to next_rcu. | Recompilation of a client program may be broken with the error message: struct ip_mc_socklist has no member named next. |
| Change | Effect | |
|---|---|---|
| 1 | Field remember_stamp has been renamed to get_peer. | Recompilation of a client program may be broken with the error message: struct inet_connection_sock_af_ops has no member named remember_stamp. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'addr'. |
| 2 | Field dst has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'dst'. |
| 3 | Field flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'flags'. |
| 4 | Field fragsize has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'fragsize'. |
| 5 | Field length has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'length'. |
| 6 | Field opt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inet_sock.h-143' has no member named 'opt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field inet_daddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_sock' has no member named 'inet_daddr'. |
| 2 | Field inet_rcv_saddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_sock' has no member named 'inet_rcv_saddr'. |
| 3 | Field opt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_sock' has no member named 'opt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_daddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_timewait_sock' has no member named 'tw_daddr'. |
| 2 | Field tw_rcv_saddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_timewait_sock' has no member named 'tw_rcv_saddr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mc_list_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct in_device' has no member named 'mc_list_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcp_ts_stamp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'tcp_ts_stamp'. |
| 2 | Field rid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'rid'. |
| 3 | Field ip_id_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'ip_id_count'. |
| 4 | Field v4daddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'v4daddr'. |
| 5 | Field tcp_ts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'tcp_ts'. |
| Change | Effect | |
|---|---|---|
| 1 | Field abs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'abs'. |
| 2 | Field absflat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'absflat'. |
| 3 | Field absfuzz has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'absfuzz'. |
| 4 | Field absmax has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'absmax'. |
| 5 | Field absmin has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'absmin'. |
| 6 | Field absres has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_dev' has no member named 'absres'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct child_device_config' has no member named 'device_id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor_visble 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 'cursor_visble'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ddc_bus 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 'ddc_bus'. |
| 2 | Field enc 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 'enc'. |
| 3 | Field i2c_bus 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 'i2c_bus'. |
| 4 | Field load_detect_temp 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 'load_detect_temp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_wedged has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_overlay' has no member named 'hw_wedged'. |
| 2 | Field virt_addr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_overlay' has no member named 'virt_addr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field destructor has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct ip_ra_chain has no member named destructor. |
| Change | Effect | |
|---|---|---|
| 1 | Field shtx has been renamed to tx_flags. | Recompilation of a client program may be broken with the error message: struct ipcm_cookie has no member named shtx. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rt6_info' has no member named 'u'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mfc_cache_array has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'mfc_cache_array'. |
| 2 | Field mroute_do_pim has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'mroute_do_pim'. |
| 3 | Field mroute_reg_vif_num has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'mroute_reg_vif_num'. |
| 4 | Field mroute_do_assert has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'mroute_do_assert'. |
| 5 | Field vif_table has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'vif_table'. |
| 6 | Field cache_resolve_queue_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'cache_resolve_queue_len'. |
| 7 | Field maxvif has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'maxvif'. |
| 8 | Field rt_secret_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'rt_secret_timer'. |
| 9 | Field nat_vmalloced has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'nat_vmalloced'. |
| 10 | Field mroute_sk has been renamed to mrt. | Recompilation of a client program may be broken with the error message: struct netns_ipv4 has no member named mroute_sk. |
| Change | Effect | |
|---|---|---|
| 1 | Field ack has been renamed to irq_ack. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named ack. |
| 2 | Field bus_lock has been renamed to irq_bus_sync_unlock. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named bus_lock. |
| 3 | Field bus_sync_unlock has been renamed to irq_cpu_online. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named bus_sync_unlock. |
| 4 | Field disable has been renamed to irq_disable. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named disable. |
| 5 | Field enable has been renamed to irq_enable. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named enable. |
| 6 | Field end has been renamed to irq_set_affinity. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named end. |
| 7 | Field eoi has been renamed to irq_eoi. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named eoi. |
| 8 | Field mask has been renamed to irq_mask. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named mask. |
| 9 | Field mask_ack has been renamed to irq_mask_ack. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named mask_ack. |
| 10 | Field retrigger has been renamed to irq_set_type. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named retrigger. |
| 11 | Field set_affinity has been renamed to irq_retrigger. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named set_affinity. |
| 12 | Field set_type has been renamed to irq_set_wake. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named set_type. |
| 13 | Field set_wake has been renamed to irq_bus_lock. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named set_wake. |
| 14 | Field shutdown has been renamed to irq_shutdown. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named shutdown. |
| 15 | Field startup has been renamed to irq_startup. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named startup. |
| 16 | Field typename has been renamed to irq_cpu_offline. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named typename. |
| 17 | Field unmask has been renamed to irq_unmask. | Recompilation of a client program may be broken with the error message: struct irq_chip has no member named unmask. |
| Change | Effect | |
|---|---|---|
| 1 | Field chip has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'chip'. |
| 2 | Field chip_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'chip_data'. |
| 3 | Field handler_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'handler_data'. |
| 4 | Field irq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'irq'. |
| 5 | Field msi_desc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'msi_desc'. |
| 6 | Field node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'node'. |
| 7 | Field status has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'status'. |
| 8 | Field affinity has been renamed to threads_oneshot. | Recompilation of a client program may be broken with the error message: struct irq_desc has no member named affinity. |
| Change | Effect | |
|---|---|---|
| 1 | The member T_RUNDOWN has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The member DIE_NMIWATCHDOG has been removed. | Recompilation of a client program may be broken. |
| 2 | The member DIE_NMI_IPI has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field todo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_key' has no member named 'todo'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct subprocess_info' has no member named 'cred'. |
| 2 | Field stdin has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct subprocess_info' has no member named 'stdin'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_policy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'pm_policy'. |
| 2 | Field port_task has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'port_task'. |
| 3 | Field port_task_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'port_task_data'. |
| 4 | Field prd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'prd'. |
| 5 | Field prd_dma has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port' has no member named 'prd_dma'. |
| Change | Effect | |
|---|---|---|
| 1 | Field drain_fifo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port_operations' has no member named 'drain_fifo'. |
| 2 | Field disable_pm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_port_operations' has no member named 'disable_pm'. |
| 3 | Field enable_pm has been renamed to set_lpm. | Recompilation of a client program may be broken with the error message: struct ata_port_operations has no member named enable_pm. |
| Change | Effect | |
|---|---|---|
| 1 | Field fs has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_ack_map has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-mac80211.h-425' has no member named 'ampdu_ack_map'. |
| Change | Effect | |
|---|---|---|
| 1 | Field alg has been renamed to cipher. | Recompilation of a client program may be broken with the error message: struct ieee80211_key_conf has no member named alg. |
| Change | Effect | |
|---|---|---|
| 1 | Field noise has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_rx_status' has no member named 'noise'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap has been renamed to bss. | Recompilation of a client program may be broken with the error message: struct ieee80211_tx_rate_control has no member named ap. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_op has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mb_cache' has no member named 'c_op'. |
| 2 | Field c_indexes_hash has been renamed to c_index_hash. | Recompilation of a client program may be broken with the error message: struct mb_cache has no member named c_indexes_hash. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_indexes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mb_cache_entry' has no member named 'e_indexes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field barriers_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mddev_s' has no member named 'barriers_work'. |
| 2 | Field biolist has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mddev_s' has no member named 'biolist'. |
| 3 | Field max_write_behind has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mddev_s' has no member named 'max_write_behind'. |
| 4 | Field write_behind has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mddev_s' has no member named 'write_behind'. |
| 5 | Field barrier has been renamed to flush_bio. | Recompilation of a client program may be broken with the error message: struct mddev_s has no member named barrier. |
| 6 | Field barrier_work has been renamed to flush_work. | Recompilation of a client program may be broken with the error message: struct mddev_s has no member named barrier_work. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct shared_policy' has no member named 'lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_mmap_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zap_details' has no member named 'i_mmap_lock'. |
| 2 | Field truncate_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zap_details' has no member named 'truncate_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_vm_mask has been renamed to cpu_vm_mask_var. | Recompilation of a client program may be broken with the error message: struct mm_struct has no member named cpu_vm_mask. |
| Change | Effect | |
|---|---|---|
| 1 | Field vm_truncate_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vm_area_struct' has no member named 'vm_truncate_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_priority has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zone' has no member named 'prev_priority'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_saved_scan has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zone_reclaim_stat' has no member named 'nr_saved_scan'. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_ctors has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct module' has no member named 'num_ctors'. |
| 2 | Field tracepoints has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct module' has no member named 'tracepoints'. |
| 3 | Field ctors has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct module' has no member named 'ctors'. |
| 4 | Field modules_which_use_me has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct module' has no member named 'modules_which_use_me'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kernel_param' has no member named 'get'. |
| 2 | Field set has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kernel_param' has no member named 'set'. |
| Change | Effect | |
|---|---|---|
| 1 | Field set has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kparam_array' has no member named 'set'. |
| 2 | Field get has been renamed to ops. | Recompilation of a client program may be broken with the error message: struct kparam_array has no member named get. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_writers has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_writers'. |
| 2 | Field mnt_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vfsmount' has no member named 'mnt_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct neigh_table' has no member named 'hash_mask'. |
| 2 | Field hash_rnd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct neigh_table' has no member named 'hash_rnd'. |
| 3 | Field hash_buckets has been renamed to nht. | Recompilation of a client program may be broken with the error message: struct neigh_table has no member named hash_buckets. |
| Change | Effect | |
|---|---|---|
| 1 | Field wait has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct socket' has no member named 'wait'. |
| 2 | Field fasync_list has been renamed to wq. | Recompilation of a client program may be broken with the error message: struct socket has no member named fasync_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field macvlan_port has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'macvlan_port'. |
| 2 | Field mc_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'mc_count'. |
| 3 | Field rx_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'rx_queue'. |
| 4 | Field refcnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'refcnt'. |
| 5 | Field br_port has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'br_port'. |
| 6 | Field mc_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_device' has no member named 'mc_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tx_packets has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netdev_queue' has no member named 'tx_packets'. |
| 2 | Field tx_bytes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netdev_queue' has no member named 'tx_bytes'. |
| 3 | Field tx_dropped has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netdev_queue' has no member named 'tx_dropped'. |
| Change | Effect | |
|---|---|---|
| 1 | Field eff_cap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlink_skb_parms' has no member named 'eff_cap'. |
| 2 | Field loginuid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlink_skb_parms' has no member named 'loginuid'. |
| 3 | Field sessionid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlink_skb_parms' has no member named 'sessionid'. |
| 4 | Field sid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netlink_skb_parms' has no member named 'sid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ct_h323_info has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field ct_pptp_info has been removed from this union. | Recompilation of a client program may be broken. |
| 3 | Field ct_sane_info has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The member NF_CT_EXT_ECACHE has been removed. | Recompilation of a client program may be broken. |
| 2 | The member NF_CT_EXT_ZONE has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_client has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_owner' has no member named 'so_client'. |
| 2 | Field so_client_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_owner' has no member named 'so_client_node'. |
| 3 | Field so_delegations has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_state_owner' has no member named 'so_delegations'. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_open_context' has no member named 'count'. |
| 2 | Field dir_cookie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_open_context' has no member named 'dir_cookie'. |
| 3 | Field lockowner has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_open_context' has no member named 'lockowner'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_delegations has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_client' has no member named 'cl_delegations'. |
| 2 | Field cl_lockowner_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_client' has no member named 'cl_lockowner_id'. |
| 3 | Field cl_openowner_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_client' has no member named 'cl_openowner_id'. |
| 4 | Field cl_state_owners has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_client' has no member named 'cl_state_owners'. |
| 5 | Field cl_call_sync has been renamed to cl_session. | Recompilation of a client program may be broken with the error message: struct nfs_client has no member named cl_call_sync. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_list has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct nfs_page has no member named wb_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_slotid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_sequence_res' has no member named 'sr_slotid'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 8 has been changed from __NL80211_IFTYPE_AFTER_LAST to NL80211_IFTYPE_P2P_CLIENT. | Recompilation of a client program may be broken with the error message: '__NL80211_IFTYPE_AFTER_LAST' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snd_pcm_substream' has no member named 'latency_id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field remaining has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-perf_event.h-487' has no member named 'remaining'. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event' has no member named 'data'. |
| 2 | Field filp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event' has no member named 'filp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bp_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event_attr' has no member named 'bp_len'. |
| 2 | Field bp_addr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event_attr' has no member named 'bp_addr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field locked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_output_handle' has no member named 'locked'. |
| 2 | Field data has been renamed to buffer. | Recompilation of a client program may be broken with the error message: struct perf_output_handle has no member named data. |
| 3 | Field head has been renamed to wakeup. | Recompilation of a client program may be broken with the error message: struct perf_output_handle has no member named head. |
| 4 | Field offset has been renamed to size. | Recompilation of a client program may be broken with the error message: struct perf_output_handle has no member named offset. |
| Change | Effect | |
|---|---|---|
| 1 | Field enable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pmu' has no member named 'enable'. |
| 2 | Field unthrottle has been renamed to pmu_cpu_context. | Recompilation of a client program may be broken with the error message: struct pmu has no member named unthrottle. |
| 3 | Field disable has been renamed to dev. | Recompilation of a client program may be broken with the error message: struct pmu has no member named disable. |
| Change | Effect | |
|---|---|---|
| 1 | Field info has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field prio_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct plist_head' has no member named 'prio_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field plist has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct plist_node' has no member named 'plist'. |
| Change | Effect | |
|---|---|---|
| 1 | Field should_wakeup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dev_pm_info' has no member named 'should_wakeup'. |
| 2 | Field status has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dev_pm_info' has no member named 'status'. |
| Change | Effect | |
|---|---|---|
| 1 | Field type_attr_map has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct policydb' has no member named 'type_attr_map'. |
| 2 | Field type_val_to_struct has been renamed to type_val_to_struct_array. | Recompilation of a client program may be broken with the error message: struct policydb has no member named type_val_to_struct. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf_offset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snapshot_handle' has no member named 'buf_offset'. |
| 2 | Field cur_offset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snapshot_handle' has no member named 'cur_offset'. |
| 3 | Field offset has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snapshot_handle' has no member named 'offset'. |
| 4 | Field prev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct snapshot_handle' has no member named 'prev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field demotion has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_processor_cx' has no member named 'demotion'. |
| 2 | Field promotion has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_processor_cx' has no member named 'promotion'. |
| Change | Effect | |
|---|---|---|
| 1 | Field llc_shared_map 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 'llc_shared_map'. |
| 2 | Field x86_hyper_vendor 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 'x86_hyper_vendor'. |
| Change | Effect | |
|---|---|---|
| 1 | Field debugctlmsr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thread_struct' has no member named 'debugctlmsr'. |
| 2 | Field ds_ctx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thread_struct' has no member named 'ds_ctx'. |
| 3 | Field xstate has been renamed to has_fpu. | Recompilation of a client program may be broken with the error message: struct thread_struct has no member named xstate. |
| Change | Effect | |
|---|---|---|
| 1 | Field allocated_dquots has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'allocated_dquots'. |
| 2 | Field cache_hits has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'cache_hits'. |
| 3 | Field drops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'drops'. |
| 4 | Field free_dquots has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'free_dquots'. |
| 5 | Field lookups has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'lookups'. |
| 6 | Field reads has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'reads'. |
| 7 | Field syncs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'syncs'. |
| 8 | Field writes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dqstats' has no member named 'writes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_xquota has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct quotactl_ops' has no member named 'get_xquota'. |
| 2 | Field set_xquota has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct quotactl_ops' has no member named 'set_xquota'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dynticks_nmi_snap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_data' has no member named 'dynticks_nmi_snap'. |
| 2 | Field preemptable has been renamed to preemptible. | Recompilation of a client program may be broken with the error message: struct rcu_data has no member named preemptable. |
| Change | Effect | |
|---|---|---|
| 1 | Field dynticks_nmi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_dynticks' has no member named 'dynticks_nmi'. |
| Change | Effect | |
|---|---|---|
| 1 | Field blocked_tasks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_node' has no member named 'blocked_tasks'. |
| Change | Effect | |
|---|---|---|
| 1 | Field orphan_cbs_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_state' has no member named 'orphan_cbs_list'. |
| 2 | Field orphan_cbs_tail has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_state' has no member named 'orphan_cbs_tail'. |
| 3 | Field orphan_qlen has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_state' has no member named 'orphan_qlen'. |
| Change | Effect | |
|---|---|---|
| 1 | Field country_ie_checksum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct regulatory_request' has no member named 'country_ie_checksum'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct anon_vma' has no member named 'lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field idev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'idev'. |
| 2 | Field u has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'u'. |
| 3 | Field fl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'fl'. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_set_freq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtc_class_ops' has no member named 'irq_set_freq'. |
| 2 | Field irq_set_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtc_class_ops' has no member named 'irq_set_state'. |
| 3 | Field update_irq_enable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtc_class_ops' has no member named 'update_irq_enable'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_spread_over has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfs_rq' has no member named 'nr_spread_over'. |
| 2 | Field shares has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfs_rq' has no member named 'shares'. |
| 3 | Field rq_weight has been renamed to load_avg. | Recompilation of a client program may be broken with the error message: struct cfs_rq has no member named rq_weight. |
| Change | Effect | |
|---|---|---|
| 1 | Field migration_thread has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'migration_thread'. |
| 2 | Field in_nohz_recently has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'in_nohz_recently'. |
| 3 | Field migration_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'migration_queue'. |
| 4 | Field bkl_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rq' has no member named 'bkl_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tk_magic has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_task' has no member named 'tk_magic'. |
| 2 | Field tk_bytes_sent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_task' has no member named 'tk_bytes_sent'. |
| 3 | Field tk_rtt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_task' has no member named 'tk_rtt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_wakeups_sync has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_sync'. |
| 2 | Field iowait_sum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'iowait_sum'. |
| 3 | Field slice_max has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'slice_max'. |
| 4 | Field nr_wakeups_affine has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_affine'. |
| 5 | Field nr_wakeups_passive has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_passive'. |
| 6 | Field sleep_max has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'sleep_max'. |
| 7 | Field sleep_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'sleep_start'. |
| 8 | Field start_runtime has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'start_runtime'. |
| 9 | Field wait_max has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'wait_max'. |
| 10 | Field wait_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'wait_start'. |
| 11 | Field exec_max has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'exec_max'. |
| 12 | Field avg_wakeup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'avg_wakeup'. |
| 13 | Field nr_forced_migrations has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_forced_migrations'. |
| 14 | Field nr_wakeups has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups'. |
| 15 | Field block_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'block_start'. |
| 16 | Field nr_wakeups_idle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_idle'. |
| 17 | Field last_wakeup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'last_wakeup'. |
| 18 | Field avg_overlap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'avg_overlap'. |
| 19 | Field nr_failed_migrations_running has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_failed_migrations_running'. |
| 20 | Field nr_wakeups_remote has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_remote'. |
| 21 | Field block_max has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'block_max'. |
| 22 | Field nr_migrations_cold has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_migrations_cold'. |
| 23 | Field nr_wakeups_local has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_local'. |
| 24 | Field wait_sum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'wait_sum'. |
| 25 | Field iowait_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'iowait_count'. |
| 26 | Field nr_failed_migrations_affine has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_failed_migrations_affine'. |
| 27 | Field nr_failed_migrations_hot has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_failed_migrations_hot'. |
| 28 | Field nr_wakeups_affine_attempts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_affine_attempts'. |
| 29 | Field nr_wakeups_migrate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'nr_wakeups_migrate'. |
| 30 | Field sum_sleep_runtime has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'sum_sleep_runtime'. |
| 31 | Field wait_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_entity' has no member named 'wait_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_power has been renamed to ref. | Recompilation of a client program may be broken with the error message: struct sched_group has no member named cpu_power. |
| Change | Effect | |
|---|---|---|
| 1 | Field bkl_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_info' has no member named 'bkl_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been renamed to sigcnt. | Recompilation of a client program may be broken with the error message: struct signal_struct has no member named count. |
| Change | Effect | |
|---|---|---|
| 1 | Field bts 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 'bts'. |
| 2 | Field cred_guard_mutex 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 'cred_guard_mutex'. |
| 3 | Field lock_depth 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 'lock_depth'. |
| Change | Effect | |
|---|---|---|
| 1 | Field acct has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'acct'. |
| 2 | Field cred_commit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'cred_commit'. |
| 3 | Field inode_delete has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'inode_delete'. |
| 4 | Field key_session_to_parent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'key_session_to_parent'. |
| 5 | Field sb_check_sb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_check_sb'. |
| 6 | Field sb_post_addmount has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_post_addmount'. |
| 7 | Field sb_post_pivotroot has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_post_pivotroot'. |
| 8 | Field sb_post_remount has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_post_remount'. |
| 9 | Field sb_umount_busy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_umount_busy'. |
| 10 | Field sb_umount_close has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sb_umount_close'. |
| 11 | Field sysctl has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'sysctl'. |
| 12 | Field task_setgid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'task_setgid'. |
| 13 | Field task_setgroups has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'task_setgroups'. |
| 14 | Field task_setuid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct security_operations' has no member named 'task_setuid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field child has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct serio' has no member named 'child'. |
| Change | Effect | |
|---|---|---|
| 1 | Field _skb_dst has been renamed to _skb_refdst. | Recompilation of a client program may be broken with the error message: struct sk_buff has no member named _skb_dst. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_rmem_alloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sock' has no member named 'sk_rmem_alloc'. |
| 2 | Field sk_peercred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sock' has no member named 'sk_peercred'. |
| 3 | Field sk_sleep has been renamed to sk_wq. | Recompilation of a client program may be broken with the error message: struct sock has no member named sk_sleep. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_nulls_node has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field skc_node has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_u16hashes has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field skc_hash has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_bind_node has been renamed to skc_node. | Recompilation of a client program may be broken with the error message: anon-union-sock.h-145 has no member named skc_bind_node. |
| 2 | Field skc_portaddr_node has been renamed to skc_nulls_node. | Recompilation of a client program may be broken with the error message: anon-union-sock.h-145 has no member named skc_portaddr_node. |
| Change | Effect | |
|---|---|---|
| 1 | Field previous_state has been renamed to media_present. | Recompilation of a client program may be broken with the error message: struct scsi_cd has no member named previous_state. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'irq'. |
| 2 | Field pcmcia_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'pcmcia_state'. |
| 3 | Field resource_setup_new has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'resource_setup_new'. |
| 4 | Field resource_setup_old has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'resource_setup_old'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tid_state_rx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_ampdu_mlme' has no member named 'tid_state_rx'. |
| 2 | Field tid_state_tx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_ampdu_mlme' has no member named 'tid_state_tx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_info' has no member named 'key'. |
| 2 | Field last_noise has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sta_info' has no member named 'last_noise'. |
| Change | Effect | |
|---|---|---|
| 1 | Field shutdown has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tid_ampdu_rx' has no member named 'shutdown'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ssn has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tid_ampdu_tx' has no member named 'ssn'. |
| Change | Effect | |
|---|---|---|
| 1 | Field warning has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct stacktrace_ops' has no member named 'warning'. |
| 2 | Field warning_symbol has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct stacktrace_ops' has no member named 'warning_symbol'. |
| Change | Effect | |
|---|---|---|
| 1 | Field xpt_pool has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct svc_xprt' has no member named 'xpt_pool'. |
| Change | Effect | |
|---|---|---|
| 1 | Field used has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_header' has no member named 'used'. |
| 2 | Field count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_header' has no member named 'count'. |
| 3 | Field ctl_entry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_header' has no member named 'ctl_entry'. |
| 4 | Field ctl_table has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ctl_table_header' has no member named 'ctl_table'. |
| Change | Effect | |
|---|---|---|
| 1 | Field resume has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_class' has no member named 'resume'. |
| 2 | Field shutdown has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_class' has no member named 'shutdown'. |
| 3 | Field suspend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_class' has no member named 'suspend'. |
| Change | Effect | |
|---|---|---|
| 1 | Field resume has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_driver' has no member named 'resume'. |
| 2 | Field shutdown has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_driver' has no member named 'shutdown'. |
| 3 | Field suspend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sysdev_driver' has no member named 'suspend'. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct attribute' has no member named 'owner'. |
| Change | Effect | |
|---|---|---|
| 1 | Field index has been renamed to clockid. | Recompilation of a client program may be broken with the error message: anon-struct-thread_info.h-34 has no member named index. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle_lastupdate has been renamed to iowait_sleeptime. | Recompilation of a client program may be broken with the error message: struct tick_sched has no member named idle_lastupdate. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mmu_gather' has no member named 'nr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field state has been renamed to key. | Recompilation of a client program may be broken with the error message: struct tracepoint has no member named state. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_dma has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct us_data' has no member named 'cr_dma'. |
| 2 | Field scanning_done has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct us_data' has no member named 'scanning_done'. |
| Change | Effect | |
|---|---|---|
| 1 | Field autosuspend_delay has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'autosuspend_delay'. |
| 2 | Field autosuspend_disabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'autosuspend_disabled'. |
| 3 | Field last_busy has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'last_busy'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctl has been renamed to unlocked_ioctl. | Recompilation of a client program may be broken with the error message: struct usb_driver has no member named ioctl. |
| Change | Effect | |
|---|---|---|
| 1 | Field nents has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_sg_request' has no member named 'nents'. |
| 2 | Field sg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_sg_request' has no member named 'sg'. |
| Change | Effect | |
|---|---|---|
| 1 | Field singlethread has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct workqueue_struct' has no member named 'singlethread'. |
| 2 | Field freezeable has been renamed to work_color. | Recompilation of a client program may be broken with the error message: struct workqueue_struct has no member named freezeable. |
| 3 | Field rt has been renamed to flush_color. | Recompilation of a client program may be broken with the error message: struct workqueue_struct has no member named rt. |
| Change | Effect | |
|---|---|---|
| 1 | Field bdi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'bdi'. |
| 2 | Field no_nrwrite_index_update has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'no_nrwrite_index_update'. |
| 3 | Field sb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct writeback_control' has no member named 'sb'. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct xt_match' has no member named 'data'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bundles has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct xfrm_policy' has no member named 'bundles'. |
| Change | Effect | |
|---|---|---|
| 1 | Field find_bundle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct xfrm_policy_afinfo' has no member named 'find_bundle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field connect_timeout has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_xprt' has no member named 'connect_timeout'. |
| 2 | Field kref has been renamed to count. | Recompilation of a client program may be broken with the error message: struct rpc_xprt has no member named kref. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter root of type struct acpi_pci_root* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter device has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter targ_ns of type struct user_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl6 of type struct flowi6* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter fl has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type void const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type void const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_ns of type void const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter submit_io of type dio_submit_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fb_helper of type struct drm_fb_helper* 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 spd of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gpe_device of type struct acpi_namespace_node* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gpe_xrupt_info of type struct acpi_gpe_xrupt_info* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter gpe_device has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 7th middle parameter scope has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter flp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter inode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fentry of type struct sock_filter const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter filter has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter sb has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter path of type struct path* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter i has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mappable_end of type unsigned long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter server of type struct nfs_server const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter clp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter server of type struct nfs_server const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter clp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl4 of type struct flowi4* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter ino has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dir of type struct inode const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type void const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type struct fsnotify_mark* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter entry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ke of type struct input_keymap_entry* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter scancode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ke of type struct input_keymap_entry const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter scancode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter connector of type struct drm_connector* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter connector of type struct drm_connector* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter connector of type struct drm_connector* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl6 of type struct flowi6* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 9th middle parameter fl has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl6 of type struct flowi6* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter fl has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl4 of type struct flowi4* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl4 of type struct flowi4* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter daddr of type __be32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter saddr of type __be32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter daddr of type __be32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local of type struct ieee80211_local* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ap of type struct ata_port* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter done has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter cache_op has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter index has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter index has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rdev of type mdk_rdev_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vma of type struct vm_area_struct* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type struct zone* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter op of type struct open_flags const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter open_flag has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter vmalloced has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter vmalloced has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter mnt_parent has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter clnt of type struct rpc_clnt* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter arg of type struct nfs4_setclientid_res* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter endian of type enum utf16_endian has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type u32* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter head of type struct hlist_head* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter event_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter task of type struct task_struct* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter of type struct ring_buffer_iter* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter buffer has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flp4 of type struct flowi4* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter rp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flp4 of type struct flowi4* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter rp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter flp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter skb of type struct sk_buff* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter daddr of type __be32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct user_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct user_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct user_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter p of type struct task_struct* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter objname of type char const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx_flags of type __u8* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter msg has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter tty has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter regs of type struct pt_regs* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pairwise of type bool has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct ipc_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct ipc_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field thread_id has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field thread_id has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field handler has been changed from struct acpi_handler_info to struct acpi_gpe_handler_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field thread_id has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field hashtable has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field filename became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct linux_binprm::filename'. |
| 2 | Field interp became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct linux_binprm::interp'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field queue_lock has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash has been changed from struct list_head to struct hlist_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct clocksource::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field io has been changed from io_req_t to struct resource[2] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field d_count has been changed from struct atomic_t to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field p has been changed from struct bus_type_private to struct subsys_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field p has been changed from struct class_private to struct subsys_private of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field type became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct device::type'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field irq has been changed from irq_req_t to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_table became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct pcmcia_driver::id_table'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field metrics has been changed from u32[14] to unsigned long of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_xattr became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct super_block::s_xattr'. |
| 2 | The pointer level of field s_files has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field event has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field bandwidth_mutex has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field slave_dig_outs became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct hda_codec::slave_dig_outs'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field label has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dac_nids became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct hda_multi_out::dac_nids'. |
| 2 | Field slave_dig_outs became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct hda_multi_out::slave_dig_outs'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field node has been changed from struct rb_node to struct timerqueue_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field active has been changed from struct rb_root to struct timerqueue_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cur_obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field pwrctx has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field ring has been changed from drm_i915_ring_buffer_t to struct intel_ring_buffer[3] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field mc_list has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field addr_list has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field old_fb_obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of field pending_flip_obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cursor_bo has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field base has been changed from struct drm_connector to struct drm_encoder of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field opt has been changed from struct ip_options to struct ip_options_rcu of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field fib_metrics has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field om_rtt has been changed from unsigned long long to ktime_t of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field om_execute has been changed from unsigned long long to ktime_t of different format. | Recompilation of a client program may be broken. |
| 3 | Type of field om_queue has been changed from unsigned long long to ktime_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field trace_events has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field owner has been changed from struct thread_info to struct task_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this type has been changed from struct to union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field ls_owner has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | Type of field ls_stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field open_stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field delegation has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field param became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct param_attribute::param'. |
| 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 pci_driver::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field period_left has been changed from struct atomic64_t to struct local64_t of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field prev_count has been changed from struct atomic64_t to struct local64_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field count has been changed from struct atomic64_t to struct local64_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field bufs has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field sym_val_to_name has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dynticks has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field rda has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tk_start has been changed from unsigned long to ktime_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field description became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct serio_driver::description'. |
| 2 | Field id_table became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct serio_driver::id_table'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sk_dst_lock has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct thermal_cooling_device::ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct thermal_zone_device::ops'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field preds has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field funcs has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tracepoint became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct tracepoint_iter::tracepoint'. |
| 2 | The pointer level of field tracepoint has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field work has been changed from struct delayed_work to struct work_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sg has been changed from struct usb_sg_request to struct scatterlist of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field ss_ep_comp has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field cpu_wq has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field prefix became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct xattr_handler::prefix'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rq_xtime has been changed from unsigned long to ktime_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct acpi_internal_rsdt to struct acpi_table_list of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter domain has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 3rd parameter busnum has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter align of type size_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter min_dump_alloc of type u16 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter timeout of type u16 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter initiator has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter list of type struct list_head** has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter list has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter watch has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter kill_dirty of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter holder of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter fsdata has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cps of type struct cb_process_state* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cps of type struct cb_process_state* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter info of type struct partition_meta_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter policy has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 3rd parameter lp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dontfrag of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dst has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter validate_stateid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter storage of type struct rtnl_link_stats64* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter buffer has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 3rd parameter len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 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 2nd parameter name has been changed from char const* to u32 (became non-const). | Recompilation of a client program may be broken. |
| 2 | The pointer level of 1st parameter features has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 2nd parameter name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter alen has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th parameter glbl has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter gfp_mask has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 1st parameter nr_to_scan has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter num_pages has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nr_pages has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 2nd parameter result has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 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 integrity of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter reserve has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fb has been changed from struct drm_framebuffer to struct drm_fb_helper of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fb_create has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter kref has been changed from struct kref to struct drm_gem_object 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 dev of type struct net_device* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter initial_ref of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter initial_obsolete of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 4 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dplx of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pa_data has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter force_poll has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter regs has been changed from struct err_regs to struct mce of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter plug has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter plug has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter supported of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ignored of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter thread_id has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter spec_dst has been changed from unsigned int to struct net_device of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 5th parameter dev has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 8th parameter mark has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 4 | The pointer level of 1st parameter src has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fib_flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter flp has been changed from struct flowi to struct flowi4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter flp has been changed from struct flowi to struct flowi4 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flen has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ctx of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter devname of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter devname of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter spdif_ctls of type unsigned short has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter tsk has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter probe of type int(*)(struct i2c_adapter*, unsigned short) has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct intel_ring_buffer of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 3rd parameter flush_domains has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter align of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object 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 map_and_fenceable of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pipelined of type struct intel_ring_buffer* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter resume has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buflen of type size_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter clp has been changed from struct nfs_client to struct nfs_server of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter clp has been changed from struct nfs_client to struct nfs_server of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buflen of type size_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter ipfragok has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter daddr has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tsk has been changed from struct task_struct to struct mm_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter task has been changed from struct task_struct to struct mm_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter inf has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter fs_dir_inode_ops has been changed from struct inode_operations const* to int (became non-const). | Recompilation of a client program may be broken. |
| 2 | The pointer level of 4th parameter fs_dir_inode_ops has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 5th parameter isvfat has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter kill_dirty of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mnt of type struct vfsmount* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter allow_dups of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter entry has been changed from struct fsnotify_mark_entry to struct fsnotify_mark of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter entry has been changed from struct fsnotify_mark_entry to struct fsnotify_mark of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter entry has been changed from struct fsnotify_mark_entry to struct fsnotify_mark of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter entry has been changed from struct fsnotify_mark_entry to struct fsnotify_mark of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter keycode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter keycode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter old of type struct intel_load_detect_pipe* has been added to 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 | Base type of parameter obj has been changed from struct drm_gem_object to struct drm_i915_gem_object of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter old of type struct intel_load_detect_pipe* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pipe of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter adapter of type struct i2c_adapter* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ddc_bus of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter response has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dontfrag of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter ipfragok has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter optp has been changed from struct ip_options to struct ip_options_rcu of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter optp has been changed from struct ip_options to struct ip_options_rcu of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter opt has been changed from struct ip_options to struct ip_options_rcu of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl4 of type struct flowi4* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter ipfragok has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uni of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter multi of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter _prealloc of type unsigned long* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | 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 no_state_check of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter cmd has been changed from struct scsi_cmnd to struct Scsi_Host of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter done has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u8 (1 byte) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mask of type struct cpumask* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter entry_size has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th parameter indexes_count has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter keys has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter thread has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter metadata_op of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter tlbp has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter step of type enum mpol_rebind_step has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sc of type struct scan_control* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter nr_anon of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter nr_file of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 4 | Parameter page_list of type struct list_head* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 5 | 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 local_state_change of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter local_state_change of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter timestamp of type u64 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sock of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter irq has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter acc_mode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter ns has been changed from struct ipc_namespace to struct task_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter base has been changed from char const* to char** (became non-const). | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter droot has been changed from struct dentry const* to struct dentry* (became non-const). | Recompilation of a client program may be broken. |
| 3 | Base type of parameter dentry has been changed from struct dentry to char of different format. | Recompilation of a client program may be broken. |
| 4 | The pointer level of 1st parameter base has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 5 | The pointer level of 4th parameter buffer has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter p has been changed from unsigned int to struct xdr_stream of different format. | 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 roc of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter stateid has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter res of type struct nfs4_setclientid_res* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fl_pid of type pid_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter dst has been changed from struct nfs4_stateid to union nfs4_stateid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp_mask of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter p has been changed from unsigned int to struct xdr_stream of different format. | 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 root_device of type char** has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter root_data of type char** has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | 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 maxlen of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter merge of type struct fsnotify_event*(*)(struct list_head*, struct fsnotify_event*) has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | The pointer level of return value has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter start_pfn has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 2nd parameter last_pfn has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd parameter acpi has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 4th parameter k8 has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dentry has been changed from struct dentry to struct path of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter info of type struct backing_dev_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter req of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter req has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 2nd parameter wh has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter wh has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter req has been changed from struct win_req_t to struct resource of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 3rd parameter wh has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter pid has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter curr has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rctx of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mii_data has been changed from struct mii_ioctl_data to struct ifreq of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wowlan of type struct cfg80211_wowlan* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter state of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lost_events of type unsigned long* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lost_events of type unsigned long* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from struct ring_buffer_iter* (8 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter flp 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 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter fl has been changed from struct flowi to struct flowi6 of different format. | 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. |
| 2 | 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 net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter calcit of type rtnl_calcit_func has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter calcit of type rtnl_calcit_func has been added to the calling stack. | 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 | Parameter chan of type struct ieee80211_channel* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ticks of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter owner has been changed from struct thread_info to struct task_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clone_flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter clone_flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bootmem has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cred of type struct cred const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter from_file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter policy has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 3rd parameter lp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter other has been changed from struct socket to struct sock of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter sock has been changed from struct socket to struct sock of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter count has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter count has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter shtx has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter bdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter xprt_list has been changed from struct list_head to struct svc_serv of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ecn_ok of type bool* 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 | 2nd parameter tty has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sock has been changed from struct socket to struct sock of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sock has been changed from struct socket to struct sock of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter boot of type ktime_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter oops_dump_mode of type enum ftrace_dump_mode has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter rctxp has been changed from int to struct pt_regs of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct trace_event* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter begin has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 3rd parameter end has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 1st parameter tracepoint has been increased from 2 to 3. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter begin has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 2nd parameter end has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tsk of type struct task_struct* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter error_code of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter trapnr of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter has_80211_header of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rate_mask of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter channel of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter band of type enum ieee80211_band has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter forsdata has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter old_ns has been changed from struct uts_namespace to struct task_struct of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter gfp_mask has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter scanned has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter classzone_idx of type enum zone_type has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mode of type enum migrate_mode 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 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qstr of type struct qstr const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter dst_p has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| 2 | The pointer level of return value has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gpe_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field initialized has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field thread_id has been changed from struct task_struct* to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field thread_id has been changed from struct task_struct* to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field scope_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field thread_id has been changed from struct task_struct* to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field states has been changed from struct acpi_device_power_state[4] to struct acpi_device_power_state[5]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field secondary has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcfc_rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tlp has been changed from struct header_log_regs to struct aer_header_log_regs. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cpuid has been changed from u8 to u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field features has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field stored_addr_hi has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field stored_addr_lo has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field stored_l1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field stored_l2 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hashbits has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field hashtable has been changed from struct hlist_head[16] to struct hlist_head*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field crunwrap_resp has been changed from int(*)(struct rpc_task*, kxdrproc_t, void*, __be32*, void*) to int(*)(struct rpc_task*, kxdrdproc_t, void*, __be32*, void*). | Recompilation of a client program may be broken. |
| 2 | Base type of field crbind has been changed from void(*)(struct rpc_task*, struct rpc_cred*, int) to struct rpc_cred*(*)(struct rpc_task*, struct rpc_cred*, int). | Recompilation of a client program may be broken. |
| 3 | Base type of field crwrap_req has been changed from int(*)(struct rpc_task*, kxdrproc_t, void*, __be32*, void*) to int(*)(struct rpc_task*, kxdreproc_t, void*, __be32*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field laptop_mode_wb_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakeup_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field last_active has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_nb has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field revision has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field behind_writes_used has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field logattrs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field check_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field swap_slot_free_notify has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_integrity_segments has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field discard_zeroes_data has been changed from signed char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field part has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_pending_since has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flush_rq has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field flush_data_in_flight has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field flush_pending_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field delay_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field flush_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field flush_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field flush_not_queueable has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field flush_queue_delayed has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Type of field queue_lock has been changed from spinlock_t* to spinlock_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field olpc_ofw_header has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field thread_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ioctl_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vfs_events has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field check_events has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field control_port_ethertype has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field control_port_no_encrypt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_state_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field basic_rates has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mcast_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_antenna has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_ringparam has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field join_mesh has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field leave_mesh has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mgmt_frame_register has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field mgmt_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field mgmt_tx_cancel_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field sched_scan_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field sched_scan_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field set_antenna has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field set_cqm_rssi_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field set_ringparam has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Base type of field add_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*, struct key_params*) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*, struct key_params*). | Recompilation of a client program may be broken. |
| 14 | Base type of field add_virtual_intf has been changed from int(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*) to struct net_device*(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*). | Recompilation of a client program may be broken. |
| 15 | Base type of field del_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*). | Recompilation of a client program may be broken. |
| 16 | Base type of field get_key has been changed from int(*)(struct wiphy*, struct net_device*, u8, u8 const*, void*, void(*)(void*, struct key_params*)) to int(*)(struct wiphy*, struct net_device*, u8, bool, u8 const*, void*, void(*)(void*, struct key_params*)). | Recompilation of a client program may be broken. |
| 17 | Base type of field set_channel has been changed from int(*)(struct wiphy*, struct ieee80211_channel*, enum nl80211_channel_type) to int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, enum nl80211_channel_type). | Recompilation of a client program may be broken. |
| 18 | Base type of field set_default_key has been changed from int(*)(struct wiphy*, struct net_device*, u8) to int(*)(struct wiphy*, struct net_device*, u8, bool, bool). | Recompilation of a client program may be broken. |
| 19 | Base type of field set_tx_power has been changed from int(*)(struct wiphy*, enum tx_power_setting, int) to int(*)(struct wiphy*, enum nl80211_tx_power_setting, int). | Recompilation of a client program may be broken. |
| 20 | Base type of field set_wds_peer has been changed from int(*)(struct wiphy*, struct net_device*, u8*) to int(*)(struct wiphy*, struct net_device*, u8 const*). | Recompilation of a client program may be broken. |
| 21 | Base type of field suspend has been changed from int(*)(struct wiphy*) to int(*)(struct wiphy*, struct cfg80211_wowlan*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bss_param has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field connected_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rx_dropped_misc has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rxrate has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field signal_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field tx_failed has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tx_retries has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field iface_combinations has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_remain_on_channel_duration has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field available_antennas_rx has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field n_iface_combinations has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field software_iftypes has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field available_antennas_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field mgmt_stypes has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field wowlan has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beacon_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mesh_id_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mesh_id_up_len 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 unregister_event has been changed from int(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*) to void(*)(struct cgroup*, struct cftype*, struct eventfd_ctx*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field can_attach_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pre_attach has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Base type of field attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*, bool) to void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*). | Recompilation of a client program may be broken. |
| 5 | Base type of field can_attach has been changed from int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*, bool) to int(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*). | Recompilation of a client program may be broken. |
| 6 | Base type of field cancel_attach has been changed from void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*, bool) to void(*)(struct cgroup_subsys*, struct cgroup*, struct task_struct*). | Recompilation of a client program may be broken. |
| 7 | Base type of field exit has been changed from void(*)(struct cgroup_subsys*, struct task_struct*) to void(*)(struct cgroup_subsys*, struct cgroup*, struct cgroup*, struct task_struct*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field info has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_beyond_eod has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pp_buf 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 | Base type of field p_decode has been changed from int(*)(void*, __be32*, void*) to int(*)(void*, struct xdr_stream*, void*). | Recompilation of a client program may be broken. |
| 2 | Base type of field p_encode has been changed from int(*)(void*, __be32*, void*) to void(*)(void*, struct xdr_stream*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_delta_ticks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field min_delta_ticks has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_tstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tstamp_sysctl_header has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field con_debug_enter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field con_debug_leave has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field port has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vc_panic_force_write has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sched_scan_mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sched_scan_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sched_scan_results_wk has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field wowlan has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field refcount 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 suspend has been changed from int(*)(struct cpufreq_policy*, pm_message_t) to int(*)(struct cpufreq_policy*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field power_specified has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mem 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 find_io has been changed from struct resource*(*)(unsigned long, int, unsigned long, struct pcmcia_socket*) to int(*)(struct pcmcia_socket*, unsigned int, unsigned int*, unsigned int, unsigned int, struct resource**). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field remove has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from u_char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field d_hash has been changed from struct hlist_node to struct hlist_bl_node. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_automount has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field d_manage has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field d_hash has been changed from int(*)(struct dentry*, struct qstr*) to int(*)(struct dentry const*, struct inode const*, struct qstr*). | Recompilation of a client program may be broken. |
| 4 | Base type of field d_delete has been changed from int(*)(struct dentry*) to int(*)(struct dentry const*). | Recompilation of a client program may be broken. |
| 5 | Base type of field d_compare has been changed from int(*)(struct dentry*, struct qstr*, struct qstr*) to int(*)(struct dentry const*, struct inode const*, struct dentry const*, struct inode const*, unsigned int, char const*, struct qstr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field discards_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field num_discard_requests has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_bin_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field namespace has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ns_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field of_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pwr_domain has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field of_match_table has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field discards_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field integrity_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field target_callbacks has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_bio has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field type_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field null_edid_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field polled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field detect has been changed from enum drm_connector_status(*)(struct drm_connector*) to enum drm_connector_status(*)(struct drm_connector*, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field framedur_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hwmode has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field linedur_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pixeldur_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field gamma_set has been changed from void(*)(struct drm_crtc*, u16*, u16*, u16*, uint32_t) to void(*)(struct drm_crtc*, u16*, u16*, u16*, uint32_t, uint32_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field color_formats has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field dirty has been changed from int(*)(struct drm_framebuffer*, unsigned int, unsigned int, struct drm_clip_rect*, unsigned int) to int(*)(struct drm_framebuffer*, struct drm_file*, unsigned int, unsigned int, struct drm_clip_rect*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_poll_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field poll_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field timings has been changed from struct std_timing[5] to struct std_timing[6]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field order has been changed from unsigned int to u8. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field head_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prev_scanned_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field scan_alignment has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field scan_check_range has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field scan_end has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field scan_hit_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field scan_hit_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field scan_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field scan_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field scanned_blocks has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allocated has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field scanned_block has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field scanned_next_free has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field scanned_preceeds_hole has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field scanned_prev_free has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _vblank_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field platformdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field usbdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field vblank_time_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dumb_destroy has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dumb_map_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field get_scanout_position has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_vblank_timestamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field kdriver has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cmd_drv has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field card_addr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field config_base has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field config_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field config_index has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field config_regs has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field io_lines has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field resource has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field vpp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_mtu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cow_metrics has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pcpuc_entries has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field default_advmss has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fifo_stall_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field phy_info_task has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bytecount has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field segs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field elevator_bio_merged_fn has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_dump_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_dump has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field get_dump_flag has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field set_rxfh_indir has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_channels has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field set_channels has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field get_rxfh_indir has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ratelimit has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_debug_enter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fb_debug_leave has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field save_graphics has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpf_func has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field u has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct net*, struct flowi*, u16, u8, void**, atomic_t**) to struct flow_cache_object*(*)(struct net*, struct flowi const*, u16, u8, struct flow_cache_object*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_mmap_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field freepage has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field migratepage has been changed from int(*)(struct address_space*, struct page*, struct page*) to int(*)(struct address_space*, struct page*, struct page*, enum migrate_mode). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bd_holder_disks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bd_write_holder has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field bd_claiming has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fa_rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_sb_list_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field f_tfile_llink has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fallocate has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field fsync has been changed from int(*)(struct file*, struct dentry*, int) to int(*)(struct file*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_vfs_rename_key has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field max_files has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of field nr_files has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 3 | Type of field nr_free_files has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_fsnotify_marks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field i_lru has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field i_wb_list 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 check_acl has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, int, unsigned int). | Recompilation of a client program may be broken. |
| 2 | Base type of field permission has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, int, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleancache_poolid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field s_uuid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field s_d_op has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field s_anon has been changed from struct hlist_head to struct hlist_bl_head. | Recompilation of a client program may be broken. |
| 5 | Type of field s_files has been changed from struct list_head to struct list_head*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field show_devname has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field show_path has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field drop_inode has been changed from void(*)(struct inode*) to int(*)(struct inode*). | Recompilation of a client program may be broken. |
| 4 | Base type of field dirty_inode has been changed from void(*)(struct inode*) to void(*)(struct inode*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(struct kiocb*, loff_t, ssize_t, void*) to void()(struct kiocb*, loff_t, ssize_t, void*, int, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tgid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field file_name has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field marks_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field priority 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 freeing_mark has been changed from void(*)(struct fsnotify_mark_entry*, struct fsnotify_group*) to void(*)(struct fsnotify_mark*, struct fsnotify_group*). | Recompilation of a client program may be broken. |
| 2 | Base type of field handle_event has been changed from int(*)(struct fsnotify_group*, struct fsnotify_event*) to int(*)(struct fsnotify_group*, struct fsnotify_mark*, struct fsnotify_mark*, struct fsnotify_event*). | Recompilation of a client program may be broken. |
| 3 | Base type of field should_send_event has been changed from bool(*)(struct fsnotify_group*, struct inode*, __u32) to bool(*)(struct fsnotify_group*, struct inode*, struct fsnotify_mark*, struct fsnotify_mark*, __u32, void*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field class has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field event has been changed from struct trace_event* to struct trace_event. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lost_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tmp_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field post_doit has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pre_doit has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ptr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field events has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field async_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field info 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. |
| 3 | Type of field in_flight has been changed from int[2] to atomic_t[2]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gm_upcall_enctypes 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 gss_import_sec_context has been changed from int(*)(void const*, size_t, struct gss_ctx*) to int(*)(void const*, size_t, struct gss_ctx*, gfp_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_streams has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field free_streams has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field map_urb_for_dma has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field unmap_urb_for_dma has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field update_device has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Base type of field pci_suspend has been changed from int(*)(struct usb_hcd*) to int(*)(struct usb_hcd*, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field primary_hcd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field shared_hcd has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field speed has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field bandwidth_mutex has been changed from struct mutex to struct mutex*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field prepare_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field afg_function_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field afg_unsol has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field conn_lists has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cvt_setups has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mfg_function_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field mfg_unsol has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field no_sticky_stream has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inputs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field num_inputs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field label has been changed from char const* to char[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hid_get_raw_report has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field feature_mapping has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field reset_resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Base type of field report_fixup has been changed from void(*)(struct hid_device*, __u8*, unsigned int) to __u8*(*)(struct hid_device*, __u8*, unsigned int*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field field has been changed from struct hid_field*[64] to struct hid_field*[128]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field clockid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_bases has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field clock_base has been changed from struct hrtimer_clock_base[2] to struct hrtimer_clock_base[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field userspace_clients_lock 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 mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unmask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field deferred_free_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gtt has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gtt_end has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field gtt_mappable_end has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field gtt_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field gtt_total has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field inactive_shrinker has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field interruptible has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field mappable_gtt_total has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field object_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field object_memory has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field pinned_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field stolen has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_mode_set has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fdi_link_train has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field init_clock_gating has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field init_pch_clock_gating has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field queue_flip has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Base type of field fbc_enabled has been changed from bool(*)(struct drm_crtc*) to bool(*)(struct drm_device*). | Recompilation of a client program may be broken. |
| 7 | Base type of field update_wm has been changed from void(*)(struct drm_device*, int, int, int, int) to void(*)(struct drm_device*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache_level has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field size has been changed from size_t to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bcs_acthd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bcs_instdone has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field bcs_ipehr has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field bcs_ipeir has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field bcs_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field display has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field error has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field fence has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field overlay has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field pinned_bo has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field pinned_bo_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field pipestat has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field vcs_acthd has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field vcs_instdone has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field vcs_ipehr has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field vcs_ipeir has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field vcs_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Base type of field ringbuffer has been changed from struct drm_i915_error_object to struct drm_i915_error_object*. | Recompilation of a client program may be broken. |
| 19 | Type of field batchbuffer has been changed from struct drm_i915_error_object*[2] to struct drm_i915_error_object*[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field setup_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache_level has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fenced_gpu_access has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ring_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field base has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field exec_handle has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field last_fenced_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field map_and_fenceable has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field sg_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field exec_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field exec_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field exec_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field fault_mappable has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field last_fenced_ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field pin_mappable has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field tiling_changed has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Base type of field bit_17 has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field backlight_level has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field broadcast_rgb_property has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field c_m has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cfb_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field cfb_y has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field chipset_power has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field corr has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field edp has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field error_completion has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field fbdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field fmax has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field force_audio_property has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field forcewake_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field fstart has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field gfx_power has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field gmbus has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field gt_irq_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field irq_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field irq_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field is_ddr3 has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field last_acthd_blt has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field last_acthd_bsd has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field last_count1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Field last_count2 has been added to this type. | This field will not be initialized or used by old client applications. |
| 26 | Field last_gpu_reset has been added to this type. | This field will not be initialized or used by old client applications. |
| 27 | Field last_instdone has been added to this type. | This field will not be initialized or used by old client applications. |
| 28 | Field last_instdone1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 29 | Field last_time1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 30 | Field last_time2 has been added to this type. | This field will not be initialized or used by old client applications. |
| 31 | Field mchdev_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 32 | Field next_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 33 | Field no_aux_handshake has been added to this type. | This field will not be initialized or used by old client applications. |
| 34 | Field num_pipe has been added to this type. | This field will not be initialized or used by old client applications. |
| 35 | Field panel_t12 has been added to this type. | This field will not be initialized or used by old client applications. |
| 36 | Field panel_t3 has been added to this type. | This field will not be initialized or used by old client applications. |
| 37 | Field pch_pf_pos has been added to this type. | This field will not be initialized or used by old client applications. |
| 38 | Field pch_pf_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 39 | Field pch_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 40 | Field pm_iir has been added to this type. | This field will not be initialized or used by old client applications. |
| 41 | Field quirks has been added to this type. | This field will not be initialized or used by old client applications. |
| 42 | Field r_t has been added to this type. | This field will not be initialized or used by old client applications. |
| 43 | Field relative_constants_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 44 | Field renderctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 45 | Field rps_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 46 | Field rps_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 47 | Field savePCH_PORT_HOTPLUG has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gen has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field has_blt_ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field has_bsd_ring has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field has_overlay has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field is_broadwater has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field is_crestline has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field is_ivybridge has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field overlay_needs_physical has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field supports_tv has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lid_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vbt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ddc_pin has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field i2c_pin has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field i2c_speed has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_bc_mc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 ave_beacon_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beacon_connection_loss_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field beacon_crc_valid has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field beacon_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field broken_ap has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field count_beacon_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field driver_smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field last_beacon_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field last_cqm_event_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field nullfunc_failed has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field request_smps_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field agg_queue_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field disable_dynamic_ps has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dynamic_ps_forced_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field dynamic_ps_user_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field fif_probe_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field hw_offchan_tx_cookie has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field hw_roc_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field hw_roc_channel_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field hw_roc_cookie has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field hw_roc_dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field hw_roc_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field hw_roc_duration has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field hw_roc_for_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field hw_roc_skb has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field hw_roc_skb_for_status has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field hw_roc_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field ifa_notifier has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field key_mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field leave_oper_channel_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field napi has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field napi_dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field probe_req_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field running_rx_handler has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Field rx_skb_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 26 | Field sched_scan_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| 27 | Field sched_scan_stopped_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 28 | Field sched_scanning has been added to this type. | This field will not be initialized or used by old client applications. |
| 29 | Field tpt_led_trigger has been added to this type. | This field will not be initialized or used by old client applications. |
| 30 | Field wiphy_ciphers_allocated has been added to this type. | This field will not be initialized or used by old client applications. |
| 31 | Field wowlan has been added to this type. | This field will not be initialized or used by old client applications. |
| 32 | Base type of field wep_rx_tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| 33 | Base type of field wep_tx_tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| 34 | Type of field mc_list has been changed from struct dev_addr_list* to struct netdev_hw_addr_list. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_filter_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field control_port_no_encrypt has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field control_port_protocol has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field default_multicast_key has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field default_unicast_key has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field old_idle has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field skb_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field state has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field addr_list has been changed from struct inet6_ifaddr* to struct list_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr_lst has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field if_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field state has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field state_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icmpv6msgdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field icmpv6dev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field icsk_user_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field queue_xmit has been changed from int(*)(struct sk_buff*, int) to int(*)(struct sk_buff*, struct flowi*). | Recompilation of a client program may be broken. |
| 2 | Base type of field send_check has been changed from void(*)(struct sock*, int, struct sk_buff*) to void(*)(struct sock*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fragments_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field base has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inet_opt has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nodefrag has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nexthop has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field daddr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field read has been changed from long(*)(struct snd_info_entry*, void*, struct file*, char*, unsigned long, unsigned long) to ssize_t(*)(struct snd_info_entry*, void*, struct file*, char*, size_t, loff_t). | Recompilation of a client program may be broken. |
| 2 | Base type of field write has been changed from long(*)(struct snd_info_entry*, void*, struct file*, char const*, unsigned long, unsigned long) to ssize_t(*)(struct snd_info_entry*, void*, struct file*, char const*, size_t, loff_t). | Recompilation of a client program may be broken. |
| 3 | Base type of field llseek has been changed from long long(*)(struct snd_info_entry*, void*, struct file*, long long, int) to loff_t(*)(struct snd_info_entry*, void*, struct file*, loff_t, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field absinfo has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hint_events_per_packet has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mt has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mtsize has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field propbit has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field slot has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field trkid has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Base type of field getkeycode has been changed from int(*)(struct input_dev*, unsigned int, unsigned int*) to int(*)(struct input_dev*, struct input_keymap_entry*). | Recompilation of a client program may be broken. |
| 9 | Base type of field setkeycode has been changed from int(*)(struct input_dev*, unsigned int, unsigned int) to int(*)(struct input_dev*, struct input_keymap_entry const*, unsigned int*). | Recompilation of a client program may be broken. |
| 10 | Type of field sync has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field iommu_superpage has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field i2c_speed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rsvd has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field enable_stall_check has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cursor_visible 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field flip_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field thread_mask 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 map has been changed from int(*)(struct iommu_domain*, unsigned long, phys_addr_t, size_t, int) to int(*)(struct iommu_domain*, unsigned long, phys_addr_t, int, int). | Recompilation of a client program may be broken. |
| 2 | Base type of field unmap has been changed from void(*)(struct iommu_domain*, unsigned long, size_t) to int(*)(struct iommu_domain*, unsigned long, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field events has been changed from unsigned long[25] to unsigned long[27]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_prefsrc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt6i_peer has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dst has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rt6i_prefsrc has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rt6i_peer_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from struct rt6_info*(*)(struct net*, struct fib6_table*, struct flowi*, int) to struct rt6_info*(*)(struct net*, struct fib6_table*, struct flowi6*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fib_scope has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field fib_dead has been changed from int to unsigned char. | Recompilation of a client program may be broken. |
| 4 | Type of field fib_metrics has been changed from u32[14] to u32*. | Recompilation of a client program may be broken. |
| 5 | Type of field fib_protocol has been changed from int to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nh_saddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nh_saddr_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field table has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tb_num_default has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field tb_data has been changed from unsigned char[] to unsigned long[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field shm_tot has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_ping_group_range has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dev_addr_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rxorigdstaddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rxpmtu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field nhoff has been changed from __u32 to __u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dontfrag has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field min_hopcount has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rxpmtu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field irq_pm_shutdown has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field irq_print_chip has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field irq_resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field irq_suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field affinity_hint has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field affinity_notify has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field core_internal_state__do_not_mess_with_it has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field irq_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field status_use_accessors has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field b_cow_tid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irqs_sum has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vet_description has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field init has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field cleanup has been changed from void(*)(char**, char**) to void(*)(struct subprocess_info*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field namespace has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field child_ns_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field blink_brightness has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field blink_delay_off has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field blink_delay_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field blink_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tdev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eh_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field eh_owner has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lpm_policy has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tdev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bmdma_prd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field bmdma_prd_dma has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field scsi_scan_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sff_pio_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field sff_pio_task_link has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field target_lpm_policy has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tdev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sff_drain_fifo has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sff_set_devctl has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field sff_irq_on has been changed from u8(*)(struct ata_port*) to void(*)(struct ata_port*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_srcaddrlen has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field auditdeny has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_addr_cnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field arp_addr_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field arp_filter_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field channel_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cqm_rssi_hyst has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field cqm_rssi_thold has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ibss_joined has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field idle has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field mcast_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field qos has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_report_rates has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_rx_aggregation_subframes has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field max_tx_aggregation_subframes has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field napi_weight has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cancel_remain_on_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field change_interface has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field channel_switch has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field get_antenna has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_ringparam has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field get_survey has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field napi_poll has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field offchannel_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field offchannel_tx_cancel_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field remain_on_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field sched_scan_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field sched_scan_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field set_antenna has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field set_bitrate_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field set_frag_threshold has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field set_ringparam has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field tx_frames_pending has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Base type of field ampdu_action has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_ampdu_mlme_action, struct ieee80211_sta*, u16, u16*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_ampdu_mlme_action, struct ieee80211_sta*, u16, u16*, u8). | Recompilation of a client program may be broken. |
| 21 | Base type of field hw_scan has been changed from int(*)(struct ieee80211_hw*, struct cfg80211_scan_request*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct cfg80211_scan_request*). | Recompilation of a client program may be broken. |
| 22 | Base type of field prepare_multicast has been changed from u64(*)(struct ieee80211_hw*, int, struct dev_addr_list*) to u64(*)(struct ieee80211_hw*, struct netdev_hw_addr_list*). | Recompilation of a client program may be broken. |
| 23 | Base type of field tx has been changed from int(*)(struct ieee80211_hw*, struct sk_buff*) to void(*)(struct ieee80211_hw*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_max_entries has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_index has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field log has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bio_set has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field can_decrease_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field event_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field plug_cnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ready has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field sync_super 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 make_request has been changed from int(*)(struct request_queue*, struct bio*) to int(*)(mddev_t*, struct bio*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field meta_bdev has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field new_raid_disk has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field shrink has been changed from int(*)(int, gfp_t) to int(*)(struct shrinker*, struct shrink_control*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field oom_disable_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ia32_compat has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat_diff has been changed from s8[29] to s8[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field classzone_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field vm_stat has been changed from atomic_long_t[29] to atomic_long_t[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field source_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tracepoints_ptrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field core_ro_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field target_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field init_ro_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Type of field trace_events has been changed from struct ftrace_event_call* to struct ftrace_event_call**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_fsnotify_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mnt_pcp has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mnt_fsnotify_marks has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mnt_longterm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mask has been changed from unsigned long[4] to unsigned long[512]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field inode has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hash has been changed from __u32(*)(void const*, struct net_device const*) to __u32(*)(void const*, struct net_device const*, __u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ha_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field passive has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ipvs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ingress_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prio_tc_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rx_handler has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rx_handler_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field wanted_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field _rx has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field gso_max_segs has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field real_num_rx_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field rx_cpu_rmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field num_rx_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field queues_kset has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field addr_assign_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field dismantle has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field tc_to_txq has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field hw_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field mc has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field rx_dropped has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field group has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field num_tc has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field pcpu_refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field phydev has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field pm_qos_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Type of field ip_ptr has been changed from void* to struct in_device*. | Recompilation of a client program may be broken. |
| 24 | Type of field vlan_features has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| 25 | Type of field dn_ptr has been changed from void* to struct dn_dev*. | Recompilation of a client program may be broken. |
| 26 | Type of field features has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| 27 | Type of field ip6_ptr has been changed from void* to struct inet6_dev*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_set_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_add_slave has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ndo_get_vf_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ndo_setup_tc has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ndo_set_vf_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ndo_fix_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ndo_netpoll_cleanup has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field ndo_del_slave has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field ndo_get_stats64 has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field ndo_netpoll_setup has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field ndo_rx_flow_steer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field numa_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field kobj has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cpu_collision has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field csd has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field dropped has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field input_queue_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field input_queue_tail has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field output_queue_tailp has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field process_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field processed has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field received_rps has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field rps_ipi_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field rps_ipi_next has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field time_squeeze 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 route has been changed from int(*)(struct dst_entry**, struct flowi*) to int(*)(struct net*, struct dst_entry**, struct flowi*, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field min_dump_alloc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field family has been changed from int to u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field netpoll has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field search_restart has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[5] to u8[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field unique_tuple has been changed from bool(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*) to void(*)(struct nf_conntrack_tuple*, struct nf_nat_range const*, enum nf_nat_manip_type, struct nf_conn const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ls_owner has been changed from fl_owner_t to struct nfs4_lock_owner. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_server_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field commits_outstanding has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field layout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_context has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_cb_ident has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cl_exchange_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cl_layouts has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cl_mvops has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cl_seqid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field delegations has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lockowner_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field openowner_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pnfs_curr_ld has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field roc_rpcwaitq has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field state_owners has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field time_delta has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_lock_context has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_lseg has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pg_moreio has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pg_test has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Base type of field pg_doio has been changed from int(*)(struct inode*, struct list_head*, unsigned int, size_t, int) to int(*)(struct nfs_pageio_descriptor*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_slot has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field server has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mounted_on_fileid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ds_clp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lseg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mds_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mds_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field pnfs_error has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field read_done_cb has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_context has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field file_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field init_client has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field open_context has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rename_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rename_setup has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field secinfo has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, struct iattr*, int, struct nameidata*) to int(*)(struct inode*, struct dentry*, struct iattr*, int, struct nfs_open_context*). | Recompilation of a client program may be broken. |
| 8 | Base type of field decode_dirent has been changed from __be32*(*)(__be32*, struct nfs_entry*, int) to int(*)(struct xdr_stream*, struct nfs_entry*, int). | Recompilation of a client program may be broken. |
| 9 | Base type of field lookup has been changed from int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct rpc_clnt*, struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*). | Recompilation of a client program may be broken. |
| 10 | Base type of field readdir has been changed from int(*)(struct dentry*, struct rpc_cred*, u64, struct page*, unsigned int, int) to int(*)(struct dentry*, struct rpc_cred*, u64, struct page**, unsigned int, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ds_clp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ds_commit_index has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field lseg has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mds_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mds_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field pnfs_error has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field write_done_cb has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_context has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field __aer_firmware_first_valid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ats has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fw_addr has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field link_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mmio_always_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Type of field res_attr has been changed from struct bin_attribute*[12] to struct bin_attribute*[18]. | Recompilation of a client program may be broken. |
| 7 | Type of field res_attr_wc has been changed from struct bin_attribute*[12] to struct bin_attribute*[18]. | Recompilation of a client program may be broken. |
| 8 | Type of field resource has been changed from struct resource[12] to struct resource[18]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct pci_dev*, bool, unsigned int, bool) to int(*)(struct pci_dev*, bool, unsigned int, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_ptr_buffer_jiffies has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field no_period_wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_pm_qos_req has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field extra_alloc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field extra_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field extra_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field refcount has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field child_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tp_event has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field shadow_ctx_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field read_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field id_header_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field header_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field hlist_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Type of field pending has been changed from struct perf_pending_entry to struct irq_work. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sample_id_all has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field precise_ip has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_cgroups has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rotate_disable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field page has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field del has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cancel_txn has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field entry has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field event_init has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field task_ctx_nr has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field pmu_enable has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field pmu_disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field start_txn has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field add has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field commit_txn has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field name has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field pmu_disable_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Base type of field start has been changed from int(*)(struct perf_event*) to void(*)(struct perf_event*, int). | Recompilation of a client program may be broken. |
| 15 | Base type of field stop has been changed from void(*)(struct perf_event*) to void(*)(struct perf_event*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hwtstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rxtstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field txtstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buffers has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field bufs has been changed from struct pipe_buffer[16] to struct pipe_buffer*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mfd_cell has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prio_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field node_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_prepared has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_suspended has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field can_wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field filename_trans has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field filename_trans_ttypes has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field len has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field type_attr_map_array has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field sym_val_to_name has been changed from char**[8] to struct flex_array*[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tclass has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field charging_blink_full_solid_trig has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field charging_blink_full_solid_trig_name has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field property_is_writeable has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field set_property has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field namelen has been changed from unsigned short to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field compute_unit_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field x86_capability has been changed from __u32[9] to __u32[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field gso_segment has been changed from struct sk_buff*(*)(struct sk_buff*, int) to struct sk_buff*(*)(struct sk_buff*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field stat has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field quota_on_meta has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field set_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct if_dqblk*) to int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*). | Recompilation of a client program may be broken. |
| 3 | Base type of field quota_off has been changed from int(*)(struct super_block*, int, int) to int(*)(struct super_block*, int). | Recompilation of a client program may be broken. |
| 4 | Base type of field get_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct if_dqblk*) to int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*). | Recompilation of a client program may be broken. |
| 5 | Base type of field quota_on has been changed from int(*)(struct super_block*, int, int, char*, int) to int(*)(struct super_block*, int, int, struct path*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field n_cbs_adopted has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field n_cbs_invoked has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field n_cbs_orphaned has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field n_rp_report_qs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dynticks_nmi_nesting has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field blkd_tasks has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field exp_tasks has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gp_tasks has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field node_kthread_status has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field node_kthread_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field wakemask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field boost has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gp_max has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gp_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field jiffies_stall has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field name has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Base type of field rda has been changed from struct rcu_data* to struct rcu_data. | Recompilation of a client program may be broken. |
| 7 | Type of field level has been changed from struct rcu_node*[1] to struct rcu_node*[2]. | Recompilation of a client program may be broken. |
| 8 | Type of field levelspread has been changed from u8[1] to u8[2]. | Recompilation of a client program may be broken. |
| 9 | Type of field node has been changed from struct rcu_node[1] to struct rcu_node[5]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field processed has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field real_end has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_overrun has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lost_events has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field refcount has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field root has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_oif has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rt_key_dst has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dst has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field fi has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rt_key_tos has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field rt_route_iif has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field rt_key_src has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field rt_peer_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field rt_mark has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aie_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field irqwork has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pie_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pie_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field timerqueue has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field uie_rtctimer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field limit has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field busylock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rcu_head has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_unacc_exec_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field skip has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field load_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field load_contribution has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field on_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field load_last has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field load_period has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_load_update_tick has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field active_balance_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field nohz_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field nohz_balance_kick has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field skip_clock_update has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field wake_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field clock_task has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_weight has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field yield_to_task has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field prio_changed has been changed from void(*)(struct rq*, struct task_struct*, int, int) to void(*)(struct rq*, struct task_struct*, int). | Recompilation of a client program may be broken. |
| 3 | Base type of field switched_from has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*). | Recompilation of a client program may be broken. |
| 4 | Base type of field select_task_rq has been changed from int(*)(struct rq*, struct task_struct*, int, int) to int(*)(struct task_struct*, int, int). | Recompilation of a client program may be broken. |
| 5 | Base type of field task_waking has been changed from void(*)(struct rq*, struct task_struct*) to void(*)(struct task_struct*). | Recompilation of a client program may be broken. |
| 6 | Base type of field switched_to has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*). | Recompilation of a client program may be broken. |
| 7 | Base type of field enqueue_task has been changed from void(*)(struct rq*, struct task_struct*, int, bool) to void(*)(struct rq*, struct task_struct*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field level has been changed from enum sched_domain_level to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field statistics has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_weight has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sgp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field oom_score_adj has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_threads has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field threadgroup_fork_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cred_guard_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field oom_score_adj_min has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_entry has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sched_task_group has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cpuset_slab_spread_rotor has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field on_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field pref_node_fork has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field sched_contributes_to_load has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field plug has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field ptrace_bp_refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field on_rq has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field mems_allowed_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field group_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Base type of field perf_event_ctxp has been changed from struct perf_event_context to struct perf_event_context*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_read_capacity_16 has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field no_read_disc_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field requeue_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sg_prot_tablesize has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sg_prot_tablesize has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unlock_native_capacity has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field queuecommand has been changed from int(*)(struct scsi_cmnd*, void(*)(struct scsi_cmnd*)) to int(*)(struct Scsi_Host*, struct scsi_cmnd*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sb_remount has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field secmark_refcount_dec has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field secmark_refcount_inc has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field secmark_relabel_packet has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Base type of field capable has been changed from int(*)(struct task_struct*, struct cred const*, int, int) to int(*)(struct task_struct*, struct cred const*, struct user_namespace*, int, int). | Recompilation of a client program may be broken. |
| 6 | Base type of field inode_init_security has been changed from int(*)(struct inode*, struct inode*, char**, void**, size_t*) to int(*)(struct inode*, struct inode*, struct qstr const*, char**, void**, size_t*). | Recompilation of a client program may be broken. |
| 7 | Base type of field inode_permission has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, int, unsigned int). | Recompilation of a client program may be broken. |
| 8 | Base type of field settime has been changed from int(*)(struct timespec*, struct timezone*) to int(*)(struct timespec const*, struct timezone const*). | Recompilation of a client program may be broken. |
| 9 | Base type of field syslog has been changed from int(*)(int, bool) to int(*)(int). | Recompilation of a client program may be broken. |
| 10 | Base type of field task_setrlimit has been changed from int(*)(unsigned int, struct rlimit*) to int(*)(struct task_struct*, unsigned int, struct rlimit*). | Recompilation of a client program may be broken. |
| 11 | Base type of field task_setscheduler has been changed from int(*)(struct task_struct*, int, struct sched_param*) to int(*)(struct task_struct*). | Recompilation of a client program may be broken. |
| 12 | Base type of field unix_stream_connect has been changed from int(*)(struct socket*, struct socket*, struct sock*) to int(*)(struct sock*, struct sock*, struct sock*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field set_ldisc has been changed from void(*)(struct uart_port*) to void(*)(struct uart_port*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_wake has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_termios has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field child_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field children has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rxhash has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ooo_okay has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[28] to unsigned long[27]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[4] to unsigned long[5]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field syncp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field mibs has been changed from unsigned long[31] to u64[31]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[77] to unsigned long[81]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rmem_alloc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_autobind has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field clear_sk has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field compat_ioctl has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_peer_cred has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_peer_pid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sk_gso_max_segs has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sk_classid has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field sk_route_nocaps has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field sk_rxhash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_dontcopy_end has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field skc_dontcopy_begin has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field skc_daddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field skc_rcv_saddr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_pages_max has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_event_changed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ignore_get_event has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tur_changed has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field tur_mismatch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcmcia_irq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pcmcia_pfc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tid_rx_timer_expired has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tid_start_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gtk has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field last_connected has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field last_rx_rate_flag has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field last_rx_rate_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field lost_packets has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ptk has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field reorder_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field reorder_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rcu_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field state has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field stop_initiator has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field tx_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_dropme has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field xpt_users has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field xpt_net has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field xpt_bc_xprt 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 xpo_create has been changed from struct svc_xprt*(*)(struct svc_serv*, struct sockaddr*, int, int) to struct svc_xprt*(*)(struct svc_serv*, struct net*, struct sockaddr*, int, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field write has been changed from ssize_t(*)(struct kobject*, struct bin_attribute*, char*, loff_t, size_t) to ssize_t(*)(struct file*, struct kobject*, struct bin_attribute*, char*, loff_t, size_t). | Recompilation of a client program may be broken. |
| 2 | Base type of field mmap has been changed from int(*)(struct kobject*, struct bin_attribute*, struct vm_area_struct*) to int(*)(struct file*, struct kobject*, struct bin_attribute*, struct vm_area_struct*). | Recompilation of a client program may be broken. |
| 3 | Base type of field read has been changed from ssize_t(*)(struct kobject*, struct bin_attribute*, char*, loff_t, size_t) to ssize_t(*)(struct file*, struct kobject*, struct bin_attribute*, char*, loff_t, size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_ns 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 handler has been changed from void(*)(int, struct tty_struct*) to void(*)(int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field slack has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field twsk_getpeer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field batch_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fast_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field local has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field pages has been changed from struct page*[506] to struct page*[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field a_preds has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field root has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field preds has been changed from struct filter_pred** to struct filter_pred*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ref_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flag_changed has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field use_max_tr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field funcs has been changed from void** to struct tracepoint_func*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tracepoint has been changed from struct tracepoint* to struct tracepoint*const*. | Recompilation of a client program may be broken. |
| 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 | Base type of field ioctl has been changed from int(*)(struct tty_struct*, struct file*, unsigned int, unsigned long) to int(*)(struct tty_struct*, unsigned int, unsigned long). | Recompilation of a client program may be broken. |
| 2 | Base type of field tiocmget has been changed from int(*)(struct tty_struct*, struct file*) to int(*)(struct tty_struct*). | Recompilation of a client program may be broken. |
| 3 | Base type of field tiocmset has been changed from int(*)(struct tty_struct*, struct file*, unsigned int, unsigned int) to int(*)(struct tty_struct*, unsigned int, unsigned int). | Recompilation of a client program may be broken. |
| 4 | Base type of field compat_ioctl has been changed from long(*)(struct tty_struct*, struct file*, unsigned int, unsigned long) to long(*)(struct tty_struct*, unsigned int, unsigned long). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field dcd_change has been changed from void(*)(struct tty_struct*, unsigned int, struct timespec*) to void(*)(struct tty_struct*, unsigned int, struct pps_event_time*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_mapped_sgs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field stream_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_dwork has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field uses_pio_for_control has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ss_ep_comp has been changed from struct usb_host_ss_ep_comp* to struct usb_ss_ep_comp_descriptor. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field uidhash_table has been changed from struct hlist_head[256] to struct hlist_head[128]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field phys_addr has been changed from unsigned long to phys_addr_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nr_cwqs_to_flush has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rescuer has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field saved_max_active has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field first_flusher has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field flush_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field flusher_overflow has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field flusher_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field mayday_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tagged_writepages has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mapping has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wallclock_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field i8042_detect 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 checkentry has been changed from bool(*)(struct xt_mtchk_param const*) to int(*)(struct xt_mtchk_param const*). | Recompilation of a client program may be broken. |
| 2 | Base type of field match has been changed from bool(*)(struct sk_buff const*, struct xt_match_param const*) to bool(*)(struct sk_buff const*, struct xt_action_param*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field jumpstack has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field stackptr has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field stacksize 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 checkentry has been changed from bool(*)(struct xt_tgchk_param const*) to int(*)(struct xt_tgchk_param const*). | Recompilation of a client program may be broken. |
| 2 | Base type of field target has been changed from unsigned int(*)(struct sk_buff*, struct xt_target_param const*) to unsigned int(*)(struct sk_buff*, struct xt_action_param const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field page_ptr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field scratch 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 migrate has been changed from int(*)(struct xfrm_selector*, u8, u8, struct xfrm_migrate*, int, struct xfrm_kmaddress*) to int(*)(struct xfrm_selector const*, u8, u8, struct xfrm_migrate const*, int, struct xfrm_kmaddress const*). | Recompilation of a client program may be broken. |
| 2 | Base type of field notify has been changed from int(*)(struct xfrm_state*, struct km_event*) to int(*)(struct xfrm_state*, struct km_event const*). | Recompilation of a client program may be broken. |
| 3 | Base type of field notify_policy has been changed from int(*)(struct xfrm_policy*, int, struct km_event*) to int(*)(struct xfrm_policy*, int, struct km_event const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flo has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field blackhole_route has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field dst_lookup has been changed from struct dst_entry*(*)(struct net*, int, xfrm_address_t*, xfrm_address_t*) to struct dst_entry*(*)(struct net*, int, xfrm_address_t const*, xfrm_address_t const*). | Recompilation of a client program may be broken. |
| 3 | Base type of field fill_dst has been changed from int(*)(struct xfrm_dst*, struct net_device*, struct flowi*) to int(*)(struct xfrm_dst*, struct net_device*, struct flowi const*). | Recompilation of a client program may be broken. |
| 4 | Base type of field get_tos has been changed from int(*)(struct flowi*) to int(*)(struct flowi const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field replay_esn has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tfcpad has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field preplay_esn has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field repl has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field output_finish has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field init_temprop has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field init_tempsel has been changed from void(*)(struct xfrm_state*, struct flowi*, struct xfrm_tmpl*, xfrm_address_t*, xfrm_address_t*) to void(*)(struct xfrm_selector*, struct flowi const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field reject has been changed from int(*)(struct xfrm_state*, struct sk_buff*, struct flowi*) to int(*)(struct xfrm_state*, struct sk_buff*, struct flowi const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_xmit_bytes_sent has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rq_rtt has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rq_cred has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field rq_reply_bytes_recvd has been changed from int to size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field xprt_net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter decode has been changed from int(*)(void*, __be32*, void*) to int(*)(void*, struct xdr_stream*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter encode has been changed from int(*)(void*, __be32*, void*) to void(*)(void*, struct xdr_stream*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter blocks has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter blocks has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter flags has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from __u32[9] to __u32[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[288] const to char const*[320] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct net_device_stats to struct rtnl_link_stats64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter features has been changed from unsigned long to struct net_device*. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter name has been changed from char const* to u32. | Recompilation of a client program may be broken. |
| 3 | Type of return value has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter all has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter mask has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| 3 | Type of 2nd parameter one has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| 4 | Type of return value has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from void* to unsigned char*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gfp_mask has been changed from gfp_t to struct shrink_control*. | Recompilation of a client program may be broken. |
| 2 | Type of 1st parameter nr_to_scan has been changed from int to struct shrinker*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct dm_kcopyd_client*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char* to char const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter handle_errors has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct err_regs*) to void(*)(int, struct mce*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter f has been changed from void(*)(int, struct err_regs*) to void(*)(int, struct mce*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[16] to char const*[9]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter address has been changed from u32(*)(void*) to u32(*)(acpi_handle, u32, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter address has been changed from u32(*)(void*) to u32(*)(acpi_handle, u32, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter personality has been changed from u_long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter personality has been changed from u_long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter thread_id has been changed from struct task_struct* to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter dev has been changed from struct net_device* to int. | Recompilation of a client program may be broken. |
| 2 | Type of 8th parameter mark has been changed from u32 to u32*. | Recompilation of a client program may be broken. |
| 3 | Type of 4th parameter oif has been changed from int to u8. | Recompilation of a client program may be broken. |
| 4 | Type of 1st parameter src has been changed from __be32 to struct sk_buff*. | Recompilation of a client program may be broken. |
| 5 | Type of 3rd parameter tos has been changed from u8 to __be32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter uevent has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void* to struct flow_cache_object*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 5th parameter file_name has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to enum ftrace_dump_mode. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct hpet_dev*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct hpet_dev*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter acctflag has been changed from int to vm_flags_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter action has been changed from u8 to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter flush_domains has been changed from uint32_t to struct drm_i915_gem_request*. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from uint32_t to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter write has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ipfragok has been changed from int to struct flowi*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter daddr has been changed from __be32 to struct inetpeer_addr*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter inf has been changed from struct autofs_info* to mode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter fs_dir_inode_ops has been changed from struct inode_operations const* to int. | Recompilation of a client program may be broken. |
| 2 | Type of 5th parameter isvfat has been changed from int to void(*)(struct super_block*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter acctflag has been changed from int to vm_flags_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter free_mark has been changed from void(*)(struct fsnotify_mark_entry*) to void(*)(struct fsnotify_mark*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from struct drm_crtc* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter bus_irq has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter gsi has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gsi has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter phys_addr has been changed from unsigned long to phys_addr_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter ipfragok has been changed from int to struct flowi*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from long(*)(long) to long(*)(int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter alg has been changed from enum ieee80211_key_alg to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter done has been changed from void(*)(struct scsi_cmnd*) to struct scsi_cmnd. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter keys has been changed from unsigned int* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter thread has been changed from mdk_thread_t* to mdk_thread_t**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter regnum has been changed from u16 to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter regnum has been changed from u16 to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter tlbp has been changed from struct mmu_gather** to struct mmu_gather*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter offlining has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter vm_flags has been changed from unsigned int to vm_flags_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[255] to int[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter irq has been changed from unsigned int to struct irq_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter base has been changed from char const* to char**. | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter buffer has been changed from char* to ssize_t. | Recompilation of a client program may be broken. |
| 3 | Type of 5th parameter buflen has been changed from ssize_t to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[37] to struct nf_conntrack_l3proto*[39]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter stat has been changed from int to enum nfs_stat. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from __be32* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nfs4_stateid to union nfs4_stateid. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from __be32* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct fsnotify_event*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 5th parameter name has been changed from char to unsigned char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter value has been changed from unsigned int to unsigned long long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter doio has been changed from int(*)(struct inode*, struct list_head*, unsigned int, size_t, int) to int(*)(struct nfs_pageio_descriptor*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter change_bridge has been changed from bool to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to snd_pcm_format_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter conf_check has been changed from int(*)(struct pcmcia_device*, cistpl_cftable_entry_t*, cistpl_cftable_entry_t*, unsigned int, void*) to int(*)(struct pcmcia_device*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter req has been changed from memreq_t* to unsigned int. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter wh has been changed from window_handle_t to struct resource*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter wh has been changed from window_handle_t to struct resource*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter req has been changed from struct irq_req_t to irqreturn_t(*)(int, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter wh has been changed from window_handle_t* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dyn_size has been changed from ssize_t to size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter pid has been changed from pid_t to struct task_struct*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_t[9] to struct jump_label_key[9]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from __u32[9] to __u32[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter addr has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct rtable*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct rtable*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[23] const to struct nla_policy[30] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long long to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter info has been changed from void* to struct svc_xprt*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter dir has been changed from int to enum dma_data_direction. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter dir has been changed from int to enum dma_data_direction. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[300] const to sys_call_ptr_t[309] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Base type of 4th parameter data has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 3 | Base type of 5th parameter resident has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 4 | Base type of 2nd parameter shared has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 5 | Base type of 3rd parameter text has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from ssize_t to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter irq_flags has been changed from unsigned long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[10] to char const*[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter begin has been changed from struct tracepoint* to struct tracepoint*const*. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter end has been changed from struct tracepoint* to struct tracepoint*const*. | Recompilation of a client program may be broken. |
| 3 | Type of 1st parameter tracepoint has been changed from struct tracepoint** to struct tracepoint*const**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter begin has been changed from struct tracepoint* to struct tracepoint*const*. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter end has been changed from struct tracepoint* to struct tracepoint*const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter features has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[9] to char const*[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter mode has been changed from int to isolate_mode_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gfp_mask has been changed from gfp_t to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of 1st parameter scanned has been changed from unsigned long to struct shrink_control*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[29] to atomic_long_t[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tfm has been changed from struct crypto_blkcipher to struct crypto_cipher. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter delta has been changed from short to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler* to struct xattr_handler const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler to struct xattr_handler const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dst_p has been changed from struct dst_entry** to struct dst_entry*. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int to struct dst_entry*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field device has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member REQ_TYPE_ATA_PC has been changed from 10 to 9. | No effect. |
| 2 | Value of member REQ_TYPE_ATA_TASKFILE has been changed from 9 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field addresses has been changed from 3 to 2. | No effect. |
| 2 | The relative position of field n_addresses has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field broadcast has been changed from 12 to 10. | No effect. |
| 2 | The relative position of field cpumask has been changed from 8 to 15. | No effect. |
| 3 | The relative position of field event_handler has been changed from 11 to 0. | No effect. |
| 4 | The relative position of field features has been changed from 1 to 8. | No effect. |
| 5 | The relative position of field irq has been changed from 7 to 14. | No effect. |
| 6 | The relative position of field list has been changed from 13 to 16. | No effect. |
| 7 | The relative position of field max_delta_ns has been changed from 2 to 3. | No effect. |
| 8 | The relative position of field min_delta_ns has been changed from 3 to 4. | No effect. |
| 9 | The relative position of field mode has been changed from 14 to 7. | No effect. |
| 10 | The relative position of field mult has been changed from 4 to 5. | No effect. |
| 11 | The relative position of field name has been changed from 0 to 12. | No effect. |
| 12 | The relative position of field next_event has been changed from 15 to 2. | No effect. |
| 13 | The relative position of field rating has been changed from 6 to 13. | No effect. |
| 14 | The relative position of field retries has been changed from 16 to 9. | No effect. |
| 15 | The relative position of field set_mode has been changed from 10 to 11. | No effect. |
| 16 | The relative position of field set_next_event has been changed from 9 to 1. | No effect. |
| 17 | The relative position of field shift has been changed from 5 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cycle_last has been changed from 14 to 1. | No effect. |
| 2 | The relative position of field disable has been changed from 5 to 11. | No effect. |
| 3 | The relative position of field enable has been changed from 4 to 10. | No effect. |
| 4 | The relative position of field flags has been changed from 10 to 12. | No effect. |
| 5 | The relative position of field list has been changed from 1 to 7. | No effect. |
| 6 | The relative position of field mask has been changed from 6 to 2. | No effect. |
| 7 | The relative position of field max_idle_ns has been changed from 9 to 5. | No effect. |
| 8 | The relative position of field mult has been changed from 7 to 3. | No effect. |
| 9 | The relative position of field name has been changed from 0 to 6. | No effect. |
| 10 | The relative position of field rating has been changed from 2 to 8. | No effect. |
| 11 | The relative position of field read has been changed from 3 to 0. | No effect. |
| 12 | The relative position of field resume has been changed from 13 to 14. | No effect. |
| 13 | The relative position of field shift has been changed from 8 to 4. | No effect. |
| 14 | The relative position of field suspend has been changed from 12 to 13. | No effect. |
| 15 | The relative position of field vread has been changed from 11 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field d_inode has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field d_lru has been changed from 7 to 12. | No effect. |
| 3 | The relative position of field d_parent has been changed from 5 to 2. | No effect. |
| 4 | The relative position of field d_u has been changed from 8 to 13. | No effect. |
| 5 | The relative position of field d_subdirs has been changed from 9 to 14. | No effect. |
| 6 | The relative position of field d_hash has been changed from 4 to 1. | No effect. |
| 7 | The relative position of field d_sb has been changed from 13 to 9. | No effect. |
| 8 | The relative position of field d_op has been changed from 12 to 8. | No effect. |
| 9 | The relative position of field d_name has been changed from 6 to 3. | No effect. |
| 10 | The relative position of field d_count has been changed from 0 to 6. | No effect. |
| 11 | The relative position of field d_fsdata has been changed from 14 to 11. | No effect. |
| 12 | The relative position of field d_iname has been changed from 15 to 5. | No effect. |
| 13 | The relative position of field d_alias has been changed from 10 to 15. | No effect. |
| 14 | The relative position of field d_flags has been changed from 1 to 0. | No effect. |
| 15 | The relative position of field d_time has been changed from 11 to 10. | No effect. |
| 16 | The relative position of field d_lock has been changed from 2 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field table has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field debugfs_cleanup has been changed from 30 to 29. | No effect. |
| 2 | The relative position of field debugfs_init has been changed from 29 to 28. | No effect. |
| 3 | The relative position of field gem_free_object has been changed from 32 to 31. | No effect. |
| 4 | The relative position of field gem_init_object has been changed from 31 to 30. | No effect. |
| 5 | The relative position of field vgaarb_irq has been changed from 33 to 32. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field _io has been changed from 12 to 9. | No effect. |
| 2 | The relative position of field _irq has been changed from 11 to 8. | No effect. |
| 3 | The relative position of field _locked has been changed from 14 to 11. | No effect. |
| 4 | The relative position of field _win has been changed from 13 to 10. | No effect. |
| 5 | The relative position of field allow_func_id_match has been changed from 15 to 12. | No effect. |
| 6 | The relative position of field card_id has been changed from 22 to 19. | No effect. |
| 7 | The relative position of field dev has been changed from 25 to 22. | No effect. |
| 8 | The relative position of field dma_mask has been changed from 24 to 21. | No effect. |
| 9 | The relative position of field func_id has been changed from 20 to 17. | No effect. |
| 10 | The relative position of field has_card_id has been changed from 17 to 14. | No effect. |
| 11 | The relative position of field has_func_id has been changed from 18 to 15. | No effect. |
| 12 | The relative position of field has_manf_id has been changed from 16 to 13. | No effect. |
| 13 | The relative position of field irq has been changed from 8 to 6. | No effect. |
| 14 | The relative position of field manf_id has been changed from 21 to 18. | No effect. |
| 15 | The relative position of field open has been changed from 6 to 24. | No effect. |
| 16 | The relative position of field prod_id has been changed from 23 to 20. | No effect. |
| 17 | The relative position of field suspended has been changed from 10 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field output has been changed from 14 to 11. | No effect. |
| 2 | The relative position of field header_len has been changed from 7 to 14. | No effect. |
| 3 | The relative position of field trailer_len has been changed from 8 to 15. | No effect. |
| 4 | The relative position of field ops has been changed from 15 to 3. | No effect. |
| 5 | The relative position of field path has been changed from 9 to 6. | No effect. |
| 6 | The relative position of field input has been changed from 13 to 10. | No effect. |
| 7 | The relative position of field expires has been changed from 6 to 5. | No effect. |
| 8 | The relative position of field __refcnt has been changed from 19 to 18. | No effect. |
| 9 | The relative position of field error has been changed from 3 to 12. | No effect. |
| 10 | The relative position of field hh has been changed from 11 to 8. | No effect. |
| 11 | The relative position of field __use has been changed from 20 to 19. | No effect. |
| 12 | The relative position of field flags has been changed from 5 to 21. | No effect. |
| 13 | The relative position of field xfrm has been changed from 12 to 9. | No effect. |
| 14 | The relative position of field obsolete has been changed from 4 to 13. | No effect. |
| 15 | The relative position of field __pad_to_align_refcnt has been changed from 18 to 17. | No effect. |
| 16 | The relative position of field lastuse has been changed from 21 to 20. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member e1000_ce4100 with value 9 has been added. | No effect. |
| 2 | Value of member e1000_82541 has been changed from 10 to 11. | No effect. |
| 3 | Value of member e1000_82541_rev_2 has been changed from 11 to 12. | No effect. |
| 4 | Value of member e1000_82546_rev_3 has been changed from 9 to 10. | No effect. |
| 5 | Value of member e1000_82547 has been changed from 12 to 13. | No effect. |
| 6 | Value of member e1000_82547_rev_2 has been changed from 13 to 14. | No effect. |
| 7 | Value of member e1000_num_macs has been changed from 14 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member e1000_phy_8201 with value 3 has been added. | No effect. |
| 2 | The member e1000_phy_8211 with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bd_openers has been changed from 3 to 1. | No effect. |
| 2 | The relative position of field bd_super has been changed from 2 to 3. | No effect. |
| 3 | The relative position of field bd_inode has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dirtied_when has been changed from 32 to 10. | No effect. |
| 2 | The relative position of field i_alloc_sem has been changed from 19 to 26. | No effect. |
| 3 | The relative position of field i_atime has been changed from 11 to 21. | No effect. |
| 4 | The relative position of field i_blkbits has been changed from 8 to 18. | No effect. |
| 5 | The relative position of field i_blocks has been changed from 14 to 24. | No effect. |
| 6 | The relative position of field i_bytes has been changed from 15 to 25. | No effect. |
| 7 | The relative position of field i_count has been changed from 3 to 15. | No effect. |
| 8 | The relative position of field i_ctime has been changed from 13 to 23. | No effect. |
| 9 | The relative position of field i_data has been changed from 25 to 30. | No effect. |
| 10 | The relative position of field i_devices has been changed from 27 to 32. | No effect. |
| 11 | The relative position of field i_dquot has been changed from 26 to 31. | No effect. |
| 12 | The relative position of field i_flags has been changed from 33 to 6. | No effect. |
| 13 | The relative position of field i_flock has been changed from 23 to 28. | No effect. |
| 14 | The relative position of field i_fop has been changed from 21 to 27. | No effect. |
| 15 | The relative position of field i_fsnotify_mask has been changed from 30 to 34. | No effect. |
| 16 | The relative position of field i_generation has been changed from 29 to 33. | No effect. |
| 17 | The relative position of field i_gid has been changed from 6 to 2. | No effect. |
| 18 | The relative position of field i_hash has been changed from 0 to 11. | No effect. |
| 19 | The relative position of field i_ino has been changed from 2 to 14. | No effect. |
| 20 | The relative position of field i_lock has been changed from 17 to 5. | No effect. |
| 21 | The relative position of field i_mapping has been changed from 24 to 29. | No effect. |
| 22 | The relative position of field i_mode has been changed from 16 to 0. | No effect. |
| 23 | The relative position of field i_mtime has been changed from 12 to 22. | No effect. |
| 24 | The relative position of field i_mutex has been changed from 18 to 9. | No effect. |
| 25 | The relative position of field i_nlink has been changed from 4 to 16. | No effect. |
| 26 | The relative position of field i_op has been changed from 20 to 3. | No effect. |
| 27 | The relative position of field i_rdev has been changed from 7 to 17. | No effect. |
| 28 | The relative position of field i_sb has been changed from 22 to 4. | No effect. |
| 29 | The relative position of field i_sb_list has been changed from 1 to 12. | No effect. |
| 30 | The relative position of field i_security has been changed from 35 to 8. | No effect. |
| 31 | The relative position of field i_size has been changed from 10 to 20. | No effect. |
| 32 | The relative position of field i_state has been changed from 31 to 7. | No effect. |
| 33 | The relative position of field i_uid has been changed from 5 to 1. | No effect. |
| 34 | The relative position of field i_version has been changed from 9 to 19. | No effect. |
| 35 | The relative position of field unnamed0 has been changed from 28 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field put_link has been changed from 11 to 5. | No effect. |
| 2 | The relative position of field lookup has been changed from 1 to 0. | No effect. |
| 3 | The relative position of field follow_link has been changed from 10 to 1. | No effect. |
| 4 | The relative position of field rename has been changed from 8 to 13. | No effect. |
| 5 | The relative position of field readlink has been changed from 9 to 4. | No effect. |
| 6 | The relative position of field symlink has been changed from 4 to 9. | No effect. |
| 7 | The relative position of field unlink has been changed from 3 to 8. | No effect. |
| 8 | The relative position of field rmdir has been changed from 6 to 11. | No effect. |
| 9 | The relative position of field check_acl has been changed from 14 to 3. | No effect. |
| 10 | The relative position of field create has been changed from 0 to 6. | No effect. |
| 11 | The relative position of field link has been changed from 2 to 7. | No effect. |
| 12 | The relative position of field mknod has been changed from 7 to 12. | No effect. |
| 13 | The relative position of field mkdir has been changed from 5 to 10. | No effect. |
| 14 | The relative position of field truncate has been changed from 12 to 14. | No effect. |
| 15 | The relative position of field permission has been changed from 13 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_dentry has been added to this type. | No effect. |
| 2 | Field i_rcu has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field data has been changed from 8 to 7. | No effect. |
| 2 | The relative position of field filter has been changed from 6 to 5. | No effect. |
| 3 | The relative position of field mod has been changed from 7 to 6. | No effect. |
| 4 | The relative position of field perf_refcount has been changed from 9 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cpu has been changed from 10 to 11. | No effect. |
| 2 | The relative position of field ent has been changed from 8 to 9. | No effect. |
| 3 | The relative position of field idx has been changed from 13 to 14. | No effect. |
| 4 | The relative position of field leftover has been changed from 9 to 10. | No effect. |
| 5 | The relative position of field pos has been changed from 12 to 13. | No effect. |
| 6 | The relative position of field seq has been changed from 7 to 8. | No effect. |
| 7 | The relative position of field started has been changed from 14 to 7. | No effect. |
| 8 | The relative position of field ts has been changed from 11 to 12. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field uses_new_polling has been changed from 9 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field label became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field clock_base has been changed from 1 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member FBC_MODULE_PARAM with value 7 has been added. | No effect. |
| 2 | The member FBC_MULTIPLE_PIPES with value 6 has been added. | No effect. |
| 3 | The member FBC_NO_OUTPUT with value 0 has been added. | No effect. |
| 4 | Value of member FBC_BAD_PLANE has been changed from 3 to 4. | No effect. |
| 5 | Value of member FBC_MODE_TOO_LARGE has been changed from 2 to 3. | No effect. |
| 6 | Value of member FBC_NOT_TILED has been changed from 4 to 5. | No effect. |
| 7 | Value of member FBC_STOLEN_TOO_SMALL has been changed from 0 to 1. | No effect. |
| 8 | Value of member FBC_UNSUPPORTED_MODE has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member I915_MAX_PIPES with value 3 has been added. | No effect. |
| 2 | The member PIPE_C with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PLANE_C with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field gtt_mapping has been changed from 1 to 2. | No effect. |
| 2 | The relative position of field gtt_mtrr has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bit_17 has been changed from 14 to 17. | No effect. |
| 2 | The relative position of field fence_reg has been changed from 9 to 7. | No effect. |
| 3 | The relative position of field gpu_write_list has been changed from 2 to 3. | No effect. |
| 4 | The relative position of field gtt_offset has been changed from 8 to 14. | No effect. |
| 5 | The relative position of field madv has been changed from 21 to 8. | No effect. |
| 6 | The relative position of field page_cpu_valid has been changed from 16 to 18. | No effect. |
| 7 | The relative position of field pin_filp has been changed from 18 to 20. | No effect. |
| 8 | The relative position of field tiling_mode has been changed from 12 to 9. | No effect. |
| 9 | The relative position of field last_rendering_seqno has been changed from 11 to 15. | No effect. |
| 10 | The relative position of field phys_obj has been changed from 19 to 21. | No effect. |
| 11 | The relative position of field pages has been changed from 6 to 12. | No effect. |
| 12 | The relative position of field stride has been changed from 13 to 16. | No effect. |
| 13 | The relative position of field user_pin_count has been changed from 17 to 19. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field lid_notifier has been changed from 50 to 49. | No effect. |
| 2 | The relative position of field lvds_ssc_freq has been changed from 49 to 48. | No effect. |
| 3 | The relative position of field pipestat has been changed from 18 to 17. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dvo_port has been changed from 0 to 1. | No effect. |
| 2 | The relative position of field dvo_wiring has been changed from 2 to 3. | No effect. |
| 3 | The relative position of field initialized has been changed from 3 to 0. | No effect. |
| 4 | The relative position of field slave_addr has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_WORK_ASSOC_BEACON_WAIT with value 3 has been added. | No effect. |
| 2 | The member IEEE80211_WORK_OFFCHANNEL_TX with value 6 has been added. | No effect. |
| 3 | Value of member IEEE80211_WORK_ASSOC has been changed from 3 to 4. | No effect. |
| 4 | Value of member IEEE80211_WORK_REMAIN_ON_CHANNEL has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field offchan_tx has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field mesh has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field sfmode has been changed from 4 to 2. | No effect. |
| 2 | The relative position of field sources has been changed from 2 to 3. | No effect. |
| 3 | The relative position of field tomb has been changed from 3 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field key has been changed from 23 to 22. | No effect. |
| 2 | The relative position of field led has been changed from 24 to 23. | No effect. |
| 3 | The relative position of field snd has been changed from 25 to 24. | No effect. |
| 4 | The relative position of field sw has been changed from 26 to 25. | No effect. |
| 5 | The relative position of field sync has been changed from 21 to 35. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dir has been changed from 6 to 9. | No effect. |
| 2 | The relative position of field next has been changed from 4 to 3. | No effect. |
| 3 | The relative position of field thread_flags has been changed from 9 to 7. | No effect. |
| 4 | The relative position of field thread has been changed from 8 to 6. | No effect. |
| 5 | The relative position of field thread_fn has been changed from 7 to 5. | No effect. |
| 6 | The relative position of field dev_id has been changed from 3 to 2. | No effect. |
| 7 | The relative position of field irq has been changed from 5 to 4. | No effect. |
| 8 | The relative position of field name has been changed from 2 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rt6i_dst has been changed from 9 to 4. | No effect. |
| 2 | The relative position of field rt6i_table has been changed from 8 to 0. | No effect. |
| 3 | The relative position of field rt6i_ref has been changed from 5 to 3. | No effect. |
| 4 | The relative position of field rt6i_metric has been changed from 4 to 7. | No effect. |
| 5 | The relative position of field rt6i_idev has been changed from 0 to 8. | No effect. |
| 6 | The relative position of field rt6i_protocol has been changed from 7 to 11. | No effect. |
| 7 | The relative position of field rt6i_flags has been changed from 3 to 5. | No effect. |
| 8 | The relative position of field rt6i_nfheader_len has been changed from 6 to 10. | No effect. |
| 9 | The relative position of field rt6i_flow_cache_genid has been changed from 10 to 9. | No effect. |
| 10 | The relative position of field rt6i_src has been changed from 11 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fib_dead has been changed from 5 to 6. | No effect. |
| 2 | The relative position of field fib_flags has been changed from 6 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field shm_tot has been changed from 13 to 12. | No effect. |
| 2 | The relative position of field shm_ctlmni has been changed from 12 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pending_mask has been changed from 10 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member T_COMMIT_RECORD with value 4 has been added. | No effect. |
| 2 | Value of member T_COMMIT has been changed from 4 to 3. | No effect. |
| 3 | Value of member T_FLUSH has been changed from 3 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member DIE_CALL has been changed from 11 to 10. | No effect. |
| 2 | Value of member DIE_GPF has been changed from 10 to 9. | No effect. |
| 3 | Value of member DIE_KERNELDEBUG has been changed from 8 to 7. | No effect. |
| 4 | Value of member DIE_NMIUNKNOWN has been changed from 14 to 12. | No effect. |
| 5 | Value of member DIE_PAGE_FAULT has been changed from 13 to 11. | No effect. |
| 6 | Value of member DIE_TRAP has been changed from 9 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field reject_error has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcudata has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_EMERG with value 6 has been added. | No effect. |
| 2 | The member KMSG_DUMP_HALT with value 4 has been added. | No effect. |
| 3 | The member KMSG_DUMP_POWEROFF with value 5 has been added. | No effect. |
| 4 | The member KMSG_DUMP_RESTART with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cursg has been changed from 15 to 17. | No effect. |
| 2 | The relative position of field cursg_ofs has been changed from 16 to 18. | No effect. |
| 3 | The relative position of field sg has been changed from 18 to 16. | No effect. |
| 4 | The relative position of field sgent has been changed from 17 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry has been added to this type. | No effect. |
| 2 | Field inode has been added to this type. | No effect. |
| 3 | Field path has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field page_table_lock has been changed from 14 to 13. | No effect. |
| 2 | The relative position of field mmap_sem has been changed from 13 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_ANON_TRANSPARENT_HUGEPAGES with value 31 has been added. | No effect. |
| 2 | The member NR_DIRTIED with value 23 has been added. | No effect. |
| 3 | The member NR_WRITTEN with value 24 has been added. | No effect. |
| 4 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 29 to 32. | No effect. |
| 5 | Value of member NUMA_FOREIGN has been changed from 25 to 27. | No effect. |
| 6 | Value of member NUMA_HIT has been changed from 23 to 25. | No effect. |
| 7 | Value of member NUMA_INTERLEAVE_HIT has been changed from 26 to 28. | No effect. |
| 8 | Value of member NUMA_LOCAL has been changed from 27 to 29. | No effect. |
| 9 | Value of member NUMA_MISS has been changed from 24 to 26. | No effect. |
| 10 | Value of member NUMA_OTHER has been changed from 28 to 30. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field num_trace_bprintk_fmt has been changed from 46 to 45. | No effect. |
| 2 | The relative position of field percpu has been changed from 41 to 42. | No effect. |
| 3 | The relative position of field percpu_size has been changed from 42 to 43. | No effect. |
| 4 | The relative position of field trace_bprintk_fmt_start has been changed from 45 to 46. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field elemsize has been changed from 3 to 1. | No effect. |
| 2 | The relative position of field num has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field flags has been changed from 7 to 11. | No effect. |
| 2 | The relative position of field refcnt has been changed from 15 to 6. | No effect. |
| 3 | The relative position of field nud_state has been changed from 8 to 12. | No effect. |
| 4 | The relative position of field confirmed has been changed from 5 to 3. | No effect. |
| 5 | The relative position of field output has been changed from 16 to 17. | No effect. |
| 6 | The relative position of field hh has been changed from 14 to 16. | No effect. |
| 7 | The relative position of field timer has been changed from 18 to 8. | No effect. |
| 8 | The relative position of field dev has been changed from 3 to 19. | No effect. |
| 9 | The relative position of field ha has been changed from 13 to 15. | No effect. |
| 10 | The relative position of field dead has been changed from 10 to 14. | No effect. |
| 11 | The relative position of field type has been changed from 9 to 13. | No effect. |
| 12 | The relative position of field lock has been changed from 12 to 5. | No effect. |
| 13 | The relative position of field updated has been changed from 6 to 4. | No effect. |
| 14 | The relative position of field probes has been changed from 11 to 10. | No effect. |
| 15 | The relative position of field arp_queue has been changed from 17 to 7. | No effect. |
| 16 | The relative position of field used has been changed from 4 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field proc_net_stat has been changed from 5 to 6. | No effect. |
| 2 | The relative position of field genl_sock has been changed from 14 to 9. | No effect. |
| 3 | The relative position of field dev_index_head has been changed from 10 to 12. | No effect. |
| 4 | The relative position of field cleanup_list has been changed from 2 to 3. | No effect. |
| 5 | The relative position of field exit_list has been changed from 3 to 4. | No effect. |
| 6 | The relative position of field sysctls has been changed from 6 to 7. | No effect. |
| 7 | The relative position of field rules_ops has been changed from 11 to 13. | No effect. |
| 8 | The relative position of field loopback_dev has been changed from 7 to 14. | No effect. |
| 9 | The relative position of field rules_mod_lock has been changed from 12 to 1. | No effect. |
| 10 | The relative position of field dev_name_head has been changed from 9 to 11. | No effect. |
| 11 | The relative position of field proc_net has been changed from 4 to 5. | No effect. |
| 12 | The relative position of field dev_base_head has been changed from 8 to 10. | No effect. |
| 13 | The relative position of field list has been changed from 1 to 2. | No effect. |
| 14 | The relative position of field rtnl has been changed from 13 to 8. | No effect. |
| 15 | The relative position of field xfrm has been changed from 25 to 27. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ethtool_ops has been changed from 18 to 17. | No effect. |
| 2 | The relative position of field netdev_ops has been changed from 17 to 16. | No effect. |
| 3 | The relative position of field dma has been changed from 8 to 26. | No effect. |
| 4 | The relative position of field dev_addr has been changed from 48 to 49. | No effect. |
| 5 | The relative position of field _tx has been changed from 51 to 52. | No effect. |
| 6 | The relative position of field unreg_list has been changed from 12 to 10. | No effect. |
| 7 | The relative position of field broadcast has been changed from 50 to 51. | No effect. |
| 8 | The relative position of field hard_header_len has been changed from 28 to 29. | No effect. |
| 9 | The relative position of field if_port has been changed from 7 to 25. | No effect. |
| 10 | The relative position of field iflink has been changed from 15 to 14. | No effect. |
| 11 | The relative position of field num_tx_queues has been changed from 52 to 53. | No effect. |
| 12 | The relative position of field qdisc has been changed from 54 to 55. | No effect. |
| 13 | The relative position of field index_hlist has been changed from 61 to 63. | No effect. |
| 14 | The relative position of field link_watch_list has been changed from 62 to 64. | No effect. |
| 15 | The relative position of field rtnl_link_state has been changed from 64 to 66. | No effect. |
| 16 | The relative position of field uc_promisc has been changed from 36 to 37. | No effect. |
| 17 | The relative position of field tx_global_lock has been changed from 56 to 57. | No effect. |
| 18 | The relative position of field state has been changed from 9 to 7. | No effect. |
| 19 | The relative position of field sysfs_groups has been changed from 71 to 72. | No effect. |
| 20 | The relative position of field todo_list has been changed from 60 to 62. | No effect. |
| 21 | The relative position of field watchdog_timeo has been changed from 58 to 60. | No effect. |
| 22 | The relative position of field header_ops has been changed from 19 to 18. | No effect. |
| 23 | The relative position of field needed_headroom has been changed from 29 to 30. | No effect. |
| 24 | The relative position of field npinfo has been changed from 66 to 68. | No effect. |
| 25 | The relative position of field stats has been changed from 16 to 15. | No effect. |
| 26 | The relative position of field vlan_features has been changed from 73 to 12. | No effect. |
| 27 | The relative position of field features has been changed from 13 to 11. | No effect. |
| 28 | The relative position of field padded has been changed from 23 to 22. | No effect. |
| 29 | The relative position of field master has been changed from 31 to 48. | No effect. |
| 30 | The relative position of field dev has been changed from 70 to 71. | No effect. |
| 31 | The relative position of field link_mode has been changed from 25 to 24. | No effect. |
| 32 | The relative position of field nd_net has been changed from 67 to 69. | No effect. |
| 33 | The relative position of field needed_tailroom has been changed from 30 to 31. | No effect. |
| 34 | The relative position of field type has been changed from 27 to 28. | No effect. |
| 35 | The relative position of field real_num_tx_queues has been changed from 53 to 54. | No effect. |
| 36 | The relative position of field dev_addrs has been changed from 49 to 50. | No effect. |
| 37 | The relative position of field ifindex has been changed from 14 to 13. | No effect. |
| 38 | The relative position of field operstate has been changed from 24 to 23. | No effect. |
| 39 | The relative position of field rtnl_link_ops has been changed from 72 to 73. | No effect. |
| 40 | The relative position of field trans_start has been changed from 57 to 59. | No effect. |
| 41 | The relative position of field watchdog_timer has been changed from 59 to 61. | No effect. |
| 42 | The relative position of field addr_list_lock has been changed from 37 to 35. | No effect. |
| 43 | The relative position of field destructor has been changed from 65 to 67. | No effect. |
| 44 | The relative position of field dev_list has been changed from 10 to 8. | No effect. |
| 45 | The relative position of field flags has been changed from 20 to 19. | No effect. |
| 46 | The relative position of field garp_port has been changed from 69 to 70. | No effect. |
| 47 | The relative position of field mtu has been changed from 26 to 27. | No effect. |
| 48 | The relative position of field napi_list has been changed from 11 to 9. | No effect. |
| 49 | The relative position of field reg_state has been changed from 63 to 65. | No effect. |
| 50 | The relative position of field tx_queue_len has been changed from 55 to 56. | No effect. |
| 51 | The relative position of field uc has been changed from 35 to 36. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field input_pkt_queue has been changed from 1 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ct_net has been changed from 9 to 8. | No effect. |
| 2 | The relative position of field ext has been changed from 8 to 7. | No effect. |
| 3 | The relative position of field proto has been changed from 7 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IP_CT_ESTABLISHED_REPLY with value 3 has been added. | No effect. |
| 2 | The member IP_CT_NEW_REPLY with value 5 has been added. | No effect. |
| 3 | The member IP_CT_RELATED_REPLY with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NF_CT_EXT_NUM has been changed from 5 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SIP_HDR_CALL_ID with value 8 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ls_count has been changed from 8 to 7. | No effect. |
| 2 | The relative position of field ls_flags has been changed from 3 to 2. | No effect. |
| 3 | The relative position of field ls_id has been changed from 6 to 5. | No effect. |
| 4 | The relative position of field ls_owner has been changed from 2 to 8. | No effect. |
| 5 | The relative position of field ls_seqid has been changed from 4 to 3. | No effect. |
| 6 | The relative position of field ls_sequence has been changed from 5 to 4. | No effect. |
| 7 | The relative position of field ls_stateid has been changed from 7 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_IFTYPE_P2P_GO with value 9 has been added. | No effect. |
| 2 | The member NUM_NL80211_IFTYPES with value 10 has been added. | No effect. |
| 3 | Value of member NL80211_IFTYPE_MAX has been changed from 7 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NUM_NL80211_KEYTYPES with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmu became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field stop has been changed from 2 to 3. | No effect. |
| 2 | The relative position of field read has been changed from 3 to 4. | No effect. |
| 3 | The relative position of field start has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed2 has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tmp_page has been changed from 3 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field alarmtimer has been added to this type. | No effect. |
| 2 | Field rcu has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_CURRENT_MAX with value 13 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_PROP_TYPE with value 39 has been added. | No effect. |
| 3 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 23 to 24. | No effect. |
| 4 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 30 to 31. | No effect. |
| 5 | Value of member POWER_SUPPLY_PROP_CAPACITY_LEVEL has been changed from 31 to 32. | No effect. |
| 6 | Value of member POWER_SUPPLY_PROP_CHARGE_AVG has been changed from 22 to 23. | No effect. |
| 7 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY has been changed from 20 to 21. | No effect. |
| 8 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY_DESIGN has been changed from 18 to 19. | No effect. |
| 9 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL has been changed from 19 to 20. | No effect. |
| 10 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN has been changed from 17 to 18. | No effect. |
| 11 | Value of member POWER_SUPPLY_PROP_CHARGE_NOW has been changed from 21 to 22. | No effect. |
| 12 | Value of member POWER_SUPPLY_PROP_CURRENT_AVG has been changed from 14 to 15. | No effect. |
| 13 | Value of member POWER_SUPPLY_PROP_CURRENT_NOW has been changed from 13 to 14. | No effect. |
| 14 | Value of member POWER_SUPPLY_PROP_ENERGY_AVG has been changed from 29 to 30. | No effect. |
| 15 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY has been changed from 27 to 28. | No effect. |
| 16 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY_DESIGN has been changed from 25 to 26. | No effect. |
| 17 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL has been changed from 26 to 27. | No effect. |
| 18 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL_DESIGN has been changed from 24 to 25. | No effect. |
| 19 | Value of member POWER_SUPPLY_PROP_ENERGY_NOW has been changed from 28 to 29. | No effect. |
| 20 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 39 to 41. | No effect. |
| 21 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 38 to 40. | No effect. |
| 22 | Value of member POWER_SUPPLY_PROP_POWER_AVG has been changed from 16 to 17. | No effect. |
| 23 | Value of member POWER_SUPPLY_PROP_POWER_NOW has been changed from 15 to 16. | No effect. |
| 24 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 40 to 42. | No effect. |
| 25 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 32 to 33. | No effect. |
| 26 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 33 to 34. | No effect. |
| 27 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG has been changed from 35 to 36. | No effect. |
| 28 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW has been changed from 34 to 35. | No effect. |
| 29 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 37 to 38. | No effect. |
| 30 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 36 to 37. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_TYPE_USB_ACA with value 6 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_TYPE_USB_CDP with value 5 has been added. | No effect. |
| 3 | The member POWER_SUPPLY_TYPE_USB_DCP with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field buffer has been changed from 1 to 2. | No effect. |
| 2 | The relative position of field commit_overrun has been changed from 10 to 11. | No effect. |
| 3 | The relative position of field commit_page has been changed from 8 to 9. | No effect. |
| 4 | The relative position of field commits has been changed from 14 to 15. | No effect. |
| 5 | The relative position of field committing has been changed from 13 to 14. | No effect. |
| 6 | The relative position of field entries has been changed from 12 to 13. | No effect. |
| 7 | The relative position of field head_page has been changed from 6 to 7. | No effect. |
| 8 | The relative position of field lock has been changed from 3 to 4. | No effect. |
| 9 | The relative position of field lock_key has been changed from 4 to 5. | No effect. |
| 10 | The relative position of field overrun has been changed from 11 to 12. | No effect. |
| 11 | The relative position of field pages has been changed from 5 to 6. | No effect. |
| 12 | The relative position of field read has been changed from 15 to 16. | No effect. |
| 13 | The relative position of field read_stamp has been changed from 17 to 18. | No effect. |
| 14 | The relative position of field reader_lock has been changed from 2 to 3. | No effect. |
| 15 | The relative position of field reader_page has been changed from 9 to 10. | No effect. |
| 16 | The relative position of field record_disabled has been changed from 18 to 1. | No effect. |
| 17 | The relative position of field tail_page has been changed from 7 to 8. | No effect. |
| 18 | The relative position of field write_stamp has been changed from 16 to 17. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field qstats has been changed from 20 to 21. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tk_cred_retry has been changed from 7 to 22. | No effect. |
| 2 | The relative position of field tk_ops has been changed from 11 to 7. | No effect. |
| 3 | The relative position of field tk_callback has been changed from 9 to 5. | No effect. |
| 4 | The relative position of field tk_rebind_retry has been changed from 8 to 23. | No effect. |
| 5 | The relative position of field tk_action has been changed from 10 to 6. | No effect. |
| 6 | The relative position of field tk_timeouts has been changed from 19 to 18. | No effect. |
| 7 | The relative position of field tk_start has been changed from 20 to 14. | No effect. |
| 8 | The relative position of field tk_garb_retry has been changed from 6 to 21. | No effect. |
| 9 | The relative position of field tk_priority has been changed from 22 to 20. | No effect. |
| 10 | The relative position of field tk_flags has been changed from 14 to 17. | No effect. |
| 11 | The relative position of field tk_owner has been changed from 21 to 15. | No effect. |
| 12 | The relative position of field tk_pid has been changed from 23 to 19. | No effect. |
| 13 | The relative position of field tk_runstate has been changed from 15 to 10. | No effect. |
| 14 | The relative position of field tk_waitqueue has been changed from 17 to 12. | No effect. |
| 15 | The relative position of field tk_workqueue has been changed from 16 to 11. | No effect. |
| 16 | The relative position of field u has been changed from 18 to 13. | No effect. |
| 17 | The relative position of field tk_calldata has been changed from 12 to 8. | No effect. |
| 18 | The relative position of field tk_msg has been changed from 5 to 4. | No effect. |
| 19 | The relative position of field tk_status has been changed from 4 to 16. | No effect. |
| 20 | The relative position of field tk_timeout has been changed from 13 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field creds has been changed from 0 to 1. | No effect. |
| 2 | The relative position of field fp has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field min_partial has been changed from 13 to 2. | No effect. |
| 2 | The relative position of field refcount has been changed from 9 to 10. | No effect. |
| 3 | The relative position of field ctor has been changed from 10 to 11. | No effect. |
| 4 | The relative position of field allocflags has been changed from 8 to 9. | No effect. |
| 5 | The relative position of field offset has been changed from 4 to 5. | No effect. |
| 6 | The relative position of field objsize has been changed from 3 to 4. | No effect. |
| 7 | The relative position of field size has been changed from 2 to 3. | No effect. |
| 8 | The relative position of field align has been changed from 12 to 13. | No effect. |
| 9 | The relative position of field oo has been changed from 5 to 6. | No effect. |
| 10 | The relative position of field min has been changed from 7 to 8. | No effect. |
| 11 | The relative position of field inuse has been changed from 11 to 12. | No effect. |
| 12 | The relative position of field max has been changed from 6 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field len has been changed from 2 to 0. | No effect. |
| 2 | The relative position of field tail has been changed from 1 to 2. | No effect. |
| 3 | The relative position of field head has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field sk_userlocks has been changed from 3 to 19. | No effect. |
| 2 | The relative position of field sk_protocol has been changed from 4 to 20. | No effect. |
| 3 | The relative position of field sk_sndtimeo has been changed from 37 to 38. | No effect. |
| 4 | The relative position of field sk_rcvlowat has been changed from 24 to 27. | No effect. |
| 5 | The relative position of field sk_write_queue has been changed from 17 to 16. | No effect. |
| 6 | The relative position of field sk_dst_cache has been changed from 10 to 11. | No effect. |
| 7 | The relative position of field sk_flags has been changed from 25 to 10. | No effect. |
| 8 | The relative position of field sk_wmem_queued has been changed from 18 to 22. | No effect. |
| 9 | The relative position of field sk_lingertime has been changed from 26 to 28. | No effect. |
| 10 | The relative position of field sk_type has been changed from 5 to 21. | No effect. |
| 11 | The relative position of field sk_err_soft has been changed from 31 to 33. | No effect. |
| 12 | The relative position of field sk_err has been changed from 30 to 32. | No effect. |
| 13 | The relative position of field sk_prot_creator has been changed from 28 to 30. | No effect. |
| 14 | The relative position of field sk_backlog has been changed from 8 to 3. | No effect. |
| 15 | The relative position of field sk_callback_lock has been changed from 29 to 31. | No effect. |
| 16 | The relative position of field sk_filter has been changed from 38 to 7. | No effect. |
| 17 | The relative position of field sk_receive_queue has been changed from 16 to 2. | No effect. |
| 18 | The relative position of field sk_route_caps has been changed from 21 to 24. | No effect. |
| 19 | The relative position of field sk_allocation has been changed from 20 to 23. | No effect. |
| 20 | The relative position of field sk_gso_max_size has been changed from 23 to 26. | No effect. |
| 21 | The relative position of field sk_gso_type has been changed from 22 to 25. | No effect. |
| 22 | The relative position of field sk_shutdown has been changed from 1 to 17. | No effect. |
| 23 | The relative position of field sk_priority has been changed from 35 to 36. | No effect. |
| 24 | The relative position of field sk_policy has been changed from 11 to 9. | No effect. |
| 25 | The relative position of field sk_drops has been changed from 32 to 5. | No effect. |
| 26 | The relative position of field sk_forward_alloc has been changed from 19 to 4. | No effect. |
| 27 | The relative position of field sk_max_ack_backlog has been changed from 34 to 35. | No effect. |
| 28 | The relative position of field sk_ack_backlog has been changed from 33 to 34. | No effect. |
| 29 | The relative position of field sk_lock has been changed from 7 to 1. | No effect. |
| 30 | The relative position of field sk_rcvtimeo has been changed from 36 to 37. | No effect. |
| 31 | The relative position of field sk_no_check has been changed from 2 to 18. | No effect. |
| 32 | The relative position of field sk_error_queue has been changed from 27 to 29. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field skc_refcnt has been changed from 1 to 10. | No effect. |
| 2 | The relative position of field skc_family has been changed from 4 to 1. | No effect. |
| 3 | The relative position of field skc_bound_dev_if has been changed from 7 to 4. | No effect. |
| 4 | The relative position of field skc_reuse has been changed from 6 to 3. | No effect. |
| 5 | The relative position of field skc_tx_queue_mapping has been changed from 2 to 9. | No effect. |
| 6 | The relative position of field unnamed1 has been changed from 3 to 5. | No effect. |
| 7 | The relative position of field skc_prot has been changed from 9 to 6. | No effect. |
| 8 | The relative position of field skc_state has been changed from 5 to 2. | No effect. |
| 9 | The relative position of field skc_net has been changed from 10 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_hash has been added to this type. | No effect. |
| 2 | Field skc_u16hashes has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_portaddr_node has been added to this type. | No effect. |
| 2 | Field skc_bind_node has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field start_site has been changed from 5 to 6. | No effect. |
| 2 | The relative position of field start_comm has been changed from 6 to 7. | No effect. |
| 3 | The relative position of field base has been changed from 4 to 2. | No effect. |
| 4 | The relative position of field start_pid has been changed from 7 to 5. | No effect. |
| 5 | The relative position of field function has been changed from 2 to 3. | No effect. |
| 6 | The relative position of field data has been changed from 3 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field print_max has been changed from 16 to 17. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter became non-volatile. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field counter became non-volatile. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ep_dev has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field ss_ep_comp has been changed from 4 to 1. | No effect. |
| 3 | The relative position of field urb_list has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field name has been changed from 2 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field checkentry has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field compat_from_user has been changed from 5 to 6. | No effect. |
| 3 | The relative position of field compat_to_user has been changed from 6 to 7. | No effect. |
| 4 | The relative position of field compatsize has been changed from 10 to 11. | No effect. |
| 5 | The relative position of field destroy has been changed from 4 to 5. | No effect. |
| 6 | The relative position of field family has been changed from 13 to 14. | No effect. |
| 7 | The relative position of field hooks has been changed from 11 to 12. | No effect. |
| 8 | The relative position of field me has been changed from 7 to 8. | No effect. |
| 9 | The relative position of field proto has been changed from 12 to 13. | No effect. |
| 10 | The relative position of field revision has been changed from 14 to 2. | No effect. |
| 11 | The relative position of field table has been changed from 8 to 9. | No effect. |
| 12 | The relative position of field target has been changed from 2 to 3. | No effect. |
| 13 | The relative position of field targetsize has been changed from 9 to 10. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field sysctl_aevent_etime has been changed from 21 to 19. | No effect. |
| 2 | The relative position of field sysctl_aevent_rseqth has been changed from 22 to 20. | No effect. |
| 3 | The relative position of field xfrm6_dst_ops has been changed from 18 to 25. | No effect. |
| 4 | The relative position of field nlsk_stash has been changed from 20 to 18. | No effect. |
| 5 | The relative position of field nlsk has been changed from 19 to 17. | No effect. |
| 6 | The relative position of field sysctl_acq_expires has been changed from 24 to 22. | No effect. |
| 7 | The relative position of field sysctl_hdr has been changed from 25 to 23. | No effect. |
| 8 | The relative position of field sysctl_larval_drop has been changed from 23 to 21. | No effect. |
| 9 | The relative position of field xfrm4_dst_ops has been changed from 17 to 24. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rq_reply_bytes_recvd has been changed from 6 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to struct rpc_cred*. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter in_avd has been renamed to avd. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter minsec has been renamed to maxsec. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | No effect. |
| 2 | 3rd parameter envp has been renamed to __envp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter buffer has been renamed to buf. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter error_fn has been renamed to error. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter features has been renamed to dev. | No effect. |
| 2 | 2nd parameter name has been renamed to features. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter nr_to_scan has been renamed to shrink. | No effect. |
| 2 | 2nd parameter gfp_mask has been renamed to sc. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter warn has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter reserve has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fb has been renamed to fb_helper. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter kref has been renamed to obj. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter node has been renamed to hole_node. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter node has been renamed to hole_node. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cur has been renamed to node. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter interlaced has been renamed to lace. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been renamed to m. | No effect. |
| 2 | 3rd parameter handle_errors has been renamed to nbcfg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter argv has been renamed to __argv. | No effect. |
| 2 | 3rd parameter envp has been renamed to __envp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter src has been renamed to skb. | No effect. |
| 2 | 2nd parameter dst has been renamed to src. | No effect. |
| 3 | 3rd parameter tos has been renamed to dst. | No effect. |
| 4 | 4th parameter oif has been renamed to tos. | No effect. |
| 5 | 5th parameter dev has been renamed to oif. | No effect. |
| 6 | 6th parameter spec_dst has been renamed to dev. | No effect. |
| 7 | 7th parameter itag has been renamed to spec_dst. | No effect. |
| 8 | 8th parameter mark has been renamed to itag. | 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 irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to hdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to hdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter acctflag has been renamed to vm_flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter id has been renamed to nr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter boxes has been renamed to box. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to ring. | No effect. |
| 2 | 2nd parameter file_priv has been renamed to file. | No effect. |
| 3 | 3rd parameter flush_domains has been renamed to request. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter obj has been renamed to gem_obj. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fl has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter clp has been renamed to server. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter clp has been renamed to server. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ipfragok has been renamed to fl_unused. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tsk has been renamed to mm. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter task has been renamed to mm. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter inf has been renamed to mode. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter fs_dir_inode_ops has been renamed to isvfat. | No effect. |
| 2 | 5th parameter isvfat has been renamed to setup. | 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 | 2nd parameter iblock_s has been renamed to iblock. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to mark. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter entry has been renamed to fsn_mark. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file_priv has been renamed to file. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter bus_irq has been renamed to gsi. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq_want has been renamed to from. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter fl has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ipfragok has been renamed to fl. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter alg has been renamed to cipher. | 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 cmd has been renamed to shost. | No effect. |
| 2 | 2nd parameter done has been renamed to cmd. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpumask has been renamed to mask. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter keys has been renamed to key. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter thread has been renamed to threadp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tlbp has been renamed to tlb. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter no_context has been renamed to unused. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter no_context has been renamed to unused. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter irq has been renamed to data. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter mode has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter ns has been renamed to tsk. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter base has been renamed to p. | No effect. |
| 2 | 2nd parameter droot has been renamed to dentry. | No effect. |
| 3 | 3rd parameter dentry has been renamed to buffer. | No effect. |
| 4 | 4th parameter buffer has been renamed to buflen. | No effect. |
| 5 | 5th parameter buflen has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter module has been renamed to ops. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ssec has been renamed to sksec. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ssec has been renamed to sksec. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter stat has been renamed to status. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to xdr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter p has been renamed to xdr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dentry has been renamed to path. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter change_bridge has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wh has been renamed to res. | No effect. |
| 2 | 3rd parameter req has been renamed to offset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wh has been renamed to res. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been renamed to handler. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter req has been renamed to res. | No effect. |
| 2 | 3rd parameter wh has been renamed to speed. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to task. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter mii_data has been renamed to ifr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fl has been renamed to fl6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter set has been renamed to nset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter a has been renamed to from. | No effect. |
| 2 | 2nd parameter b has been renamed to to. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter xprt_list has been renamed to serv. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter info has been renamed to xpt. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sock has been renamed to sk. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sock has been renamed to sk. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter rctxp has been renamed to regs. | No effect. |
| 2 | 4th parameter irq_flags has been renamed to rctxp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter old_ns has been renamed to tsk. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter scanned has been renamed to shrink. | No effect. |
| 2 | 2nd parameter gfp_mask has been renamed to nr_pages_scanned. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dst_p has been renamed to dst_orig. | No effect. |