| Module Name | vmlinux |
|---|---|
| Version #1 | 3.4.69 |
| Version #2 | 3.9.11 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 753 |
|---|---|
| Total Source Files | 1387 |
| Total Objects | 1 |
| Total Symbols / Types | 15440 / 8381 |
| Verdict | Incompatible (56%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 2076 |
| Removed Symbols | High | 833 |
| Problems with Data Types | High | 481 |
| Medium | 1366 | |
| Low | 1293 | |
| Problems with Symbols | High | 148 |
| Medium | 8796 | |
| Low | 318 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 27 |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_ops has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ops has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | 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. |
| 3 | Field start has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field 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. |
| 5 | Field unbind has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 previous has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field information_elements has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field len_beacon_ies has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_information_elements has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 len_proberesp_ies has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 tsf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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. |
| 2 | Field channel_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_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 hierarchy_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. |
| 2 | Field populate has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 post_clone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 subsys_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 beacon_ies_allocated has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ref has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_beacons_nlpid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_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 tgcred has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field split_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tio_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 tio_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 property_ids has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field property_values has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_hadjusted has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field crtc_vadjusted has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 saved_fb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_hit_size has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dma_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 queue_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 queue_slots has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field queuelist has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_buffers_idlelocked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field reclaim_buffers_locked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field reclaim_buffers has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tz_utc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_super has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark_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 free_g_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 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 register_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 request_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. |
| 4 | Field unregister_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 conn_lists has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ignore_misc_bit has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field post_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 aud_synch_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 baseline_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. |
| 3 | Field cea_edid_ver has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 conn_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 eld_ver has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 manufacture_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. |
| 7 | Field monitor_name has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field port_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. |
| 9 | Field product_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. |
| 10 | Field sad has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sad_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. |
| 12 | Field spk_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. |
| 13 | Field support_ai has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 support_hdcp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout 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_end has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_mappable_end has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_mapping has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_total has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field mappable_gtt_total has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dpms has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field setup_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 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. |
| 2 | Field last_fenced_ring has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_rendering_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 num_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. |
| 5 | Field pending_gpu_write has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field adpa has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field allow_batchbuffer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field back_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. |
| 4 | Field 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. |
| 5 | Field c_m has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 chipset_power has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 corr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 counter has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field cpp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 cur_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. |
| 11 | Field current_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. |
| 12 | Field dvob has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 dvoc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 error_completion has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 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. |
| 16 | Field error_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. |
| 17 | Field first_error has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 flip_pending_is_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. |
| 19 | Field front_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. |
| 20 | Field fstart has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gfx_power has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 hangcheck_count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 23 | Field hangcheck_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. |
| 24 | Field has_gem has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 hws_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. |
| 26 | Field idle_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. |
| 27 | Field idle_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. |
| 28 | Field int_edp_connector has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 int_lvds_connector has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 last_acthd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 31 | Field last_acthd_blt has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 last_acthd_bsd has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 | Field last_count1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 34 | Field last_count2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 35 | Field last_gpu_reset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 36 | Field last_instdone has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 37 | Field last_instdone1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 38 | Field last_time1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 39 | Field last_time2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 40 | Field lid_notifier has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 41 | Field lvds has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 42 | Field lvds_val has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 43 | Field mchdev_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. |
| 44 | Field modeset_on_lid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 45 | Field page_flipping has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 46 | Field pch_irq_mask has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 47 | Field pm_iir has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 48 | Field ppcr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 49 | Field pwrctx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 50 | Field r_t has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 51 | Field renderctx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 52 | Field rps_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. |
| 53 | Field rps_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. |
| 54 | Field saveADPA has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 55 | Field saveAR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 56 | Field saveBCLRPAT_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 57 | Field saveBCLRPAT_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 58 | Field saveBLC_CPU_PWM_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 59 | Field saveBLC_CPU_PWM_CTL2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 60 | Field saveBLC_HIST_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 61 | Field saveBLC_PWM_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 62 | Field saveBLC_PWM_CTL2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 63 | Field saveCACHE_MODE_0 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 64 | Field saveCR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 65 | Field saveCURABASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 66 | Field saveCURACNTR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 67 | Field saveCURAPOS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 68 | Field saveCURBBASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 69 | Field saveCURBCNTR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 70 | Field saveCURBPOS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 71 | Field saveCURSIZE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 72 | Field saveDACMASK has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 73 | Field saveDEIER has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 74 | Field saveDEIMR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 75 | Field saveDISP_ARB_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 76 | Field saveDPFC_CB_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 77 | Field saveDPLL_A_MD has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 78 | Field saveDPLL_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 79 | Field saveDPLL_B_MD has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 80 | Field saveDP_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 81 | Field saveDP_C has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 82 | Field saveDP_D has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 83 | Field saveDSPAADDR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 84 | Field saveDSPACNTR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 85 | Field saveDSPAPOS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 86 | Field saveDSPARB has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 87 | Field saveDSPASIZE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 88 | Field saveDSPASTRIDE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 89 | Field saveDSPASURF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 90 | Field saveDSPATILEOFF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 91 | Field saveDSPBADDR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 92 | Field saveDSPBCNTR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 93 | Field saveDSPBPOS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 94 | Field saveDSPBSIZE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 95 | Field saveDSPBSTRIDE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 96 | Field saveDSPBSURF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 97 | Field saveDSPBTILEOFF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 98 | Field saveDVOA has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 99 | Field saveDVOB has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 100 | Field saveDVOC has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 101 | Field saveFBC_CFB_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 102 | Field saveFBC_CONTROL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 103 | Field saveFBC_CONTROL2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 104 | Field saveFBC_LL_BASE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 105 | Field saveFDI_RXA_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 106 | Field saveFDI_RXA_IMR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 107 | Field saveFDI_RXB_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 108 | Field saveFDI_RXB_IMR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 109 | Field saveFDI_TXA_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 110 | Field saveFDI_TXB_CTL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 111 | Field saveFENCE has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 112 | Field saveFPA0 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 113 | Field saveFPB0 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 114 | Field saveFPB1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 115 | Field saveGR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 116 | Field saveGTIER has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 117 | Field saveGTIMR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 118 | Field saveHBLANK_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 119 | Field saveHBLANK_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 120 | Field saveHSYNC_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 121 | Field saveHSYNC_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 122 | Field saveHTOTAL_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 123 | Field saveHTOTAL_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 124 | Field saveHWS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 125 | Field saveIER has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 126 | Field saveIIR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 127 | Field saveIMR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 128 | Field saveLVDS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 129 | Field saveMCHBAR_RENDER_STANDBY has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 130 | Field saveMI_ARB_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. |
| 131 | Field saveMSR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 132 | Field savePCH_DREF_CONTROL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 133 | Field savePCH_PORT_HOTPLUG has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 134 | Field savePFA_CTL_1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 135 | Field savePFA_WIN_POS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 136 | Field savePFA_WIN_SZ has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 137 | Field savePFB_CTL_1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 138 | Field savePFB_WIN_POS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 139 | Field savePFB_WIN_SZ has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 140 | Field savePFIT_CONTROL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 141 | Field savePFIT_PGM_RATIOS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 142 | Field savePIPEACONF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 143 | Field savePIPEASRC has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 144 | Field savePIPEASTAT has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 145 | Field savePIPEA_DATA_M1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 146 | Field savePIPEA_DATA_N1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 147 | Field savePIPEA_DP_LINK_M has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 148 | Field savePIPEA_DP_LINK_N has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 149 | Field savePIPEA_GMCH_DATA_M has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 150 | Field savePIPEA_GMCH_DATA_N has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 151 | Field savePIPEA_LINK_M1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 152 | Field savePIPEA_LINK_N1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 153 | Field savePIPEBCONF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 154 | Field savePIPEBSRC has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 155 | Field savePIPEBSTAT has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 156 | Field savePIPEB_DATA_M1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 157 | Field savePIPEB_DATA_N1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 158 | Field savePIPEB_DP_LINK_M has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 159 | Field savePIPEB_DP_LINK_N has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 160 | Field savePIPEB_GMCH_DATA_M has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 161 | Field savePIPEB_GMCH_DATA_N has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 162 | Field savePIPEB_LINK_M1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 163 | Field savePIPEB_LINK_N1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 164 | Field savePP_CONTROL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 165 | Field savePP_DIVISOR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 166 | Field savePP_OFF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 167 | Field savePP_OFF_DELAYS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 168 | Field savePP_ON has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 169 | Field savePP_ON_DELAYS has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 170 | Field saveSR has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 171 | Field saveSWF0 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 172 | Field saveSWF1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 173 | Field saveSWF2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 174 | Field saveTRANSACONF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 175 | Field saveTRANSBCONF has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 176 | Field saveTRANS_HBLANK_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 177 | Field saveTRANS_HBLANK_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 178 | Field saveTRANS_HSYNC_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 179 | Field saveTRANS_HSYNC_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 180 | Field saveTRANS_HTOTAL_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 181 | Field saveTRANS_HTOTAL_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 182 | Field saveTRANS_VBLANK_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 183 | Field saveTRANS_VBLANK_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 184 | Field saveTRANS_VSYNC_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 185 | Field saveTRANS_VSYNC_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 186 | Field saveTRANS_VTOTAL_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 187 | Field saveTRANS_VTOTAL_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 188 | Field saveVBLANK_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 189 | Field saveVBLANK_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 190 | Field saveVGA0 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 191 | Field saveVGA1 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 192 | Field saveVGACNTRL has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 193 | Field saveVGA_PD has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 194 | Field saveVSYNC_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 195 | Field saveVSYNC_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 196 | Field saveVTOTAL_A has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 197 | Field saveVTOTAL_B has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 198 | Field save_palette_a has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 199 | Field save_palette_b has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 200 | Field sr01 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 201 | Field tex_lru_log_granularity has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 202 | Field vblank_pipe has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_period has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field last_probe_resp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 ssid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_smps has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_dynamic_ps has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dynamic_ps_user_timeout has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 hw_roc_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. |
| 4 | Field hw_roc_channel_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field hw_roc_duration has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 hw_roc_for_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. |
| 7 | Field hw_roc_skb has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_roc_skb_for_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. |
| 9 | Field power_constr_level has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 recalc_smps has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 running_rx_handler has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_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. |
| 13 | Field sched_scan_ies has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sched_scanning has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 tmp_channel_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 16 | Field wmm_acm has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 work_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. |
| 18 | Field work_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. |
| 19 | Field work_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 ht_information_ie has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sent_assoc has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_opmode_valid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 ch_switch_elem has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ch_switch_elem_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. |
| 3 | Field pwr_constr_elem_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. |
| 4 | Field wpa has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 wpa_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 off has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout 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 removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_dport has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmtu_expires has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field pmtu_learned has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pmtu_orig has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 redirect_learned has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtsize has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field slot has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 trkid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fops has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dpms_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 idle_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 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. |
| 2 | Field irq_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 irq_mask has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field 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. |
| 5 | Field waiting_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 user_ns has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field backup_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. |
| 2 | Field ftp_app has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 master_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. |
| 4 | Field sync_mcast_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. |
| 5 | Field sync_buff has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 sync_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 nat_bysource has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field current_rt_cache_rebuild_count has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field nat_htable_size has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field rt_genid has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field sysctl_rt_cache_rebuild_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 serial_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 acpi_handle has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tsk has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_filter_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 channel_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field last_tsf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tx_frags has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field faultstamp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout 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_interval has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field token_priority has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_stat has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_longterm has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wext_nlevents has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gro_receive has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_segment has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_send_check has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_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 help has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_ip has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_table has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ctl_table_header has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_compat_table has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ctl_compat_table_header has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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_id_uniquifier has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field server_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. |
| 3 | Field cl_boot_time has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field impl_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 wb_complete has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sa_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 sr_renewal_time has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field sr_session has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir_attr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | Field lseg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 npages has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pagevec has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 req has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ds_commit_index has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 lseg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 npages has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 pagevec has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 req has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field secondary has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field subordinate has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcie_type has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field can_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field info has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hit_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 latency_ticks has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field power has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 time has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field usage has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gro_receive has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_segment has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_send_check has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gro_receive has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_segment has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 gso_send_check has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field n_rp_need_fqs has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field passed_quiesce_gpnum has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqs_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. |
| 2 | Field fqs_need_gp has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 onofflock has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_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. |
| 2 | Field rt_key_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 rt_key_src has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_oif has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_route_iif has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 load_avg has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_stime has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field replacement_session_keyring has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 scm_work_list has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field prev_utime has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 dentry_open has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tun_dev_post_create has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_cgrp_prioidx has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout 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_sndmsg_off has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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_sndmsg_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_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 skc_rcv_saddr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_flavor has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bytes_acked has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cooling_devices has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tc2 has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure 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 real_raw has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field read_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 read_buf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field echo_buf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field process_char_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. |
| 6 | Field canon_column has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 lnext has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 buf has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 9 | Field echo_pos has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 10 | Field read_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. |
| 11 | Field echo_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. |
| 12 | Field erasing has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 icanon has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 read_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. |
| 15 | Field read_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. |
| 16 | Field read_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. |
| 17 | Field column has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 echo_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. |
| 19 | Field raw has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 atomic_read_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. |
| 21 | Field canon_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. |
| 22 | Field canon_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. |
| 23 | Field num_overrun has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 output_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. |
| 25 | Field overrun_time has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 26 | Field low_latency has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cdev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field children has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field usbfs_dentry has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mapping has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum ieee80211_agg_stop_reason 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 initiator 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 reason of type enum ieee80211_agg_stop_reason 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 initiator 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 uid has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ioc of type struct io_context* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct perf_event* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qid of type struct kqid 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 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 qid of type struct kqid 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 type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 3rd middle parameter 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 qid of type struct kqid 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 type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 3rd middle parameter 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 color of type unsigned long has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter color of type unsigned long has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter color of type unsigned long has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dev of type struct drm_device* 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 dev of type struct drm_device* 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 flags has been changed from int (4 bytes) to unsigned short (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter bio of type struct bio* 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 n has been changed from int (4 bytes) to __u64 (8 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter siginfo of type siginfo_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 signr 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 regs has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buf of type unsigned char* 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 eld 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 tx has been changed from bool (1 byte) to enum ieee80211_agg_stop_reason (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 tlb of type struct mmu_gather* 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 cache_level 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 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter saddr of type struct in6_addr const* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Parameter sport of type __be16 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 saddr of type __be32 const has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | Parameter sport of type __be16 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 base of type struct inet_peer_base* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter family 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 device of type dev_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 gpu_pdev of type struct pci_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter st of type struct sg_table* 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 sg_list has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 2nd middle parameter sg_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 | 1st middle parameter intel_encoder 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 intel_encoder has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter perm of type key_perm_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 | 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 | 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 wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd 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. |
| 3 | 5th middle parameter channel_type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 4 | 6th middle parameter channel_type_valid 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 wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 4th middle parameter channel_type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 4th middle parameter channel_type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th 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 | The pointer level of 6th parameter msgflg 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 4th parameter nd has been changed from struct nameidata* (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 user_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 user_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 user_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 qid of type struct kqid has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 2nd middle parameter 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 helper of type struct nf_conntrack_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. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter pf 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 lockowner of type struct nfs_lockowner 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 | 4th middle parameter fl_owner 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 wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter netdev 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 | 5th middle parameter channel_type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 2nd middle parameter netdev 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 | 5th middle parameter channel_type has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_cred of type struct cred* 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 zonelist of type struct zonelist* 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 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. |
| 3 | Parameter order of type int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 4 | 1st middle parameter regs 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. |
| 5 | 2nd middle parameter error_code 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 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 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. |
| 3 | 2nd middle parameter mnt has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pgdat of type pg_data_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 compl_ops of type struct nfs_pgio_completion_ops 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 | Type of 1st parameter key has been changed from struct key* (4 bytes) to struct key const* (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | 4th 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 | 4th 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 | Parameter user_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 | The parameter child_tid became passed at the different offset on the stack (12 instead of 0). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter regs became passed at the different offset on the stack (16 instead of 4). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dev of type struct device* 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 | Parameter type of type enum dev_pm_qos_req_type 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 neigh has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter src_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 | 4th middle parameter ts 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. |
| 2 | 5th middle parameter tsage 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 wiphy of type struct wiphy* 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 wiphy of type struct wiphy* 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 path of type struct path* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter mnt has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 3 | 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 | Parameter flags of type int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock const* (4 bytes) to struct sock* (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock const* (4 bytes) to struct sock* (4 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter orig 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 5th parameter tc1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
| 2 | The pointer level of 6th parameter tc2 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 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 | Parameter user_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. |
| 2 | Parameter pid_ns of type struct pid_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 tailroom of type size_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 | 5th middle parameter ie 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 ns 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 prep of type struct key_preparsed_payload* 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 data 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 prep of type struct key_preparsed_payload* 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 data 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 sdata of type struct ieee80211_sub_if_data* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter vif 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 sdata of type struct ieee80211_sub_if_data* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 1st middle parameter vif 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 buffer_len of type size_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 chan 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 band of type enum ieee80211_band has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter_flags of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter_flags of type u32 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter status of type u16 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 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 walk_state of type struct acpi_walk_state* 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 walk_state of type struct acpi_walk_state* 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 user_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 user_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 user_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 xprt of type struct rpc_xprt* 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 | Size of field port has been changed from 164 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 | Size of field dispatch has been changed from 8 bytes to 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 handler_obj has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field device 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 device_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field system_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field system_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field system_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field system_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field system_notify has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field name has been changed from char* (4 bytes) to char[16] (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 busnum 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 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 match has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field find_bridge 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 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. |
| 2 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 pnp has been changed from 84 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field power has been changed from 288 bytes to 108 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field wakeup has been changed from 72 bytes to 36 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lockable 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 states has been changed from 280 bytes to 100 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 flags has been changed from 1 byte to 2 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 resources has been changed from struct acpi_handle_list (44 bytes) to struct list_head (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 | Type of field resources has been changed from struct acpi_handle_list (44 bytes) to struct list_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ops has been changed from 32 bytes to 12 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field drv has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field os_accessible has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field subsystem_id has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field intr_status has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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 | Size of field wq has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 cpu_mask_to_apicid 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 gid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field uid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 mark has been changed from 72 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mark has been changed from 72 bytes to 64 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. | Layout of 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 completions has been changed from struct prop_local_percpu (36 bytes) to struct fprop_local_percpu (32 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 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 bp has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field chunks has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field chunkshift has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field file has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field file_pages has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 6 | Field filemap has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field filemap_attr has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 8 | Field last_page_size has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 9 | Field lock has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 10 | Field missing_pages has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 11 | Field pages has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 12 | Field sb_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 bi_cnt has been changed from 12 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field bi_end_io has been changed from 14 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field bi_io_vec has been changed from 13 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field bi_max_vecs has been changed from 11 to 13. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field should_sort 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_write_same_sectors has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field root_rl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_rqs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 bypass_depth has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 request_fn_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 nr_rqs_elvpriv has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 delay_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Size of field backing_dev_info has been changed from 384 bytes to 380 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 8 | Size of field limits has been changed from 60 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. |
| 9 | Type of field queue_lock has been changed from spinlock_t* (4 bytes) to spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache_request has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 IEEE80211_NUM_BANDS has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_beacon_bss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | The relative position of field beacon_ies 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. |
| 4 | The relative position of field beacon_interval 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. |
| 5 | The relative position of field bssid has been changed from 1 to 6. | 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 capability 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 proberesp_ies 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. |
| 8 | The relative position of field signal 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field mfp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field mcast_rate has been changed from int[2] (8 bytes) to int[3] (12 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 get_et_sset_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field get_et_stats has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field get_et_strings has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 libertas_set_mesh_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. |
| 5 | Field set_cqm_txe_config has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field set_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. |
| 7 | Field set_monitor_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. |
| 8 | Field set_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 flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | Type of field rates has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | The relative position of field wiphy has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field rssi_thold has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshNbrOffsetMaxNeighbor has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_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 chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field sync_method has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Type of field mcast_rate has been changed from int[2] (8 bytes) to int[3] (12 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 rxrate has been changed from 4 bytes to 6 bytes. | 1) Size of the inclusive type has been 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 txrate has been changed from 4 bytes to 6 bytes. | 1) Size of the inclusive type has been 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 rx_bytes has been changed from u32 (4 bytes) to u64 (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field tx_bytes has been changed from u32 (4 bytes) to u64 (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field extended_capabilities has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field extended_capabilities_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field extended_capabilities_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 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field wowlan has been changed from 16 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. |
| 6 | Type of field bands has been changed from struct ieee80211_supported_band*[2] (8 bytes) to struct ieee80211_supported_band*[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | Field wext 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 address has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ibss_fixed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 identifier has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 p2p_started has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 preset_chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field ap_unexpected_nlpid 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 wext 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 allcg_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 cgroup_ida has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 top_cgroup has been changed from 232 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 free_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 allcg_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 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. |
| 4 | Field callback_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. |
| 5 | Field files has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field subsys has been changed from struct cgroup_subsys_state*[32] (128 bytes) to struct cgroup_subsys_state*[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 7 | The relative position of field pidlists 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. |
| 8 | The relative position of field pidlist_mutex 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. |
| 9 | The relative position of field release_list has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field base_cftset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_cftypes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cftsets has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 css_free has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Size of field idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field subsys has been changed from struct cgroup_subsys_state*[32] (128 bytes) to struct cgroup_subsys_state*[4] (16 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field parts has been changed from 26624 bytes to 4 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The pointer level of field parts 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 resume 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 suspend 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 auto_assign_helper_warned has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field nat_bysource has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 nat_htable_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 helper_sysctl_header has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl_auto_assign_helper has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 nf_ct_proto has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tmpl has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field port has been changed from 124 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 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 poll_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field numa_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_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 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 | Size of field pub has been changed from 56 bytes to 36 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 | Field proberesp_ies_allocated has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_registrations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_registrations_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 dfs_update_channels_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 num_running_ifaces has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 num_running_monitor_ifaces has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 wdev_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. |
| 7 | Size of field wiphy has been changed from 416 bytes to 448 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 220 bytes to 224 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 c_detect_tlb has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 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 | Field initialized has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_cpu has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj_driver has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field states_usage has been changed from 160 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 disable has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field process_keyring has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field session_keyring has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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_alias has been changed from struct list_head to struct hlist_node of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_weak_revalidate 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 len has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field hash has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_supported has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field max_io_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field num_write_bios has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 num_write_same_bios has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 per_bio_data_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. |
| 6 | Field split_discard_bios has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | This type became opaque. | The internal structure of this type is hidden in the new library version and may be different. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field archdata has been changed from 4 bytes to 0 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 acpi_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 | Field throttle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfn_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 get_sgtable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field display_info has been changed from 80 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field kdev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 invert_dimensions has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | 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. |
| 3 | Size of field mode has been changed from 200 bytes to 196 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field hwmode has been changed from 200 bytes to 196 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 raw_edid has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 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. |
| 2 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fb_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 crtc_idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field output_poll_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field c has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field hfreq_start_khz has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field j has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field k has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field m has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 6 | Field sec_gtf_toggle has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 44 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 | Size of field mode_set has been changed from 36 bytes to 28 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_color has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field scan_hit_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. |
| 3 | Size of field head_node has been changed from 32 bytes to 36 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field color has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 ctx_idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field mode_config has been changed from 320 bytes to 352 bytes. | 1) Size of the inclusive type has been 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 object_name_idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Field queue_reserved has been removed from the middle position of this structural type. | 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_get_sg_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. |
| 2 | Field gem_prime_import_sg_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. |
| 3 | Field gem_prime_pin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gem_prime_vmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gem_prime_vunmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fbs_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 object_idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The pointer level of field pid has been increased from 0 to 1. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kdev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 drv has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flags has been changed from int (4 bytes) to unsigned short (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field pending_confirm 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 relative position of field __refcnt has been changed from 17 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field __use has been changed from 18 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field error has been changed from 12 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field header_len has been changed from 14 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field lastuse has been changed from 19 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field obsolete has been changed from 13 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field trailer_len has been changed from 15 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field unnamed0 has been changed from 5 to 19. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field redirect 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 get_hw_state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fifo_stall_task has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field phy_info_task has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field watchdog_task has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobject has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 efi_pstore_info has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash has been changed from struct hlist_head* (4 bytes) to struct hlist_head[64] (256 bytes). | 1) Size of the inclusive type has been 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 registered has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field hash has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 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 time_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tz_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field fsinfo_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 s_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 | Size of field options has been changed from 28 bytes to 32 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field delete has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field thoff 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 | Type of field i_mmap has been changed from struct prio_tree_root (8 bytes) to struct rb_root (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field i_data has been changed from 96 bytes to 92 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | The relative position of field i_bytes has been changed from 18 to 19. | 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 unnamed1 has been changed from 29 to 30. | 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 dirtied_when has been changed from 24 to 25. | 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 i_ctime 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 i_version has been changed from 32 to 31. | 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_blocks 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. |
| 8 | The relative position of field i_blkbits has been changed from 31 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 i_count has been changed from 30 to 32. | 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_state has been changed from 22 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 i_mutex has been changed from 23 to 24. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field i_lru has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field i_atime has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field i_sb_list has been changed from 28 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field i_size has been changed from 20 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field i_lock has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field i_mtime has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field i_hash has been changed from 25 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field i_size_seqcount has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field i_wb_list has been changed from 26 to 27. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fiemap has been changed from 21 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field truncate 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 lm_release_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 s_writers has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field s_lock has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field s_frozen has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field s_wait_unfrozen has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field s_dirt 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 i_dentry has been changed from struct list_head (8 bytes) to struct hlist_head (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fsn_fa has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field mark_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 fa has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field buffer_iter has been changed from struct ring_buffer_iter*[8] (32 bytes) to struct ring_buffer_iter** (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field ent 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. |
| 3 | The relative position of field idx 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. |
| 4 | The relative position of field seq 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 | The relative position of field ts has been changed from 15 to 14. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The pointer level of field buffer_iter 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 cpu has been changed from 14 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field ent_size has been changed from 13 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field leftover has been changed from 12 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field lost_events has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field pos has been changed from 16 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field started has been changed from 8 to 17. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dwork has been changed from 68 bytes to 76 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 part0 has been changed from 292 bytes to 300 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_sects_seq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field __dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 rcu_head 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 uuid has been changed from u8[16] (16 bytes) to char[37] (37 bytes). | 1) Size of the inclusive type has been changed. 2) Previous 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 phy has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 rsrc_start has been changed from u64 (8 bytes) to resource_size_t (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field rsrc_len has been changed from u64 (8 bytes) to resource_size_t (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ops has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ops 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 conn_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 hash_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. |
| 3 | Field power_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. |
| 4 | Field power_filter has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field power_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. |
| 6 | Field power_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. |
| 7 | Field power_off_acct has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power_on_acct has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power_transition has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 power_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. |
| 11 | Field user_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. |
| 12 | Size of field patch_ops has been changed from 44 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field resume has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field stream 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field chmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field gated_jack has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | Field 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 dev_rdesc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_rsize has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 input_configured has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | Size of field driver has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field field has been changed from struct hid_field*[128] (512 bytes) to struct hid_field*[256] (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 | Field usage_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field hugepage_activelist has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rar_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 acpi_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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member PCH_CPT has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member PCH_IBX has been changed from 0 to 1. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field bound_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 shrinker_no_lock_stealing has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gtt_space has been changed from 88 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field stolen has been changed from 88 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Size of field retire_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 6 | Field deferred_free_list has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | Field flushing_list has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | Field pinned_list has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | Field wedged 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 crtc_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. |
| 2 | Field crtc_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. |
| 3 | Field modeset_global_resources has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 update_linetime_wm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field force_wake_get 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 force_wake_put 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 fdi_link_train has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field init_clock_gating has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field write_eld has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field page_cpu_valid 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 pending_flip 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 | The relative position of field pages has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field console_resume_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 ddi_plls has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 dpio_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field enable_hotplug_processing has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gmbus_wait_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 gpio_mmio_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. |
| 7 | Field gpu_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. |
| 8 | Field gt has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 10 | Field hw_contexts_disabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field ips has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 l3_parity has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 last_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. |
| 14 | Field modeset_restore has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 modeset_restore_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. |
| 16 | Field num_pch_pll has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pch_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. |
| 18 | Field pch_plls has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 pm_qos has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 slab has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Size of field display has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 23 | Size of field fence_regs has been changed from 320 bytes to 256 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 24 | Size of field ring has been changed from 660 bytes to 588 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 25 | Type of field sprite_scaling_enabled has been changed from bool (1 byte) to unsigned int (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 26 | Type of field gmbus has been changed from struct intel_gmbus* (4 bytes) to struct intel_gmbus[6] (2472 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 27 | The relative position of field child_dev has been changed from 70 to 68. | 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 compressed_fb has been changed from 73 to 71. | 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 lvds_border_bits has been changed from 59 to 57. | 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 lvds_downclock has been changed from 67 to 65. | 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 lvds_downclock_avail has been changed from 66 to 64. | 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 mchbar_need_disable has been changed from 71 to 69. | 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 mm has been changed from 57 to 55. | 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 orig_clock has been changed from 68 to 66. | 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 pch_pf_pos has been changed from 60 to 58. | 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 pipe_to_crtc_mapping has been changed from 63 to 61. | 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 plane_to_crtc_mapping has been changed from 62 to 60. | 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 render_reclock_avail has been changed from 65 to 63. | 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 sdvo_mappings has been changed from 58 to 56. | 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 backlight has been changed from 76 to 74. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field broadcast_rgb_property has been changed from 77 to 75. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field child_dev_num has been changed from 69 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field compressed_llb has been changed from 74 to 72. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field fbdev has been changed from 75 to 73. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field force_audio_property has been changed from 78 to 76. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field no_fbc_reason has been changed from 72 to 70. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field pch_pf_size has been changed from 61 to 59. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field pending_flip_queue has been changed from 64 to 62. | Applications will access incorrect memory when attempting to access this field. |
| 49 | Field fmax has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 50 | Field max_delay has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 51 | Field min_delay has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 52 | Field saveAR_INDEX has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 53 | Field saveLBB has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field display_mmio_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field is_haswell has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_valleyview has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hint has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prefix has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 bitmap has been changed from unsigned long (4 bytes) to unsigned long[8] (32 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field ary has been changed from struct idr_layer*[32] (128 bytes) to struct idr_layer*[256] (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. |
| 4 | Field rcu_head 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 device_ts_presp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_bc_mc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field dtim_count has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field num_sta_authorized has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field num_sta_ps has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 5 | Field ps_bc_buf has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 6 | Field tim has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_frame_registrations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field csa_connection_drop_work has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field status_acked has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field estab_plinks has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 4 | Size of field mshstats has been changed from 28 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 5 | Size of field mshcfg has been changed from 44 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chanctx_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 chanctx_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. |
| 3 | Field hw_scan_ies_bufsize has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 ifa6_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. |
| 5 | Field in_reconfig has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 p2p_sdata has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 radar_detected_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. |
| 8 | Field roc_cookie_counter has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 roc_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 rx_chains has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 11 | Field rx_path_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. |
| 12 | Field sched_scan_sdata has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Size of field ack_status_frames has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 14 | Size of field hw has been changed from 84 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. |
| 15 | Size of field scan_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 16 | Type of field agg_queue_stop has been changed from atomic_t[4] (16 bytes) to atomic_t[16] (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. |
| 17 | Type of field pending has been changed from struct sk_buff_head[4] (64 bytes) to struct sk_buff_head[16] (256 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 18 | Type of field queue_stop_reasons has been changed from unsigned long[4] (16 bytes) to unsigned long[16] (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. |
| 19 | The relative position of field ack_status_frames has been changed from 105 to 104. | 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 ack_status_lock has been changed from 106 to 105. | 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 hw_roc_start has been changed from 102 to 101. | 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 napi has been changed from 108 to 107. | 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 napi_dev has been changed from 107 to 106. | 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 _oper_channel_type has been changed from 64 to 66. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field csa_channel has been changed from 66 to 64. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field hw_roc_done has been changed from 103 to 102. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_ht_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 ap_vht_cap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 need_beacon has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ie has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field ie_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_power_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 cleanup_stations has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field cleanup_stations_lock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field cleanup_stations_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. |
| 5 | Field dfs_cac_timer_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. |
| 6 | Field radar_required has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field recalc_smps has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 9 | Field suspend_bss_conf has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 user_power_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. |
| 11 | Size of field u has been changed from 460 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. |
| 12 | Size of field wdev has been changed from 404 bytes to 188 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 13 | Size of field vif has been changed from 132 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. |
| 14 | Type of field rc_rateidx_mask has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 15 | Field old_idle has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field awake_window has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ch_switch_ie has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field ht_operation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 opmode_notif has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vht_operation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field estab_plinks 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 ibss has been changed from 168 bytes to 172 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 mesh has been changed from 356 bytes to 712 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 mgd has been changed from 460 bytes to 476 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 cnf has been changed from 80 bytes to 84 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field icsk_inet has been changed from 560 bytes to 556 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field net_frag_header_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field get_peer 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 fragments has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field fragments_tail has been changed from 7 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field last_in has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field len has been changed from 9 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field list has been changed from 0 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field lock has been changed from 3 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field meat has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field net has been changed from 1 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field stamp has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field timer has been changed from 5 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field qsize 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. |
| 2 | The relative position of field secret_timer has been changed from 5 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 constructor has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field destructor has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field match has been changed from 10 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field rnd has been changed from 2 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field secret_interval has been changed from 4 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field skb_free has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru_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 | Type of field mem has been changed from struct atomic_t (4 bytes) to struct percpu_counter (24 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | The relative position of field lru_list has been changed from 2 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field mem 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field fastuid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 fastreuse has been changed from short (2 bytes) to signed char (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dst has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field length has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 36 bytes to 28 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_dst_ifindex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 416 bytes to 420 bytes. | 1) Size of the inclusive type has been 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 cork has been changed from 96 bytes to 88 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 | Field inet_num has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_dport has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field tw_num has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cnf has been changed from 108 bytes to 112 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from int[25] (100 bytes) to int[26] (104 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| 2 | Field tcp_ts_stamp 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 unnamed1 has been changed from 16 bytes to 8 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 work has been changed from 68 bytes to 76 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 sync has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 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 legacy_minors has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 cursor has been changed from struct intel_cursor_error_state[2] (32 bytes) to struct intel_cursor_error_state[3] (48 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field pipe has been changed from struct intel_pipe_error_state[2] (64 bytes) to struct intel_pipe_error_state[3] (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. |
| 3 | Type of field plane has been changed from struct intel_plane_error_state[2] (56 bytes) to struct intel_plane_error_state[3] (84 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 base has been changed from 756 bytes to 864 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_transcoder has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field dspaddr_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. |
| 3 | Field primary_disabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field unpin_work_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. |
| 5 | Size of field base has been changed from 476 bytes to 788 bytes. | 1) Size of the inclusive type has been 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 no_pll 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 use_pll_a has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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. |
| 3 | Field get_hw_state has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field new_crtc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 post_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. |
| 6 | Field pre_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. |
| 7 | Field pre_pll_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. |
| 8 | Size of field base has been changed from 44 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. |
| 9 | Field clone_mask has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field helper has been changed from 120 bytes to 112 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field base has been changed from 92 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pending has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gpu_caches_dirty has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_enable_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field set_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. |
| 4 | Field map 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 lock has been changed from struct mutex (20 bytes) to spinlock_t (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field lock has been changed from 6 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field curr_lock 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 dev_id has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field flags has been changed from 1 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field irq has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field next has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field percpu_dev_id has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field thread has been changed from 7 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field thread_fn has been changed from 6 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_ref has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_mp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fc_mp_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field fc_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 rt6i_nsiblings 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 rt6i_genid 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 rt6i_siblings 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 rt6i_flow_cache_genid has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field rt6i_peer_genid 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 tclassid 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 r has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field backup_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 threads_mask has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field sysctl_sync_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. |
| 4 | Field ms has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field sysctl_backup_only has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl_pmtu_disc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl_sync_ports has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl_sync_qlen_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. |
| 9 | Field sysctl_sync_refresh_period has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl_sync_sock_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. |
| 11 | Size of field defense_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ipcs_idr 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 mq_msg_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. |
| 2 | Field mq_msgsize_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. |
| 3 | Size of field ids has been changed from 132 bytes to 156 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 mroute_do_assert has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field mroute_do_pim has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_tcp_ecn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field fib_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. |
| 3 | Field fib_has_custom_rules has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tcp_metrics_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. |
| 5 | Field xfrm4_hdr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fib_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. |
| 7 | Field peers has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tcp_metrics_hash_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. |
| 9 | Size of field frags has been changed from 28 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. |
| 10 | The relative position of field fib_table_hash has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field fibnl has been changed from 8 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field icmp_sk has been changed from 9 to 10. | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndisc_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_dst_cookie has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ip6table_nat has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field peers has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sysctl has been changed from 48 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Size of field frags has been changed from 28 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 | Field xfrm6_hdr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field icmp_hdr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 route_hdr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent_irq 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 preparse has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_preparse has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_used_at has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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 | Size of field unnamed0 has been changed from 4 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 4 | The relative position of field unnamed0 has been changed from 6 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field serial_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 graveyard_link 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 revoked_at 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 expiry 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 KMSG_DUMP_EMERG has been changed from 2 to 3. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member KMSG_DUMP_HALT has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member KMSG_DUMP_OOPS has been changed from 1 to 2. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member KMSG_DUMP_PANIC 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 KMSG_DUMP_POWEROFF has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member KMSG_DUMP_RESTART has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | 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 max_reason has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Type of field registered has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 4 | The relative position of field dump 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. |
| 5 | The relative position of field list 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 | Size of field kp has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ainsn has been changed from 8 bytes to 12 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kp has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kp has been changed from 64 bytes to 68 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field delayed_set_value has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_brightness_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 devslp_timing has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 tdev has been changed from 220 bytes to 224 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 | Field acpi_handle has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tdev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field device has been changed from 2704 bytes to 2720 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 hotplug_task has been changed from 68 bytes to 76 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field link has been changed from 3280 bytes to 3300 bytes. | 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 sff_pio_task has been changed from 68 bytes to 76 bytes. | 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 tdev has been changed from 220 bytes to 224 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Field acpi_handle 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 end_eh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_eh has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 cmdbuf has been changed from unsigned char[6] (6 bytes) to unsigned char[8] (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sta 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 rates has been changed from struct ieee80211_tx_rate[5] (15 bytes) to struct ieee80211_tx_rate[4] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rates has been changed from struct ieee80211_tx_rate[5] (15 bytes) to struct ieee80211_tx_rate[4] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The relative position of field ack_signal has been changed from 2 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field ampdu_ack_len 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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field driver_rates has been changed from struct ieee80211_tx_rate[5] (15 bytes) to struct ieee80211_tx_rate[4] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ibss_creator has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 4 | Field sync_device_ts has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 5 | Field sync_dtim_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. |
| 6 | Field sync_tsf has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field arp_addr_cnt has been changed from u8 (1 byte) to 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. |
| 8 | Type of field mcast_rate has been changed from int[2] (8 bytes) to int[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field radar_enabled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chanctx_data_size has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field conf has been changed from 36 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_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. |
| 2 | Field set_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. |
| 3 | Field sta_rc_update has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field start_ap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 stop_ap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_reference has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field device_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. |
| 3 | Field vendor_radiotap_bitmap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 vendor_radiotap_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. |
| 5 | Field vht_nss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field antenna has been changed from int (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 7 | Type of field band has been changed from enum ieee80211_band (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 8 | Type of field freq has been changed from int (4 bytes) to u16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 9 | Type of field rate_idx has been changed from int (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 10 | Type of field rx_flags has been changed from unsigned int (4 bytes) to u8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 11 | Type of field signal has been changed from int (4 bytes) to s8 (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 12 | The relative position of field antenna has been changed from 4 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field band has been changed from 1 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field flag has been changed from 6 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field rate_idx has been changed from 5 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field rx_flags has been changed from 7 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field signal has been changed from 3 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_cap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 supp_rates has been changed from u32[2] (8 bytes) to u32[3] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chanctx_conf has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field hw_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. |
| 3 | Size of field bss_conf has been changed from 116 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 control has been changed from 28 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field status has been changed from 24 bytes to 20 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_space has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field space has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field new_data_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field bitmap_info 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. |
| 2 | Type of field resync_mismatches has been changed from sector_t to struct atomic64_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field bucket has been changed from struct rmc_entry[256] (6144 bytes) to struct list_head[256] (2048 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_exe_file_vmas 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 rb_subtree_gap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 vm_rb 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. |
| 3 | The relative position of field vm_flags 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. |
| 4 | The relative position of field vm_start has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field vm_end has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field vm_mm has been changed from 0 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field vm_page_prot has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field vm_next has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field vm_prev has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 27 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field free_list has been changed from struct list_head[5] (40 bytes) to struct list_head[4] (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 | Type of field vm_stat_diff has been changed from s8[27] (27 bytes) to s8[28] (28 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 pfmemalloc_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. |
| 2 | Field reclaim_nodes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 node_zones has been changed from 3328 bytes to 3072 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 compact_blockskip_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. |
| 2 | Field compact_cached_free_pfn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 compact_cached_migrate_pfn has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 compact_considered has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 compact_defer_shift has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 compact_order_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 managed_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. |
| 8 | Size of field free_area has been changed from 484 bytes to 396 bytes. | 1) Size of the inclusive type has been 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 lruvec 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. |
| 10 | Type of field vm_stat has been changed from atomic_long_t[27] (108 bytes) to atomic_long_t[28] (112 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id has been changed from __u8[16] (16 bytes) to __u8[9] (9 bytes). | 1) Size of the inclusive type has been changed. 2) Previous 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 bInterfaceNumber has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_inum has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | 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. |
| 3 | 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 intent 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 gc_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nf_frag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ifindex has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 proc_inum has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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. |
| 5 | Size of field ct has been changed from 88 bytes to 308 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Size of field ipv6 has been changed from 384 bytes to 576 bytes. | 1) Size of the inclusive type has been 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 packet has been changed from 8 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. |
| 8 | Size of field ipv4 has been changed from 168 bytes to 384 bytes. | 1) Size of the inclusive type has been 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 xt has been changed from 104 bytes to 108 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dev_list has been changed from 8 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field gro_count has been changed from 6 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field gro_list has been changed from 9 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field poll has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field poll_lock has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field poll_owner has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field skb has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field pm_qos_req has been changed from 92 bytes to 100 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 hw_enc_features has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field mrp_port 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 qdisc_tx_busylock 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 | Field upper_dev_list has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | The relative position of field _rx has been changed from 58 to 57. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field _tx has been changed from 65 to 64. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field ax25_ptr has been changed from 51 to 50. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field base_addr has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field broadcast has been changed from 56 to 55. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field destructor has been changed from 82 to 81. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field dev_addr has been changed from 54 to 53. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field dev_addrs has been changed from 55 to 54. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field dev_list has been changed from 9 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field dismantle has been changed from 80 to 79. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field features has been changed from 12 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field garp_port has been changed from 86 to 85. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field group has been changed from 96 to 95. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field hw_features has been changed from 13 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field ieee80211_ptr has been changed from 52 to 51. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field ifalias has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field index_hlist has been changed from 77 to 76. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field ingress_queue has been changed from 64 to 63. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field irq has been changed from 7 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field last_rx has been changed from 53 to 52. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field link_watch_list has been changed from 78 to 77. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field mem_end has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 29 | The relative position of field mem_start has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 30 | The relative position of field name_hlist has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field napi_list has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field nd_net has been changed from 84 to 83. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field npinfo has been changed from 83 to 82. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field num_rx_queues has been changed from 59 to 58. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field num_tx_queues has been changed from 66 to 65. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field pcpu_refcnt has been changed from 75 to 74. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field pm_qos_req has been changed from 1 to 96. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field qdisc has been changed from 68 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field queues_kset has been changed from 57 to 56. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field real_num_rx_queues has been changed from 60 to 59. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field real_num_tx_queues has been changed from 67 to 66. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field reg_state has been changed from 79 to 78. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field rtnl_link_state has been changed from 81 to 80. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field rx_cpu_rmap has been changed from 61 to 60. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field rx_handler has been changed from 62 to 61. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field rx_handler_data has been changed from 63 to 62. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field state has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field todo_list has been changed from 76 to 75. | Applications will access incorrect memory when attempting to access this field. |
| 49 | The relative position of field trans_start has been changed from 72 to 71. | Applications will access incorrect memory when attempting to access this field. |
| 50 | The relative position of field tx_global_lock has been changed from 70 to 69. | Applications will access incorrect memory when attempting to access this field. |
| 51 | The relative position of field tx_queue_len has been changed from 69 to 68. | Applications will access incorrect memory when attempting to access this field. |
| 52 | The relative position of field unnamed0 has been changed from 85 to 84. | Applications will access incorrect memory when attempting to access this field. |
| 53 | The relative position of field unreg_list has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 54 | The relative position of field vlan_features has been changed from 15 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 55 | The relative position of field wanted_features has been changed from 14 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 56 | The relative position of field watchdog_timeo has been changed from 73 to 72. | Applications will access incorrect memory when attempting to access this field. |
| 57 | The relative position of field watchdog_timer has been changed from 74 to 73. | Applications will access incorrect memory when attempting to access this field. |
| 58 | The relative position of field xps_maps has been changed from 71 to 70. | Applications will access incorrect memory when attempting to access this field. |
| 59 | Field ec_ptr 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. |
| 60 | Field master 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 ipv6 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 local_ip has been changed from __be32 (4 bytes) to union inet_addr (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 remote_ip has been changed from __be32 (4 bytes) to union inet_addr (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_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 | Field neigh_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. |
| 3 | Size of field tx_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field name has been changed from char const* (4 bytes) to char[16] (16 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 data_len has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field from_nlattr has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 name has been changed from char const* (4 bytes) to char[16] (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 init_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 | Value of member SDP_HDR_MEDIA has been changed from 6 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lockowner has been changed from fl_owner_t (4 bytes) to struct nfs_lockowner (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field pid has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fc_slot_table has been changed from 184 bytes to 304 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field bc_slot_table has been changed from 184 bytes to 304 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_target_highest_slotid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field d2_target_highest_slotid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 generation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 session has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 server_highest_slotid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_highest_slotid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 | Type of field used_slots has been changed from unsigned long[8] (32 bytes) to unsigned long[32] (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. |
| 8 | The relative position of field highest_used_slotid has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_mds_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field cl_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 | Field cl_preserve_clid has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_nfs_mod has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 cl_renewd has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field openowner_id has been changed from 24 bytes to 28 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field lockowner_id has been changed from 24 bytes to 28 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field backing_dev_info has been changed from 384 bytes to 380 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wb_verf has been changed from struct nfs_writeverf (12 bytes) to struct nfs_write_verifier (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 pg_completion_ops has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field fattr has been changed from 152 bytes to 156 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 sa_cache_this has been changed from 1 byte to 1 bit. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| 2 | Field slot_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. |
| 3 | 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. |
| 4 | Field generation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 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. |
| 2 | The relative position of field cinfo has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field fh 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 seq_res has been changed from 14 to 0. | 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 stateid has been changed from 0 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field f_attr has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field rflags has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field header has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 args has been changed from 44 bytes to 40 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field fattr has been changed from 152 bytes to 156 bytes. | 1) Size of the inclusive type has been 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 res has been changed from 32 bytes to 36 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Type of field pages has been changed from struct list_head (8 bytes) to struct nfs_page_array (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. |
| 6 | The relative position of field args 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. |
| 7 | The relative position of field ds_clp has been changed from 7 to 9. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field list has been changed from 3 to 0. | 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 mds_offset 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. |
| 10 | The relative position of field pages 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. |
| 11 | The relative position of field res 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. |
| 12 | The relative position of field task 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. |
| 13 | The relative position of field timestamp 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. |
| 14 | Field page_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. |
| 15 | Field pnfs_error has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field read_done_cb has been changed from 8 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_args has been changed from 12 bytes to 8 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 | The relative position of field lock_context has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field offset 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. |
| 4 | The relative position of field pages 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. |
| 5 | The relative position of field seq_args has been changed from 7 to 0. | 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 context has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field count has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field fh has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field pgbase has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_res 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. |
| 2 | The relative position of field eof has been changed from 2 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field seq_res has been changed from 3 to 0. | 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 count has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field fattr has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field commit_rpc_prepare has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field submount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_pageio_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. |
| 4 | Field return_delegation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 try_mount has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field alloc_client has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 7 | Field have_delegation has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 read_pageio_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. |
| 9 | Field secinfo 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 header has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 args has been changed from 52 bytes to 48 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field fattr has been changed from 152 bytes to 156 bytes. | 1) Size of the inclusive type has been 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 res has been changed from 36 bytes to 40 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 5 | Type of field pages has been changed from struct list_head (8 bytes) to struct nfs_page_array (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. |
| 6 | The relative position of field args 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 ds_clp has been changed from 7 to 10. | 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 list has been changed from 4 to 0. | 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 mds_offset 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. |
| 10 | The relative position of field pages has been changed from 3 to 9. | 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 res 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. |
| 12 | The relative position of field task 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. |
| 13 | The relative position of field timestamp 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. |
| 14 | Field page_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. |
| 15 | Field pnfs_error has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field write_done_cb has been changed from 8 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_args has been changed from 12 bytes to 8 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 | The relative position of field bitmask 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. |
| 3 | The relative position of field lock_context 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. |
| 4 | The relative position of field offset 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 seq_args has been changed from 9 to 0. | 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 context has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field count has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field fh has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field pages has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field pgbase has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field stable has been changed from 5 to 6. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field seq_res 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. |
| 2 | The relative position of field seq_res has been changed from 4 to 0. | 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 server 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. |
| 4 | The relative position of field count has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field fattr has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field verf has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field verifier has been changed from __be32[2] to struct nfs_write_verifier of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | The relative position of field committed has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field verifier has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NL80211_AUTHTYPE_AUTOMATIC has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member __NL80211_AUTHTYPE_NUM 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 | Value of member NUM_NL80211_IFTYPES has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field srcu has been changed from 28 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 sklist_lock has been changed from spinlock_t (2 bytes) to struct mutex (20 bytes). | 1) Size of the inclusive type has been changed. 2) Previous 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 busn_res has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 d3cold_allowed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field d3cold_delay has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field match_driver has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 4 | Field no_d3cold has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 sriov_configure has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 driver has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 220 bytes to 224 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field streams 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 wall_clock has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_ptr_wrap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field latency_pm_qos_req has been changed from 92 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_base_rdpmc has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tp_target has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field bp_target 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 is_fake has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 pebs_event_reset has been changed from u64[4] (32 bytes) to u64[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 | Size of field unnamed0 has been changed from 72 bytes to 76 bytes. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ip has been changed from __u64[255] (2040 bytes) to __u64[127] (1016 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 attr has been changed from 80 bytes to 96 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr_offset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field check_microcode has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 events_sysfs_show has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 max_pebs_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. |
| 5 | Field pebs_aliases has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rdpmc_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. |
| 7 | The relative position of field bts_active has been changed from 37 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field pebs has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed3 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 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 c45_ids has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_c45 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 state_queue has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field match_phy_device has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ts_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 driver has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_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 nr_hashed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 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 | Field id_auto has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 acpi_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 driver has been changed from 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field constraints has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field 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 work has been changed from 68 bytes to 76 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 expire_count has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field prevent_sleep_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 start_prevent_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. |
| 4 | Field wakeup_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 88 bytes to 92 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 alarmtimer has been changed from 36 bytes to 100 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field it has been changed from 72 bytes to 108 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 alarm has been changed from 44 bytes to 108 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 31 to 39. | 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 32 to 42. | 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 23 to 25. | 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 21 to 23. | 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 19 to 21. | 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 20 to 22. | 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 18 to 20. | 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 22 to 24. | 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 15 to 17. | 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 14 to 16. | 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 30 to 38. | 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 28 to 36. | 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 26 to 34. | 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 27 to 35. | 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 25 to 33. | 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 29 to 37. | 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 42 to 56. | 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 41 to 55. | 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 17 to 19. | 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 16 to 18. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 21 | Value of member POWER_SUPPLY_PROP_SCOPE has been changed from 40 to 54. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 22 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 43 to 57. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 23 | Value of member POWER_SUPPLY_PROP_TECHNOLOGY has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 24 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 33 to 43. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 25 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 34 to 46. | 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_EMPTY_AVG has been changed from 36 to 50. | 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_EMPTY_NOW has been changed from 35 to 49. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 28 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 38 to 52. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 29 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 37 to 51. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 30 | Value of member POWER_SUPPLY_PROP_TYPE has been changed from 39 to 53. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 31 | Value of member POWER_SUPPLY_PROP_VOLTAGE_AVG has been changed from 12 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 32 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 33 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN_DESIGN has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 34 | Value of member POWER_SUPPLY_PROP_VOLTAGE_NOW has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field tzd has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 nlink has been changed from 2 bytes to 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 | Size of field power has been changed from 864 bytes to 436 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 states has been changed from 576 bytes to 416 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hlt_works_ok has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_demux has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_demux has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 ps2dev has been changed from 48 bytes to 52 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field resync_work has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_buf has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 dq_id has been changed from unsigned int (4 bytes) to struct kqid (8 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 dq_type has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_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 n_nocbs_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 nxtcompleted has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_kthread_status has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field node_kthread_task has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_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. |
| 2 | Field barrier_cpu_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 barrier_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 call has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_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. |
| 6 | Field expedited_done_exit has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_done_lost has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_done_tries has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_normal has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_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. |
| 11 | Field expedited_stoppedcpus has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_tryfail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_workdone1 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_workdone2 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 expedited_wrap has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gp_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. |
| 17 | Field gp_kthread has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 gp_wq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 19 | Field n_barrier_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. |
| 20 | Field onoff_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. |
| 21 | Field orphan_donelist has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 orphan_donetail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 orphan_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. |
| 24 | Field orphan_nxtlist has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 orphan_nxttail has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 qlen has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 qlen_lazy has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 fqslock has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_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 user_reg_hint_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 cookie_ts has been changed from 1 byte to 1 bit. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pages has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dropped_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 nr_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. |
| 3 | The relative position of field entries has been changed from 16 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field commit_overrun has been changed from 14 to 16. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rwsem has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field head 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 fi 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 peer 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 rt_peer_genid 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 rt_spec_dst 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 | The relative position of field rt_gateway has been changed from 6 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field rt_iif has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 7 | Field rt_key_tos has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field queue_timeout has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 __remaining has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field piter has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field decay_counter has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field removed_load has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 runnable_load_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. |
| 4 | Field last_decay has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 blocked_load_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 tg_runnable_contrib has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 rq has been changed from 12 to 14. | 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 tg 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. |
| 9 | The relative position of field leaf_cfs_rq_list has been changed from 14 to 16. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | Field load_unacc_exec_time 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 load_last 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 load_stamp 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 load_contribution 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 | The relative position of field h_load has been changed from 16 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field on_list has been changed from 13 to 15. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field css has been changed from 16 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 count 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 h_load_throttle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 cfs has been changed from 132 bytes to 144 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field migrate_task_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_cpus_allowed has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field oom_flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Type of field oom_score_adj has been changed from int (4 bytes) to short (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field oom_score_adj_min has been changed from int (4 bytes) to short (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 4 | Field prev_stime 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 oom_adj 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 prev_utime 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 runnable_avg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field load_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. |
| 3 | Size of field css has been changed from 16 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 nr_cpus_allowed has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field prev_cputime has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 3 | Field task_frag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 task_works has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 no_new_privs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 se has been changed from 300 bytes to 328 bytes. | 1) Size of the inclusive type has been 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 seccomp has been changed from struct seccomp_t (4 bytes) to struct seccomp (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. |
| 8 | Field irq_thread has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member SDEV_BLOCK has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member SDEV_CREATED_BLOCK has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field disk_events_disable_depth has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_write_same has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 use_16_for_rw has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_report_opcodes has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sdev_dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 6 | Size of field sdev_gendev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field shost_dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 file_open has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field kernel_module_from_file has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 mmap_file has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_owned_by has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tun_dev_alloc_security has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 6 | Field tun_dev_attach_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 tun_dev_free_security has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 8 | Field tun_dev_open has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field throttle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unthrottle has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handle_break has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field port has been changed from 124 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 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rx_bytes has been changed from unsigned long (4 bytes) to u64 (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Type of field rx_packets has been changed from unsigned long (4 bytes) to u64 (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field tx_packets has been changed from unsigned long (4 bytes) to u64 (8 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Type of field tx_bytes has been changed from unsigned long (4 bytes) to u64 (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 inner_transport_header has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field inner_network_header has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from 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 params has been changed from 152 bytes to 156 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[84] (336 bytes) to unsigned long[92] (368 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 flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field release_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. |
| 2 | Field mtu_reduced has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_frag has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_rx_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 | Size of field __sk_common has been changed from 52 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 unnamed3 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field unnamed4 has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 skc_reuse has been changed from 1 byte to 4 bits. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | The relative position of field skc_dontcopy_begin 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 unnamed1 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. |
| 6 | The relative position of field unnamed2 has been changed from 9 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | Size of field unnamed0 has been changed from 4 bytes to 8 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. |
| 8 | Size of field unnamed1 has been changed from 8 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. |
| 9 | Size of field unnamed2 has been changed from 8 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. |
| 10 | The relative position of field skc_bound_dev_if has been changed from 4 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field skc_net has been changed from 7 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field skc_prot has been changed from 6 to 7. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_addrpair 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 unnamed0 has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 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 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_bind_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_portaddr_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_portpair 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 unnamed0 has been added to this type. | Size of the union has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | 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. |
| 4 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 callback_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 cur_max_bandwidth has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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_ack_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. |
| 4 | Field last_rx_rate_vht_nss has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 sta has been changed from 44 bytes to 72 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 last_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_next_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. |
| 2 | Size of field rq_cred has been changed from 12 bytes to 20 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 mtu_info has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field repair has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 repair_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. |
| 4 | Field tsoffset has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 tsq_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 tsq_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. |
| 7 | Size of field unused has been changed from 2 bits to 1 bit. | 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 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 | Field thermal_instances has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 updated has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 device has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 emul_temperature has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field governor has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 temperature has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 thermal_instances has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 trip_temp_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. |
| 6 | Field trip_type_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. |
| 7 | Field tzp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 device has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been 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 idr has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 10 | Size of field poll_queue has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 11 | Type of field passive has been changed from bool (1 byte) to int (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 12 | The relative position of field devdata has been changed from 3 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field trips has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_trend has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout 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_trip_hyst has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 set_emul_temp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 set_trip_hyst has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 set_trip_temp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_timers 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 twsk_getpeer 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 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. |
| 2 | Field 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. |
| 3 | Size of field fullmm has been changed from 4 bytes to 1 bit. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allocated_snapshot has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) 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 print_max has been changed from int (4 bytes) to bool (1 byte). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Type of field use_max_tr has been changed from int (4 bytes) to bool (1 byte). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ent has been changed from 12 bytes to 8 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field buf has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field itty has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 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 iflags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field legacy_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 | Type of field termios_locked has been changed from struct ktermios* (4 bytes) to struct ktermios (44 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Type of field termios has been changed from struct ktermios* (4 bytes) to struct ktermios (44 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | The relative position of field winsize has been changed from 18 to 19. | 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 termiox 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. |
| 6 | The relative position of field ctrl_lock has been changed from 9 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field ctrl_status has been changed from 24 to 25. | 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 minimum_to_wake has been changed from 36 to 37. | 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 termios_mutex 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. |
| 10 | The relative position of field closing 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. |
| 11 | The relative position of field count 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. |
| 12 | The relative position of field name 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. |
| 13 | The relative position of field flow_stopped has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field link has been changed from 26 to 27. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field packet has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field stopped has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field flags has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field fasync has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field warned has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field hw_stopped has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field termios has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field atomic_write_lock has been changed from 37 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field receive_room has been changed from 25 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field termios_locked has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field pgrp has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field session has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 27 | Field echo_overrun has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cdevs has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Field ports has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 scan_dwork has been changed from 68 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field usbfs_dentry has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 60 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_hub_initiated_lpm has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | Size of field drvwrap has been changed from 60 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field endpoint has been changed from 1 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field extra has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field string has been changed from 2 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field extralen has been changed from 4 to 1. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous 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 56 bytes to 60 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | Field uidhash_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. |
| 3 | Field destroyer 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 creator 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 220 bytes to 224 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[52] (208 bytes) to unsigned long[59] (236 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field nr_to_write has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field pages_skipped has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field range_end has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field range_start has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field sync_mode has been changed from 0 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field paging has been changed from 8 bytes to 4 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pagetable_setup_done 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 compose_msi_msg has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wallclock_init 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 polq has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure 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_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_tmo has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field swapper has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of 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 hw became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter state became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 148 bytes to 176 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*[10] (40 bytes) to char const*[11] (44 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 40 bytes to 44 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct hlist_head[257] (1028 bytes) to struct hlist_head[512] (2048 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1028 bytes to 2048 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter tx has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter tx 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 232 bytes to 240 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 240 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter alarm became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter function became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to u16 (2 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_device_id[4] const (112 bytes) to struct pci_device_id[5] const (140 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 88 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 108 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 28 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 1892 bytes to 1888 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 168 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 276 bytes to 280 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 384 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 48 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 820 bytes to 828 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 8 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 1600 bytes to 2496 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 316 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter running has been changed from struct list_head (8 bytes) to struct async_domain (20 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter running has been changed from struct list_head (8 bytes) to struct async_domain (20 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter list has been changed from struct list_head (8 bytes) to struct async_domain (20 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter dirlen 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 | 1st parameter cb has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from char (1 byte) to struct filename (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from char (1 byte) to struct filename (16 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter parent of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type unsigned char const has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter signr of type long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter code 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 name has been changed from char (1 byte) to struct filename (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter ssid has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 4th parameter tsid has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 5th parameter tclass has been removed from the calling stack. | This parameter will be ignored by the function. |
| 4 | 6th parameter perms has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter nd has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd 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 idx became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bitmap became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter q became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter from became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter page became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter to became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter desc became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter from became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter page became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bus became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cache_request 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 272 bytes to 316 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter count has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter css became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ss became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter buflen became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter cgrp became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter task became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter count became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter p became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct nfs_parsed_mount_data (384 bytes) to struct nfs_mount_info (20 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter mntfh has been changed from struct nfs_fh (130 bytes) to struct nfs_subversion (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter noresvport has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ds_timeo of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter ds_retrans of type unsigned 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 data has been changed from struct nfs_parsed_mount_data (384 bytes) to struct nfs_mount_info (20 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter mntfh has been changed from struct nfs_fh (130 bytes) to struct nfs_subversion (32 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter noresvport has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter clp became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ip_addr became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter timeparms became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clnt became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter flags became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter msg became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter req of type struct nlm_rqst* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter busno became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter node became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter ops became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 6th parameter i has been changed from struct list_head (8 bytes) to struct nf_hook_ops (28 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter task of type struct task_struct* 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 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 44 bytes to 68 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 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter policy became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter freqs became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter state became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter list became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter list became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu_online 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter inode 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 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ifindex became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ifindex became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sa became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter i_pos has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter bh became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter de became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter dir became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uio of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uio of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter throttle of type struct dm_kcopyd_throttle* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter per_bio_data_size 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 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter wait has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter sb became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter type became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter fb became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter funcs became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter index became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter property became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter block of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter print_bad_edid of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rb of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter info became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter color of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[14] const (56 bytes) to u32[15] const (60 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 48 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 8 bytes to 9 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hcd of type struct usb_hcd* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hcd of type struct usb_hcd* 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 164 bytes to 184 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 __u64 (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter device became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter handler became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter handler_type became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gpe_device became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter gpe_number became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter wake_device became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter exit_code has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 3rd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter opt became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter opt_space became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nexthdr became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from int (4 bytes) to 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter spec_dst has been changed from unsigned int (4 bytes) to struct in_device (276 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter file became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 28 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter curr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pi became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter uaddr became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd 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 type became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter type became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter size of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter codec became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nid became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter eapd_workaround has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter codec became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter direct became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter nid became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter eld has been changed from struct hdmi_eld (724 bytes) to struct parsed_hdmi_eld (456 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter eld_size 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 e has been changed from struct hdmi_eld (724 bytes) to struct parsed_hdmi_eld (456 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter codec became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter codec became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter tag became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hdev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter ht_cap has been changed from struct ieee80211_sta_ht_cap (22 bytes) to struct sta_info (812 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 92 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter gpe_register_info has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter gpe_event_info became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter 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 704 bytes to 800 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter request has been changed from struct drm_i915_gem_request (36 bytes) to unsigned int (4 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pipelined has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter seqno has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter obj became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter obj became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter write became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter obj became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter do_retire has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter purgeable_only has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cache_level of type enum i915_cache_level has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter obj became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mask became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pipe became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter idp became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 3rd parameter new_dev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter relax of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter relax of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter force of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mode became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter name became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter parent became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dentry became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct inode (328 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter index of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter priv of type void* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter i_pos became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter page_size_log of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ctx became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter is_sync became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags 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 handler became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pdev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pdev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gtt_total of type size_t* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter stolen_size of type size_t* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter mappable_base of type phys_addr_t* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Parameter mappable_end of type unsigned long* 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 struct intel_gtt const* (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter obj has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pipe became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter port of type enum port has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter port of type enum port has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pipe of type enum pipe has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dev has been changed from struct drm_device (936 bytes) to struct drm_connector (864 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter num_dwords became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ring became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_sdvob 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 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_procinfo[18] (648 bytes) to struct rpc_procinfo[] (4 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter level became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned long[] (4 bytes) to unsigned long[8] (32 bytes). | Applications will obtain a different value and execution may change. |
| 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 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter user_ns has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter xfer_mode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 232 bytes to 240 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 240 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 240 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 240 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 240 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 240 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 240 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd 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 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fl became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fl became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter conflock became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter filp became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter fl became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hw became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hw became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hw became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter group of type struct fsnotify_group* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mark became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter nb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter val became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gfp_mask became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mddev became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter nr_iovecs became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bio became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter gfp_mask became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mddev became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter mddev has been changed from struct mddev (692 bytes) to struct md_thread (36 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_new of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nr_accounted has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 6th parameter details has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup* (became non-const). | This function may change parameter setup, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup* (became non-const). | This function may change parameter setup, 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 dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ie became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter macaddr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter misc became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sae_data of type u8 const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter sae_data_len 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 dev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sae_data of type u8 const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter sae_data_len 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 dev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter success became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter vif became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_rmap_locks of type bool* 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 eax 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 edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter file became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter flags became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mm became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 44 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 832 bytes to 768 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 44 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 832 bytes to 768 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 3456 bytes to 3200 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_rmap_locks of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter mtext 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 | Base type of 2nd parameter pathname has been changed from char (1 byte) to struct filename (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mask became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from char (1 byte) to struct filename (16 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd 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 | Type of this global data has been changed from struct ctl_path[2] (8 bytes) to int (4 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Parameter name of type char const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter flags of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Parameter path of type struct path* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from char (1 byte) to struct filename (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter nd has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ns of type struct ipc_namespace* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mnt became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter m became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 88 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 108 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 28 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 1892 bytes to 1888 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 168 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 276 bytes to 280 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 384 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 48 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 820 bytes to 828 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 8 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 1600 bytes to 2496 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 316 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter adapter became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter adapter became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter npinfo of type struct netpoll_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ndev of type struct net_device* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter gfp of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 60 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 60 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 60 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[40] (160 bytes) to struct nf_conntrack_l3proto*[41] (164 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 160 bytes to 164 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 100 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter delim 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 2nd parameter elem has been changed from struct list_head (8 bytes) to struct nf_hook_ops (28 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 | 1st parameter pf has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 2nd parameter qh 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 void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter subsys_id of type __u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter subsys_id of type __u8 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 u32[2] const (8 bytes) to u32[3] const (12 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler const*[] (4 bytes) to struct xattr_handler const*[2] (8 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter roc has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter fl_pid has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 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 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter gfp has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter netdev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter netdev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter netdev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter netdev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter netdev has been changed from struct net_device (1088 bytes) to struct wireless_dev (188 bytes). | This parameter may be incorrectly initialized by applications. |
| 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 | Parameter nodemask of type nodemask_t* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter force_kill of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fd became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter file became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter context has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter high_limit of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type struct zone* 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 edx 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 eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lockdep_ok of type enum lockdep_ok has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter drv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mod_name became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter owner became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter type became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cap became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter state became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter driver became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 96 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 3056 bytes to 3060 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[18] (576 bytes) to struct event_constraint[11] (352 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 576 bytes to 352 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 224 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter key became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter phydev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_c45 of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter phydev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tsk became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char[6] const (6 bytes) to char[] const (4 bytes). | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 276 bytes to 280 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 130 bytes to 129 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter child_tid 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 5th parameter regs has been changed from struct pt_regs (68 bytes) to int (4 bytes). | This parameter may be incorrectly initialized by applications. |
| 3 | The parameter clone_flags became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter newsp became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter parent_tid became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter argv became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter envp became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter name became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter regs 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 628 bytes to 632 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter device has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter device has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter device has been changed from struct acpi_device (776 bytes) to struct device (224 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter state has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter prot became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter protocol became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter code became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter type became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter value became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mcs_group[12] const (480 bytes) to struct mcs_group[13] const (520 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 480 bytes to 520 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter secs of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter c_old of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter c of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 256 bytes to 448 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 136 bytes to 156 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 256 bytes to 448 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 256 bytes to 448 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 136 bytes to 156 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 256 bytes to 448 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter delta_jiffies of type unsigned long* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter head has been changed from struct list_head (8 bytes) to struct nfs_pgio_header (88 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter task became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter eof of type loff_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter file became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter check_access 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 bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter desired_bw_khz has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 4th parameter reg_rule 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 int to struct ieee80211_reg_rule 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 | Parameter user_reg_hint_type of type enum nl80211_user_reg_hint_type has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter alpha2 became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter force of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter counter became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter val became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long (4 bytes) to u64 (8 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu_id of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter buffer became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter size became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter buffer became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter vma became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter page became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter delay has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[30] const (120 bytes) to struct nla_policy[34] const (136 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 120 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter rmdevice 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 | 7th parameter beacon has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter sdata has been changed from struct ieee80211_sub_if_data (1400 bytes) to struct ieee80211_local (3776 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Type of return value has been changed from ieee80211_rx_result (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter miter became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter action became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter q became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter task became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 432 bytes to 416 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 28 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 68 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 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sdev became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_state of type enum scsi_device_state 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 | Parameter new_state of type enum scsi_device_state has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type char* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter security of type void* 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 struct dentry* (4 bytes) to struct path (8 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 88 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 108 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 28 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 1892 bytes to 1888 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 168 bytes to 384 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 28 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 276 bytes to 280 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 44 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 274 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 275 | Size of this global data has been changed from 384 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 276 | Size of this global data has been changed from 48 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 277 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 278 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 279 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 280 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 281 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 282 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 283 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 284 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 285 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 286 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 287 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 288 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 289 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 290 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 291 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 292 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 293 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 294 | Size of this global data has been changed from 820 bytes to 828 bytes. | Applications will obtain a different value and execution may change. |
| 295 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 296 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 297 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 298 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 299 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 300 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 301 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 302 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 303 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 304 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 305 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 306 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 307 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 308 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 309 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 310 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 311 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 312 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 313 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 314 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 315 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 316 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 317 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 318 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 319 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 320 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 321 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 322 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 323 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 324 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 325 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 326 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 327 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 328 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 329 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 330 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 331 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 332 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 333 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 334 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 335 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 336 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 337 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 338 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 339 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 340 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 341 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 342 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 343 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 344 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 345 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 346 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 347 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 348 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 349 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 350 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 351 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 352 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 353 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 354 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 355 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 356 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 357 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 358 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 359 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 360 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 361 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 362 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 363 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 364 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 365 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 366 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 367 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 368 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 369 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 370 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 371 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 372 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 373 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 374 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 375 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 376 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 377 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 378 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 379 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 380 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 381 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 382 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 383 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 384 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 385 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 386 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 387 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 388 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 389 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 390 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 391 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 392 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 393 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 394 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 395 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 396 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 397 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 398 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 399 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 400 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 401 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 402 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 403 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 404 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 405 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 406 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 407 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 408 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 409 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 410 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 411 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 412 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 413 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 414 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 415 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 416 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 417 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 418 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 419 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 420 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 421 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 422 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 423 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 424 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 425 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 426 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 427 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 428 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 429 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 430 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 431 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 432 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 433 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 434 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 435 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 436 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 437 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 438 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 439 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 440 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 441 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 442 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 443 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 444 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 445 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 446 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 447 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 448 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 449 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 450 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 451 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 452 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 453 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 454 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 455 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 456 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 457 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 458 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 459 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 460 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 461 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 462 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 463 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 464 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 465 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 466 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 467 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 468 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 469 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 470 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 471 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 472 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 473 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 474 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 475 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 476 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 477 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 478 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 479 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 480 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 481 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 482 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 483 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 484 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 485 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 486 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 487 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 488 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 489 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 490 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 491 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 492 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 493 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 494 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 495 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 496 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 497 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 498 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 499 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 500 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 501 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 502 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 503 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 504 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 505 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 506 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 507 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 508 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 509 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 510 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 511 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 512 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 513 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 514 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 515 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 516 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 517 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 518 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 519 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 520 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 521 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 522 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 523 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 524 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 525 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 526 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 527 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 528 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 529 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 530 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 531 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 532 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 533 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 534 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 535 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 536 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 537 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 538 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 539 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 540 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 541 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 542 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 543 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 544 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 545 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 546 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 547 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 548 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 549 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 550 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 551 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 552 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 553 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 554 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 555 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 556 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 557 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 558 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 559 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 560 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 561 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 562 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 563 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 564 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 565 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 566 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 567 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 568 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 569 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 570 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 571 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 572 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 573 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 574 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 575 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 576 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 577 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 578 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 579 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 580 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 581 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 582 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 583 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 584 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 585 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 586 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 587 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 588 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 589 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 590 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 591 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 592 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 593 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 594 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 595 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 596 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 597 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 598 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 599 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 600 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 601 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 602 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 603 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 604 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 605 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 606 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 607 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 608 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 609 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 610 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 611 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 612 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 613 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 614 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 615 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 616 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 617 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 618 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 619 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 620 | Size of this global data has been changed from 8 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 621 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 622 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 623 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 624 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 625 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 626 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 627 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 628 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 629 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 630 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 631 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 632 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 633 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 634 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 635 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 636 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 637 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 638 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 639 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 640 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 641 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 642 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 643 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 644 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 645 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 646 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 647 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 648 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 649 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 650 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 651 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 652 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 653 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 654 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 655 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 656 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 657 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 658 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 659 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 660 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 661 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 662 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 663 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 664 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 665 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 666 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 667 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 668 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 669 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 670 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 671 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 672 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 673 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 674 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 675 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 676 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 677 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 678 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 679 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 680 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 681 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 682 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 683 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 684 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 685 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 686 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 687 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 688 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 689 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 690 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 691 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 692 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 693 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 694 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 695 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 696 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 697 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 698 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 699 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 700 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 701 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 702 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 703 | Size of this global data has been changed from 2 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 704 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 705 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 706 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 707 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 708 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 709 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 710 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 711 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 712 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 713 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 714 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 715 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 716 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 717 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 718 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 719 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 720 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 721 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 722 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 723 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 724 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 725 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 726 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 727 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 728 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 729 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 730 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 731 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 732 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 733 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 734 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 735 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 736 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 737 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 738 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 739 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 740 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 741 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 742 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 743 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 744 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 745 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 746 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 747 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 748 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 749 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 750 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 751 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 752 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 753 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 754 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 755 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 756 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 757 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 758 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 759 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 760 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 761 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 762 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 763 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 764 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 765 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 766 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 767 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 768 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 769 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 770 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 771 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 772 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 773 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 774 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 775 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 776 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 777 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 778 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 779 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 780 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 781 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 782 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 783 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| 784 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 785 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 786 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 787 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 788 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 789 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 790 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 791 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 792 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 793 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 794 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 795 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 796 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 797 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 798 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 799 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 800 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 801 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 802 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 803 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 804 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 805 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 806 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 807 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 808 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 809 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 810 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 811 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 812 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 813 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 814 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 815 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 816 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 817 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 818 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 819 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 820 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 821 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 822 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 823 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 824 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 825 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 826 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 827 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 828 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 829 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 830 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 831 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 832 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 833 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 834 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 835 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 836 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 837 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 838 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 839 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 840 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 841 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 842 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 843 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 844 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 845 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 846 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 847 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 848 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 849 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 850 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 851 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 852 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 853 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 854 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 855 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 856 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 857 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 858 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 859 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 860 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 861 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 862 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 863 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 864 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 865 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 866 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 867 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 868 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 869 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 870 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 871 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 872 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 873 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 874 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 875 | Size of this global data has been changed from 1600 bytes to 2496 bytes. | Applications will obtain a different value and execution may change. |
| 876 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 877 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 878 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 879 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 880 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 881 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 882 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 883 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| 884 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 885 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 886 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 887 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 888 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 889 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 890 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 891 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 892 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 893 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 894 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 895 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 896 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 897 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 898 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 899 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 900 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 901 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 902 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 903 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 904 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 905 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 906 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 907 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 908 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 909 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 910 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 911 | Size of this global data has been changed from 416 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 912 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 913 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 914 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 915 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 916 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 917 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 918 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 919 | Size of this global data has been changed from 540 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 920 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 921 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 922 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 923 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 924 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 925 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 926 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 927 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 928 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 929 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 930 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 931 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 932 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 933 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 934 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 935 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 936 | Size of this global data has been changed from 664 bytes to 736 bytes. | Applications will obtain a different value and execution may change. |
| 937 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 938 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 939 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 940 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 941 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 942 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 943 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 944 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 945 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 946 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 947 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 948 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 949 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 950 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 951 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 952 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 953 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 954 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 955 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 956 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 957 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 958 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 959 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 960 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 961 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 962 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 963 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 964 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 965 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 966 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter alg became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shmlba of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter newset has been changed from sigset_t const* to sigset_t* (became non-const). | This function may change parameter newset, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter uoss became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter uss became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter frag_size of type unsigned int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter d_max_in of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tidle of type struct task_struct* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter use_effective has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sp became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sb became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter page became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from long to atomic_long_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter entry became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter force became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[349] const (1396 bytes) to sys_call_ptr_t[351] const (1404 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1396 bytes to 1404 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter cpu_dev has been changed from struct device (220 bytes) to struct cpuidle_device (304 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter cpu_dev has been changed from struct device (220 bytes) to struct cpuidle_device (304 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter offset became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter page became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sk became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter foc of type struct tcp_fastopen_cookie* 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 addr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter family became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter afinfo became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fastopen of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter foc of type struct tcp_fastopen_cookie* 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 | Type of 1st parameter sk has been changed from struct sock const* to struct sock* (became non-const). | This function may change parameter sk, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mss became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock const* to struct sock* (became non-const). | This function may change parameter sk, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pmtu became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter upper of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter lower of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter devdata 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 ops has been changed from struct thermal_zone_device_ops const* to void* (became non-const). | This function may change parameter 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 tz became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ts became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter cpumask became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter mm became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter va became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter icanon of type unsigned 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 tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tty has been changed from struct tty_struct (996 bytes) to struct tty_port (168 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter driver became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter index became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cmd became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter file became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter tty became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tty of type struct tty_struct* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tty of type struct tty_struct* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter ie_len has been removed from the calling stack. | This parameter will be ignored by the function. |
| 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 | The parameter sk became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter afinfo became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 192 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mem_flags became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter urb became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 120 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 60 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 116 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 232 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 64 bytes to 68 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 184 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 184 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 496 bytes to 512 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 868 bytes to 872 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 92 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 36 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 996 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 80 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 1376 bytes to 1424 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 8 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 552 bytes to 568 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 4 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 444 bytes to 692 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 908 bytes to 912 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 200 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 164 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 92 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 332 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 628 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 24 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 68 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 108 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 292 bytes to 300 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1244 bytes to 1284 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 392 bytes to 400 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 80 bytes to 101 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 236 bytes to 272 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 140 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 20 bytes to 24 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 644 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 88 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 72 bytes to 324 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 120 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 1128 bytes to 1168 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 84 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 432 bytes to 416 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 148 bytes to 1076 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 44 bytes to 52 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 140 bytes to 136 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 4 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 64 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 96 bytes to 100 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 4432 bytes to 4412 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 16 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 300 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 180 bytes to 128 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 52 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 124 bytes to 168 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 56 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 96 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 20 bytes to 16 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 72 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 384 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 220 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 104 bytes to 108 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 52 bytes to 60 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter datalen has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter datalen 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 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter from became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter n became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter to became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter from became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter n became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter to became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter from became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter n became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter to became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u16 (2 bytes) to u32 (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_basic of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | 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 | Parameter need_basic of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | 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 | The pointer level of 1st parameter local 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 | Base type of 1st parameter local has been changed from struct ieee80211_local (3520 bytes) to struct ieee80211_sub_if_data (1780 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx_flags of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter channel of type struct ieee80211_channel* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter scan of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter basic_rates of type u32* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter size became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from acpi_name (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter old_ns of type struct uts_namespace* 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 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter arg became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter cmd became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter v86 became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter vma has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | The parameter page became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 208 bytes to 236 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[27] (108 bytes) to atomic_long_t[28] (112 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 108 bytes to 112 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*[81] const (324 bytes) to char const*[89] const (356 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 324 bytes to 356 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter block 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 local has been changed from struct ieee80211_local (3520 bytes) to struct ieee80211_sub_if_data (1780 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter delay became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter dwork became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter wq became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | 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 | 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 | 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 | Base type of 1st parameter p has been changed from struct nfs_write_data (476 bytes) to struct nfs_commit_data (408 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct nfs_write_data (476 bytes) to struct nfs_commit_data (408 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter head has been changed from struct list_head (8 bytes) to struct nfs_pgio_header (88 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter data has been changed from struct nfs_write_data (476 bytes) to struct nfs_commit_data (408 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter head became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter req became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter req became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter wbc became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter data became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter task became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 8 bytes to 4 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 112 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 16 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter p became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter xdr became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rt_max_size has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter family became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter fl became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter skb became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter x became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 68 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Field dl_read has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 dl_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. |
| 3 | Field dma has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 244 bytes to 260 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field setup has been changed from int(*)(struct serial_private*, struct pciserial_board const*, struct uart_port*, int) to int(*)(struct serial_private*, struct pciserial_board const*, struct uart_8250_port*, 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 16 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handler_list_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field global has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field handler_list_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 field notify has been changed from 20 bytes to 24 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 8 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_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 notify_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 | Size of this type has been changed from 32 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field next has been changed from struct acpi_object_notify_handler (32 bytes) to union acpi_operand_object* (4 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_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 notify_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 notify_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 | Size of field notify has been changed from 32 bytes to 36 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field implementation has been changed from ACPI_INTERNAL_METHOD to acpi_internal_method. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcfg_added has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 sd has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 segment has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 start_bus has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 24 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Field end_bus 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 | The pointer level of field name has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 8 | Field resources has been renamed to res_offset. | 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 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 add has been changed from int(*)(acpi_handle) to int(*)(struct acpi_pci_root*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field remove has been changed from void(*)(acpi_handle) to void(*)(struct acpi_pci_root*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 setup has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 20 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field bus has been renamed to name. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field physical_node_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 | Field physical_node_id_bitmap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 physical_node_list has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field physical_node_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. |
| 5 | Field power_dependent has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 remove has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 776 bytes to 588 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eject_pending 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 match_driver 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 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field str_obj has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 sun has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 84 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 288 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 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 72 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 260 bytes to 244 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcfg_addr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1 byte to 2 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct acpi_device*, int) to int(*)(struct acpi_device*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field revision_iD has been renamed to revision_ID. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 17 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 31 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 6 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 | Size of field extended_irq has been changed from 16 bytes to 17 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field gpio has been changed from 31 bytes to 32 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field irq has been changed from 6 bytes to 7 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field init has been changed from int(*)(struct nlattr*, struct nlattr*, struct tc_action*, int, int) to int(*)(struct net*, struct nlattr*, struct nlattr*, struct tc_action*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tcfc_rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field C2latency has been renamed to c2_latency. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field C3latency has been renamed to c3_latency. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field S4bios_request has been renamed to s4_bios_request. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 68 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field compatible_id_list has been changed from struct acpica_device_id_list to struct acpi_pnp_device_id_list. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field hardware_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field unique_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field clk has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 44 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 588 bytes to 596 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 200 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bank4 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field revision_iD has been renamed to revision_ID. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field eoi_write has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Base type of field cpu_mask_to_apicid_and has been changed from unsigned int(*)(struct cpumask const*, struct cpumask const*) to int(*)(struct cpumask const*, struct cpumask const*, unsigned int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field vector_allocation_domain has been changed from void(*)(int, struct cpumask*) to void(*)(int, struct cpumask*, struct cpumask const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field audio_tstamp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 audio_tstamp has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_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 20 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field head has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field head has been changed from struct rcu_head to struct callback_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 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 uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field gid has been changed from gid_t to kgid_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 644 bytes to 640 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field suid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field euid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field fsuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field target_uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field target_auid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field egid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field fsgid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 11 | Type of field sgid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field name has been changed from char (1 byte) to struct filename (16 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field list_pseudoflavors has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cr_uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field cr_rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field audited has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 denied has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 requested has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 result has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 tclass has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 8 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Field auditdeny has been renamed to ssid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field slad has been renamed to tsid. | 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 384 bytes to 380 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 300 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field load_binary has been changed from int(*)(struct linux_binprm*, struct pt_regs*) to int(*)(struct linux_binprm*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field counts 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 storage 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 bi_destructor has been renamed to bi_pool. | 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 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 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 1128 bytes to 1168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | The pointer level of field queue_lock has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field hdr has been changed from 115 bytes to 119 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Field ext_cmd_line_ptr 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 ext_ramdisk_image 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 ext_ramdisk_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. |
| 5 | Field kbd_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. |
| 6 | Field sentinel 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 handover_offset has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 115 bytes to 119 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field min_alignment 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 xloadflags has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sae_data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field sae_data_len has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | 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 56 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field beacon_ies has been changed from unsigned char (1 byte) to struct cfg80211_bss_ies (20 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Base type of field proberesp_ies has been changed from unsigned char (1 byte) to struct cfg80211_bss_ies (20 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 4 | Field free_priv 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 152 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 this type has been changed from 40 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_mac_acl has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 start_p2p_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. |
| 3 | Field start_radar_detection has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 stop_p2p_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. |
| 5 | Size of this type has been changed from 272 bytes to 316 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Base type of field add_virtual_intf has been changed from struct net_device*(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*) to struct wireless_dev*(*)(struct wiphy*, char const*, enum nl80211_iftype, u32*, struct vif_params*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field cancel_remain_on_channel has been changed from int(*)(struct wiphy*, struct net_device*, u64) to int(*)(struct wiphy*, struct wireless_dev*, u64). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field del_virtual_intf has been changed from int(*)(struct wiphy*, struct net_device*) to int(*)(struct wiphy*, struct wireless_dev*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field get_channel has been changed from struct ieee80211_channel*(*)(struct wiphy*) to int(*)(struct wiphy*, struct wireless_dev*, struct cfg80211_chan_def*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 10 | Base type of field get_tx_power has been changed from int(*)(struct wiphy*, int*) to int(*)(struct wiphy*, struct wireless_dev*, int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 11 | Base type of field mgmt_frame_register has been changed from void(*)(struct wiphy*, struct net_device*, u16, bool) to void(*)(struct wiphy*, struct wireless_dev*, u16, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 12 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, bool, u64*) to int(*)(struct wiphy*, struct wireless_dev*, struct ieee80211_channel*, bool, unsigned int, u8 const*, size_t, bool, bool, u64*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 13 | Base type of field mgmt_tx_cancel_wait has been changed from int(*)(struct wiphy*, struct net_device*, u64) to int(*)(struct wiphy*, struct wireless_dev*, u64). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 14 | Base type of field remain_on_channel has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, enum nl80211_channel_type, unsigned int, u64*) to int(*)(struct wiphy*, struct wireless_dev*, struct ieee80211_channel*, unsigned int, u64*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 15 | Base type of field scan has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_scan_request*) to int(*)(struct wiphy*, 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 set_tx_power has been changed from int(*)(struct wiphy*, enum nl80211_tx_power_setting, int) to int(*)(struct wiphy*, struct wireless_dev*, enum nl80211_tx_power_setting, 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 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field dev has been renamed to wdev. | 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 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pkt_offset has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_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 dfs_state_entered has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 radar_detect_widths has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_cap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 44 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshAwakeWindowDuration has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 dot11MeshHWMPactivePathToRootTimeout has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 dot11MeshHWMPconfirmationInterval has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 dot11MeshHWMProotInterval has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ht_opmode has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 power_mode has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Size of this type has been changed from 44 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field dtim_period 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 nss has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 4 bytes to 6 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_pm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 nonpeer_pm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 peer_pm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 t_offset has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 84 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field macaddr has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 4 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 416 bytes to 448 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field max_acl_mac_addrs 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 reg_notifier has been changed from int(*)(struct wiphy*, struct regulatory_request*) to void(*)(struct wiphy*, struct regulatory_request*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_pkt_offset has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 tcp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 16 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_unexpected_nlportid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 cac_start_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. |
| 3 | Field cac_started has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 404 bytes to 188 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4432 bytes to 4412 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field actual_subsys_bits has been renamed to actual_subsys_mask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field subsys_bits has been renamed to subsys_mask. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field xattrs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 232 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field rcu_head has been renamed to cft_q_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 128 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field broken_hierarchy 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 warned_broken_hierarchy 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 create has been renamed to css_alloc. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 5 | Field destroy has been renamed to css_offline. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 6 | Field pre_destroy has been renamed to css_online. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dput_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 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 164 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | 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 26676 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 | Type of field rcu has been changed from struct rcu_head to struct callback_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 88 bytes to 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 464 bytes to 508 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 396 bytes to 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 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 672 bytes to 800 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field netdev_list has been renamed to wdev_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 228 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 324 bytes to 328 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 44 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 268 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 628 bytes to 632 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field power_specified has been renamed to refcnt. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field disabled has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 112 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field suid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field fsuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field euid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field fsgid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field egid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field sgid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field blocks has been changed from gid_t* to kgid_t*. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field small_block has been changed from gid_t[32] to kgid_t[32]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field d_revalidate has been changed from int(*)(struct dentry*, struct nameidata*) to int(*)(struct dentry*, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field d_rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field regs 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 regs has been changed from struct debugfs_reg32* to struct debugfs_reg32 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_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 52 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field num_discard_requests has been renamed to num_discard_bios. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field num_flush_requests has been renamed to num_flush_bios. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 bytes to 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 has been changed from int(*)(struct dm_target*, struct bio*, int, union map_info*) to int(*)(struct dm_target*, struct bio*, int). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct dm_target*, struct bio*, union map_info*) to int(*)(struct dm_target*, struct bio*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct dm_target*, status_type_t, char*, unsigned int) to void(*)(struct dm_target*, status_type_t, unsigned int, char*, unsigned int). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field target_request_nr has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_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 iommu_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. |
| 3 | Size of this type has been changed from 220 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 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 328 bytes to 324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmap_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 vmapping_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. |
| 3 | Size of this type has been changed from 44 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 vmap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 vunmap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 44 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 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 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bad_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 756 bytes to 864 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 476 bytes to 788 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_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 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 200 bytes to 196 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 44 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 320 bytes to 352 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field poll_running 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 funcs 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 funcs has been changed from struct drm_mode_config_funcs* to struct drm_mode_config_funcs const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 356 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_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 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 68 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| 2 | Field formula 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 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field mode_fixup has been changed from bool(*)(struct drm_encoder*, struct drm_display_mode*, struct drm_display_mode*) to bool(*)(struct drm_encoder*, struct drm_display_mode const*, struct drm_display_mode*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 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 | Field color_adjust has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 88 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 76 bytes to 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 936 bytes to 960 bytes. | The fields or parameters of 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. |
| 2 | Field gem_vm_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 gem_vm_ops has been changed from struct vm_operations_struct* to struct vm_operations_struct 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 136 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field pid has been changed from pid_t to struct pid*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field uid has been changed from uid_t to kuid_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 320 bytes to 324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 340 bytes to 344 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field expires 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 _neighbour has been renamed to from. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dn_next 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 rt6_next 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 expires has been renamed to next. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field from has been renamed to rt_next. | 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 neigh_lookup has been changed from struct neighbour*(*)(struct dst_entry const*, void const*) to struct neighbour*(*)(struct dst_entry const*, struct sk_buff*, void const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field update_pmtu has been changed from void(*)(struct dst_entry*, u32) to void(*)(struct dst_entry*, struct sock*, 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 48 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field dpms has been changed from void(*)(struct intel_dvo_device*, int) to void(*)(struct intel_dvo_device*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field mode_fixup has been changed from bool(*)(struct intel_dvo_device*, struct drm_display_mode*, struct drm_display_mode*) to bool(*)(struct intel_dvo_device*, struct drm_display_mode const*, struct drm_display_mode*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1976 bytes to 2000 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_variable_store has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 72 bytes to 324 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 hash 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 | Base type has been changed from void*()(struct request_queue*) to int()(struct request_queue*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*, struct request*, gfp_t) to int()(struct request_queue*, struct request*, struct bio*, gfp_t). | 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 228 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field reserved2 has been replaced by eth_tp_mdix_ctrl. | This field will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_eee has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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_module_eeprom has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_module_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. |
| 4 | Field get_ts_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. |
| 5 | Field set_eee has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 164 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 encode_fh has been changed from int(*)(struct dentry*, __u32*, int*, int) to int(*)(struct inode*, __u32*, int*, struct inode*). | 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 28 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field nfs 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 | Type of field fs_gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field fs_uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir_hash_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 dir_hashtable has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 dirty has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1184 bytes to 2244 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 rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_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 92 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field priv has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 12 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field assoc_mapping has been renamed to private_data. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field swap_activate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 swap_deactivate has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 68 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fa_rcu has been changed from struct rcu_head to struct callback_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 140 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 show_fdinfo has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_writers_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. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field euid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ia_gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field ia_uid has been changed from uid_t to kuid_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 332 bytes to 328 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field i_gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field i_uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field atomic_open 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 lookup has been changed from struct dentry*(*)(struct inode*, struct dentry*, struct nameidata*) to struct dentry*(*)(struct inode*, struct dentry*, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, umode_t, struct nameidata*) to int(*)(struct inode*, struct dentry*, umode_t, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Field truncate_range has been renamed to update_time. | 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 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 92 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 | Type of field i_rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fu_rcuhead has been changed from struct rcu_head to struct callback_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 112 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 field idr has been changed from 20 bytes to 24 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 12 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field padding has been removed from this type. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field snapshot has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 8332 bytes to 8308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | The pointer level of field buffer_iter has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_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 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 | Field rcu_head has been renamed to callback_head. | 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 392 bytes to 400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 292 bytes to 300 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 101 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_usb3_lpm_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 | Field enable_usb3_lpm_timeout has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field find_raw_port_number has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 156 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 248 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 172 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field primary_dig_out_type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 212 bytes to 220 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_notify has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fixup_id has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field fixup_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 fixup_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. |
| 4 | Field jackpoll_interval has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 jackpoll_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. |
| 6 | Field verbs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 708 bytes to 948 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 8 | Field cached_write has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Field d3_stop_clk 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 epss 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 in_pm 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 inv_eapd 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 inv_jack_detect 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 pcm_format_first 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 pm_down_notified 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 power_on 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 44 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 suspend has been changed from int(*)(struct hda_codec*, pm_message_t) to int(*)(struct hda_codec*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Field pre_resume has been renamed to check_power_status. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field own_chmap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 112 bytes to 124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field gating_jack 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 phantom_jack 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 724 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 3760 bytes to 3772 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field group 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 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 540 bytes to 1052 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field x2apic_available has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 356 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 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 264 bytes to 268 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 116 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gtt_list has been renamed to unbound_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field gtt_start has been renamed to stolen_base. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field hpd_irq_setup has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 68 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field init_pch_clock_gating has been renamed to off. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dma_buf_vmapping has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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_global_gtt_mapping has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_read_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. |
| 4 | Field last_write_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. |
| 5 | Field ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field pages_pin_count has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Field stolen has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 vmapping_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. |
| 9 | Size of this type has been changed from 216 bytes to 212 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 10 | The pointer level of field pages 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. |
| 11 | Type of field pages has been changed from struct page** to struct sg_table*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 12 | Field sg_list has been renamed to has_dma_mapping. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 13 | Field tiling_changed has been renamed to fence_dirty. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dri1 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 regfile has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 5212 bytes to 7848 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field fdi_rx_polarity_inverted 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 | The pointer level of field gmbus has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 6 | Type of field gt_lock has been changed from struct spinlock to spinlock_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Field saveDPLL_A has been renamed to fdi_rx_config. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 8 | Field saveFPA1 has been renamed to hw_context_size. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 clear_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. |
| 3 | Field insert_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. |
| 4 | Size of this type has been changed from 20 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_key_cons has been renamed to idmap_upcall_data. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 148 bytes to 1076 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 rann_interval has been changed from u32 to __le32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field rann_metric has been changed from u32 to __le32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field rann_seq has been changed from u32 to __le32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_notify_cw 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 vht_opmode_notif 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 | Name of member with value 6 has been changed from IEEE80211_QUEUE_STOP_REASON_CHTYPE_CHANGE to IEEE80211_QUEUE_STOP_REASON_OFFCHANNEL. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ssid_len has been renamed to device_ts_beacon. | 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 probe_resp has been changed from struct sk_buff (184 bytes) to struct probe_resp (12 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Field ps 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 num_mcast_sta has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 172 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 460 bytes to 476 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field connection_loss 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 dtim_period 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 p2p_noa_index 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 status_fc 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 status_received 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 adjusting_tbtt has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 nonpeer_pm has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ps has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ps_peers_deep_sleep has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ps_peers_light_sleep has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 sync_offset_clockdrift_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. |
| 7 | Field sync_offset_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. |
| 8 | Field sync_ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | Size of this type has been changed from 356 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field monitor_chandef has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 3520 bytes to 3776 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field radar_detect_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. |
| 4 | Field use_chanctx 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 hw_roc_cookie has been renamed to monitor_sdata. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 6 | Field hw_roc_dev has been renamed to hw_roc_start_time. | 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 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field timeout_started 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 data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field data_len has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field sae_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. |
| 4 | Field sae_trans has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 timeout_started has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 36 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1400 bytes to 1780 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field wmm_acm 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 arp_filter_state has been renamed to needed_rx_chains. | 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 44 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 148 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cf_params 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 challenge became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Field country_elem became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 5 | Field ds_params became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 6 | Field erp_info became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 7 | Field ext_supp_rates became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 8 | Field fh_params became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 9 | Field ht_cap_elem became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 10 | Field ibss_params became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 11 | Field ie_start became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 12 | Field mesh_config became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 13 | Field mesh_id became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 14 | Field peering became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 15 | Field perr became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 16 | Field prep became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 17 | Field preq became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 18 | Field pwr_constr_elem became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 19 | Field quiet_elem became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 20 | Field rann became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 21 | Field rsn became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 22 | Field ssid became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 23 | Field supp_rates became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 24 | Field tim became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 25 | Field timeout_int became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 26 | Field wmm_info became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 27 | Field wmm_param became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 28 | Type of field cf_params has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 29 | Type of field challenge has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 30 | Type of field country_elem has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 31 | Type of field ds_params has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 32 | Type of field erp_info has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 33 | Type of field ext_supp_rates has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 34 | Type of field fh_params has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 35 | Type of field ht_cap_elem has been changed from struct ieee80211_ht_cap* to struct ieee80211_ht_cap const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 36 | Type of field ibss_params has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 37 | Type of field ie_start has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 38 | Type of field mesh_config has been changed from struct ieee80211_meshconf_ie* to struct ieee80211_meshconf_ie const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 39 | Type of field mesh_id has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 40 | Type of field peering has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 41 | Type of field perr has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 42 | Type of field prep has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 43 | Type of field preq has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 44 | Type of field pwr_constr_elem has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 45 | Type of field quiet_elem has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 46 | Type of field rann has been changed from struct ieee80211_rann_ie* to struct ieee80211_rann_ie const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 47 | Type of field rsn has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 48 | Type of field ssid has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 49 | Type of field supp_rates has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 50 | Type of field tim has been changed from struct ieee80211_tim_ie* to struct ieee80211_tim_ie const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 51 | Type of field timeout_int has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 52 | Type of field wmm_info has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 53 | Type of field wmm_param has been changed from u8* to u8 const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 54 | Field ht_info_elem has been renamed to vht_cap_elem. | 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 28 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 460 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 276 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 rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field icsk_accept_queue has been changed from 20 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_rx_dst_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 | Size of this type has been changed from 44 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field bind_conflict has been changed from int(*)(struct sock const*, struct inet_bind_bucket const*) to int(*)(struct sock const*, struct inet_bind_bucket const*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_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 348 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field match has been changed from int(*)(struct inet_frag_queue*, void*) to bool(*)(struct inet_frag_queue*, 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 28 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 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field fastreuseport 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 36 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 96 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 560 bytes to 556 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field __tw_common has been changed from 52 bytes to 56 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 272 bytes to 276 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ifa_cstamp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 ifa_preferred_lft has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ifa_tstamp has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ifa_valid_lft has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Size of this type has been changed from 60 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 108 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 16 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 156 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 gc_rcu has been changed from struct rcu_head to struct callback_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 16 bytes to 8 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 16 bytes to 8 bytes. | Size of the inclusive type has been changed. |
| 3 | Type of field rcu has been changed from struct rcu_head to struct callback_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 100 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field devres_managed has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 max_vals has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 num_vals has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 vals has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 676 bytes to 684 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Base type of field mt has been changed from struct input_mt_slot (48 bytes) to struct input_mt (24 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 152 bytes to 228 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field PR has been renamed to YQ_CN_PR. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field edid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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_hw_state has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field new_encoder has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 panel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 760 bytes to 888 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ddi_pll_sel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 pch_pll has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 reset_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. |
| 4 | Size of this type has been changed from 1356 bytes to 1628 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field busy has been renamed to eld_vld. | 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 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cloneable 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 connectors_active 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 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 field ifb has been changed from 96 bytes to 104 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 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 dev has been renamed to crtc. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_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. |
| 2 | Field itlb_before_ctx_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 last_context_obj has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 220 bytes to 196 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Base type of field add_request has been changed from int(*)(struct intel_ring_buffer*, u32*) to int(*)(struct intel_ring_buffer*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field dispatch_execbuffer has been changed from int(*)(struct intel_ring_buffer*, u32, u32) to int(*)(struct intel_ring_buffer*, u32, u32, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field get_seqno has been changed from u32(*)(struct intel_ring_buffer*) to u32(*)(struct intel_ring_buffer*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex 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 64 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flags has been changed from unsigned long to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field irq has been changed from int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field __rcu_head has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_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 116 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tb6_peers has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 44 bytes to 64 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 rt6i_peer 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 rt6i_peer has been changed from struct inet_peer* to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fib_type 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 rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field nh_exceptions has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 nh_pcpu_rth_output has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 nh_rth_input has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 60 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 conn_schedule has been changed from int(*)(int, struct sk_buff*, struct ip_vs_proto_data*, int*, struct ip_vs_conn**) to int(*)(int, struct sk_buff*, struct ip_vs_proto_data*, int*, struct ip_vs_conn**, struct ip_vs_iphdr*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field dnat_handler has been changed from int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*) to int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*, struct ip_vs_iphdr*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field conn_out_get has been changed from struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, unsigned int, int) to struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field conn_in_get has been changed from struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, unsigned int, int) to struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field snat_handler has been changed from int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*) to int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*, struct ip_vs_iphdr*). | 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 820 bytes to 828 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 cgid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field cuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_id has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 44 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_inum has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 236 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1892 bytes to 1888 bytes. | The fields or parameters of 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 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field sysctl_ping_group_range has been changed from unsigned int[2] to kgid_t[2]. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Field tcp_sock has been renamed to fib_main. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field frag_max_size has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | 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. |
| 3 | Type of field ra has been changed from __u16 to __be16. | 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 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 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 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 136 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field daddr_cache 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 daddr_cache has been changed from struct in6_addr* to struct in6_addr 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 384 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field table has been renamed to hdr. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | The member SYSTEM_SUSPEND_DISK 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 52 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field update has been changed from int(*)(struct key*, void const*, size_t) to int(*)(struct key*, struct key_preparsed_payload*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field instantiate has been changed from int(*)(struct key*, void const*, size_t) to int(*)(struct key*, struct key_preparsed_payload*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field mic_failures has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 412 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 88 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field gid has been changed from gid_t to kgid_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 4 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field tkip has been changed from 412 bytes to 416 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_idx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cur_seq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 next_idx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field next_seq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 16 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Base type of field dump has been changed from void(*)(struct kmsg_dumper*, enum kmsg_dump_reason, char const*, unsigned long, char const*, unsigned long) to void(*)(struct kmsg_dumper*, enum kmsg_dump_reason). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field if_modifier has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 68 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field activated has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 140 bytes to 164 bytes. | The fields or parameters of 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 1360 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 bytes to 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 3280 bytes to 3300 bytes. | The fields or parameters of 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 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 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 16 bytes to 13 bytes. | The fields or parameters of 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. |
| 2 | Field antenna 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 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p_ctwindow has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 txpower has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 116 bytes to 152 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field p2p_oppps 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field netdev_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. |
| 2 | Field offchannel_tx_hw_queue has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 radiotap_mcs_details has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 radiotap_vht_details has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 84 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 add_chanctx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 assign_vif_chanctx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 change_chanctx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_et_sset_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 get_et_stats has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field get_et_strings has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 get_rssi has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 ipv6_addr_change has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 mgd_prepare_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 remove_chanctx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 restart_complete has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 unassign_vif_chanctx has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 216 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 14 | Base type of field remain_on_channel has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_channel*, enum nl80211_channel_type, int) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 15 | Base type of field rssi_callback has been changed from void(*)(struct ieee80211_hw*, enum ieee80211_rssi_event) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_rssi_event). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 16 | Base type of field tx has been changed from void(*)(struct ieee80211_hw*, struct sk_buff*) to void(*)(struct ieee80211_hw*, struct ieee80211_tx_control*, struct sk_buff*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_delimiter_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 vendor_radiotap_align has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 vendor_radiotap_oui has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field vendor_radiotap_subns 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 | Type of field flag has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field bandwidth has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field rx_nss has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 smps_mode has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 44 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 antenna_sel_tx has been renamed to hw_queue. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field cab_queue 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 rate_update has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32, enum nl80211_channel_type) to void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of 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 236 bytes to 244 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field private 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 32 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field run has been changed from void(*)(struct mddev*) to void(*)(struct md_thread*). | 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 692 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field plug_cnt has been renamed to reshape_backwards. | 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 6148 bytes to 2052 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 request_microcode_fw has been changed from enum ucode_state(*)(int, struct device*) to enum ucode_state(*)(int, struct device*, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field remap_pages has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field highest_vm_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 | Field uprobes_state has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 432 bytes to 416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field reserved_vm 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 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field slab_page 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 list 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 slab has been renamed to slab_cache. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field nonlinear 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 prio_tree_node has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| 3 | Field vm_set has been renamed to linear. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfmemalloc 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 units 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 44 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_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. |
| 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 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3456 bytes to 3200 bytes. | The fields or parameters of 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 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 20 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field pad1 has been replaced by group. | This field will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Field data 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 data has been changed from void* to void const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 32 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 140 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 96 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | 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 316 bytes to 324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field diag_nlsk has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 rt_genid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1600 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 ndo_bridge_dellink has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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_bridge_getlink has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_bridge_setlink has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_change_carrier has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_fdb_add has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_fdb_del has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_fdb_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. |
| 8 | Size of this type has been changed from 148 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Base type of field ndo_netpoll_setup has been changed from int(*)(struct net_device*, struct netpoll_info*) to int(*)(struct net_device*, struct netpoll_info*, gfp_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 44 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field vstats 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 | Type of field loginuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been renamed to portid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 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 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 124 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field rx_flags has been changed from int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 36 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 172 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_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 12 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field name has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 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 queue_num has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 76 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | The pointer level of field name has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 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 ctl_table_path has been changed from struct ctl_path (4 bytes) to char (1 byte). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 100 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ctl_table has been renamed to init_net. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field ctl_table_header has been renamed to net_id. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field ctl_table_users has been renamed to get_net_proto. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 2 has been changed from SDP_HDR_OWNER_IP4 to SDP_HDR_OWNER. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Name of member with value 3 has been changed from SDP_HDR_CONNECTION_IP4 to SDP_HDR_CONNECTION. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | The member SDP_HDR_CONNECTION_IP6 has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| 4 | The member SDP_HDR_OWNER_IP6 has been removed. | This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ls_flags has been changed from int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field call_sync has been changed from int(*)(struct rpc_clnt*, struct nfs_server*, struct rpc_message*, struct nfs4_sequence_args*, struct nfs4_sequence_res*, int) to int(*)(struct rpc_clnt*, struct nfs_server*, struct rpc_message*, struct nfs4_sequence_args*, struct nfs4_sequence_res*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_delegreturn_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 so_reclaim_seqcount has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field detect_trunking has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 28 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field lockowner 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 mdsthreshold has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_target_max_rqst_sz has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 fc_target_max_resp_sz has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 444 bytes to 692 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 184 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field target_max_slots has been renamed to max_slotid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_implid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 cl_serverscope has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 cl_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 496 bytes to 512 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field net has been renamed to cl_serverowner. | 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 908 bytes to 912 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_dreq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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_layout_private 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 52 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 46100 bytes to 46104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 12 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field sa_session has been renamed to sa_slot. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_highest_slotid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 sr_target_highest_slotid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field interrupted has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 4 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 mdsthreshold has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 152 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field gid has been changed from __u32 to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field uid has been changed from __u32 to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_request has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 access_result has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 access_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. |
| 4 | Size of this type has been changed from 256 bytes to 268 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 448 bytes to 424 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 44 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 32 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clone_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. |
| 2 | Field free_client has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field create_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. |
| 4 | Size of this type has been changed from 184 bytes to 224 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 rpc_clnt*, struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(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 nfs_open_context*) to int(*)(struct inode*, struct dentry*, struct iattr*, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 7 | Base type of field commit_done has been changed from int(*)(struct rpc_task*, struct nfs_write_data*) to int(*)(struct rpc_task*, struct nfs_commit_data*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 8 | Base type of field init_client has been changed from int(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t, int) to struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 9 | Base type of field commit_setup has been changed from void(*)(struct nfs_write_data*, struct rpc_message*) to void(*)(struct nfs_commit_data*, struct rpc_message*). | 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 476 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 52 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NL80211_AUTHTYPE_MAX has been changed from 3 to 4. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NL80211_IFTYPE_MAX has been changed from 9 to 10. | 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 52 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 full_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 full_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 8 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 372 bytes to 400 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rom has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 romlen has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 824 bytes to 840 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field broken_intx_masking 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 io_window_1k 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 pcie_flags_reg 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 runtime_d3cold 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 116 bytes to 124 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field err_handler 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 err_handler has been changed from struct pci_error_handlers* to struct pci_error_handlers 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 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 236 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field err_handler 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 err_handler has been changed from struct pci_error_handlers* to struct pci_error_handlers 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 336 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 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 640 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 chmap_kctl has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 56 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 308 bytes to 316 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field bp_list has been renamed to tp_list. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3056 bytes to 3060 bytes. | The fields or parameters of 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 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 2048 bytes to 1024 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 552 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sample_regs_user has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 exclude_callchain_kernel has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 exclude_callchain_user has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 sample_stack_user has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 __reserved_2 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. |
| 6 | Size of this type has been changed from 80 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 7 | Size of field __reserved_1 has been changed from 43 bits to 41 bits. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field regs_user has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 stack_user_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. |
| 3 | Size of this type has been changed from 84 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 224 bytes to 236 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field pebs_broken 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 76 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 72 bytes to 76 bytes. | Size of the inclusive type has been changed. |
| 3 | Size of field unnamed2 has been changed from 20 bytes to 12 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 424 bytes to 428 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 416 bytes to 468 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 128 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_inum has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 52 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field pid_gid has been changed from gid_t to kgid_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 244 bytes to 252 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_init has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field qos 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 syscore has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 116 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field autosleep_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 320 bytes to 324 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 380 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 88 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 276 bytes to 280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_role has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 default_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 | Field default_user has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Size of this type has been changed from 28 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field default_range 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 44 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_id 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 | Type of field a_rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 24 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_PROP_CURRENT_MAX has been changed from 13 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_PROP_CYCLE_COUNT has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX_DESIGN has been changed from 9 to 10. | 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 108 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 84 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field inum has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1100 bytes to 672 bytes. | The fields or parameters of 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 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 864 bytes to 436 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 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 28 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 320 bytes to 332 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field erase has been changed from int(*)(enum pstore_type_id, u64, struct pstore_info*) to int(*)(enum pstore_type_id, u64, int, struct timespec, struct pstore_info*). | 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(*)(u64*, enum pstore_type_id*, struct timespec*, char**, struct pstore_info*) to ssize_t(*)(u64*, enum pstore_type_id*, int*, struct timespec*, char**, struct pstore_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field write has been changed from int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, size_t, struct pstore_info*) to int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, int, size_t, struct pstore_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field quota_sync 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. |
| 2 | Base type of field set_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*) to int(*)(struct super_block*, struct kqid, struct fs_disk_quota*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field get_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*) to int(*)(struct super_block*, struct kqid, struct fs_disk_quota*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | 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 rcu_head*, void(*)(struct rcu_head*)) to void()(struct callback_head*, void(*)(struct callback_head*)). | 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 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field nxtlist has been changed from struct rcu_head to struct callback_head. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field nxttail has been changed from struct rcu_head** to struct callback_head**. | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqslock 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 flavors has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 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 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 28 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 num_timeout 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 retrans has been renamed to num_retrans. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fastopenq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 20 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field resize_disabled has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field update_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. |
| 2 | Field update_pages_work has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Field nr_pages_to_update has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field new_pages has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Size of this type has been changed from 92 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rb_root has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 36 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_uncached has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 144 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field rt_is_input 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_uses_gateway 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 rt_src has been renamed to rt_pmtu. | 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 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 552 bytes to 556 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_num_rx_queues has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field get_tx_queues has been renamed to get_num_tx_queues. | 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 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field change has been changed from int(*)(struct tcf_proto*, unsigned long, u32, struct nlattr**, unsigned long*) to int(*)(struct net*, struct sk_buff*, struct tcf_proto*, unsigned long, u32, struct nlattr**, unsigned long*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 132 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field nr_running has been changed from unsigned long to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field h_nr_running has been changed from unsigned long to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Field load_period has been renamed to tg_load_contrib. | 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 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 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 1376 bytes to 1424 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field nr_running has been changed from unsigned long to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rt_nr_running has been changed from unsigned long 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 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 300 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 | Field cpumask 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 watchdog_stamp 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 prev_cputime has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 628 bytes to 624 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 68 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_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 1244 bytes to 1284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field loginuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field rcu has been changed from struct rcu_head to struct callback_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 64 bytes to 60 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field creds has been changed from struct ucred to struct scm_creds. | 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 1024 bytes to 1016 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 664 bytes to 676 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field no_dif 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 wce_default_on 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 300 bytes to 304 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 700 bytes to 708 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 664 bytes to 688 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field sb_mount has been changed from int(*)(char*, struct path*, char*, unsigned long, void*) to int(*)(char const*, struct path*, char const*, unsigned long, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field tun_dev_attach has been changed from int(*)(struct sock*) to int(*)(struct sock*, void*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Field file_mmap has been renamed to mmap_addr. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sequence has been renamed to seqcount. | 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 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 164 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 144 bytes to 188 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field pm_state has been changed from int to enum uart_pm_state. | 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 372 bytes to 376 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 92 bytes to 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _sigsys 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 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 16 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfmemalloc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field head_frag 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 encapsulation 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 objsize has been renamed to object_size. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 20 bytes to 16 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 180 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 cpu_up has been changed from int(*)(unsigned int) to int(*)(unsigned int, 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 336 bytes to 368 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | 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 416 bytes to 420 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field skc_reuseport 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 4 bytes to 8 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 8 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field batch_check0 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 batch_check1 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 batch_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. |
| 4 | Field batch_queue has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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_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. |
| 6 | Field running has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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. |
| 8 | Size of this type has been changed from 28 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Type of field completed has been changed from int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field seq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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. |
| 3 | Type of field c has been changed from int[2] to unsigned long[2]. | 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 556 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 764 bytes to 812 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field last_rx_rate_flag has been changed from int to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 136 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rcu_head has been renamed to callback_head. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sp_task_pending 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 3616 bytes to 3624 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_flavor has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 cr_principal has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 12 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Type of field cr_gid has been changed from gid_t to kgid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field cr_uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field permissions has been changed from int(*)(struct ctl_table_root*, struct nsproxy*, struct ctl_table*) to int(*)(struct ctl_table_header*, struct ctl_table*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fastopen_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 fastopen_rsk has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 1260 bytes to 1288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Field do_early_retrans 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 early_retrans_delayed 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 syn_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. |
| 7 | Field syn_data_acked has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field syn_fastopen 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 260 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 408 bytes to 444 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field tc1 has been renamed to trip_hyst_attrs. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 36 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle_tick has been renamed to last_tick. | 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 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 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field need_flush_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 | Size of this type has been changed from 60 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 72 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field uid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 84 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 48 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field low_latency 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 996 bytes to 400 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 termios has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| 3 | The pointer level of field termios_locked 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 180 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field num has been changed from int to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field flags has been changed from int to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field wq_idle has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 20 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 dcd_change has been changed from void(*)(struct tty_struct*, unsigned int, struct pps_event_time*) to void(*)(struct tty_struct*, 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 2 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type has been changed from __kernel_nlink_t to __u32. | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field insn has been changed from unsigned long to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field fixup has been changed from unsigned long 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 332 bytes to 340 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_stop_on_short 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 resuming_ports 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 lpm_disable_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 | Field u1_params has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 u2_params has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 560 bytes to 592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field usb3_lpm_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. |
| 6 | Field port_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 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 116 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 276 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field may_mount_sysfs has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field owner has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 parent has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 gid_map has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field proc_inum has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been 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 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. |
| 7 | Field projid_map has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 8 | Field uid_map has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 9 | 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. |
| 10 | Size of this type has been changed from 536 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 11 | Field may_mount_proc 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 proc_inum has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 400 bytes to 404 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 228 bytes to 232 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field caller 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 caller has been changed from void* to void const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 208 bytes to 236 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rescue_wq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field current_cwq has been renamed to current_pwq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field gcwq has been renamed to pool. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_wq has been renamed to pool_wq. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 2 | Field nr_cwqs_to_flush has been renamed to nr_pwqs_to_flush. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field wq has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Field cpu has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Size of this type has been changed from 68 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 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 8 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field pagetable_setup_start has been renamed to pagetable_init. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field setup_hpet_msi has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 16 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_post_init has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notrack_deprecated_warning has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. 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 108 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nwords has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 28 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been renamed to portid. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfkey_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 | Type of field loginuid has been changed from uid_t to kuid_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field acquire has been changed from int(*)(struct xfrm_state*, struct xfrm_tmpl*, struct xfrm_policy*, int) to int(*)(struct xfrm_state*, struct xfrm_tmpl*, struct xfrm_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 664 bytes to 736 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 bytes to 44 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 540 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 868 bytes to 872 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 timer has been changed from void(*)(struct rpc_task*) to void(*)(struct rpc_xprt*, struct rpc_task*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field connect has been changed from void(*)(struct rpc_task*) to void(*)(struct rpc_xprt*, struct rpc_task*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from ACPI_GBL_EVENT_HANDLER to acpi_gbl_event_handler. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from acpi_tbl_handler to acpi_table_handler. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter dst_dev has been changed from struct net_device* to struct net_device const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st 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. |
| 2 | Type of 2nd parameter skb has been changed from struct sk_buff* to struct sk_buff const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | 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 | 3rd parameter running has been renamed to domain. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter running has been renamed to domain. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter list has been renamed to domain. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from uid_t to kuid_t. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter dirlen has been renamed to parentlen. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter dirlen has been changed from int* to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter loginuid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter callback has been changed from int(*)(u32, u32, u32, u16, u32, u32*) to int(*)(u32). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nd has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter nd has been changed from struct nameidata* to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter data has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Base type of 4th parameter match has been changed from int(*)(struct device*, void*) to int(*)(struct device*, void const*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to mount_info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter mntfh has been renamed to nfs_mod. | 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. |
| 2 | Type of return value has been changed from int to struct nfs_client*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to mount_info. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter mntfh has been renamed to nfs_mod. | 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. |
| 2 | Type of return value has been changed from int to struct nfs_client*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter i has been renamed to elemp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter name has been changed from struct qstr* to struct qstr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter parent has been changed from struct dentry* to struct dentry const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter inode has been changed from struct inode** to struct inode*. | 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 struct qstr* to struct qstr const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter parent has been changed from struct dentry* to struct dentry const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char 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 unsigned char* to unsigned char const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to device. | Renaming of a parameter 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 mode1 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. |
| 2 | Type of 2nd parameter mode2 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 | Type of 1st parameter handler has been changed from ACPI_GBL_EVENT_HANDLER to acpi_gbl_event_handler. | 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 u8 (1 byte). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter spec_dst has been renamed to idev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter i has been changed from struct iov_iter* to struct iov_iter const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter rcu has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter new_root has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter old_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 2nd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter grp has been changed from gid_t to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter grp has been changed from gid_t to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter grp has been changed from gid_t to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter eld has been renamed to e. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to hid. | 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 | 4th parameter ht_cap has been renamed to sta. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 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. |
| 3 | Type of 3rd parameter ht_cap_ie has been changed from struct ieee80211_ht_cap* to struct ieee80211_ht_cap const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter tx has been renamed to reason. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter owner has been changed from void* to struct dev_state*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter owner has been changed from void* to struct dev_state*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter owner has been changed from void* to struct dev_state*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter length has been renamed to nr_pages. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 7th parameter i has been changed from int to long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| 4 | Base type of 6th parameter length has been changed from int to unsigned long. | 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 unsigned long (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter request has been renamed to out_seqno. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter gid has been changed from __u32 to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter gid has been changed from __u32* to kgid_t*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter uid has been changed from __u32* to kuid_t*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter uid has been changed from __u32 to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter new_dev has been renamed to new_wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter family has been renamed to base. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter family has been changed from int to struct inet_peer_base*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to inode. | 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. |
| 2 | Type of return value has been changed from int to struct inode*. | 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 pdev has been renamed to bridge_pdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to connector. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter mode has been changed from struct drm_display_mode* to struct drm_display_mode const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter sdvo_reg has been changed from int to uint32_t. | 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 4th parameter gid has been changed from gid_t to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter uid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter uid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter uid has been renamed to user. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter gid has been renamed to group. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter gid has been changed from gid_t to kgid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter uid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mddev has been renamed to thread. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter run has been changed from void(*)(struct mddev*) to void(*)(struct md_thread*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter acknowledged has been renamed to is_new. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter nr_pages has been changed from int to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter nr_pages has been changed from int to unsigned long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter address has been renamed to start. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter snd_pid has been renamed to snd_portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nlpid has been renamed to nlportid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter sw_elem has been changed from struct ieee80211_channel_sw_ie* to struct ieee80211_channel_sw_ie 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 unsigned int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pmtype has been renamed to buf. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter mtext has been renamed to bufsz. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 4th parameter msgsz has been renamed to msgtyp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | 5th parameter msgtyp has been renamed to msgflg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 5 | 6th parameter msgflg has been renamed to msg_handler. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 6 | Type of 6th parameter msgflg has been changed from int to long(*)(void*, struct msg_msg*, size_t). | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 7 | Type of 4th parameter msgsz has been changed from size_t to long. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 8 | Type of 5th parameter msgtyp has been changed from long to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 9 | Type of 3rd parameter mtext has been changed from void* to size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 10 | Type of 2nd parameter pmtype has been changed from long* to void*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter is_dir has been renamed to lookup_flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter is_dir has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter path has been changed from struct path* to struct path const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter is_dir has been renamed to lookup_flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 4th parameter is_dir has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nd has been renamed to want_excl. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 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. |
| 2 | 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. |
| 3 | Type of 3rd parameter type_page 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 this global data has been changed from unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, enum nf_ct_ftp_type, unsigned int, unsigned int, struct nf_conntrack_expect*) to unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, enum nf_ct_ftp_type, unsigned int, unsigned int, unsigned int, struct nf_conntrack_expect*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, unsigned int, unsigned int, struct nf_conntrack_expect*) to unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, unsigned int, unsigned int, unsigned int, struct nf_conntrack_expect*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from void(*)(struct sk_buff*, s16) to void(*)(struct sk_buff*, unsigned int, s16). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int(*)(struct sk_buff*, struct nf_conn*, enum ip_conntrack_info) to int(*)(struct sk_buff*, struct nf_conn*, enum ip_conntrack_info, unsigned int). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nfs4_minor_version_ops const*[] to struct nfs4_minor_version_ops const*[1]. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter nlpid has been renamed to nlportid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter new_address has been renamed to address. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 3rd parameter new_table_length has been renamed to table_length. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter limit has been renamed to low_limit. | 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 unsigned 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 int to unsigned long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to doing. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 7th parameter unknown has been changed from int(*)(char*, char*) to int(*)(char*, char*, char const*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter dev has been changed from struct pci_dev* to struct pci_dev const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter i has been renamed to gsi. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter l has been changed from struct snd_pcm_hw_constraint_list* to struct snd_pcm_hw_constraint_list const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[3] to char const*[3] 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 return value has been changed from int to pid_t. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter parent_tid has been renamed to parent_tidptr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 4th parameter child_tid has been renamed to tls_val. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 5th parameter regs has been renamed to child_tidptr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | Type of 4th parameter child_tid has been changed from void* to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 5 | Type of 3rd parameter parent_tid has been changed from void* to int*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to filename. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter unused has been renamed to arg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rhp has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to hdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | 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. |
| 2 | Type of return value has been changed from int to struct ieee80211_reg_rule const*. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter country_ie has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pci_bus has been renamed to bus. | 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 u64 (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 u64 (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 unsigned int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flp4 has been renamed to fl4. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sdata has been renamed to local. | 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 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. |
| 2 | 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 this global data has been changed from 1 to 0. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter newset has been changed from sigset_t const* to sigset_t*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter set has been renamed to uset. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter history0 has been renamed to unused1. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter history1 has been renamed to unused2. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fclone has been renamed to flags. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter logical_apicid has been renamed to apicid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to kuid_t. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter hndl has been changed from struct sock_diag_handler* to struct sock_diag_handler const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter hnld has been changed from struct sock_diag_handler* to struct sock_diag_handler const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from long to unsigned long. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rgid has been renamed to rgidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter egid has been renamed to egidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter sgid has been renamed to sgidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ruid has been renamed to ruidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter euid has been renamed to euidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter suid has been renamed to suidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cpu_dev has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cpu_dev has been renamed to dev. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter handler has been changed from acpi_table_handler to acpi_tbl_table_handler. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter handler has been changed from acpi_table_entry_handler to acpi_tbl_entry_handler. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter handler has been changed from acpi_table_entry_handler to acpi_tbl_entry_handler. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter handler has been changed from acpi_tbl_handler to acpi_table_handler. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter table_ptr has been renamed to table. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter handler has been changed from acpi_tbl_handler to acpi_table_handler. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter orig has been renamed to tz. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter orig has been changed from u32 to struct thermal_zone_device*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter devdata has been renamed to mask. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 4th parameter ops has been renamed to devdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 5th parameter tc1 has been renamed to ops. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 4 | 6th parameter tc2 has been renamed to tzp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 5 | Type of 3rd parameter devdata has been changed from void* to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 6 | Type of 4th parameter ops has been changed from struct thermal_zone_device_ops const* to void*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 7 | Type of 5th parameter tc1 has been changed from int to struct thermal_zone_device_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 8 | Type of 6th parameter tc2 has been changed from int to struct thermal_zone_params const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 9 | Type of 1st 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 | 2nd parameter va has been renamed to start. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter va has been renamed to start. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter loginuid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rgid has been renamed to rgidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter egid has been renamed to egidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter sgid has been renamed to sgidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ruid has been renamed to ruidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter euid has been renamed to euidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 3 | 3rd parameter suid has been renamed to suidp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter uid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter s has been renamed to str. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter n has been renamed to count. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter component_id has been renamed to base_offset. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_cid_list has been changed from struct acpica_device_id_list to struct acpi_pnp_device_id_list. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to band. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter local has been changed from struct ieee80211_local* to enum ieee80211_band. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter start has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter start has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 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 int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to long. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter caller 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 8th parameter caller 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 3rd parameter caller has been changed from void* to void const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter data has been changed from void* to struct nfs_commit_data*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to hdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to dst. | 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 unsigned int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter auid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter auid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter auid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter auid has been changed from uid_t to kuid_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_BAND_60GHZ with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PCH_LPT with value 3 has been added. | No effect. |
| 2 | The member PCH_NONE with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SCAN_ABORT with value 5 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_UNDEF with value 0 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_FREE_CMA_PAGES with value 27 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member MODULE_STATE_UNFORMED with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_AUTHTYPE_SAE with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_CQM_RSSI_BEACON_LOSS_EVENT with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_IFTYPE_P2P_DEVICE with value 10 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_AUTHENTIC with value 5 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_PROP_CAPACITY_ALERT_MAX with value 41 has been added. | No effect. |
| 3 | The member POWER_SUPPLY_PROP_CAPACITY_ALERT_MIN with value 40 has been added. | No effect. |
| 4 | The member POWER_SUPPLY_PROP_CHARGE_CONTROL_LIMIT with value 31 has been added. | No effect. |
| 5 | The member POWER_SUPPLY_PROP_CHARGE_CONTROL_LIMIT_MAX with value 32 has been added. | No effect. |
| 6 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT with value 27 has been added. | No effect. |
| 7 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT_MAX with value 28 has been added. | No effect. |
| 8 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_VOLTAGE with value 29 has been added. | No effect. |
| 9 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_VOLTAGE_MAX with value 30 has been added. | No effect. |
| 10 | The member POWER_SUPPLY_PROP_TEMP_ALERT_MAX with value 45 has been added. | No effect. |
| 11 | The member POWER_SUPPLY_PROP_TEMP_ALERT_MIN with value 44 has been added. | No effect. |
| 12 | The member POWER_SUPPLY_PROP_TEMP_AMBIENT_ALERT_MAX with value 48 has been added. | No effect. |
| 13 | The member POWER_SUPPLY_PROP_TEMP_AMBIENT_ALERT_MIN with value 47 has been added. | No effect. |
| 14 | The member POWER_SUPPLY_PROP_VOLTAGE_OCV with value 14 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SDEV_TRANSPORT_OFFLINE with value 7 has been added. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.4.69 |
| Version #2 | 3.9.11 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 753 |
|---|---|
| Total Source Files | 1387 |
| Total Objects | 1 |
| Total Symbols / Types | 15466 / 8383 |
| Verdict | Incompatible (55.9%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 2085 |
| Removed Symbols | High | 840 |
| Problems with Data Types | High | 723 |
| Medium | 76 | |
| Low | 1144 | |
| Problems with Symbols | High | 134 |
| Medium | 280 | |
| Low | 132 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 412 |
| Other Changes in Symbols | - | 151 |
| Change | Effect | |
|---|---|---|
| 1 | Field handler_obj has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_notify_info' has no member named 'handler_obj'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_device' has no member named 'device_notify'. |
| 2 | Field system_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_device' has no member named 'system_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_notify_common' has no member named 'device_notify'. |
| 2 | Field system_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_notify_common' has no member named 'system_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_power_resource' has no member named 'device_notify'. |
| 2 | Field system_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_power_resource' has no member named 'system_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_processor' has no member named 'device_notify'. |
| 2 | Field system_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_processor' has no member named 'system_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_thermal_zone' has no member named 'device_notify'. |
| 2 | Field system_notify has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_object_thermal_zone' has no member named 'system_notify'. |
| Change | Effect | |
|---|---|---|
| 1 | Field busnum has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_root_info' has no member named 'busnum'. |
| 2 | Field resources has been renamed to res_offset. | Recompilation of a client program may be broken with the error message: struct pci_root_info has no member named resources. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_pci_driver' has no member named 'next'. |
| Change | Effect | |
|---|---|---|
| 1 | Field find_bridge has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_bus_type' has no member named 'find_bridge'. |
| 2 | Field bus has been renamed to name. | Recompilation of a client program may be broken with the error message: struct acpi_bus_type has no member named bus. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device' has no member named 'bus_ops'. |
| 2 | Field ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device' has no member named 'ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field lockable 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 'lockable'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bind has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_ops' has no member named 'bind'. |
| 2 | Field resume has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_ops' has no member named 'resume'. |
| 3 | Field start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_ops' has no member named 'start'. |
| 4 | Field suspend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_ops' has no member named 'suspend'. |
| 5 | Field unbind has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_ops' has no member named 'unbind'. |
| Change | Effect | |
|---|---|---|
| 1 | Field id 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 'id'. |
| Change | Effect | |
|---|---|---|
| 1 | Field revision_iD has been renamed to revision_ID. | Recompilation of a client program may be broken with the error message: struct acpi_resource_extended_address64 has no member named revision_iD. |
| Change | Effect | |
|---|---|---|
| 1 | Field C2latency has been renamed to c2_latency. | Recompilation of a client program may be broken with the error message: struct acpi_table_fadt has no member named C2latency. |
| 2 | Field C3latency has been renamed to c3_latency. | Recompilation of a client program may be broken with the error message: struct acpi_table_fadt has no member named C3latency. |
| 3 | Field S4bios_request has been renamed to s4_bios_request. | Recompilation of a client program may be broken with the error message: struct acpi_table_fadt has no member named S4bios_request. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct kioctx has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field revision_iD has been renamed to revision_ID. | Recompilation of a client program may be broken with the error message: struct aml_resource_extended_address64 has no member named revision_iD. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_mask_to_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_mask_to_apicid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field previous has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct audit_context' has no member named 'previous'. |
| Change | Effect | |
|---|---|---|
| 1 | Field auditdeny has been renamed to ssid. | Recompilation of a client program may be broken with the error message: struct selinux_audit_data has no member named auditdeny. |
| 2 | Field slad has been renamed to tsid. | Recompilation of a client program may be broken with the error message: struct selinux_audit_data has no member named slad. |
| Change | Effect | |
|---|---|---|
| 1 | Field revision has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_battery' has no member named 'revision'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'bp'. |
| 2 | Field chunks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'chunks'. |
| 3 | Field chunkshift has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'chunkshift'. |
| 4 | Field file has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'file'. |
| 5 | Field file_pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'file_pages'. |
| 6 | Field filemap has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'filemap'. |
| 7 | Field filemap_attr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'filemap_attr'. |
| 8 | Field last_page_size has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'last_page_size'. |
| 9 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'lock'. |
| 10 | Field missing_pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'missing_pages'. |
| 11 | Field pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'pages'. |
| 12 | Field sb_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bitmap' has no member named 'sb_page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bi_destructor has been renamed to bi_pool. | Recompilation of a client program may be broken with the error message: struct bio has no member named bi_destructor. |
| Change | Effect | |
|---|---|---|
| 1 | Field should_sort has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct blk_plug' has no member named 'should_sort'. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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 'rq'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tsf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_bss' has no member named 'tsf'. |
| 2 | Field information_elements has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_bss' has no member named 'information_elements'. |
| 3 | Field len_proberesp_ies has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_bss' has no member named 'len_proberesp_ies'. |
| 4 | Field len_information_elements has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_bss' has no member named 'len_information_elements'. |
| 5 | Field len_beacon_ies has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_bss' has no member named 'len_beacon_ies'. |
| 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_ibss_params' has no member named 'channel'. |
| 2 | Field channel_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_ibss_params' has no member named 'channel_type'. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_channel 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 'set_channel'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been renamed to wdev. | Recompilation of a client program may be broken with the error message: struct cfg80211_scan_request has no member named dev. |
| Change | Effect | |
|---|---|---|
| 1 | Field wext has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wiphy' has no member named 'wext'. |
| Change | Effect | |
|---|---|---|
| 1 | Field wext has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'wext'. |
| 2 | Field ap_unexpected_nlpid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wireless_dev' has no member named 'ap_unexpected_nlpid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field actual_subsys_bits has been renamed to actual_subsys_mask. | Recompilation of a client program may be broken with the error message: struct cgroupfs_root has no member named actual_subsys_bits. |
| 2 | Field subsys_bits has been renamed to subsys_mask. | Recompilation of a client program may be broken with the error message: struct cgroupfs_root has no member named subsys_bits. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct css_id has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to cft_q_node. | Recompilation of a client program may be broken with the error message: struct cgroup has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field hierarchy_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'hierarchy_mutex'. |
| 2 | Field populate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'populate'. |
| 3 | Field post_clone has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'post_clone'. |
| 4 | Field subsys_key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'subsys_key'. |
| 5 | Field create has been renamed to css_alloc. | Recompilation of a client program may be broken with the error message: struct cgroup_subsys has no member named create. |
| 6 | Field destroy has been renamed to css_offline. | Recompilation of a client program may be broken with the error message: struct cgroup_subsys has no member named destroy. |
| 7 | Field pre_destroy has been renamed to css_online. | Recompilation of a client program may be broken with the error message: struct cgroup_subsys has no member named pre_destroy. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct css_set has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field ref has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_internal_bss' has no member named 'ref'. |
| 2 | Field proberesp_ies_allocated has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_internal_bss' has no member named 'proberesp_ies_allocated'. |
| 3 | Field beacon_ies_allocated has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cfg80211_internal_bss' has no member named 'beacon_ies_allocated'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_beacons_nlpid 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 'ap_beacons_nlpid'. |
| 2 | Field netdev_list has been renamed to wdev_list. | Recompilation of a client program may be broken with the error message: struct cfg80211_registered_device has no member named netdev_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field power_specified has been renamed to refcnt. | Recompilation of a client program may be broken with the error message: struct cpuidle_driver has no member named power_specified. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_state' has no member named 'disable'. |
| Change | Effect | |
|---|---|---|
| 1 | Field driver_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuidle_state_usage' has no member named 'driver_data'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tgcred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cred' has no member named 'tgcred'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hash has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct qstr' has no member named 'hash'. |
| 2 | Field len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct qstr' has no member named 'len'. |
| Change | Effect | |
|---|---|---|
| 1 | Field split_io has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_target' has no member named 'split_io'. |
| 2 | Field num_discard_requests has been renamed to num_discard_bios. | Recompilation of a client program may be broken with the error message: struct dm_target has no member named num_discard_requests. |
| 3 | Field num_flush_requests has been renamed to num_flush_bios. | Recompilation of a client program may be broken with the error message: struct dm_target has no member named num_flush_requests. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct target_type' has no member named 'flush'. |
| Change | Effect | |
|---|---|---|
| 1 | Field target_request_nr has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tio_pool has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dm_md_mempools' has no member named 'tio_pool'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tio_pool 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 'tio_pool'. |
| Change | Effect | |
|---|---|---|
| 1 | Field property_ids has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'property_ids'. |
| 2 | Field property_values has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'property_values'. |
| Change | Effect | |
|---|---|---|
| 1 | Field raw_edid 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 'raw_edid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_hadjusted has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_mode' has no member named 'crtc_hadjusted'. |
| 2 | Field crtc_vadjusted has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_display_mode' has no member named 'crtc_vadjusted'. |
| Change | Effect | |
|---|---|---|
| 1 | Field head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_mode_set' has no member named 'head'. |
| Change | Effect | |
|---|---|---|
| 1 | Field c has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'c'. |
| 2 | Field hfreq_start_khz has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'hfreq_start_khz'. |
| 3 | Field j has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'j'. |
| 4 | Field k has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'k'. |
| 5 | Field m has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'm'. |
| 6 | Field sec_gtf_toggle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct detailed_data_monitor_range' has no member named 'sec_gtf_toggle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_fb_helper' has no member named 'mode'. |
| 2 | Field saved_fb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_fb_helper' has no member named 'saved_fb'. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_hit_size 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 'scan_hit_size'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dma_wait has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_buf' has no member named 'dma_wait'. |
| Change | Effect | |
|---|---|---|
| 1 | Field queue_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 'queue_count'. |
| 2 | Field queue_slots 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 'queue_slots'. |
| 3 | Field queuelist 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 'queuelist'. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_buffers_idlelocked 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 'reclaim_buffers_idlelocked'. |
| 2 | Field reclaim_buffers_locked 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 'reclaim_buffers_locked'. |
| 3 | Field reclaim_buffers 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 'reclaim_buffers'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct dst_entry has no member named rcu_head. |
| 2 | Field _neighbour has been renamed to from. | Recompilation of a client program may be broken with the error message: struct dst_entry has no member named _neighbour. |
| Change | Effect | |
|---|---|---|
| 1 | Field from has been renamed to rt_next. | Recompilation of a client program may be broken with the error message: anon-union-dst.h-39 has no member named from. |
| 2 | Field expires has been renamed to next. | Recompilation of a client program may be broken with the error message: anon-union-dst.h-39 has no member named expires. |
| Change | Effect | |
|---|---|---|
| 1 | Field tz_utc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fat_mount_options' has no member named 'tz_utc'. |
| Change | Effect | |
|---|---|---|
| 1 | Field assoc_mapping has been renamed to private_data. | Recompilation of a client program may be broken with the error message: struct address_space has no member named assoc_mapping. |
| Change | Effect | |
|---|---|---|
| 1 | Field truncate 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 'truncate'. |
| 2 | Field truncate_range has been renamed to update_time. | Recompilation of a client program may be broken with the error message: struct inode_operations has no member named truncate_range. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_dirt 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_dirt'. |
| 2 | Field s_frozen 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_frozen'. |
| 3 | Field s_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct super_block' has no member named 's_lock'. |
| 4 | Field s_wait_unfrozen 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_wait_unfrozen'. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_super 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 'write_super'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark_lock 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_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_g_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fsnotify_mark' has no member named 'free_g_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fa has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inotify_group_private_data' has no member named 'fa'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct disk_part_tbl has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hd_struct' has no member named 'rcu_head'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_beep' has no member named 'mode'. |
| 2 | Field register_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_beep' has no member named 'register_work'. |
| 3 | Field request_enable has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_beep' has no member named 'request_enable'. |
| 4 | Field unregister_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_beep' has no member named 'unregister_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field conn_lists 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 'conn_lists'. |
| 2 | Field ignore_misc_bit 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 'ignore_misc_bit'. |
| Change | Effect | |
|---|---|---|
| 1 | Field post_suspend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_codec_ops' has no member named 'post_suspend'. |
| 2 | Field pre_resume has been renamed to check_power_status. | Recompilation of a client program may be broken with the error message: struct hda_codec_ops has no member named pre_resume. |
| Change | Effect | |
|---|---|---|
| 1 | Field aud_synch_delay has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'aud_synch_delay'. |
| 2 | Field baseline_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'baseline_len'. |
| 3 | Field cea_edid_ver has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'cea_edid_ver'. |
| 4 | Field conn_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'conn_type'. |
| 5 | Field eld_ver has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'eld_ver'. |
| 6 | Field manufacture_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'manufacture_id'. |
| 7 | Field monitor_name has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'monitor_name'. |
| 8 | Field port_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'port_id'. |
| 9 | Field product_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'product_id'. |
| 10 | Field sad has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'sad'. |
| 11 | Field sad_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'sad_count'. |
| 12 | Field spk_alloc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'spk_alloc'. |
| 13 | Field support_ai has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'support_ai'. |
| 14 | Field support_hdcp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hdmi_eld' has no member named 'support_hdcp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field deferred_free_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'deferred_free_list'. |
| 2 | Field flushing_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'flushing_list'. |
| 3 | Field gtt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'gtt'. |
| 4 | Field gtt_end has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'gtt_end'. |
| 5 | Field gtt_mappable_end has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'gtt_mappable_end'. |
| 6 | Field gtt_mapping has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'gtt_mapping'. |
| 7 | Field gtt_total has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'gtt_total'. |
| 8 | Field mappable_gtt_total has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'mappable_gtt_total'. |
| 9 | Field pinned_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'pinned_list'. |
| 10 | Field wedged has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-i915_drv.h-601' has no member named 'wedged'. |
| 11 | Field gtt_list has been renamed to unbound_list. | Recompilation of a client program may be broken with the error message: anon-struct-i915_drv.h-601 has no member named gtt_list. |
| 12 | Field gtt_start has been renamed to stolen_base. | Recompilation of a client program may be broken with the error message: anon-struct-i915_drv.h-601 has no member named gtt_start. |
| Change | Effect | |
|---|---|---|
| 1 | Field dpms has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'dpms'. |
| 2 | Field force_wake_get has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'force_wake_get'. |
| 3 | Field force_wake_put has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_display_funcs' has no member named 'force_wake_put'. |
| 4 | Field init_pch_clock_gating has been renamed to off. | Recompilation of a client program may be broken with the error message: struct drm_i915_display_funcs has no member named init_pch_clock_gating. |
| Change | Effect | |
|---|---|---|
| 1 | Field setup_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_fence_reg' has no member named 'setup_seqno'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gpu_write_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_gem_object' has no member named 'gpu_write_list'. |
| 2 | Field last_fenced_ring 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 'last_fenced_ring'. |
| 3 | Field last_rendering_seqno 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 'last_rendering_seqno'. |
| 4 | Field num_sg 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 'num_sg'. |
| 5 | Field page_cpu_valid 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 'page_cpu_valid'. |
| 6 | Field pending_flip 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 'pending_flip'. |
| 7 | Field pending_gpu_write 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 'pending_gpu_write'. |
| 8 | Field sg_list has been renamed to has_dma_mapping. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named sg_list. |
| 9 | Field tiling_changed has been renamed to fence_dirty. | Recompilation of a client program may be broken with the error message: struct drm_i915_gem_object has no member named tiling_changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field adpa 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 'adpa'. |
| 2 | Field allow_batchbuffer 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 'allow_batchbuffer'. |
| 3 | Field back_offset 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 'back_offset'. |
| 4 | Field busy 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 'busy'. |
| 5 | Field c_m 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 'c_m'. |
| 6 | Field chipset_power 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 'chipset_power'. |
| 7 | Field corr 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 'corr'. |
| 8 | Field counter 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 'counter'. |
| 9 | Field cpp 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 'cpp'. |
| 10 | Field cur_delay 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 'cur_delay'. |
| 11 | Field current_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 'current_page'. |
| 12 | Field dvob 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 'dvob'. |
| 13 | Field dvoc 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 'dvoc'. |
| 14 | Field error_completion 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 'error_completion'. |
| 15 | Field error_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'error_lock'. |
| 16 | Field error_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'error_work'. |
| 17 | Field first_error 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 'first_error'. |
| 18 | Field flip_pending_is_done 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 'flip_pending_is_done'. |
| 19 | Field fmax 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 'fmax'. |
| 20 | Field front_offset 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 'front_offset'. |
| 21 | Field fstart 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 'fstart'. |
| 22 | Field gfx_power 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 'gfx_power'. |
| 23 | Field hangcheck_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'hangcheck_count'. |
| 24 | Field hangcheck_timer 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 'hangcheck_timer'. |
| 25 | Field has_gem 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 'has_gem'. |
| 26 | Field hws_map 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_map'. |
| 27 | Field idle_timer 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 'idle_timer'. |
| 28 | Field idle_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'idle_work'. |
| 29 | Field int_edp_connector has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'int_edp_connector'. |
| 30 | Field int_lvds_connector has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'int_lvds_connector'. |
| 31 | Field last_acthd 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 'last_acthd'. |
| 32 | Field last_acthd_blt 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 'last_acthd_blt'. |
| 33 | Field last_acthd_bsd 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 'last_acthd_bsd'. |
| 34 | Field last_count1 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 'last_count1'. |
| 35 | Field last_count2 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 'last_count2'. |
| 36 | Field last_gpu_reset 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 'last_gpu_reset'. |
| 37 | Field last_instdone 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 'last_instdone'. |
| 38 | Field last_instdone1 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 'last_instdone1'. |
| 39 | Field last_time1 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 'last_time1'. |
| 40 | Field last_time2 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 'last_time2'. |
| 41 | Field lid_notifier 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 'lid_notifier'. |
| 42 | Field lvds 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'. |
| 43 | Field lvds_val has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'lvds_val'. |
| 44 | Field max_delay 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 'max_delay'. |
| 45 | Field mchdev_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'mchdev_lock'. |
| 46 | Field min_delay 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 'min_delay'. |
| 47 | Field modeset_on_lid 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 'modeset_on_lid'. |
| 48 | Field page_flipping 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 'page_flipping'. |
| 49 | Field pch_irq_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'pch_irq_mask'. |
| 50 | Field pm_iir 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 'pm_iir'. |
| 51 | Field ppcr 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 'ppcr'. |
| 52 | Field pwrctx 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 'pwrctx'. |
| 53 | Field r_t 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 'r_t'. |
| 54 | Field renderctx 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 'renderctx'. |
| 55 | Field rps_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'rps_lock'. |
| 56 | Field rps_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'rps_work'. |
| 57 | Field saveADPA 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 'saveADPA'. |
| 58 | Field saveAR 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 'saveAR'. |
| 59 | Field saveAR_INDEX 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 'saveAR_INDEX'. |
| 60 | Field saveBCLRPAT_A 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 'saveBCLRPAT_A'. |
| 61 | Field saveBCLRPAT_B 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 'saveBCLRPAT_B'. |
| 62 | Field saveBLC_CPU_PWM_CTL 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 'saveBLC_CPU_PWM_CTL'. |
| 63 | Field saveBLC_CPU_PWM_CTL2 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 'saveBLC_CPU_PWM_CTL2'. |
| 64 | Field saveBLC_HIST_CTL 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 'saveBLC_HIST_CTL'. |
| 65 | Field saveBLC_PWM_CTL 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 'saveBLC_PWM_CTL'. |
| 66 | Field saveBLC_PWM_CTL2 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 'saveBLC_PWM_CTL2'. |
| 67 | Field saveCACHE_MODE_0 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 'saveCACHE_MODE_0'. |
| 68 | Field saveCR 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 'saveCR'. |
| 69 | Field saveCURABASE 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 'saveCURABASE'. |
| 70 | Field saveCURACNTR 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 'saveCURACNTR'. |
| 71 | Field saveCURAPOS 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 'saveCURAPOS'. |
| 72 | Field saveCURBBASE 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 'saveCURBBASE'. |
| 73 | Field saveCURBCNTR 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 'saveCURBCNTR'. |
| 74 | Field saveCURBPOS 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 'saveCURBPOS'. |
| 75 | Field saveCURSIZE 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 'saveCURSIZE'. |
| 76 | Field saveDACMASK 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 'saveDACMASK'. |
| 77 | Field saveDEIER 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 'saveDEIER'. |
| 78 | Field saveDEIMR 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 'saveDEIMR'. |
| 79 | Field saveDISP_ARB_CTL 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 'saveDISP_ARB_CTL'. |
| 80 | Field saveDPFC_CB_BASE 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 'saveDPFC_CB_BASE'. |
| 81 | Field saveDPLL_A_MD 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 'saveDPLL_A_MD'. |
| 82 | Field saveDPLL_B 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 'saveDPLL_B'. |
| 83 | Field saveDPLL_B_MD 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 'saveDPLL_B_MD'. |
| 84 | Field saveDP_B 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 'saveDP_B'. |
| 85 | Field saveDP_C 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 'saveDP_C'. |
| 86 | Field saveDP_D 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 'saveDP_D'. |
| 87 | Field saveDSPAADDR 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 'saveDSPAADDR'. |
| 88 | Field saveDSPACNTR 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 'saveDSPACNTR'. |
| 89 | Field saveDSPAPOS 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 'saveDSPAPOS'. |
| 90 | Field saveDSPARB 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 'saveDSPARB'. |
| 91 | Field saveDSPASIZE 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 'saveDSPASIZE'. |
| 92 | Field saveDSPASTRIDE 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 'saveDSPASTRIDE'. |
| 93 | Field saveDSPASURF 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 'saveDSPASURF'. |
| 94 | Field saveDSPATILEOFF 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 'saveDSPATILEOFF'. |
| 95 | Field saveDSPBADDR 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 'saveDSPBADDR'. |
| 96 | Field saveDSPBCNTR 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 'saveDSPBCNTR'. |
| 97 | Field saveDSPBPOS 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 'saveDSPBPOS'. |
| 98 | Field saveDSPBSIZE 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 'saveDSPBSIZE'. |
| 99 | Field saveDSPBSTRIDE 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 'saveDSPBSTRIDE'. |
| 100 | Field saveDSPBSURF 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 'saveDSPBSURF'. |
| 101 | Field saveDSPBTILEOFF 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 'saveDSPBTILEOFF'. |
| 102 | Field saveDVOA 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 'saveDVOA'. |
| 103 | Field saveDVOB 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 'saveDVOB'. |
| 104 | Field saveDVOC 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 'saveDVOC'. |
| 105 | Field saveFBC_CFB_BASE 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 'saveFBC_CFB_BASE'. |
| 106 | Field saveFBC_CONTROL 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 'saveFBC_CONTROL'. |
| 107 | Field saveFBC_CONTROL2 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 'saveFBC_CONTROL2'. |
| 108 | Field saveFBC_LL_BASE 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 'saveFBC_LL_BASE'. |
| 109 | Field saveFDI_RXA_CTL 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 'saveFDI_RXA_CTL'. |
| 110 | Field saveFDI_RXA_IMR 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 'saveFDI_RXA_IMR'. |
| 111 | Field saveFDI_RXB_CTL 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 'saveFDI_RXB_CTL'. |
| 112 | Field saveFDI_RXB_IMR 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 'saveFDI_RXB_IMR'. |
| 113 | Field saveFDI_TXA_CTL 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 'saveFDI_TXA_CTL'. |
| 114 | Field saveFDI_TXB_CTL 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 'saveFDI_TXB_CTL'. |
| 115 | Field saveFENCE 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 'saveFENCE'. |
| 116 | Field saveFPA0 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 'saveFPA0'. |
| 117 | Field saveFPB0 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 'saveFPB0'. |
| 118 | Field saveFPB1 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 'saveFPB1'. |
| 119 | Field saveGR 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 'saveGR'. |
| 120 | Field saveGTIER 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 'saveGTIER'. |
| 121 | Field saveGTIMR 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 'saveGTIMR'. |
| 122 | Field saveHBLANK_A 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 'saveHBLANK_A'. |
| 123 | Field saveHBLANK_B 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 'saveHBLANK_B'. |
| 124 | Field saveHSYNC_A 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 'saveHSYNC_A'. |
| 125 | Field saveHSYNC_B 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 'saveHSYNC_B'. |
| 126 | Field saveHTOTAL_A 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 'saveHTOTAL_A'. |
| 127 | Field saveHTOTAL_B 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 'saveHTOTAL_B'. |
| 128 | Field saveHWS 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 'saveHWS'. |
| 129 | Field saveIER 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 'saveIER'. |
| 130 | Field saveIIR 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 'saveIIR'. |
| 131 | Field saveIMR 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 'saveIMR'. |
| 132 | Field saveLBB 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 'saveLBB'. |
| 133 | Field saveLVDS 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 'saveLVDS'. |
| 134 | Field saveMCHBAR_RENDER_STANDBY 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 'saveMCHBAR_RENDER_STANDBY'. |
| 135 | Field saveMI_ARB_STATE 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 'saveMI_ARB_STATE'. |
| 136 | Field saveMSR 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 'saveMSR'. |
| 137 | Field savePCH_DREF_CONTROL 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 'savePCH_DREF_CONTROL'. |
| 138 | Field savePCH_PORT_HOTPLUG 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 'savePCH_PORT_HOTPLUG'. |
| 139 | Field savePFA_CTL_1 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 'savePFA_CTL_1'. |
| 140 | Field savePFA_WIN_POS has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'savePFA_WIN_POS'. |
| 141 | Field savePFA_WIN_SZ 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 'savePFA_WIN_SZ'. |
| 142 | Field savePFB_CTL_1 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 'savePFB_CTL_1'. |
| 143 | Field savePFB_WIN_POS has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'savePFB_WIN_POS'. |
| 144 | Field savePFB_WIN_SZ 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 'savePFB_WIN_SZ'. |
| 145 | Field savePFIT_CONTROL 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 'savePFIT_CONTROL'. |
| 146 | Field savePFIT_PGM_RATIOS 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 'savePFIT_PGM_RATIOS'. |
| 147 | Field savePIPEACONF 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 'savePIPEACONF'. |
| 148 | Field savePIPEASRC 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 'savePIPEASRC'. |
| 149 | Field savePIPEASTAT 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 'savePIPEASTAT'. |
| 150 | Field savePIPEA_DATA_M1 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 'savePIPEA_DATA_M1'. |
| 151 | Field savePIPEA_DATA_N1 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 'savePIPEA_DATA_N1'. |
| 152 | Field savePIPEA_DP_LINK_M 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 'savePIPEA_DP_LINK_M'. |
| 153 | Field savePIPEA_DP_LINK_N 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 'savePIPEA_DP_LINK_N'. |
| 154 | Field savePIPEA_GMCH_DATA_M 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 'savePIPEA_GMCH_DATA_M'. |
| 155 | Field savePIPEA_GMCH_DATA_N 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 'savePIPEA_GMCH_DATA_N'. |
| 156 | Field savePIPEA_LINK_M1 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 'savePIPEA_LINK_M1'. |
| 157 | Field savePIPEA_LINK_N1 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 'savePIPEA_LINK_N1'. |
| 158 | Field savePIPEBCONF 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 'savePIPEBCONF'. |
| 159 | Field savePIPEBSRC 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 'savePIPEBSRC'. |
| 160 | Field savePIPEBSTAT 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 'savePIPEBSTAT'. |
| 161 | Field savePIPEB_DATA_M1 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 'savePIPEB_DATA_M1'. |
| 162 | Field savePIPEB_DATA_N1 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 'savePIPEB_DATA_N1'. |
| 163 | Field savePIPEB_DP_LINK_M 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 'savePIPEB_DP_LINK_M'. |
| 164 | Field savePIPEB_DP_LINK_N 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 'savePIPEB_DP_LINK_N'. |
| 165 | Field savePIPEB_GMCH_DATA_M 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 'savePIPEB_GMCH_DATA_M'. |
| 166 | Field savePIPEB_GMCH_DATA_N 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 'savePIPEB_GMCH_DATA_N'. |
| 167 | Field savePIPEB_LINK_M1 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 'savePIPEB_LINK_M1'. |
| 168 | Field savePIPEB_LINK_N1 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 'savePIPEB_LINK_N1'. |
| 169 | Field savePP_CONTROL 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 'savePP_CONTROL'. |
| 170 | Field savePP_DIVISOR 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 'savePP_DIVISOR'. |
| 171 | Field savePP_OFF 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 'savePP_OFF'. |
| 172 | Field savePP_OFF_DELAYS 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 'savePP_OFF_DELAYS'. |
| 173 | Field savePP_ON 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 'savePP_ON'. |
| 174 | Field savePP_ON_DELAYS 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 'savePP_ON_DELAYS'. |
| 175 | Field saveSR 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 'saveSR'. |
| 176 | Field saveSWF0 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 'saveSWF0'. |
| 177 | Field saveSWF1 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 'saveSWF1'. |
| 178 | Field saveSWF2 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 'saveSWF2'. |
| 179 | Field saveTRANSACONF 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 'saveTRANSACONF'. |
| 180 | Field saveTRANSBCONF 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 'saveTRANSBCONF'. |
| 181 | Field saveTRANS_HBLANK_A 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 'saveTRANS_HBLANK_A'. |
| 182 | Field saveTRANS_HBLANK_B 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 'saveTRANS_HBLANK_B'. |
| 183 | Field saveTRANS_HSYNC_A 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 'saveTRANS_HSYNC_A'. |
| 184 | Field saveTRANS_HSYNC_B 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 'saveTRANS_HSYNC_B'. |
| 185 | Field saveTRANS_HTOTAL_A 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 'saveTRANS_HTOTAL_A'. |
| 186 | Field saveTRANS_HTOTAL_B 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 'saveTRANS_HTOTAL_B'. |
| 187 | Field saveTRANS_VBLANK_A 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 'saveTRANS_VBLANK_A'. |
| 188 | Field saveTRANS_VBLANK_B 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 'saveTRANS_VBLANK_B'. |
| 189 | Field saveTRANS_VSYNC_A 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 'saveTRANS_VSYNC_A'. |
| 190 | Field saveTRANS_VSYNC_B 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 'saveTRANS_VSYNC_B'. |
| 191 | Field saveTRANS_VTOTAL_A 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 'saveTRANS_VTOTAL_A'. |
| 192 | Field saveTRANS_VTOTAL_B 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 'saveTRANS_VTOTAL_B'. |
| 193 | Field saveVBLANK_A 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 'saveVBLANK_A'. |
| 194 | Field saveVBLANK_B 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 'saveVBLANK_B'. |
| 195 | Field saveVGA0 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 'saveVGA0'. |
| 196 | Field saveVGA1 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 'saveVGA1'. |
| 197 | Field saveVGACNTRL 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 'saveVGACNTRL'. |
| 198 | Field saveVGA_PD 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 'saveVGA_PD'. |
| 199 | Field saveVSYNC_A 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 'saveVSYNC_A'. |
| 200 | Field saveVSYNC_B 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 'saveVSYNC_B'. |
| 201 | Field saveVTOTAL_A 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 'saveVTOTAL_A'. |
| 202 | Field saveVTOTAL_B 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 'saveVTOTAL_B'. |
| 203 | Field save_palette_a 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 'save_palette_a'. |
| 204 | Field save_palette_b 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 'save_palette_b'. |
| 205 | Field sr01 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 'sr01'. |
| 206 | Field tex_lru_log_granularity 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 'tex_lru_log_granularity'. |
| 207 | Field vblank_pipe 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 'vblank_pipe'. |
| 208 | Field saveDPLL_A has been renamed to fdi_rx_config. | Recompilation of a client program may be broken with the error message: struct drm_i915_private has no member named saveDPLL_A. |
| 209 | Field saveFPA1 has been renamed to hw_context_size. | Recompilation of a client program may be broken with the error message: struct drm_i915_private has no member named saveFPA1. |
| Change | Effect | |
|---|---|---|
| 1 | Field idmap_key_cons has been renamed to idmap_upcall_data. | Recompilation of a client program may be broken with the error message: struct idmap has no member named idmap_key_cons. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct idr_layer' has no member named 'rcu_head'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 6 has been changed from IEEE80211_QUEUE_STOP_REASON_CHTYPE_CHANGE to IEEE80211_QUEUE_STOP_REASON_OFFCHANNEL. | Recompilation of a client program may be broken with the error message: 'IEEE80211_QUEUE_STOP_REASON_CHTYPE_CHANGE' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct beacon_data has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_period has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss' has no member named 'dtim_period'. |
| 2 | Field last_probe_resp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss' has no member named 'last_probe_resp'. |
| 3 | Field ssid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss' has no member named 'ssid'. |
| 4 | Field ssid_len has been renamed to device_ts_beacon. | Recompilation of a client program may be broken with the error message: struct ieee80211_bss has no member named ssid_len. |
| Change | Effect | |
|---|---|---|
| 1 | Field dtim_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'dtim_count'. |
| 2 | Field ps_bc_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'ps_bc_buf'. |
| 3 | Field tim has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'tim'. |
| 4 | Field dtim_bc_mc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'dtim_bc_mc'. |
| 5 | Field num_sta_authorized has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'num_sta_authorized'. |
| 6 | Field num_sta_ps has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ap' has no member named 'num_sta_ps'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_smps 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 'ap_smps'. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_dynamic_ps 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 'disable_dynamic_ps'. |
| 2 | Field dynamic_ps_user_timeout 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 'dynamic_ps_user_timeout'. |
| 3 | Field hw_roc_channel has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'hw_roc_channel'. |
| 4 | Field hw_roc_channel_type 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 'hw_roc_channel_type'. |
| 5 | Field hw_roc_duration 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 'hw_roc_duration'. |
| 6 | Field hw_roc_for_tx 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 'hw_roc_for_tx'. |
| 7 | Field hw_roc_skb 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 'hw_roc_skb'. |
| 8 | Field hw_roc_skb_for_status 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 'hw_roc_skb_for_status'. |
| 9 | Field power_constr_level 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 'power_constr_level'. |
| 10 | Field recalc_smps 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 'recalc_smps'. |
| 11 | Field running_rx_handler 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 'running_rx_handler'. |
| 12 | Field rx_skb_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'rx_skb_queue'. |
| 13 | Field sched_scan_ies 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 'sched_scan_ies'. |
| 14 | Field sched_scanning 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 'sched_scanning'. |
| 15 | Field tmp_channel_type 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 'tmp_channel_type'. |
| 16 | Field wmm_acm 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 'wmm_acm'. |
| 17 | Field work_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'work_list'. |
| 18 | Field work_timer 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_timer'. |
| 19 | Field work_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'work_work'. |
| 20 | Field hw_roc_cookie has been renamed to monitor_sdata. | Recompilation of a client program may be broken with the error message: struct ieee80211_local has no member named hw_roc_cookie. |
| 21 | Field hw_roc_dev has been renamed to hw_roc_start_time. | Recompilation of a client program may be broken with the error message: struct ieee80211_local has no member named hw_roc_dev. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_information_ie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_mgd_assoc_data' has no member named 'ht_information_ie'. |
| 2 | Field sent_assoc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_mgd_assoc_data' has no member named 'sent_assoc'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ie has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_mgd_auth_data' has no member named 'ie'. |
| 2 | Field ie_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_mgd_auth_data' has no member named 'ie_len'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_opmode_valid 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 'ht_opmode_valid'. |
| 2 | Field old_idle 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 'old_idle'. |
| 3 | Field arp_filter_state has been renamed to needed_rx_chains. | Recompilation of a client program may be broken with the error message: struct ieee80211_sub_if_data has no member named arp_filter_state. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_tx_data' has no member named 'channel'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ch_switch_elem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'ch_switch_elem'. |
| 2 | Field ch_switch_elem_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'ch_switch_elem_len'. |
| 3 | Field pwr_constr_elem_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'pwr_constr_elem_len'. |
| 4 | Field wpa has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'wpa'. |
| 5 | Field wpa_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'wpa_len'. |
| 6 | Field ht_info_elem has been renamed to vht_cap_elem. | Recompilation of a client program may be broken with the error message: struct ieee802_11_elems has no member named ht_info_elem. |
| Change | Effect | |
|---|---|---|
| 1 | Field estab_plinks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mesh_stats' has no member named 'estab_plinks'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_peer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_connection_sock_af_ops' has no member named 'get_peer'. |
| Change | Effect | |
|---|---|---|
| 1 | Field off has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_cork' has no member named 'off'. |
| 2 | Field page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_cork' has no member named 'page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field inet_dport 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_dport'. |
| 2 | Field inet_num 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_num'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tw_dport 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_dport'. |
| 2 | Field tw_num 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_num'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct in_device has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct in_ifaddr has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcp_ts has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inetpeer.h-53' has no member named 'tcp_ts'. |
| 2 | Field tcp_ts_stamp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-inetpeer.h-53' has no member named 'tcp_ts_stamp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pmtu_expires 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 'pmtu_expires'. |
| 2 | Field pmtu_learned 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 'pmtu_learned'. |
| 3 | Field pmtu_orig 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 'pmtu_orig'. |
| 4 | Field redirect_learned has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet_peer' has no member named 'redirect_learned'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mtsize 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 'mtsize'. |
| 2 | Field slot 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 'slot'. |
| 3 | Field sync 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 'sync'. |
| 4 | Field trkid 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 'trkid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_handler' has no member named 'fops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field PR has been renamed to YQ_CN_PR. | Recompilation of a client program may be broken with the error message: anon-struct-intel_drv.h-234 has no member named PR. |
| Change | Effect | |
|---|---|---|
| 1 | Field dpms_mode 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 'dpms_mode'. |
| 2 | Field idle_timer 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 'idle_timer'. |
| 3 | Field no_pll has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'no_pll'. |
| 4 | Field use_pll_a 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 'use_pll_a'. |
| 5 | Field busy has been renamed to eld_vld. | Recompilation of a client program may be broken with the error message: struct intel_crtc has no member named busy. |
| Change | Effect | |
|---|---|---|
| 1 | Field clone_mask 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 'clone_mask'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been renamed to crtc. | Recompilation of a client program may be broken with the error message: struct intel_unpin_work has no member named dev. |
| Change | Effect | |
|---|---|---|
| 1 | Field gpu_write_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'gpu_write_list'. |
| 2 | Field irq_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'irq_lock'. |
| 3 | Field irq_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'irq_mask'. |
| 4 | Field irq_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'irq_seqno'. |
| 5 | Field map has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'map'. |
| 6 | Field waiting_seqno has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_ring_buffer' has no member named 'waiting_seqno'. |
| Change | Effect | |
|---|---|---|
| 1 | Field curr_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_ec' has no member named 'curr_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct key_user' has no member named 'user_ns'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt6i_flow_cache_genid 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 'rt6i_flow_cache_genid'. |
| 2 | Field rt6i_peer_genid 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 'rt6i_peer_genid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field r has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fib_result' has no member named 'r'. |
| Change | Effect | |
|---|---|---|
| 1 | Field backup_thread has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'backup_thread'. |
| 2 | Field ftp_app has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'ftp_app'. |
| 3 | Field sync_buff has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'sync_buff'. |
| 4 | Field sync_mcast_addr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'sync_mcast_addr'. |
| 5 | Field master_thread has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'master_thread'. |
| 6 | Field sync_queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'sync_queue'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_genid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'rt_genid'. |
| 2 | Field sysctl_rt_cache_rebuild_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipv4' has no member named 'sysctl_rt_cache_rebuild_count'. |
| 3 | Field current_rt_cache_rebuild_count 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 'current_rt_cache_rebuild_count'. |
| 4 | Field nat_bysource 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_bysource'. |
| 5 | Field nat_htable_size 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_htable_size'. |
| 6 | Field tcp_sock has been renamed to fib_main. | Recompilation of a client program may be broken with the error message: struct netns_ipv4 has no member named tcp_sock. |
| Change | Effect | |
|---|---|---|
| 1 | Field table has been renamed to hdr. | Recompilation of a client program may be broken with the error message: struct netns_sysctl_ipv6 has no member named table. |
| Change | Effect | |
|---|---|---|
| 1 | The member SYSTEM_SUSPEND_DISK has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field serial_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct key' has no member named 'serial_node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field expiry has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field revoked_at has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_handle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_device' has no member named 'acpi_handle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_handle has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ata_host' has no member named 'acpi_handle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_handle 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 'acpi_handle'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tsk has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct common_audit_data' has no member named 'tsk'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sta has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-mac80211.h-546' has no member named 'sta'. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_filter_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss_conf' has no member named 'arp_filter_enabled'. |
| 2 | Field channel_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss_conf' has no member named 'channel_type'. |
| 3 | Field last_tsf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss_conf' has no member named 'last_tsf'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tx_frags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_ops' has no member named 'tx_frags'. |
| Change | Effect | |
|---|---|---|
| 1 | Field antenna_sel_tx has been renamed to hw_queue. | Recompilation of a client program may be broken with the error message: struct ieee80211_tx_info has no member named antenna_sel_tx. |
| Change | Effect | |
|---|---|---|
| 1 | Field plug_cnt has been renamed to reshape_backwards. | Recompilation of a client program may be broken with the error message: struct mddev has no member named plug_cnt. |
| Change | Effect | |
|---|---|---|
| 1 | Field faultstamp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'faultstamp'. |
| 2 | Field num_exe_file_vmas has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'num_exe_file_vmas'. |
| 3 | Field last_interval has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'last_interval'. |
| 4 | Field token_priority has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named 'token_priority'. |
| Change | Effect | |
|---|---|---|
| 1 | Field slab has been renamed to slab_cache. | Recompilation of a client program may be broken with the error message: anon-union-mm_types.h-122 has no member named slab. |
| Change | Effect | |
|---|---|---|
| 1 | Field prio_tree_node has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field vm_set has been renamed to linear. | Recompilation of a client program may be broken with the error message: anon-union-mm_types.h-230 has no member named vm_set. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_stat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct zone' has no member named 'reclaim_stat'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_longterm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mount' has no member named 'mnt_longterm'. |
| Change | Effect | |
|---|---|---|
| 1 | Field intent has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nameidata' has no member named 'intent'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct neigh_parms has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field wext_nlevents has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net' has no member named 'wext_nlevents'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ec_ptr 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 'ec_ptr'. |
| 2 | Field master 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 'master'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct packet_type' has no member named 'gro_complete'. |
| 2 | Field gro_receive has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct packet_type' has no member named 'gro_receive'. |
| 3 | Field gso_segment has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct packet_type' has no member named 'gso_segment'. |
| 4 | Field gso_send_check has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct packet_type' has no member named 'gso_send_check'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been renamed to portid. | Recompilation of a client program may be broken with the error message: struct nl_info has no member named pid. |
| Change | Effect | |
|---|---|---|
| 1 | Field arp_tx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netpoll_info' has no member named 'arp_tx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field help has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conn_help' has no member named 'help'. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_ip has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conntrack_expect' has no member named 'saved_ip'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_table has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conntrack_l3proto' has no member named 'ctl_table'. |
| 2 | Field ctl_table_header has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conntrack_l3proto' has no member named 'ctl_table_header'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctl_compat_table has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conntrack_l4proto' has no member named 'ctl_compat_table'. |
| 2 | Field ctl_compat_table_header has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nf_conntrack_l4proto' has no member named 'ctl_compat_table_header'. |
| 3 | Field ctl_table has been renamed to init_net. | Recompilation of a client program may be broken with the error message: struct nf_conntrack_l4proto has no member named ctl_table. |
| 4 | Field ctl_table_header has been renamed to net_id. | Recompilation of a client program may be broken with the error message: struct nf_conntrack_l4proto has no member named ctl_table_header. |
| 5 | Field ctl_table_users has been renamed to get_net_proto. | Recompilation of a client program may be broken with the error message: struct nf_conntrack_l4proto has no member named ctl_table_users. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 2 has been changed from SDP_HDR_OWNER_IP4 to SDP_HDR_OWNER. | Recompilation of a client program may be broken with the error message: 'SDP_HDR_OWNER_IP4' was not declared in this scope. |
| 2 | Name of member with value 3 has been changed from SDP_HDR_CONNECTION_IP4 to SDP_HDR_CONNECTION. | Recompilation of a client program may be broken with the error message: 'SDP_HDR_CONNECTION_IP4' was not declared in this scope. |
| 3 | The member SDP_HDR_CONNECTION_IP6 has been removed. | Recompilation of a client program may be broken. |
| 4 | The member SDP_HDR_OWNER_IP6 has been removed. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_lock_context' has no member named 'pid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field target_max_slots has been renamed to max_slotid. | Recompilation of a client program may be broken with the error message: struct nfs4_slot_table has no member named target_max_slots. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_boot_time 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_boot_time'. |
| 2 | Field cl_id_uniquifier 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_id_uniquifier'. |
| 3 | Field impl_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 'impl_id'. |
| 4 | Field server_scope 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 'server_scope'. |
| 5 | Field net has been renamed to cl_serverowner. | Recompilation of a client program may be broken with the error message: struct nfs_client has no member named net. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_complete has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_page' has no member named 'wb_complete'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sa_slotid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs4_sequence_args' has no member named 'sa_slotid'. |
| 2 | Field sa_session has been renamed to sa_slot. | Recompilation of a client program may be broken with the error message: struct nfs4_sequence_args has no member named sa_session. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_renewal_time 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_renewal_time'. |
| 2 | Field sr_session 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_session'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir_attr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_openres' has no member named 'dir_attr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'cred'. |
| 2 | Field inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'inode'. |
| 3 | Field lseg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'lseg'. |
| 4 | Field mds_ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'mds_ops'. |
| 5 | Field npages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'npages'. |
| 6 | Field page_array has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'page_array'. |
| 7 | Field pagevec has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'pagevec'. |
| 8 | Field pnfs_error has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'pnfs_error'. |
| 9 | Field req has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_read_data' has no member named 'req'. |
| Change | Effect | |
|---|---|---|
| 1 | Field secinfo has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_rpc_ops' has no member named 'secinfo'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'cred'. |
| 2 | Field ds_commit_index has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'ds_commit_index'. |
| 3 | Field inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'inode'. |
| 4 | Field lseg has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'lseg'. |
| 5 | Field mds_ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'mds_ops'. |
| 6 | Field npages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'npages'. |
| 7 | Field page_array has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'page_array'. |
| 8 | Field pagevec has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'pagevec'. |
| 9 | Field pnfs_error has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'pnfs_error'. |
| 10 | Field req has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct nfs_write_data' has no member named 'req'. |
| Change | Effect | |
|---|---|---|
| 1 | Field secondary has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_bus' has no member named 'secondary'. |
| 2 | Field subordinate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_bus' has no member named 'subordinate'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pcie_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_dev' has no member named 'pcie_type'. |
| Change | Effect | |
|---|---|---|
| 1 | Field can_wakeup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pci_platform_pm_ops' has no member named 'can_wakeup'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bp_target has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-perf_event.h-690' has no member named 'bp_target'. |
| 2 | Field info has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-perf_event.h-690' has no member named 'info'. |
| 3 | Field bp_list has been renamed to tp_list. | Recompilation of a client program may be broken with the error message: anon-struct-perf_event.h-690 has no member named bp_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct perf_event has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct perf_event_context has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field constraints 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 'constraints'. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dev_pm_qos_request' has no member named 'node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hit_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct wakeup_source' has no member named 'hit_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field e_id has been renamed to unnamed0. | Recompilation of a client program may be broken with the error message: struct posix_acl_entry has no member named e_id. |
| Change | Effect | |
|---|---|---|
| 1 | Field latency_ticks 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 'latency_ticks'. |
| 2 | Field power 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 'power'. |
| 3 | Field time 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 'time'. |
| 4 | Field usage 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 'usage'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_processor_power' has no member named 'dev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field hlt_works_ok 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 'hlt_works_ok'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_protocol' has no member named 'gro_complete'. |
| 2 | Field gro_receive has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_protocol' has no member named 'gro_receive'. |
| 3 | Field gso_segment has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_protocol' has no member named 'gso_segment'. |
| 4 | Field gso_send_check has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inet6_protocol' has no member named 'gso_send_check'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gro_complete has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_protocol' has no member named 'gro_complete'. |
| 2 | Field gro_receive has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_protocol' has no member named 'gro_receive'. |
| 3 | Field gso_segment has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_protocol' has no member named 'gso_segment'. |
| 4 | Field gso_send_check has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct net_protocol' has no member named 'gso_send_check'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dq_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot' has no member named 'dq_type'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: anon-union-radix-tree.c-52 has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field n_rp_need_fqs 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 'n_rp_need_fqs'. |
| 2 | Field passed_quiesce_gpnum 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 'passed_quiesce_gpnum'. |
| Change | Effect | |
|---|---|---|
| 1 | Field node_kthread_status 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 'node_kthread_status'. |
| 2 | Field node_kthread_task 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 'node_kthread_task'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqs_active 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 'fqs_active'. |
| 2 | Field fqs_need_gp 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 'fqs_need_gp'. |
| 3 | Field fqslock 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 'fqslock'. |
| 4 | Field onofflock 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 'onofflock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field retrans has been renamed to num_retrans. | Recompilation of a client program may be broken with the error message: struct request_sock has no member named retrans. |
| Change | Effect | |
|---|---|---|
| 1 | Field pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ring_buffer' has no member named 'pages'. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex 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 'mutex'. |
| 2 | Field head 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 'head'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fi has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'fi'. |
| 2 | Field peer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'peer'. |
| 3 | Field rt_dst has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_dst'. |
| 4 | Field rt_key_dst has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_key_dst'. |
| 5 | Field rt_key_src has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_key_src'. |
| 6 | Field rt_key_tos has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_key_tos'. |
| 7 | Field rt_mark has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_mark'. |
| 8 | Field rt_oif has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_oif'. |
| 9 | Field rt_peer_genid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_peer_genid'. |
| 10 | Field rt_route_iif has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_route_iif'. |
| 11 | Field rt_spec_dst has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rtable' has no member named 'rt_spec_dst'. |
| 12 | Field rt_src has been renamed to rt_pmtu. | Recompilation of a client program may be broken with the error message: struct rtable has no member named rt_src. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_tx_queues has been renamed to get_num_tx_queues. | Recompilation of a client program may be broken with the error message: struct rtnl_link_ops has no member named get_tx_queues. |
| Change | Effect | |
|---|---|---|
| 1 | Field __nents has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sg_mapping_iter' 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 sg_mapping_iter' has no member named '__sg'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct Qdisc has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_stamp 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 'load_stamp'. |
| 2 | Field load_contribution 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 'load_contribution'. |
| 3 | Field load_avg 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 'load_avg'. |
| 4 | Field load_last 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 'load_last'. |
| 5 | Field load_unacc_exec_time 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 'load_unacc_exec_time'. |
| 6 | Field load_period has been renamed to tg_load_contrib. | Recompilation of a client program may be broken with the error message: struct cfs_rq has no member named load_period. |
| Change | Effect | |
|---|---|---|
| 1 | Field count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rpc_wait_queue' has no member named 'count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_cpus_allowed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_rt_entity' has no member named 'nr_cpus_allowed'. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_stime has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct signal_struct' has no member named 'prev_stime'. |
| 2 | Field prev_utime has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct signal_struct' has no member named 'prev_utime'. |
| 3 | Field oom_adj has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct signal_struct' has no member named 'oom_adj'. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_stime 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 'prev_stime'. |
| 2 | Field replacement_session_keyring 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 'replacement_session_keyring'. |
| 3 | Field scm_work_list 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 'scm_work_list'. |
| 4 | Field irq_thread 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 'irq_thread'. |
| 5 | Field prev_utime 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 'prev_utime'. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_ns has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_struct' has no member named 'user_ns'. |
| Change | Effect | |
|---|---|---|
| 1 | Field list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct scm_fp_list' has no member named 'list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dentry_open 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 'dentry_open'. |
| 2 | Field tun_dev_post_create 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 'tun_dev_post_create'. |
| 3 | Field file_mmap has been renamed to mmap_addr. | Recompilation of a client program may be broken with the error message: struct security_operations has no member named file_mmap. |
| Change | Effect | |
|---|---|---|
| 1 | Field sequence has been renamed to seqcount. | Recompilation of a client program may be broken with the error message: struct seqlock_t has no member named sequence. |
| Change | Effect | |
|---|---|---|
| 1 | Field objsize has been renamed to object_size. | Recompilation of a client program may be broken with the error message: struct kmem_cache has no member named objsize. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kmem_cache_cpu' has no member named 'node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_sndmsg_off 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_sndmsg_off'. |
| 2 | Field sk_cgrp_prioidx 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_cgrp_prioidx'. |
| 3 | Field sk_sndmsg_page 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_sndmsg_page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_daddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sock_common' has no member named 'skc_daddr'. |
| 2 | Field skc_rcv_saddr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sock_common' has no member named 'skc_rcv_saddr'. |
| 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_portaddr_node has been removed from this union. | Recompilation of a client program may be broken. |
| 2 | Field skc_bind_node has been removed from this union. | Recompilation of a client program may be broken. |
| 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 mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct srcu_struct' has no member named 'mutex'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct tid_ampdu_rx has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu_head has been renamed to callback_head. | Recompilation of a client program may be broken with the error message: struct tid_ampdu_tx has no member named rcu_head. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_flavor has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct svc_rqst' has no member named 'rq_flavor'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bytes_acked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'bytes_acked'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cooling_devices has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thermal_zone_device' has no member named 'cooling_devices'. |
| 2 | Field tc2 has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thermal_zone_device' has no member named 'tc2'. |
| 3 | Field tc1 has been renamed to trip_hyst_attrs. | Recompilation of a client program may be broken with the error message: struct thermal_zone_device has no member named tc1. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle_tick has been renamed to last_tick. | Recompilation of a client program may be broken with the error message: struct tick_sched has no member named idle_tick. |
| Change | Effect | |
|---|---|---|
| 1 | Field twsk_getpeer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct timewait_sock_ops' has no member named 'twsk_getpeer'. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'entries'. |
| Change | Effect | |
|---|---|---|
| 1 | Field canon_column has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'canon_column'. |
| 2 | Field echo_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'echo_lock'. |
| 3 | Field read_flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_flags'. |
| 4 | Field canon_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'canon_head'. |
| 5 | Field output_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'output_lock'. |
| 6 | Field read_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_lock'. |
| 7 | Field echo_cnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'echo_cnt'. |
| 8 | Field low_latency has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'low_latency'. |
| 9 | Field read_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_buf'. |
| 10 | Field buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'buf'. |
| 11 | Field echo_pos has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'echo_pos'. |
| 12 | Field overrun_time has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'overrun_time'. |
| 13 | Field column has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'column'. |
| 14 | Field echo_overrun has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'echo_overrun'. |
| 15 | Field read_cnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_cnt'. |
| 16 | Field read_head has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_head'. |
| 17 | Field atomic_read_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'atomic_read_lock'. |
| 18 | Field erasing has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'erasing'. |
| 19 | Field process_char_map has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'process_char_map'. |
| 20 | Field raw has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'raw'. |
| 21 | Field canon_data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'canon_data'. |
| 22 | Field lnext has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'lnext'. |
| 23 | Field read_tail has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'read_tail'. |
| 24 | Field echo_buf has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'echo_buf'. |
| 25 | Field icanon has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'icanon'. |
| 26 | Field num_overrun has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'num_overrun'. |
| 27 | Field real_raw has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'real_raw'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cdev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_driver' has no member named 'cdev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field usbfs_dentry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_bus' has no member named 'usbfs_dentry'. |
| Change | Effect | |
|---|---|---|
| 1 | Field children 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 'children'. |
| 2 | Field usbfs_dentry 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 'usbfs_dentry'. |
| Change | Effect | |
|---|---|---|
| 1 | Field kref has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'kref'. |
| 2 | Field destroyer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'destroyer'. |
| 3 | Field creator has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'creator'. |
| 4 | Field uidhash_table has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct user_namespace' has no member named 'uidhash_table'. |
| Change | Effect | |
|---|---|---|
| 1 | Field current_cwq has been renamed to current_pwq. | Recompilation of a client program may be broken with the error message: struct worker has no member named current_cwq. |
| 2 | Field gcwq has been renamed to pool. | Recompilation of a client program may be broken with the error message: struct worker has no member named gcwq. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_wq has been renamed to pool_wq. | Recompilation of a client program may be broken with the error message: struct workqueue_struct has no member named cpu_wq. |
| 2 | Field nr_cwqs_to_flush has been renamed to nr_pwqs_to_flush. | Recompilation of a client program may be broken with the error message: struct workqueue_struct has no member named nr_cwqs_to_flush. |
| Change | Effect | |
|---|---|---|
| 1 | Field mapping has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct x86_init_ops' has no member named 'mapping'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pagetable_setup_done has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct x86_init_paging' has no member named 'pagetable_setup_done'. |
| 2 | Field pagetable_setup_start has been renamed to pagetable_init. | Recompilation of a client program may be broken with the error message: struct x86_init_paging has no member named pagetable_setup_start. |
| Change | Effect | |
|---|---|---|
| 1 | Field wallclock_init has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct x86_platform_ops' has no member named 'wallclock_init'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pid has been renamed to portid. | Recompilation of a client program may be broken with the error message: struct km_event has no member named pid. |
| Change | Effect | |
|---|---|---|
| 1 | Field shutdown 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 'shutdown'. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum ieee80211_agg_stop_reason has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter initiator has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter reason of type enum ieee80211_agg_stop_reason has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 3rd middle parameter initiator has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter uid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ioc of type struct io_context* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter event of type struct perf_event* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qid of type struct kqid has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qid of type struct kqid has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qid of type struct kqid has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 3rd middle parameter id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter color 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 color 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 color 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 dev of type struct drm_device* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter dev of type struct drm_device* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter bio of type struct bio* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter siginfo of type siginfo_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter signr has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buf of type unsigned char* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter eld has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tlb of type struct mmu_gather* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cache_level 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 | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter saddr of type struct in6_addr const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter sport of type __be16 const 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 const has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | Parameter sport of type __be16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter base of type struct inet_peer_base* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter device of type dev_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gpu_pdev of type struct pci_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter st of type struct sg_table* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter sg_list has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd middle parameter sg_len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter intel_encoder has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter intel_encoder has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter perm of type key_perm_t has been added to the calling stack at the middle position. | 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 | 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 wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 5th middle parameter channel_type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 6th middle parameter channel_type_valid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 4th middle parameter channel_type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 4th middle parameter channel_type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter user_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 user_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 user_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 qid of type struct kqid has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd middle parameter id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter helper of type struct nf_conntrack_helper* 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 pf has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lockowner of type struct nfs_lockowner const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 4th middle parameter fl_owner has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter netdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 5th middle parameter channel_type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wdev of type struct wireless_dev* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter netdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 5th middle parameter channel_type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_cred of type struct cred* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zonelist of type struct zonelist* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 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. |
| 3 | Parameter order of type int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 4 | 1st middle parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 5 | 2nd middle parameter error_code has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter path of type struct path const* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd middle parameter mnt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pgdat of type pg_data_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter compl_ops of type struct nfs_pgio_completion_ops const* has been added to the calling stack at the middle position. | 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 | 4th middle parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter user_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 dev of type struct device* 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 type of type enum dev_pm_qos_req_type has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter neigh has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter src_net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter ts has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 5th middle parameter tsage has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wiphy of type struct wiphy* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wiphy of type struct wiphy* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter path of type struct path* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter mnt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 2nd middle parameter dentry has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter 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 | Parameter user_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. |
| 2 | Parameter pid_ns of type struct pid_namespace* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tailroom of type size_t has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 5th middle parameter ie has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter ns has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prep of type struct key_preparsed_payload* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter data has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter prep of type struct key_preparsed_payload* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 2nd middle parameter data has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sdata of type struct ieee80211_sub_if_data* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter vif has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sdata of type struct ieee80211_sub_if_data* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 1st middle parameter vif has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buffer_len of type size_t has been added to the calling stack at the middle position. | 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 at the middle position. | 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 at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter_flags of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter iter_flags of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter status of type u16 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 u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter walk_state of type struct acpi_walk_state* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter walk_state of type struct acpi_walk_state* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter user_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 user_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 user_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 xprt of type struct rpc_xprt* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field resources has been changed from struct acpi_handle_list to struct list_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field resources has been changed from struct acpi_handle_list to struct list_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field name has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field completions has been changed from struct prop_local_percpu to struct fprop_local_percpu of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field queue_lock has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field proberesp_ies has been changed from unsigned char to struct cfg80211_bss_ies of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of field beacon_ies has been changed from unsigned char to struct cfg80211_bss_ies of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field parts has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field d_alias has been changed from struct list_head to struct hlist_node of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field regs became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct debugfs_regset32::regs'. |
| Change | Effect | |
|---|---|---|
| 1 | This type became opaque. | The internal structure of this type is hidden in the new library version and recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field funcs became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct drm_mode_config::funcs'. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_vm_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct drm_driver::gem_vm_ops'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field pid has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field hash has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field i_mmap has been changed from struct prio_tree_root to struct rb_root of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field i_dentry has been changed from struct list_head to struct hlist_head of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field buffer_iter has been increased from 1 to 2. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field pages has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field gmbus has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field bitmap has been changed from unsigned long to unsigned long[8] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field probe_resp has been changed from struct sk_buff to struct probe_resp of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cf_params became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::cf_params'. |
| 2 | Field challenge became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::challenge'. |
| 3 | Field country_elem became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::country_elem'. |
| 4 | Field ds_params became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ds_params'. |
| 5 | Field erp_info became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::erp_info'. |
| 6 | Field ext_supp_rates became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ext_supp_rates'. |
| 7 | Field fh_params became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::fh_params'. |
| 8 | Field ht_cap_elem became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ht_cap_elem'. |
| 9 | Field ibss_params became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ibss_params'. |
| 10 | Field ie_start became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ie_start'. |
| 11 | Field mesh_config became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::mesh_config'. |
| 12 | Field mesh_id became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::mesh_id'. |
| 13 | Field peering became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::peering'. |
| 14 | Field perr became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::perr'. |
| 15 | Field prep became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::prep'. |
| 16 | Field preq became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::preq'. |
| 17 | Field pwr_constr_elem became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::pwr_constr_elem'. |
| 18 | Field quiet_elem became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::quiet_elem'. |
| 19 | Field rann became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::rann'. |
| 20 | Field rsn became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::rsn'. |
| 21 | Field ssid became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::ssid'. |
| 22 | Field supp_rates became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::supp_rates'. |
| 23 | Field tim became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::tim'. |
| 24 | Field timeout_int became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::timeout_int'. |
| 25 | Field wmm_info became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::wmm_info'. |
| 26 | Field wmm_param became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ieee802_11_elems::wmm_param'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mem has been changed from struct atomic_t to struct percpu_counter of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field mt has been changed from struct input_mt_slot to struct input_mt of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pending has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from struct mutex to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field rt6i_peer has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field daddr_cache became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ipv6_pinfo::daddr_cache'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field resync_mismatches has been changed from sector_t to struct atomic64_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct of_device_id::data'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field remote_ip has been changed from __be32 to union inet_addr of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field local_ip has been changed from __be32 to union inet_addr of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field name has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field ctl_table_path has been changed from struct ctl_path to char of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field lockowner has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field wb_verf has been changed from struct nfs_writeverf to struct nfs_write_verifier of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pages has been changed from struct list_head to struct nfs_page_array of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pages has been changed from struct list_head to struct nfs_page_array of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field verifier has been changed from __be32[2] to struct nfs_write_verifier of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field full_name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct device_node::full_name'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sklist_lock has been changed from spinlock_t to struct mutex of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field err_handler became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct pci_driver::err_handler'. |
| Change | Effect | |
|---|---|---|
| 1 | Field err_handler became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct pcie_port_service_driver::err_handler'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dq_id has been changed from unsigned int to struct kqid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field seccomp has been changed from struct seccomp_t to struct seccomp of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field termios has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 2 | The pointer level of field termios_locked has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field caller became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct vm_struct::caller'. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter tx has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter tx has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter running has been changed from struct list_head to struct async_domain of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter running has been changed from struct list_head to struct async_domain of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter list has been changed from struct list_head to struct async_domain of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter dirlen has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cb has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter parent of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter name has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type unsigned char const has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter signr of type long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter code 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 name has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter ssid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th parameter tsid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 5th parameter tclass has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 6th parameter perms has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter nd has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cache_request 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 | 2nd parameter count has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct nfs_parsed_mount_data to struct nfs_mount_info of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter mntfh has been changed from struct nfs_fh to struct nfs_subversion of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter noresvport 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 ds_timeo of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter ds_retrans of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter data has been changed from struct nfs_parsed_mount_data to struct nfs_mount_info of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter mntfh has been changed from struct nfs_fh to struct nfs_subversion of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter noresvport 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 req of type struct nlm_rqst* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter i has been changed from struct list_head to struct nf_hook_ops of different format. | 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. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu_online 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 4th parameter inode has been increased from 2 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flush_old of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter i_pos has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uio of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uio of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter throttle of type struct dm_kcopyd_throttle* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter per_bio_data_size of type unsigned int has been added to 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 wait has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter block of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter print_bad_edid of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter rb of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter color of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hcd of type struct usb_hcd* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hcd of type struct usb_hcd* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter exit_code has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 3rd parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs 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 in_device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd has been increased from 1 to 0. | 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 size of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter eapd_workaround has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter eld has been changed from struct hdmi_eld to struct parsed_hdmi_eld of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter eld_size 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 e has been changed from struct hdmi_eld to struct parsed_hdmi_eld of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter ht_cap has been changed from struct ieee80211_sta_ht_cap to struct sta_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter gpe_register_info has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter request has been changed from struct drm_i915_gem_request to unsigned int of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pipelined has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter seqno has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter do_retire has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter purgeable_only has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter nonblocking of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cache_level of type enum i915_cache_level 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 | Base type of parameter new_dev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter relax of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter relax of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter force of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter family has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct inode of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter index of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter priv of type void* 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 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter page_size_log of type int 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 | 1st parameter pdev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gtt_total of type size_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter stolen_size of type size_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter mappable_base of type phys_addr_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 4 | Parameter mappable_end of type unsigned long* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 5 | Type of return value has been changed from struct intel_gtt const* (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter obj has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter port of type enum port has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter port of type enum port has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter pipe of type enum pipe has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct drm_device to struct drm_connector of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_sdvob of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool (1 byte) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter user_ns has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter group of type struct fsnotify_group* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter mddev has been changed from struct mddev to struct md_thread of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_new of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter nr_accounted has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 6th parameter details has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter setup has been changed from struct mesh_setup const* to struct mesh_setup* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sae_data of type u8 const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter sae_data_len of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sae_data of type u8 const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter sae_data_len of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_rmap_locks of type bool* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_rmap_locks 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 6th parameter msgflg has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 3rd parameter mtext has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter pathname has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 3rd parameter nd has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct ctl_path[2] to int of different format. | Recompilation of a client program may be broken. |
| 2 | Parameter name of type char const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter flags of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 4 | Parameter path of type struct path* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from char to struct filename of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 4th parameter nd has been increased from 1 to 0. | 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. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter npinfo of type struct netpoll_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter ndev of type struct net_device* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter gfp of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter net has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter delim 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 elem has been changed from struct list_head to struct nf_hook_ops 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 | 1st parameter pf has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 2nd parameter qh has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 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 subsys_id of type __u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter subsys_id of type __u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter roc has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter fl_pid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter gfp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter netdev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter netdev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter netdev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter netdev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter netdev has been changed from struct net_device to struct wireless_dev of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 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 | Parameter nodemask of type nodemask_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter force_kill of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter context has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter high_limit of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type struct zone* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter lockdep_ok of type enum lockdep_ok has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter is_c45 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 regs has been changed from struct pt_regs to int of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 4th parameter child_tid has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter device has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter device has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter device has been changed from struct acpi_device to struct device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter state has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter secs of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter c_old of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | Parameter c of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter delta_jiffies 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 head has been changed from struct list_head to struct nfs_pgio_header of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter eof of type loff_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter check_access has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter desired_bw_khz has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th parameter reg_rule 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 int to struct ieee80211_reg_rule const*). | Recompilation of a client program may be broken. |
| 4 | 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 user_reg_hint_type of type enum nl80211_user_reg_hint_type has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter force of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cpu_id of type int has been added to the calling stack. | 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 delay has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter rmdevice 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 | 7th parameter beacon has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter sdata has been changed from struct ieee80211_sub_if_data to struct ieee80211_local of different format. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from ieee80211_rx_result (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter new_state of type enum scsi_device_state 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 new_state of type enum scsi_device_state has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter filter of type char* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter security of type void* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter shmlba of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter newset has been changed from sigset_t const* to sigset_t* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter frag_size of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter d_max_in of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tidle of type struct task_struct* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter use_effective 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 | Type of this global data has been changed from long to atomic_long_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter cpu_dev has been changed from struct device to struct cpuidle_device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter cpu_dev has been changed from struct device to struct cpuidle_device of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter foc of type struct tcp_fastopen_cookie* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter fastopen of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter foc of type struct tcp_fastopen_cookie* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock const* to struct sock* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter sk has been changed from struct sock const* to struct sock* (became non-const). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 1st parameter orig has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter upper of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter lower of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter ops has been changed from struct thermal_zone_device_ops const* to void* (became non-const). | Recompilation of a client program may be broken. |
| 2 | The pointer level of 3rd parameter devdata has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| 3 | The pointer level of 5th parameter tc1 has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| 4 | The pointer level of 6th parameter tc2 has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter icanon of type unsigned int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tty has been changed from struct tty_struct to struct tty_port of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tty of type struct tty_struct* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tty of type struct tty_struct* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter ie_len has been removed from 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 | 3rd parameter datalen has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter datalen has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter need_basic of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | 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 | Parameter need_basic of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | 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 | The pointer level of 1st parameter local has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter local has been changed from struct ieee80211_local to struct ieee80211_sub_if_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tx_flags of type u32 has been added to the calling stack. | 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. | Recompilation of a client program may be broken. |
| 2 | Parameter scan of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter basic_rates of type u32* 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 acpi_name (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter old_ns of type struct uts_namespace* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter regs has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter file has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter vma has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter block 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 local has been changed from struct ieee80211_local to struct ieee80211_sub_if_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter p has been changed from struct nfs_write_data to struct nfs_commit_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from struct nfs_write_data to struct nfs_commit_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter head has been changed from struct list_head to struct nfs_pgio_header of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter data has been changed from struct nfs_write_data to struct nfs_commit_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter cinfo of type struct nfs_commit_info* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rt_max_size has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dl_read has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dl_write has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dma 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 setup has been changed from int(*)(struct serial_private*, struct pciserial_board const*, struct uart_port*, int) to int(*)(struct serial_private*, struct pciserial_board const*, struct uart_8250_port*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field handler_list_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field handler_list_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field global has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_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 next has been changed from struct acpi_object_notify_handler to union acpi_operand_object*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field end_bus has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mcfg_added has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sd has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field segment has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field start_bus has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Type of field name has been changed from char* to char[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field add has been changed from int(*)(acpi_handle) to int(*)(struct acpi_pci_root*). | Recompilation of a client program may be broken. |
| 3 | Base type of field remove has been changed from void(*)(acpi_handle) to void(*)(struct acpi_pci_root*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field match has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field setup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handler has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field physical_node_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field physical_node_id_bitmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field physical_node_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field physical_node_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field power_dependent has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field remove has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eject_pending has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field match_driver has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field str_obj has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sun has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mcfg_addr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field os_accessible 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 acpi_device*, int) to int(*)(struct acpi_device*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wake_capable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field init has been changed from int(*)(struct nlattr*, struct nlattr*, struct tc_action*, int, int) to int(*)(struct net*, struct nlattr*, struct nlattr*, struct tc_action*, int, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tcfc_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field subsystem_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field compatible_id_list has been changed from struct acpica_device_id_list to struct acpi_pnp_device_id_list. | Recompilation of a client program may be broken. |
| 3 | Type of field hardware_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Recompilation of a client program may be broken. |
| 4 | Type of field unique_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field clk has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field intr_status has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field timer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bank4 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field eoi_write has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field cpu_mask_to_apicid_and has been changed from unsigned int(*)(struct cpumask const*, struct cpumask const*) to int(*)(struct cpumask const*, struct cpumask const*, unsigned int*). | Recompilation of a client program may be broken. |
| 3 | Base type of field vector_allocation_domain has been changed from void(*)(int, struct cpumask*) to void(*)(int, struct cpumask*, struct cpumask const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field audio_tstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field audio_tstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field uid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| 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 list_pseudoflavors has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cr_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field audited has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field denied has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field requested has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field result has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field tclass 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 load_binary has been changed from int(*)(struct linux_binprm*, struct pt_regs*) to int(*)(struct linux_binprm*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field counts has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field storage has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_write_same_sectors has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bypass_depth has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field request_fn_active has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field root_rl has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field nr_rqs has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | 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 ext_cmd_line_ptr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ext_ramdisk_image has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ext_ramdisk_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field kbd_status has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field sentinel has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handover_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field min_alignment has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field xloadflags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cache_request has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sae_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sae_data_len has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_beacon_bss has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ies has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mfp 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 chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field mcast_rate has been changed from int[2] to int[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_et_sset_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_et_stats has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field get_et_strings has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field libertas_set_mesh_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field set_cqm_txe_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field set_mac_acl has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field set_mcast_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field set_monitor_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field set_wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field start_p2p_device has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field start_radar_detection has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field stop_p2p_device has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Base type of field add_virtual_intf has been changed from struct net_device*(*)(struct wiphy*, char*, enum nl80211_iftype, u32*, struct vif_params*) to struct wireless_dev*(*)(struct wiphy*, char const*, enum nl80211_iftype, u32*, struct vif_params*). | Recompilation of a client program may be broken. |
| 14 | Base type of field cancel_remain_on_channel has been changed from int(*)(struct wiphy*, struct net_device*, u64) to int(*)(struct wiphy*, struct wireless_dev*, u64). | Recompilation of a client program may be broken. |
| 15 | Base type of field del_virtual_intf has been changed from int(*)(struct wiphy*, struct net_device*) to int(*)(struct wiphy*, struct wireless_dev*). | Recompilation of a client program may be broken. |
| 16 | Base type of field get_channel has been changed from struct ieee80211_channel*(*)(struct wiphy*) to int(*)(struct wiphy*, struct wireless_dev*, struct cfg80211_chan_def*). | Recompilation of a client program may be broken. |
| 17 | Base type of field get_tx_power has been changed from int(*)(struct wiphy*, int*) to int(*)(struct wiphy*, struct wireless_dev*, int*). | Recompilation of a client program may be broken. |
| 18 | Base type of field mgmt_frame_register has been changed from void(*)(struct wiphy*, struct net_device*, u16, bool) to void(*)(struct wiphy*, struct wireless_dev*, u16, bool). | Recompilation of a client program may be broken. |
| 19 | Base type of field mgmt_tx has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, bool, enum nl80211_channel_type, bool, unsigned int, u8 const*, size_t, bool, bool, u64*) to int(*)(struct wiphy*, struct wireless_dev*, struct ieee80211_channel*, bool, unsigned int, u8 const*, size_t, bool, bool, u64*). | Recompilation of a client program may be broken. |
| 20 | Base type of field mgmt_tx_cancel_wait has been changed from int(*)(struct wiphy*, struct net_device*, u64) to int(*)(struct wiphy*, struct wireless_dev*, u64). | Recompilation of a client program may be broken. |
| 21 | Base type of field remain_on_channel has been changed from int(*)(struct wiphy*, struct net_device*, struct ieee80211_channel*, enum nl80211_channel_type, unsigned int, u64*) to int(*)(struct wiphy*, struct wireless_dev*, struct ieee80211_channel*, unsigned int, u64*). | Recompilation of a client program may be broken. |
| 22 | Base type of field scan has been changed from int(*)(struct wiphy*, struct net_device*, struct cfg80211_scan_request*) to int(*)(struct wiphy*, struct cfg80211_scan_request*). | Recompilation of a client program may be broken. |
| 23 | Base type of field set_tx_power has been changed from int(*)(struct wiphy*, enum nl80211_tx_power_setting, int) to int(*)(struct wiphy*, struct wireless_dev*, enum nl80211_tx_power_setting, int). | 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 scan_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field rates has been changed from u32[2] to u32[3]. | 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 rssi_thold has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field scan_start has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pkt_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfs_state_entered has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dfs_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field radar_detect_widths has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_cap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dot11MeshAwakeWindowDuration has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dot11MeshHWMPactivePathToRootTimeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dot11MeshHWMPconfirmationInterval has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field dot11MeshHWMProotInterval has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field dot11MeshNbrOffsetMaxNeighbor has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ht_opmode has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field power_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dtim_period has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sync_method has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field mcast_rate has been changed from int[2] to int[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nss has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nonpeer_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field peer_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field t_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field rx_bytes has been changed from u32 to u64. | Recompilation of a client program may be broken. |
| 6 | Type of field tx_bytes has been changed from u32 to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field macaddr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field extended_capabilities_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_acl_mac_addrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field extended_capabilities has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field extended_capabilities_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Base type of field reg_notifier has been changed from int(*)(struct wiphy*, struct regulatory_request*) to void(*)(struct wiphy*, struct regulatory_request*). | Recompilation of a client program may be broken. |
| 6 | Type of field bands has been changed from struct ieee80211_supported_band*[2] to struct ieee80211_supported_band*[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_pkt_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tcp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cac_started has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field identifier has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field preset_chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ibss_fixed has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ap_unexpected_nlportid has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field cac_start_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field address has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field p2p_started has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allcg_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cgroup_ida has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allcg_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field xattrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field files has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field id has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field free_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Type of field subsys has been changed from struct cgroup_subsys_state*[32] to struct cgroup_subsys_state*[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field base_cftset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field base_cftypes has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field broken_hierarchy has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cftsets has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field css_free has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field warned_broken_hierarchy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dput_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 subsys has been changed from struct cgroup_subsys_state*[32] to struct cgroup_subsys_state*[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field resume has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nat_bysource has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nat_htable_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tmpl has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field auto_assign_helper_warned has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field helper_sysctl_header has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field nf_ct_proto has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field sysctl_auto_assign_helper has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field numa_level has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hidden_list 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field beacon_registrations has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beacon_registrations_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dfs_update_channels_wk has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field num_running_ifaces has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field num_running_monitor_ifaces has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field wdev_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field c_detect_tlb 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 | Field initialized has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobj_driver has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field session_keyring has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field process_keyring has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field blocks has been changed from gid_t* to kgid_t*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_weak_revalidate has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field d_revalidate has been changed from int(*)(struct dentry*, struct nameidata*) to int(*)(struct dentry*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field d_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_io_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field num_write_bios has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field num_write_same_bios has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field per_bio_data_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field split_discard_bios 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 dm_target*, struct bio*, int, union map_info*) to int(*)(struct dm_target*, struct bio*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct dm_target*, struct bio*, union map_info*) to int(*)(struct dm_target*, struct bio*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct dm_target*, status_type_t, char*, unsigned int) to void(*)(struct dm_target*, status_type_t, unsigned int, char*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field iommu_group has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_match_table has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field throttle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vmap_ptr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vmapping_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field vunmap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfn_base has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_sgtable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bad_edid_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field properties has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field invert_dimensions has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field properties has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_property 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 | Field poll_running has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fb_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field properties has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_property 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 formula 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 mode_fixup has been changed from bool(*)(struct drm_encoder*, struct drm_display_mode*, struct drm_display_mode*) to bool(*)(struct drm_encoder*, struct drm_display_mode const*, struct drm_display_mode*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field color_adjust has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field scan_color has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field scan_hit_end has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field color has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_prime_get_sg_table has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gem_prime_vmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gem_prime_import_sg_table has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field gem_prime_vunmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field gem_prime_pin has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fbs_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field pid has been changed from pid_t to struct pid*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field expires has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pending_confirm has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field flags has been changed from int to unsigned short. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field redirect has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field neigh_lookup has been changed from struct neighbour*(*)(struct dst_entry const*, void const*) to struct neighbour*(*)(struct dst_entry const*, struct sk_buff*, void const*). | Recompilation of a client program may be broken. |
| 3 | Base type of field update_pmtu has been changed from void(*)(struct dst_entry*, u32) to void(*)(struct dst_entry*, struct sock*, struct sk_buff*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_hw_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field dpms has been changed from void(*)(struct intel_dvo_device*, int) to void(*)(struct intel_dvo_device*, bool). | Recompilation of a client program may be broken. |
| 3 | Base type of field mode_fixup has been changed from bool(*)(struct intel_dvo_device*, struct drm_display_mode*, struct drm_display_mode*) to bool(*)(struct intel_dvo_device*, struct drm_display_mode const*, struct drm_display_mode*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field query_variable_store has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kobject has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash has been changed from struct hlist_head* to struct hlist_head[64]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void*()(struct request_queue*) to int()(struct request_queue*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*, struct request*, gfp_t) to int()(struct request_queue*, struct request*, struct bio*, gfp_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_eee has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_eee has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field get_module_eeprom has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field get_ts_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_module_info 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 encode_fh has been changed from int(*)(struct dentry*, __u32*, int*, int) to int(*)(struct inode*, __u32*, int*, struct inode*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nfs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field time_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field tz_set has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir_hash_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dir_hashtable has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dirty has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field fsinfo_inode has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field s_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field delete has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field thoff has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field swap_activate has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field swap_deactivate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fa_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field f_inode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field show_fdinfo has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_writers_key has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field atomic_open has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, umode_t, struct nameidata*) to int(*)(struct inode*, struct dentry*, umode_t, bool). | Recompilation of a client program may be broken. |
| 3 | Base type of field lookup has been changed from struct dentry*(*)(struct inode*, struct dentry*, struct nameidata*) to struct dentry*(*)(struct inode*, struct dentry*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_writers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field i_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fu_rcuhead has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fsn_fa has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field snapshot has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field buffer_iter has been changed from struct ring_buffer_iter*[8] to struct ring_buffer_iter**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_sects_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field uuid has been changed from u8[16] to char[37]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_usb3_lpm_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field enable_usb3_lpm_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field find_raw_port_number has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field phy has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rsrc_len has been changed from u64 to resource_size_t. | Recompilation of a client program may be broken. |
| 3 | Type of field rsrc_start has been changed from u64 to resource_size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field primary_dig_out_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pm_notify has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cached_write has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field conn_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field d3_stop_clk has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field epss has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field fixup_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field fixup_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field fixup_name has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field hash_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field in_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field inv_eapd has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field inv_jack_detect has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field jackpoll_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field jackpoll_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field pcm_format_first has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field pm_down_notified has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field power_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field power_filter has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field power_jiffies has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field power_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field power_off_acct has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field power_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field power_on_acct has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field power_transition has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field power_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Field user_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 26 | Field verbs 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 hda_codec*, pm_message_t) to int(*)(struct hda_codec*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field own_chmap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chmap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gated_jack has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field gating_jack has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field phantom_jack 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 lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_rdesc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dev_rsize has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field group has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field input_configured has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field report has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field field has been changed from struct hid_field*[128] to struct hid_field*[256]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field usage_index has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hugepage_activelist has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rar_set has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field x2apic_available has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bound_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field shrinker_no_lock_stealing has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crtc_disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field crtc_enable has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field hpd_irq_setup has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field modeset_global_resources has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field update_linetime_wm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dma_buf_vmapping has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field has_global_gtt_mapping has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field last_read_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field last_write_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field pages_pin_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field stolen has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field vmapping_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Type of field pages has been changed from struct page** to struct sg_table*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field console_resume_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ddi_plls has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dpio_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field dri1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field enable_hotplug_processing has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field fdi_rx_polarity_inverted has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field gmbus_wait_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field gpio_mmio_base has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field gpu_error has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field gt has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field gtt has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field hw_contexts_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field ips has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field l3_parity has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field last_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field modeset_restore has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field modeset_restore_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field num_pch_pll has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field pch_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field pch_plls has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field pm_qos has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field regfile has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field rps has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field slab has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Type of field gmbus has been changed from struct intel_gmbus* to struct intel_gmbus[6]. | Recompilation of a client program may be broken. |
| 26 | Type of field sprite_scaling_enabled has been changed from bool to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field clear_range has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field insert_entries has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field display_mmio_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_haswell has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field is_valleyview has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hint has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field prefix has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field ary has been changed from struct idr_layer*[32] to struct idr_layer*[256]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field device_ts_presp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field num_mcast_sta has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field auth_frame_registrations has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field connection_loss has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field csa_connection_drop_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dtim_period has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field p2p_noa_index has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field status_acked has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field status_fc has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field status_received has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field adjusting_tbtt has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field estab_plinks has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field nonpeer_pm has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ps_peers_deep_sleep has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field ps_peers_light_sleep has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field sync_offset_clockdrift_max has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field sync_offset_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field sync_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chanctx_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chanctx_mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field hw_scan_ies_bufsize has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ifa6_notifier has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field in_reconfig has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field monitor_chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field p2p_sdata has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field radar_detect_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field radar_detected_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field roc_cookie_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field roc_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field rx_chains has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field rx_path_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field sched_scan_sdata has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field use_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Type of field agg_queue_stop has been changed from atomic_t[4] to atomic_t[16]. | Recompilation of a client program may be broken. |
| 17 | Type of field pending has been changed from struct sk_buff_head[4] to struct sk_buff_head[16]. | Recompilation of a client program may be broken. |
| 18 | Type of field queue_stop_reasons has been changed from unsigned long[4] to unsigned long[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_ht_param has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ap_vht_cap has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field need_beacon has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field timeout_started 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 data_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sae_status has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sae_trans has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field timeout_started has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_power_level has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cleanup_stations has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cleanup_stations_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cleanup_stations_wk has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field dfs_cac_timer_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field radar_required has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field recalc_smps has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field suspend_bss_conf has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field user_power_level has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field wmm_acm has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Type of field rc_rateidx_mask has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field awake_window has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ch_switch_ie has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ht_operation has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field opmode_notif has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field vht_operation has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field net_frag_header_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_rx_dst_set has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field bind_conflict has been changed from int(*)(struct sock const*, struct inet_bind_bucket const*) to int(*)(struct sock const*, struct inet_bind_bucket const*, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field match has been changed from int(*)(struct inet_frag_queue*, void*) to bool(*)(struct inet_frag_queue*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lru_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fastreuseport has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fastuid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field fastreuse has been changed from short to signed char. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx_dst_ifindex has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ifa_tstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ifa_cstamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ifa_valid_lft has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ifa_preferred_lft has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from int[25] to int[26]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gc_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field devres_managed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_vals has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field num_vals has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vals 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 legacy_minors has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cursor has been changed from struct intel_cursor_error_state[2] to struct intel_cursor_error_state[3]. | Recompilation of a client program may be broken. |
| 2 | Type of field pipe has been changed from struct intel_pipe_error_state[2] to struct intel_pipe_error_state[3]. | Recompilation of a client program may be broken. |
| 3 | Type of field plane has been changed from struct intel_plane_error_state[2] to struct intel_plane_error_state[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field edid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_hw_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field new_encoder has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field panel has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_transcoder has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ddi_pll_sel has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dspaddr_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field pch_pll has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field primary_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field reset_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field unpin_work_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cloneable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field connectors_active has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field enable has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_hw_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field new_crtc has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field post_disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field pre_enable has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field pre_pll_enable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_context has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field gpu_caches_dirty has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field irq_enable_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field itlb_before_ctx_switch has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field last_context_obj has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field set_seqno has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Base type of field add_request has been changed from int(*)(struct intel_ring_buffer*, u32*) to int(*)(struct intel_ring_buffer*). | Recompilation of a client program may be broken. |
| 8 | Base type of field dispatch_execbuffer has been changed from int(*)(struct intel_ring_buffer*, u32, u32) to int(*)(struct intel_ring_buffer*, u32, u32, unsigned int). | Recompilation of a client program may be broken. |
| 9 | Base type of field get_seqno has been changed from u32(*)(struct intel_ring_buffer*) to u32(*)(struct intel_ring_buffer*, bool). | Recompilation of a client program may be broken. |
| 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 | Type of field flags has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| 2 | Type of field irq has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_ref has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field __rcu_head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_mp has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fc_mp_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fc_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tb6_peers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt6i_nsiblings has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rt6i_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rt6i_siblings has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field rt6i_peer has been changed from struct inet_peer* to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fib_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nh_exceptions has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nh_pcpu_rth_output has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field nh_rth_input has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tclassid 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 conn_schedule has been changed from int(*)(int, struct sk_buff*, struct ip_vs_proto_data*, int*, struct ip_vs_conn**) to int(*)(int, struct sk_buff*, struct ip_vs_proto_data*, int*, struct ip_vs_conn**, struct ip_vs_iphdr*). | Recompilation of a client program may be broken. |
| 2 | Base type of field snat_handler has been changed from int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*) to int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*, struct ip_vs_iphdr*). | Recompilation of a client program may be broken. |
| 3 | Base type of field conn_out_get has been changed from struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, unsigned int, int) to struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, int). | Recompilation of a client program may be broken. |
| 4 | Base type of field dnat_handler has been changed from int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*) to int(*)(struct sk_buff*, struct ip_vs_protocol*, struct ip_vs_conn*, struct ip_vs_iphdr*). | Recompilation of a client program may be broken. |
| 5 | Base type of field conn_in_get has been changed from struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, unsigned int, int) to struct ip_vs_conn*(*)(int, struct sk_buff const*, struct ip_vs_iphdr const*, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_sync_qlen_max has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ms has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sysctl_sync_ports has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sysctl_sync_refresh_period has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field sysctl_pmtu_disc has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field threads_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field backup_threads has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field sysctl_backup_only has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field sysctl_sync_retries has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field sysctl_sync_sock_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mq_msg_default has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field proc_inum has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mq_msgsize_default has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mroute_do_assert has been changed from int to bool. | Recompilation of a client program may be broken. |
| 2 | Type of field mroute_do_pim has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysctl_tcp_ecn has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fib_default has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fib_local has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field tcp_metrics_hash_log has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field xfrm4_hdr has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field fib_has_custom_rules has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field peers has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field tcp_metrics_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field frag_max_size 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 ndisc_notify 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 rx_dst_cookie has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ip6table_nat has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field peers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field xfrm6_hdr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field icmp_hdr has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field route_hdr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent_irq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_preparse has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field preparse has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Base type of field update has been changed from int(*)(struct key*, void const*, size_t) to int(*)(struct key*, struct key_preparsed_payload*). | Recompilation of a client program may be broken. |
| 4 | Base type of field instantiate has been changed from int(*)(struct key*, void const*, size_t) to int(*)(struct key*, struct key_preparsed_payload*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mic_failures has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_used_at has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| 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 cur_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cur_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field max_reason has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field next_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field next_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Base type of field dump has been changed from void(*)(struct kmsg_dumper*, enum kmsg_dump_reason, char const*, unsigned long, char const*, unsigned long) to void(*)(struct kmsg_dumper*, enum kmsg_dump_reason). | Recompilation of a client program may be broken. |
| 8 | Type of field registered has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field if_modifier has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field activated has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field delayed_set_value has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_brightness_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field devslp_timing has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field end_eh has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sched_eh has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cmdbuf has been changed from unsigned char[6] to unsigned char[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rates has been changed from struct ieee80211_tx_rate[5] to struct ieee80211_tx_rate[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field antenna has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rates has been changed from struct ieee80211_tx_rate[5] to struct ieee80211_tx_rate[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field driver_rates has been changed from struct ieee80211_tx_rate[5] to struct ieee80211_tx_rate[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ibss_creator has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field p2p_ctwindow has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field p2p_oppps has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field sync_device_ts has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field sync_dtim_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field sync_tsf has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field txpower has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Type of field arp_addr_cnt has been changed from u8 to int. | Recompilation of a client program may be broken. |
| 11 | Type of field mcast_rate has been changed from int[2] to int[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field radar_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chanctx_data_size has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field netdev_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field offchannel_tx_hw_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field radiotap_mcs_details has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field radiotap_vht_details has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field assign_vif_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field change_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field get_et_sset_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field get_et_stats has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field get_et_strings has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field get_rssi has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field ipv6_addr_change has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field mgd_prepare_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field remove_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field restart_complete has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field set_default_unicast_key has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field set_wakeup has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field sta_rc_update has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field start_ap has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field stop_ap has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field unassign_vif_chanctx has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Base type of field remain_on_channel has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_channel*, enum nl80211_channel_type, int) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int). | Recompilation of a client program may be broken. |
| 19 | Base type of field rssi_callback has been changed from void(*)(struct ieee80211_hw*, enum ieee80211_rssi_event) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, enum ieee80211_rssi_event). | Recompilation of a client program may be broken. |
| 20 | Base type of field tx has been changed from void(*)(struct ieee80211_hw*, struct sk_buff*) to void(*)(struct ieee80211_hw*, struct ieee80211_tx_control*, struct sk_buff*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ampdu_delimiter_crc has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ampdu_reference has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field device_timestamp has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vendor_radiotap_align has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field vendor_radiotap_bitmap has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field vendor_radiotap_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field vendor_radiotap_oui has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field vendor_radiotap_subns has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field vht_nss has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Type of field antenna has been changed from int to u8. | Recompilation of a client program may be broken. |
| 11 | Type of field band has been changed from enum ieee80211_band to u8. | Recompilation of a client program may be broken. |
| 12 | Type of field flag has been changed from int to u32. | Recompilation of a client program may be broken. |
| 13 | Type of field freq has been changed from int to u16. | Recompilation of a client program may be broken. |
| 14 | Type of field rate_idx has been changed from int to u8. | Recompilation of a client program may be broken. |
| 15 | Type of field rx_flags has been changed from unsigned int to u8. | Recompilation of a client program may be broken. |
| 16 | Type of field signal has been changed from int to s8. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rx_nss has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field vht_cap has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field supp_rates has been changed from u32[2] to u32[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cab_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field chanctx_conf has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field hw_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field rate_update has been changed from void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32, enum nl80211_channel_type) to void(*)(void*, struct ieee80211_supported_band*, struct ieee80211_sta*, void*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_space has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field space has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field new_data_offset 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 run has been changed from void(*)(struct mddev*) to void(*)(struct md_thread*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field bucket has been changed from struct rmc_entry[256] to struct list_head[256]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field request_microcode_fw has been changed from enum ucode_state(*)(int, struct device*) to enum ucode_state(*)(int, struct device*, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field remap_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field highest_vm_end has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field uprobes_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rb_subtree_gap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field free_list has been changed from struct list_head[5] to struct list_head[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field reclaim_stat 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[27] to s8[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfmemalloc_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field reclaim_nodes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compact_blockskip_flush has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field compact_cached_free_pfn has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field compact_cached_migrate_pfn has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field compact_considered has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field compact_defer_shift has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field compact_order_failed has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field managed_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Type of field vm_stat has been changed from atomic_long_t[27] to atomic_long_t[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field id has been changed from __u8[16] to __u8[9]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field bInterfaceNumber has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_inum 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. |
| 3 | 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 rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field diag_nlsk has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ifindex has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field user_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field proc_inum has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rt_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field nf_frag has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_enc_features has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field upper_dev_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mrp_port has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field qdisc_tx_busylock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_fdb_del has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_bridge_setlink has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ndo_fdb_dump has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ndo_change_carrier has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ndo_bridge_getlink has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ndo_bridge_dellink has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field ndo_fdb_add has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Base type of field ndo_netpoll_setup has been changed from int(*)(struct net_device*, struct netpoll_info*) to int(*)(struct net_device*, struct netpoll_info*, gfp_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cleanup_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ipv6 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. |
| 2 | Field dev_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field neigh_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field rx_flags has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_addr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field name has been changed from char const* to char[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data_len 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 | Field from_nlattr has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field queue_num has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field name has been changed from char const* to char[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field init_net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ls_flags has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field call_sync has been changed from int(*)(struct rpc_clnt*, struct nfs_server*, struct rpc_message*, struct nfs4_sequence_args*, struct nfs4_sequence_res*, int) to int(*)(struct rpc_clnt*, struct nfs_server*, struct rpc_message*, struct nfs4_sequence_args*, struct nfs4_sequence_res*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field so_delegreturn_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field so_reclaim_seqcount has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field detect_trunking has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lockowner has been changed from fl_owner_t to struct nfs_lockowner. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mdsthreshold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fc_target_max_resp_sz has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fc_target_max_rqst_sz has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field d_target_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field generation has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field session has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field d2_target_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field server_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field target_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Type of field used_slots has been changed from unsigned long[8] to unsigned long[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cl_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cl_implid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cl_mds_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cl_net has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cl_nfs_mod has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field cl_preserve_clid has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field cl_serverscope has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pg_completion_ops has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pg_dreq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sr_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sr_target_highest_slotid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sr_timestamp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field slot_nr has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field table has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field generation has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field interrupted has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mdsthreshold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field access_request has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field access_result has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field access_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field header has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alloc_client has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field clone_server has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field commit_rpc_prepare has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field create_server has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field free_client has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field have_delegation has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field read_pageio_init has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field return_delegation has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field submount has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field try_mount has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field write_pageio_init has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Base type of field commit_done has been changed from int(*)(struct rpc_task*, struct nfs_write_data*) to int(*)(struct rpc_task*, struct nfs_commit_data*). | Recompilation of a client program may be broken. |
| 13 | Base type of field commit_setup has been changed from void(*)(struct nfs_write_data*, struct rpc_message*) to void(*)(struct nfs_commit_data*, struct rpc_message*). | Recompilation of a client program may be broken. |
| 14 | Base type of field create has been changed from int(*)(struct inode*, struct dentry*, struct iattr*, int, struct nfs_open_context*) to int(*)(struct inode*, struct dentry*, struct iattr*, int). | Recompilation of a client program may be broken. |
| 15 | Base type of field init_client has been changed from int(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t, int) to struct nfs_client*(*)(struct nfs_client*, struct rpc_timeout const*, char const*, rpc_authflavor_t). | Recompilation of a client program may be broken. |
| 16 | Base type of field lookup has been changed from int(*)(struct rpc_clnt*, struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*) to int(*)(struct inode*, struct qstr*, struct nfs_fh*, struct nfs_fattr*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field header has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field busn_res has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field broken_intx_masking has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field d3cold_allowed has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field d3cold_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field io_window_1k has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field match_driver has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field no_d3cold has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field pcie_flags_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field rom has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field romlen has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field runtime_d3cold has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sriov_configure has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wall_clock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_ptr_wrap has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chmap_kctl has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_base_rdpmc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tp_target has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_fake has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pebs_event_reset has been changed from u64[4] to u64[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ip has been changed from __u64[255] to __u64[127]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field exclude_callchain_kernel has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sample_regs_user has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sample_stack_user has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field exclude_callchain_user has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field regs_user has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field stack_user_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr_offset has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field check_microcode has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field events_sysfs_show has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field max_pebs_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field pebs_aliases has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field pebs_broken has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field rdpmc_index has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field c45_ids has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_c45 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ts_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field match_phy_device has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field proc_inum has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field user_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field nr_hashed has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_auto has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acpi_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_init has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field qos has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field syscore 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 type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field autosleep_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field expire_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field prevent_sleep_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field start_prevent_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field wakeup_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field default_range has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field default_role has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field default_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field default_user has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field a_rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tcd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tzd has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inum has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_demux has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field early_demux has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_buf has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field erase has been changed from int(*)(enum pstore_type_id, u64, struct pstore_info*) to int(*)(enum pstore_type_id, u64, int, struct timespec, struct pstore_info*). | Recompilation of a client program may be broken. |
| 3 | Base type of field read has been changed from ssize_t(*)(u64*, enum pstore_type_id*, struct timespec*, char**, struct pstore_info*) to ssize_t(*)(u64*, enum pstore_type_id*, int*, struct timespec*, char**, struct pstore_info*). | Recompilation of a client program may be broken. |
| 4 | Base type of field write has been changed from int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, size_t, struct pstore_info*) to int(*)(enum pstore_type_id, enum kmsg_dump_reason, u64*, unsigned int, int, size_t, struct pstore_info*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field get_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*) to int(*)(struct super_block*, struct kqid, struct fs_disk_quota*). | Recompilation of a client program may be broken. |
| 2 | Base type of field quota_sync has been changed from int(*)(struct super_block*, int, int) to int(*)(struct super_block*, int). | Recompilation of a client program may be broken. |
| 3 | Base type of field set_dqblk has been changed from int(*)(struct super_block*, int, qid_t, struct fs_disk_quota*) to int(*)(struct super_block*, struct kqid, struct fs_disk_quota*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(struct rcu_head*, void(*)(struct rcu_head*)) to void()(struct callback_head*, void(*)(struct callback_head*)). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field n_nocbs_invoked has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field nxtcompleted has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Base type of field nxtlist has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| 5 | Base type of field nxttail has been changed from struct rcu_head** to struct callback_head**. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqslock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field barrier_completion has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field barrier_cpu_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field barrier_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field call has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field expedited_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field expedited_done_exit has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field expedited_done_lost has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field expedited_done_tries has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field expedited_normal has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field expedited_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field expedited_stoppedcpus has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field expedited_tryfail has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field expedited_workdone1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field expedited_workdone2 has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field expedited_wrap has been added to this type. | This field will not be initialized or used by old client applications. |
| 16 | Field flavors has been added to this type. | This field will not be initialized or used by old client applications. |
| 17 | Field gp_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 18 | Field gp_kthread has been added to this type. | This field will not be initialized or used by old client applications. |
| 19 | Field gp_wq has been added to this type. | This field will not be initialized or used by old client applications. |
| 20 | Field n_barrier_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 21 | Field onoff_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 22 | Field orphan_donelist has been added to this type. | This field will not be initialized or used by old client applications. |
| 23 | Field orphan_donetail has been added to this type. | This field will not be initialized or used by old client applications. |
| 24 | Field orphan_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 25 | Field orphan_nxtlist has been added to this type. | This field will not be initialized or used by old client applications. |
| 26 | Field orphan_nxttail has been added to this type. | This field will not be initialized or used by old client applications. |
| 27 | Field qlen has been added to this type. | This field will not be initialized or used by old client applications. |
| 28 | Field qlen_lazy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field user_reg_hint_type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field fastopenq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field resize_disabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field new_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field update_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field update_pages_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field dropped_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field nr_pages_to_update has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rb_root has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rwsem has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt_is_input has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rt_uncached has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rt_uses_gateway has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_num_rx_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field __remaining has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field piter has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field change has been changed from int(*)(struct tcf_proto*, unsigned long, u32, struct nlattr**, unsigned long*) to int(*)(struct net*, struct sk_buff*, struct tcf_proto*, unsigned long, u32, struct nlattr**, unsigned long*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field tg_runnable_contrib has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field blocked_load_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field removed_load has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field decay_counter has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field runnable_load_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field last_decay has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Type of field nr_running has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| 8 | Type of field h_nr_running has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field h_load_throttle has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field nr_running has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rt_nr_running has been changed from unsigned long to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field migrate_task_rq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field avg has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpumask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field watchdog_stamp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_cputime has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field oom_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field oom_score_adj has been changed from int to short. | Recompilation of a client program may be broken. |
| 4 | Type of field oom_score_adj_min has been changed from int to short. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field load_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field runnable_avg has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_cpus_allowed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field task_works has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field task_frag has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field prev_cputime has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field creds has been changed from struct ucred to struct scm_creds. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_dif has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field no_write_same has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field use_16_for_rw has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field wce_default_on has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field disk_events_disable_depth has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field no_report_opcodes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field file_open has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field kernel_module_from_file has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mmap_file has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field skb_owned_by has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field tun_dev_alloc_security has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field tun_dev_attach_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tun_dev_free_security has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field tun_dev_open has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Base type of field sb_mount has been changed from int(*)(char*, struct path*, char*, unsigned long, void*) to int(*)(char const*, struct path*, char const*, unsigned long, void*). | Recompilation of a client program may be broken. |
| 10 | Base type of field tun_dev_attach has been changed from int(*)(struct sock*) to int(*)(struct sock*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field throttle has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unthrottle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handle_break has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field pm_state has been changed from int to enum uart_pm_state. | 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 tx_bytes has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| 3 | Type of field rx_bytes has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| 4 | Type of field rx_packets has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| 5 | Type of field tx_packets has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field encapsulation has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pfmemalloc has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field head_frag has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field inner_network_header has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field inner_transport_header 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 cpu_up has been changed from int(*)(unsigned int) to int(*)(unsigned int, struct task_struct*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[84] to unsigned long[92]. | 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field release_cb has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mtu_reduced has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_frag has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_rx_dst has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_reuseport has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field batch_check0 has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field batch_check1 has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field batch_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field batch_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field queue_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field running has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field work has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Type of field completed has been changed from int to unsigned int. | 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. |
| 2 | Type of field c has been changed from int[2] to unsigned long[2]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field callback_head has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cur_max_bandwidth has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field last_ack_signal has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field last_rx_rate_vht_nss has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Type of field last_rx_rate_flag has been changed from int to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_rx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_tx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sp_task_pending has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rq_next_page has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cr_flavor has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cr_principal 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 permissions has been changed from int(*)(struct ctl_table_root*, struct nsproxy*, struct ctl_table*) to int(*)(struct ctl_table_header*, struct ctl_table*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field do_early_retrans has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field early_retrans_delayed has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field fastopen_req has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field fastopen_rsk has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field mtu_info has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field repair has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field repair_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field syn_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field syn_data_acked has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field syn_fastopen has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field tsoffset has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field tsq_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field tsq_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field thermal_instances has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field updated has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field emul_temperature has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field governor has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field temperature has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field thermal_instances has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field trip_temp_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field trip_type_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tzp has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Type of field passive has been changed from bool to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_trend has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_trip_hyst has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field set_emul_temp has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field set_trip_hyst has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field set_trip_temp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_timers has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field end has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field need_flush_all has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field start has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field entries has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field allocated_snapshot has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field print_max has been changed from int to bool. | Recompilation of a client program may be broken. |
| 3 | Type of field use_max_tr has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field low_latency has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field buf has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field iflags has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field itty has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field legacy_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field termios has been changed from struct ktermios* to struct ktermios. | Recompilation of a client program may be broken. |
| 3 | Type of field termios_locked has been changed from struct ktermios* to struct ktermios. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cdevs has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ports has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field flags has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 4 | Type of field num has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field wq_idle 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 dcd_change has been changed from void(*)(struct tty_struct*, unsigned int, struct pps_event_time*) to void(*)(struct tty_struct*, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from __kernel_nlink_t to __u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fixup has been changed from unsigned long to int. | Recompilation of a client program may be broken. |
| 2 | Type of field insn has been changed from unsigned long to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_stop_on_short has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field resuming_ports has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field u1_params has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field usb3_lpm_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field u2_params has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field port_is_suspended has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field lpm_disable_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field disable_hub_initiated_lpm 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. |
| 2 | Field may_mount_sysfs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field group has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field may_mount_proc has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field parent has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field proc_inum has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field gid_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field owner has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field uid_map has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field projid_map has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_inum has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field event has been changed from unsigned long[52] to unsigned long[59]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rescue_wq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compose_msi_msg has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field setup_hpet_msi has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field apic_post_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field notrack_deprecated_warning has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nwords has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfkey_supported 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 acquire has been changed from int(*)(struct xfrm_state*, struct xfrm_tmpl*, struct xfrm_policy*, int) to int(*)(struct xfrm_state*, struct xfrm_tmpl*, struct xfrm_policy*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field polq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field init_dst has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field saved_tmo has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field swapper 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 connect has been changed from void(*)(struct rpc_task*) to void(*)(struct rpc_xprt*, struct rpc_task*). | Recompilation of a client program may be broken. |
| 2 | Base type of field timer has been changed from void(*)(struct rpc_task*) to void(*)(struct rpc_xprt*, struct rpc_task*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from ACPI_GBL_EVENT_HANDLER to acpi_gbl_event_handler. | 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*[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from acpi_tbl_handler to acpi_table_handler. | 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 struct hlist_head[257] to struct hlist_head[512]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to u16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_device_id[4] const to struct pci_device_id[5] const. | 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 uid_t to kuid_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter dirlen has been changed from int* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter callback has been changed from int(*)(u32, u32, u32, u16, u32, u32*) to int(*)(u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter nd has been changed from struct nameidata* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 4th parameter match has been changed from int(*)(struct device*, void*) to int(*)(struct device*, void const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct nfs_client*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct nfs_client*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter inode has been changed from struct inode** to struct inode*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter flags has been changed from int to unsigned short. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[14] const to u32[15] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter n has been changed from int to __u64. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int 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 | Base type of 1st parameter rcu has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter tx has been changed from bool to enum ieee80211_agg_stop_reason. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter owner has been changed from void* to struct dev_state*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter owner has been changed from void* to struct dev_state*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter owner has been changed from void* to struct dev_state*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 7th parameter i has been changed from int to long. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int to long. | Recompilation of a client program may be broken. |
| 3 | Base type of 6th parameter length has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from insn_attr_t const*[4] to insn_attr_t const*[4] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter family has been changed from int to struct inet_peer_base*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to struct inode*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from bool to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter sdvo_reg has been changed from int to uint32_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rpc_procinfo[18] to struct rpc_procinfo[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned long[] to unsigned long[8]. | 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 nd has been changed from struct nameidata* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter run has been changed from void(*)(struct mddev*) to void(*)(struct md_thread*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter nr_pages has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter nr_pages has been changed from int to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int to long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 6th parameter msgflg has been changed from int to long(*)(void*, struct msg_msg*, size_t). | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter msgsz has been changed from size_t to long. | Recompilation of a client program may be broken. |
| 3 | Type of 5th parameter msgtyp has been changed from long to int. | Recompilation of a client program may be broken. |
| 4 | Type of 3rd parameter mtext has been changed from void* to size_t. | Recompilation of a client program may be broken. |
| 5 | Type of 2nd parameter pmtype has been changed from long* to void*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter nd has been changed from struct nameidata* to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter is_dir has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter is_dir has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter nd has been changed from struct nameidata* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, enum nf_ct_ftp_type, unsigned int, unsigned int, struct nf_conntrack_expect*) to unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, enum nf_ct_ftp_type, unsigned int, unsigned int, unsigned int, struct nf_conntrack_expect*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, unsigned int, unsigned int, struct nf_conntrack_expect*) to unsigned int(*)(struct sk_buff*, enum ip_conntrack_info, unsigned int, unsigned int, unsigned int, struct nf_conntrack_expect*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nf_conntrack_l3proto*[40] to struct nf_conntrack_l3proto*[41]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*) to unsigned int(*)(struct sk_buff*, unsigned int, unsigned int, char const**, unsigned int*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from void(*)(struct sk_buff*, s16) to void(*)(struct sk_buff*, unsigned int, s16). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int(*)(struct sk_buff*, struct nf_conn*, enum ip_conntrack_info) to int(*)(struct sk_buff*, struct nf_conn*, enum ip_conntrack_info, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from u32[2] const to u32[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct xattr_handler const*[] to struct xattr_handler const*[2]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nfs4_minor_version_ops const*[] to struct nfs4_minor_version_ops const*[1]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned int to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter unknown has been changed from int(*)(char*, char*) to int(*)(char*, char*, char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[3] to char const*[3] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[18] to struct event_constraint[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char[6] const to char[] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to pid_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter child_tid has been changed from void* to int. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter parent_tid 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 long. | 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 bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mcs_group[12] const to struct mcs_group[13] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter rhp has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter func has been changed from void(*)(struct rcu_head*) to void(*)(struct callback_head*). | Recompilation of a client program may be broken. |
| 2 | Base type of 1st parameter head has been changed from struct rcu_head to struct callback_head. | 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 struct ieee80211_reg_rule const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[30] const to struct nla_policy[34] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from 1 to 0. | 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 long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to kuid_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from sys_call_ptr_t[349] const to sys_call_ptr_t[351] const. | 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 return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter orig has been changed from u32 to struct thermal_zone_device*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter devdata has been changed from void* to int. | Recompilation of a client program may be broken. |
| 2 | Type of 4th parameter ops has been changed from struct thermal_zone_device_ops const* to void*. | Recompilation of a client program may be broken. |
| 3 | Type of 5th parameter tc1 has been changed from int to struct thermal_zone_device_ops const*. | Recompilation of a client program may be broken. |
| 4 | Type of 6th parameter tc2 has been changed from int to struct thermal_zone_params const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_cid_list has been changed from struct acpica_device_id_list to struct acpi_pnp_device_id_list. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter return_id has been changed from struct acpica_device_id to struct acpi_pnp_device_id. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u16 to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter local has been changed from struct ieee80211_local* to enum ieee80211_band. | 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 long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from atomic_long_t[27] to atomic_long_t[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from char const*[81] const to char const*[89] const. | 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 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 return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter data has been changed from void* to struct nfs_commit_data*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field notify_list has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bi_io_vec has been changed from 13 to 15. | No effect. |
| 2 | The relative position of field bi_end_io has been changed from 14 to 11. | No effect. |
| 3 | The relative position of field bi_max_vecs has been changed from 11 to 13. | No effect. |
| 4 | The relative position of field bi_cnt has been changed from 12 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_BAND_60GHZ with value 2 has been added. | No effect. |
| 2 | Value of member IEEE80211_NUM_BANDS has been changed from 2 to 3. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field beacon_interval has been changed from 2 to 4. | No effect. |
| 2 | The relative position of field signal has been changed from 6 to 3. | No effect. |
| 3 | The relative position of field proberesp_ies has been changed from 5 to 2. | No effect. |
| 4 | The relative position of field beacon_ies has been changed from 4 to 1. | No effect. |
| 5 | The relative position of field capability has been changed from 3 to 5. | No effect. |
| 6 | The relative position of field bssid has been changed from 1 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field wiphy has been changed from 6 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field release_list has been changed from 10 to 11. | No effect. |
| 2 | The relative position of field pidlist_mutex has been changed from 12 to 13. | No effect. |
| 3 | The relative position of field pidlists has been changed from 11 to 12. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field lastuse has been changed from 19 to 18. | No effect. |
| 2 | The relative position of field unnamed0 has been changed from 5 to 19. | No effect. |
| 3 | The relative position of field header_len has been changed from 14 to 13. | No effect. |
| 4 | The relative position of field obsolete has been changed from 13 to 12. | No effect. |
| 5 | The relative position of field trailer_len has been changed from 15 to 14. | No effect. |
| 6 | The relative position of field __use has been changed from 18 to 17. | No effect. |
| 7 | The relative position of field error has been changed from 12 to 11. | No effect. |
| 8 | The relative position of field __refcnt has been changed from 17 to 16. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field rt6_next has been added to this type. | No effect. |
| 2 | Field dn_next has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field registered has been changed from 5 to 4. | No effect. |
| 2 | The relative position of field hash has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field reserved2 has been replaced by eth_tp_mdix_ctrl. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dirtied_when has been changed from 24 to 25. | No effect. |
| 2 | The relative position of field i_atime has been changed from 14 to 15. | No effect. |
| 3 | The relative position of field i_blkbits has been changed from 31 to 20. | No effect. |
| 4 | The relative position of field i_blocks has been changed from 19 to 21. | No effect. |
| 5 | The relative position of field i_bytes has been changed from 18 to 19. | No effect. |
| 6 | The relative position of field i_count has been changed from 30 to 32. | No effect. |
| 7 | The relative position of field i_ctime has been changed from 16 to 17. | No effect. |
| 8 | The relative position of field i_hash has been changed from 25 to 26. | No effect. |
| 9 | The relative position of field i_lock has been changed from 17 to 18. | No effect. |
| 10 | The relative position of field i_lru has been changed from 27 to 28. | No effect. |
| 11 | The relative position of field i_mtime has been changed from 15 to 16. | No effect. |
| 12 | The relative position of field i_mutex has been changed from 23 to 24. | No effect. |
| 13 | The relative position of field i_sb_list has been changed from 28 to 29. | No effect. |
| 14 | The relative position of field i_size has been changed from 20 to 14. | No effect. |
| 15 | The relative position of field i_size_seqcount has been changed from 21 to 22. | No effect. |
| 16 | The relative position of field i_state has been changed from 22 to 23. | No effect. |
| 17 | The relative position of field i_version has been changed from 32 to 31. | No effect. |
| 18 | The relative position of field i_wb_list has been changed from 26 to 27. | No effect. |
| 19 | The relative position of field unnamed1 has been changed from 29 to 30. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fiemap has been changed from 21 to 20. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cpu has been changed from 14 to 13. | No effect. |
| 2 | The relative position of field ent has been changed from 10 to 9. | No effect. |
| 3 | The relative position of field ent_size has been changed from 13 to 12. | No effect. |
| 4 | The relative position of field idx has been changed from 17 to 16. | No effect. |
| 5 | The relative position of field leftover has been changed from 12 to 11. | No effect. |
| 6 | The relative position of field lost_events has been changed from 11 to 10. | No effect. |
| 7 | The relative position of field pos has been changed from 16 to 15. | No effect. |
| 8 | The relative position of field seq has been changed from 9 to 8. | No effect. |
| 9 | The relative position of field started has been changed from 8 to 17. | No effect. |
| 10 | The relative position of field ts has been changed from 15 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field resume has been changed from 8 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PCH_LPT with value 3 has been added. | No effect. |
| 2 | The member PCH_NONE with value 0 has been added. | No effect. |
| 3 | Value of member PCH_CPT has been changed from 1 to 2. | No effect. |
| 4 | Value of member PCH_IBX has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fdi_link_train has been changed from 9 to 10. | No effect. |
| 2 | The relative position of field init_clock_gating has been changed from 10 to 11. | No effect. |
| 3 | The relative position of field write_eld has been changed from 8 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field pages has been changed from 20 to 21. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field backlight has been changed from 76 to 74. | No effect. |
| 2 | The relative position of field broadcast_rgb_property has been changed from 77 to 75. | No effect. |
| 3 | The relative position of field child_dev has been changed from 70 to 68. | No effect. |
| 4 | The relative position of field child_dev_num has been changed from 69 to 67. | No effect. |
| 5 | The relative position of field compressed_fb has been changed from 73 to 71. | No effect. |
| 6 | The relative position of field compressed_llb has been changed from 74 to 72. | No effect. |
| 7 | The relative position of field fbdev has been changed from 75 to 73. | No effect. |
| 8 | The relative position of field force_audio_property has been changed from 78 to 76. | No effect. |
| 9 | The relative position of field lvds_border_bits has been changed from 59 to 57. | No effect. |
| 10 | The relative position of field lvds_downclock has been changed from 67 to 65. | No effect. |
| 11 | The relative position of field lvds_downclock_avail has been changed from 66 to 64. | No effect. |
| 12 | The relative position of field mchbar_need_disable has been changed from 71 to 69. | No effect. |
| 13 | The relative position of field mm has been changed from 57 to 55. | No effect. |
| 14 | The relative position of field no_fbc_reason has been changed from 72 to 70. | No effect. |
| 15 | The relative position of field orig_clock has been changed from 68 to 66. | No effect. |
| 16 | The relative position of field pch_pf_pos has been changed from 60 to 58. | No effect. |
| 17 | The relative position of field pch_pf_size has been changed from 61 to 59. | No effect. |
| 18 | The relative position of field pending_flip_queue has been changed from 64 to 62. | No effect. |
| 19 | The relative position of field pipe_to_crtc_mapping has been changed from 63 to 61. | No effect. |
| 20 | The relative position of field plane_to_crtc_mapping has been changed from 62 to 60. | No effect. |
| 21 | The relative position of field render_reclock_avail has been changed from 65 to 63. | No effect. |
| 22 | The relative position of field sdvo_mappings has been changed from 58 to 56. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_notify_cw has been added to this type. | No effect. |
| 2 | Field vht_opmode_notif has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SCAN_ABORT with value 5 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field _oper_channel_type has been changed from 64 to 66. | No effect. |
| 2 | The relative position of field ack_status_frames has been changed from 105 to 104. | No effect. |
| 3 | The relative position of field ack_status_lock has been changed from 106 to 105. | No effect. |
| 4 | The relative position of field csa_channel has been changed from 66 to 64. | No effect. |
| 5 | The relative position of field hw_roc_done has been changed from 103 to 102. | No effect. |
| 6 | The relative position of field hw_roc_start has been changed from 102 to 101. | No effect. |
| 7 | The relative position of field napi has been changed from 108 to 107. | No effect. |
| 8 | The relative position of field napi_dev has been changed from 107 to 106. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field fragments has been changed from 6 to 5. | No effect. |
| 2 | The relative position of field fragments_tail has been changed from 7 to 6. | No effect. |
| 3 | The relative position of field last_in has been changed from 11 to 10. | No effect. |
| 4 | The relative position of field len has been changed from 9 to 8. | No effect. |
| 5 | The relative position of field list has been changed from 0 to 3. | No effect. |
| 6 | The relative position of field lock has been changed from 3 to 0. | No effect. |
| 7 | The relative position of field meat has been changed from 10 to 9. | No effect. |
| 8 | The relative position of field net has been changed from 1 to 11. | No effect. |
| 9 | The relative position of field stamp has been changed from 8 to 7. | No effect. |
| 10 | The relative position of field timer has been changed from 5 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field constructor has been changed from 7 to 8. | No effect. |
| 2 | The relative position of field destructor has been changed from 8 to 9. | No effect. |
| 3 | The relative position of field match has been changed from 10 to 7. | No effect. |
| 4 | The relative position of field qsize has been changed from 3 to 5. | No effect. |
| 5 | The relative position of field rnd has been changed from 2 to 4. | No effect. |
| 6 | The relative position of field secret_interval has been changed from 4 to 2. | No effect. |
| 7 | The relative position of field secret_timer has been changed from 5 to 3. | No effect. |
| 8 | The relative position of field skb_free has been changed from 9 to 10. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field lru_list has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field mem has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dst has been changed from 4 to 5. | No effect. |
| 2 | The relative position of field length has been changed from 5 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field lock has been changed from 6 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dev_id has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field flags has been changed from 1 to 7. | No effect. |
| 3 | The relative position of field irq has been changed from 5 to 6. | No effect. |
| 4 | The relative position of field next has been changed from 4 to 3. | No effect. |
| 5 | The relative position of field percpu_dev_id has been changed from 3 to 2. | No effect. |
| 6 | The relative position of field thread has been changed from 7 to 5. | No effect. |
| 7 | The relative position of field thread_fn has been changed from 6 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field icmp_sk has been changed from 9 to 10. | No effect. |
| 2 | The relative position of field fib_table_hash has been changed from 7 to 8. | No effect. |
| 3 | The relative position of field fibnl has been changed from 8 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field unnamed0 has been changed from 6 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field serial_node has been added to this type. | No effect. |
| 2 | Field graveyard_link has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member KMSG_DUMP_UNDEF with value 0 has been added. | No effect. |
| 2 | Value of member KMSG_DUMP_EMERG has been changed from 2 to 3. | No effect. |
| 3 | Value of member KMSG_DUMP_HALT has been changed from 4 to 5. | No effect. |
| 4 | Value of member KMSG_DUMP_OOPS has been changed from 1 to 2. | No effect. |
| 5 | Value of member KMSG_DUMP_PANIC has been changed from 0 to 1. | No effect. |
| 6 | Value of member KMSG_DUMP_POWEROFF has been changed from 5 to 6. | No effect. |
| 7 | Value of member KMSG_DUMP_RESTART has been changed from 3 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dump has been changed from 0 to 1. | No effect. |
| 2 | The relative position of field list has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field ack_signal has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field ampdu_ack_len has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field antenna has been changed from 4 to 6. | No effect. |
| 2 | The relative position of field band has been changed from 1 to 5. | No effect. |
| 3 | The relative position of field flag has been changed from 6 to 1. | No effect. |
| 4 | The relative position of field rate_idx has been changed from 5 to 3. | No effect. |
| 5 | The relative position of field rx_flags has been changed from 7 to 4. | No effect. |
| 6 | The relative position of field signal has been changed from 3 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field vm_next has been changed from 3 to 2. | No effect. |
| 2 | The relative position of field vm_prev has been changed from 4 to 3. | No effect. |
| 3 | The relative position of field vm_rb has been changed from 7 to 4. | No effect. |
| 4 | The relative position of field vm_mm has been changed from 0 to 5. | No effect. |
| 5 | The relative position of field vm_flags has been changed from 6 to 7. | No effect. |
| 6 | The relative position of field vm_page_prot has been changed from 5 to 6. | No effect. |
| 7 | The relative position of field vm_end has been changed from 2 to 1. | No effect. |
| 8 | The relative position of field vm_start has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field slab_page has been added to this type. | No effect. |
| 2 | Field list has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field nonlinear has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field pfmemalloc has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field units has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NR_FREE_CMA_PAGES with value 27 has been added. | No effect. |
| 2 | Value of member NR_VM_ZONE_STAT_ITEMS has been changed from 27 to 28. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field pad1 has been replaced by group. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member MODULE_STATE_UNFORMED with value 3 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dev_list has been changed from 8 to 10. | No effect. |
| 2 | The relative position of field gro_count has been changed from 6 to 3. | No effect. |
| 3 | The relative position of field gro_list has been changed from 9 to 8. | No effect. |
| 4 | The relative position of field poll has been changed from 3 to 4. | No effect. |
| 5 | The relative position of field poll_lock has been changed from 4 to 5. | No effect. |
| 6 | The relative position of field poll_owner has been changed from 5 to 6. | No effect. |
| 7 | The relative position of field skb has been changed from 10 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tx_global_lock has been changed from 70 to 69. | No effect. |
| 2 | The relative position of field napi_list has been changed from 10 to 9. | No effect. |
| 3 | The relative position of field real_num_rx_queues has been changed from 60 to 59. | No effect. |
| 4 | The relative position of field rx_handler has been changed from 62 to 61. | No effect. |
| 5 | The relative position of field base_addr has been changed from 6 to 5. | No effect. |
| 6 | The relative position of field dev_addrs has been changed from 55 to 54. | No effect. |
| 7 | The relative position of field broadcast has been changed from 56 to 55. | No effect. |
| 8 | The relative position of field reg_state has been changed from 79 to 78. | No effect. |
| 9 | The relative position of field link_watch_list has been changed from 78 to 77. | No effect. |
| 10 | The relative position of field npinfo has been changed from 83 to 82. | No effect. |
| 11 | The relative position of field _rx has been changed from 58 to 57. | No effect. |
| 12 | The relative position of field group has been changed from 96 to 95. | No effect. |
| 13 | The relative position of field dev_addr has been changed from 54 to 53. | No effect. |
| 14 | The relative position of field state has been changed from 8 to 7. | No effect. |
| 15 | The relative position of field unnamed0 has been changed from 85 to 84. | No effect. |
| 16 | The relative position of field rx_handler_data has been changed from 63 to 62. | No effect. |
| 17 | The relative position of field mem_end has been changed from 4 to 3. | No effect. |
| 18 | The relative position of field ifalias has been changed from 3 to 2. | No effect. |
| 19 | The relative position of field tx_queue_len has been changed from 69 to 68. | No effect. |
| 20 | The relative position of field dismantle has been changed from 80 to 79. | No effect. |
| 21 | The relative position of field trans_start has been changed from 72 to 71. | No effect. |
| 22 | The relative position of field queues_kset has been changed from 57 to 56. | No effect. |
| 23 | The relative position of field pm_qos_req has been changed from 1 to 96. | No effect. |
| 24 | The relative position of field last_rx has been changed from 53 to 52. | No effect. |
| 25 | The relative position of field mem_start has been changed from 5 to 4. | No effect. |
| 26 | The relative position of field watchdog_timer has been changed from 74 to 73. | No effect. |
| 27 | The relative position of field xps_maps has been changed from 71 to 70. | No effect. |
| 28 | The relative position of field ax25_ptr has been changed from 51 to 50. | No effect. |
| 29 | The relative position of field rx_cpu_rmap has been changed from 61 to 60. | No effect. |
| 30 | The relative position of field irq has been changed from 7 to 6. | No effect. |
| 31 | The relative position of field nd_net has been changed from 84 to 83. | No effect. |
| 32 | The relative position of field qdisc has been changed from 68 to 67. | No effect. |
| 33 | The relative position of field name_hlist has been changed from 2 to 1. | No effect. |
| 34 | The relative position of field features has been changed from 12 to 11. | No effect. |
| 35 | The relative position of field todo_list has been changed from 76 to 75. | No effect. |
| 36 | The relative position of field unreg_list has been changed from 11 to 10. | No effect. |
| 37 | The relative position of field pcpu_refcnt has been changed from 75 to 74. | No effect. |
| 38 | The relative position of field garp_port has been changed from 86 to 85. | No effect. |
| 39 | The relative position of field index_hlist has been changed from 77 to 76. | No effect. |
| 40 | The relative position of field hw_features has been changed from 13 to 12. | No effect. |
| 41 | The relative position of field watchdog_timeo has been changed from 73 to 72. | No effect. |
| 42 | The relative position of field num_rx_queues has been changed from 59 to 58. | No effect. |
| 43 | The relative position of field vlan_features has been changed from 15 to 14. | No effect. |
| 44 | The relative position of field _tx has been changed from 65 to 64. | No effect. |
| 45 | The relative position of field dev_list has been changed from 9 to 8. | No effect. |
| 46 | The relative position of field ieee80211_ptr has been changed from 52 to 51. | No effect. |
| 47 | The relative position of field destructor has been changed from 82 to 81. | No effect. |
| 48 | The relative position of field ingress_queue has been changed from 64 to 63. | No effect. |
| 49 | The relative position of field num_tx_queues has been changed from 66 to 65. | No effect. |
| 50 | The relative position of field rtnl_link_state has been changed from 81 to 80. | No effect. |
| 51 | The relative position of field real_num_tx_queues has been changed from 67 to 66. | No effect. |
| 52 | The relative position of field wanted_features has been changed from 14 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field vstats has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field name became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member SDP_HDR_MEDIA has been changed from 6 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field highest_used_slotid has been changed from 5 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cinfo has been changed from 2 to 3. | No effect. |
| 2 | The relative position of field f_attr has been changed from 4 to 5. | No effect. |
| 3 | The relative position of field fh has been changed from 1 to 2. | No effect. |
| 4 | The relative position of field rflags has been changed from 3 to 4. | No effect. |
| 5 | The relative position of field seq_res has been changed from 14 to 0. | No effect. |
| 6 | The relative position of field stateid has been changed from 0 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field args has been changed from 4 to 3. | No effect. |
| 2 | The relative position of field ds_clp has been changed from 7 to 9. | No effect. |
| 3 | The relative position of field list has been changed from 3 to 0. | No effect. |
| 4 | The relative position of field mds_offset has been changed from 9 to 7. | No effect. |
| 5 | The relative position of field pages has been changed from 2 to 8. | No effect. |
| 6 | The relative position of field read_done_cb has been changed from 8 to 6. | No effect. |
| 7 | The relative position of field res has been changed from 5 to 4. | No effect. |
| 8 | The relative position of field task has been changed from 0 to 1. | No effect. |
| 9 | The relative position of field timestamp has been changed from 6 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field context has been changed from 1 to 2. | No effect. |
| 2 | The relative position of field count has been changed from 4 to 5. | No effect. |
| 3 | The relative position of field fh has been changed from 0 to 1. | No effect. |
| 4 | The relative position of field lock_context has been changed from 2 to 3. | No effect. |
| 5 | The relative position of field offset has been changed from 3 to 4. | No effect. |
| 6 | The relative position of field pages has been changed from 6 to 7. | No effect. |
| 7 | The relative position of field pgbase has been changed from 5 to 6. | No effect. |
| 8 | The relative position of field seq_args has been changed from 7 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field count has been changed from 1 to 2. | No effect. |
| 2 | The relative position of field eof has been changed from 2 to 3. | No effect. |
| 3 | The relative position of field fattr has been changed from 0 to 1. | No effect. |
| 4 | The relative position of field seq_res has been changed from 3 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field args has been changed from 5 to 4. | No effect. |
| 2 | The relative position of field ds_clp has been changed from 7 to 10. | No effect. |
| 3 | The relative position of field list has been changed from 4 to 0. | No effect. |
| 4 | The relative position of field mds_offset has been changed from 10 to 8. | No effect. |
| 5 | The relative position of field pages has been changed from 3 to 9. | No effect. |
| 6 | The relative position of field res has been changed from 6 to 5. | No effect. |
| 7 | The relative position of field task has been changed from 0 to 1. | No effect. |
| 8 | The relative position of field timestamp has been changed from 9 to 6. | No effect. |
| 9 | The relative position of field write_done_cb has been changed from 8 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bitmask has been changed from 8 to 9. | No effect. |
| 2 | The relative position of field context has been changed from 1 to 2. | No effect. |
| 3 | The relative position of field count has been changed from 4 to 5. | No effect. |
| 4 | The relative position of field fh has been changed from 0 to 1. | No effect. |
| 5 | The relative position of field lock_context has been changed from 2 to 3. | No effect. |
| 6 | The relative position of field offset has been changed from 3 to 4. | No effect. |
| 7 | The relative position of field pages has been changed from 7 to 8. | No effect. |
| 8 | The relative position of field pgbase has been changed from 6 to 7. | No effect. |
| 9 | The relative position of field seq_args has been changed from 9 to 0. | No effect. |
| 10 | The relative position of field stable has been changed from 5 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field count has been changed from 2 to 3. | No effect. |
| 2 | The relative position of field fattr has been changed from 0 to 1. | No effect. |
| 3 | The relative position of field seq_res has been changed from 4 to 0. | No effect. |
| 4 | The relative position of field server has been changed from 3 to 4. | No effect. |
| 5 | The relative position of field verf has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field committed has been changed from 0 to 1. | No effect. |
| 2 | The relative position of field verifier has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_AUTHTYPE_SAE with value 4 has been added. | No effect. |
| 2 | Value of member NL80211_AUTHTYPE_MAX has been changed from 3 to 4. | No effect. |
| 3 | Value of member NL80211_AUTHTYPE_AUTOMATIC has been changed from 4 to 5. | No effect. |
| 4 | Value of member __NL80211_AUTHTYPE_NUM has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_CQM_RSSI_BEACON_LOSS_EVENT with value 2 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NL80211_IFTYPE_P2P_DEVICE with value 10 has been added. | No effect. |
| 2 | Value of member NL80211_IFTYPE_MAX has been changed from 9 to 10. | No effect. |
| 3 | Value of member NUM_NL80211_IFTYPES has been changed from 10 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field bts_active has been changed from 37 to 36. | No effect. |
| 2 | The relative position of field pebs has been changed from 36 to 37. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed3 has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_AUTHENTIC with value 5 has been added. | No effect. |
| 2 | The member POWER_SUPPLY_PROP_CAPACITY_ALERT_MAX with value 41 has been added. | No effect. |
| 3 | The member POWER_SUPPLY_PROP_CAPACITY_ALERT_MIN with value 40 has been added. | No effect. |
| 4 | The member POWER_SUPPLY_PROP_CHARGE_CONTROL_LIMIT with value 31 has been added. | No effect. |
| 5 | The member POWER_SUPPLY_PROP_CHARGE_CONTROL_LIMIT_MAX with value 32 has been added. | No effect. |
| 6 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT with value 27 has been added. | No effect. |
| 7 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT_MAX with value 28 has been added. | No effect. |
| 8 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_VOLTAGE with value 29 has been added. | No effect. |
| 9 | The member POWER_SUPPLY_PROP_CONSTANT_CHARGE_VOLTAGE_MAX with value 30 has been added. | No effect. |
| 10 | The member POWER_SUPPLY_PROP_TEMP_ALERT_MAX with value 45 has been added. | No effect. |
| 11 | The member POWER_SUPPLY_PROP_TEMP_ALERT_MIN with value 44 has been added. | No effect. |
| 12 | The member POWER_SUPPLY_PROP_TEMP_AMBIENT_ALERT_MAX with value 48 has been added. | No effect. |
| 13 | The member POWER_SUPPLY_PROP_TEMP_AMBIENT_ALERT_MIN with value 47 has been added. | No effect. |
| 14 | The member POWER_SUPPLY_PROP_VOLTAGE_OCV with value 14 has been added. | No effect. |
| 15 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 24 to 26. | No effect. |
| 16 | Value of member POWER_SUPPLY_PROP_CURRENT_MAX has been changed from 13 to 15. | No effect. |
| 17 | Value of member POWER_SUPPLY_PROP_CYCLE_COUNT has been changed from 6 to 7. | No effect. |
| 18 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX has been changed from 7 to 8. | No effect. |
| 19 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX_DESIGN has been changed from 9 to 10. | No effect. |
| 20 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 31 to 39. | No effect. |
| 21 | Value of member POWER_SUPPLY_PROP_CAPACITY_LEVEL has been changed from 32 to 42. | No effect. |
| 22 | Value of member POWER_SUPPLY_PROP_CHARGE_AVG has been changed from 23 to 25. | No effect. |
| 23 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY has been changed from 21 to 23. | No effect. |
| 24 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY_DESIGN has been changed from 19 to 21. | No effect. |
| 25 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL has been changed from 20 to 22. | No effect. |
| 26 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN has been changed from 18 to 20. | No effect. |
| 27 | Value of member POWER_SUPPLY_PROP_CHARGE_NOW has been changed from 22 to 24. | No effect. |
| 28 | Value of member POWER_SUPPLY_PROP_CURRENT_AVG has been changed from 15 to 17. | No effect. |
| 29 | Value of member POWER_SUPPLY_PROP_CURRENT_NOW has been changed from 14 to 16. | No effect. |
| 30 | Value of member POWER_SUPPLY_PROP_ENERGY_AVG has been changed from 30 to 38. | No effect. |
| 31 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY has been changed from 28 to 36. | No effect. |
| 32 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY_DESIGN has been changed from 26 to 34. | No effect. |
| 33 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL has been changed from 27 to 35. | No effect. |
| 34 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL_DESIGN has been changed from 25 to 33. | No effect. |
| 35 | Value of member POWER_SUPPLY_PROP_ENERGY_NOW has been changed from 29 to 37. | No effect. |
| 36 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 42 to 56. | No effect. |
| 37 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 41 to 55. | No effect. |
| 38 | Value of member POWER_SUPPLY_PROP_POWER_AVG has been changed from 17 to 19. | No effect. |
| 39 | Value of member POWER_SUPPLY_PROP_POWER_NOW has been changed from 16 to 18. | No effect. |
| 40 | Value of member POWER_SUPPLY_PROP_SCOPE has been changed from 40 to 54. | No effect. |
| 41 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 43 to 57. | No effect. |
| 42 | Value of member POWER_SUPPLY_PROP_TECHNOLOGY has been changed from 5 to 6. | No effect. |
| 43 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 33 to 43. | No effect. |
| 44 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 34 to 46. | No effect. |
| 45 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG has been changed from 36 to 50. | No effect. |
| 46 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW has been changed from 35 to 49. | No effect. |
| 47 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 38 to 52. | No effect. |
| 48 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 37 to 51. | No effect. |
| 49 | Value of member POWER_SUPPLY_PROP_TYPE has been changed from 39 to 53. | No effect. |
| 50 | Value of member POWER_SUPPLY_PROP_VOLTAGE_AVG has been changed from 12 to 13. | No effect. |
| 51 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN has been changed from 8 to 9. | No effect. |
| 52 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN_DESIGN has been changed from 10 to 11. | No effect. |
| 53 | Value of member POWER_SUPPLY_PROP_VOLTAGE_NOW has been changed from 11 to 12. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field commit_overrun has been changed from 14 to 16. | No effect. |
| 2 | The relative position of field entries has been changed from 16 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rt_gateway has been changed from 6 to 5. | No effect. |
| 2 | The relative position of field rt_iif has been changed from 5 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field rq has been changed from 12 to 14. | No effect. |
| 2 | The relative position of field leaf_cfs_rq_list has been changed from 14 to 16. | No effect. |
| 3 | The relative position of field h_load has been changed from 16 to 13. | No effect. |
| 4 | The relative position of field tg has been changed from 15 to 17. | No effect. |
| 5 | The relative position of field on_list has been changed from 13 to 15. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SDEV_TRANSPORT_OFFLINE with value 7 has been added. | No effect. |
| 2 | Value of member SDEV_BLOCK has been changed from 7 to 8. | No effect. |
| 3 | Value of member SDEV_CREATED_BLOCK has been changed from 8 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field _sigsys has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field skc_prot has been changed from 6 to 7. | No effect. |
| 2 | The relative position of field skc_dontcopy_begin has been changed from 8 to 9. | No effect. |
| 3 | The relative position of field unnamed1 has been changed from 5 to 1. | No effect. |
| 4 | The relative position of field unnamed2 has been changed from 9 to 2. | No effect. |
| 5 | The relative position of field skc_bound_dev_if has been changed from 4 to 6. | No effect. |
| 6 | The relative position of field skc_net has been changed from 7 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed0 has been added to this type. | No effect. |
| 2 | Field skc_addrpair has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_u16hashes has been added to this type. | No effect. |
| 2 | Field skc_hash has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field skc_portpair has been added to this type. | No effect. |
| 2 | Field unnamed0 has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field devdata has been changed from 3 to 4. | No effect. |
| 2 | The relative position of field trips has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field stopped has been changed from 19 to 20. | No effect. |
| 2 | The relative position of field fasync has been changed from 27 to 28. | No effect. |
| 3 | The relative position of field link has been changed from 26 to 27. | No effect. |
| 4 | The relative position of field termiox has been changed from 12 to 13. | No effect. |
| 5 | The relative position of field ctrl_lock has been changed from 9 to 10. | No effect. |
| 6 | The relative position of field hw_stopped has been changed from 20 to 21. | No effect. |
| 7 | The relative position of field minimum_to_wake has been changed from 36 to 37. | No effect. |
| 8 | The relative position of field termios_locked has been changed from 11 to 12. | No effect. |
| 9 | The relative position of field winsize has been changed from 18 to 19. | No effect. |
| 10 | The relative position of field session has been changed from 15 to 16. | No effect. |
| 11 | The relative position of field ctrl_status has been changed from 24 to 25. | No effect. |
| 12 | The relative position of field receive_room has been changed from 25 to 26. | No effect. |
| 13 | The relative position of field termios_mutex has been changed from 8 to 9. | No effect. |
| 14 | The relative position of field atomic_write_lock has been changed from 37 to 8. | No effect. |
| 15 | The relative position of field closing has been changed from 35 to 36. | No effect. |
| 16 | The relative position of field count has been changed from 17 to 18. | No effect. |
| 17 | The relative position of field flags has been changed from 16 to 17. | No effect. |
| 18 | The relative position of field flow_stopped has been changed from 21 to 22. | No effect. |
| 19 | The relative position of field name has been changed from 13 to 14. | No effect. |
| 20 | The relative position of field packet has been changed from 22 to 23. | No effect. |
| 21 | The relative position of field pgrp has been changed from 14 to 15. | No effect. |
| 22 | The relative position of field termios has been changed from 10 to 11. | No effect. |
| 23 | The relative position of field warned has been changed from 23 to 24. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field endpoint has been changed from 1 to 3. | No effect. |
| 2 | The relative position of field extra has been changed from 3 to 2. | No effect. |
| 3 | The relative position of field string has been changed from 2 to 4. | No effect. |
| 4 | The relative position of field extralen has been changed from 4 to 1. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field nr_to_write has been changed from 1 to 0. | No effect. |
| 2 | The relative position of field pages_skipped has been changed from 2 to 1. | No effect. |
| 3 | The relative position of field range_end has been changed from 4 to 3. | No effect. |
| 4 | The relative position of field range_start has been changed from 3 to 2. | No effect. |
| 5 | The relative position of field sync_mode has been changed from 0 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter running has been renamed to domain. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter running has been renamed to domain. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter list has been renamed to domain. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter dirlen has been renamed to parentlen. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nd has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to mount_info. | No effect. |
| 2 | 2nd parameter mntfh has been renamed to nfs_mod. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter data has been renamed to mount_info. | No effect. |
| 2 | 2nd parameter mntfh has been renamed to nfs_mod. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter i has been renamed to elemp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to device. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to u8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 7th parameter spec_dst has been renamed to idev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter eld has been renamed to e. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to hid. | 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 | 4th parameter ht_cap has been renamed to sta. | No effect. |
| 2 | Type of return value has been changed from void to bool. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter tx has been renamed to reason. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter length has been renamed to nr_pages. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to unsigned long. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter request has been renamed to out_seqno. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter new_dev has been renamed to new_wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter family has been renamed to base. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to inode. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pdev has been renamed to bridge_pdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to connector. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter uid has been renamed to user. | No effect. |
| 2 | 3rd parameter gid has been renamed to group. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter trigger has been renamed to trig. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter mddev has been renamed to thread. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter acknowledged has been renamed to is_new. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter address has been renamed to start. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter snd_pid has been renamed to snd_portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter nlpid has been renamed to nlportid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to unsigned int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pmtype has been renamed to buf. | No effect. |
| 2 | 3rd parameter mtext has been renamed to bufsz. | No effect. |
| 3 | 4th parameter msgsz has been renamed to msgtyp. | No effect. |
| 4 | 5th parameter msgtyp has been renamed to msgflg. | No effect. |
| 5 | 6th parameter msgflg has been renamed to msg_handler. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter nd has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter is_dir has been renamed to lookup_flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter is_dir has been renamed to lookup_flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter nd has been renamed to want_excl. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | No effect. |
| 2 | 3rd parameter nlpid has been renamed to nlportid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter netdev has been renamed to wdev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter new_address has been renamed to address. | No effect. |
| 2 | 3rd parameter new_table_length has been renamed to table_length. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 8th parameter limit has been renamed to low_limit. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to doing. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter i has been renamed to gsi. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter parent_tid has been renamed to parent_tidptr. | No effect. |
| 2 | 4th parameter child_tid has been renamed to tls_val. | No effect. |
| 3 | 5th parameter regs has been renamed to child_tidptr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter name has been renamed to filename. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter unused has been renamed to arg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to hdr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pci_bus has been renamed to bus. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to u64. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to u64. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to unsigned int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter flp4 has been renamed to fl4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter sdata has been renamed to local. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter origin has been renamed to whence. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter set has been renamed to uset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter history0 has been renamed to unused1. | No effect. |
| 2 | 2nd parameter history1 has been renamed to unused2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter fclone has been renamed to flags. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter logical_apicid has been renamed to apicid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rgid has been renamed to rgidp. | No effect. |
| 2 | 2nd parameter egid has been renamed to egidp. | No effect. |
| 3 | 3rd parameter sgid has been renamed to sgidp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ruid has been renamed to ruidp. | No effect. |
| 2 | 2nd parameter euid has been renamed to euidp. | No effect. |
| 3 | 3rd parameter suid has been renamed to suidp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cpu_dev has been renamed to dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter cpu_dev has been renamed to dev. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter table_ptr has been renamed to table. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter orig has been renamed to tz. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter devdata has been renamed to mask. | No effect. |
| 2 | 4th parameter ops has been renamed to devdata. | No effect. |
| 3 | 5th parameter tc1 has been renamed to ops. | No effect. |
| 4 | 6th parameter tc2 has been renamed to tzp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter va has been renamed to start. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter va has been renamed to start. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tty has been renamed to port. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter rgid has been renamed to rgidp. | No effect. |
| 2 | 2nd parameter egid has been renamed to egidp. | No effect. |
| 3 | 3rd parameter sgid has been renamed to sgidp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ruid has been renamed to ruidp. | No effect. |
| 2 | 2nd parameter euid has been renamed to euidp. | No effect. |
| 3 | 3rd parameter suid has been renamed to suidp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter s has been renamed to str. | No effect. |
| 2 | 2nd parameter n has been renamed to count. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter component_id has been renamed to base_offset. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to band. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to hdr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter head has been renamed to dst. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to unsigned int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |