- Linux-kselftest-mirror - lists.linaro.org

bpf: test_xdp_vlan.sh: Kernel panic: Unable to handle kernel paging request at virtual address 000080096d61a000

by Naresh Kamboju

Kernel panic while running bpf: test_xdp_vlan.sh test case on arm64 Juno hardware Linux version 5.2.0-rc3-next-20190604 bpf: test_xdp_vlan.sh # --- 100.64.41.2 ping statistics --- 100.64.41.2: ping_statistics # # 3 packets transmitted, 3 received, 0% packet loss, time 2049ms packets: transmitted,_3 # # rtt min/avg/max/mdev = 0.172/0.193/0.205/0.022 ms min/avg/max/mdev: =_0.172/0.193/0.205/0.022 # # PING 100.64.41.1 (100.64.41.1) 56(84) bytes of data. 100.64.41.1: (100.64.41.1)_56(84) # # 64 bytes from 100.64.41.1 icmp_seq=1 ttl=64 time=0.146 ms bytes: from_100.64.41.1 # # 64 bytes from 100.64.41.1 icmp_seq=2 ttl=64 time=0.182 ms bytes: from_100.64.41.1 # [ 492.263541] ip6_tunnel: gre6_dev xmit: Local address not yet configured! [ 788.768658] ip6_tunnel: gre6_dev xmit: Local address not yet configured! [ 940.373938] Unable to handle kernel paging request at virtual address 000080096d61a000 [ 940.381873] Mem abort info: [ 940.384717] ESR = 0x96000004 [ 940.387797] Exception class = DABT (current EL), IL = 32 bits [ 940.393715] SET = 0, FnV = 0 [ 940.396788] EA = 0, S1PTW = 0 [ 940.399949] Data abort info: [ 940.402805] ISV = 0, ISS = 0x00000004 [ 940.406647] CM = 0, WnR = 0 [ 940.409639] user pgtable: 4k pages, 48-bit VAs, pgdp=000000093bee0000 [ 940.416065] [000080096d61a000] pgd=0000000000000000 [ 940.421079] Internal error: Oops: 96000004 [#1] PREEMPT SMP [ 940.426598] Modules linked in: sit act_gact cls_flower cls_bpf sch_ingress xt_tcpudp iptable_filter ip_tables x_tables tun algif_hash af_alg tda998x drm_kms_helper drm crct10dif_ce drm_panel_orientation_quirks fuse [last unloaded: test_bpf] [ 940.447715] CPU: 2 PID: 8748 Comm: ping Not tainted 5.2.0-rc3-next-20190604 #1 [ 940.454865] Hardware name: ARM Juno development board (r2) (DT) [ 940.460727] pstate: 80000005 (Nzcv daif -PAN -UAO) [ 940.465480] pc : ip6_pol_route+0x1f4/0x738 [ 940.469537] lr : ip6_pol_route+0x1d8/0x738 [ 940.473590] sp : ffff000013fb3010 [ 940.476870] x29: ffff000013fb3010 x28: ffff000011be3000 [ 940.482132] x27: ffff80096f228a00 x26: ffff80096f364000 [ 940.487393] x25: ffff000010da3500 x24: 000000000000004e [ 940.492654] x23: ffff00001198e000 x22: ffff000013fb3240 [ 940.497915] x21: ffff00001195f000 x20: ffff80096bf95a00 [ 940.503175] x19: ffff000013fb3268 x18: 0000000000000000 [ 940.508435] x17: 0000000000000001 x16: 0000000000000000 [ 940.513696] x15: 0000000000000000 x14: 1312111000000000 [ 940.518956] x13: 0002ccaf00000000 x12: 5cf61adb01002c22 [ 940.524216] x11: 0000000000000002 x10: 0000000000000003 [ 940.529477] x9 : 0000000000000000 x8 : ffff00001195f848 [ 940.534738] x7 : ffff000013fb2ffb x6 : 0000000000000000 [ 940.539998] x5 : ffff80096f364000 x4 : 0000000000000001 [ 940.545258] x3 : 0000000000000004 x2 : 000080096d61a000 [ 940.550519] x1 : ffff80092e761700 x0 : 0000000000000000 [ 940.555780] Call trace: [ 940.558202] ip6_pol_route+0x1f4/0x738 [ 940.561914] ip6_pol_route_input+0x4c/0x60 [ 940.565971] fib6_rule_lookup+0xc8/0x170 [ 940.569855] ip6_route_input_lookup+0x70/0x88 [ 940.574169] ip6_route_input+0xe4/0x238 [ 940.577969] ip6_rcv_finish_core.isra.0+0x48/0x168 [ 940.582713] ip6_rcv_finish+0x68/0xc0 [ 940.586339] ipv6_rcv+0x70/0x228 [ 940.589536] __netif_receive_skb_one_core+0x68/0x90 [ 940.594366] __netif_receive_skb+0x28/0x80 [ 940.598422] process_backlog+0xe4/0x240 [ 940.602220] net_rx_action+0x120/0x4a8 [ 940.605933] __do_softirq+0x11c/0x580 [ 940.609559] do_softirq.part.3+0x94/0x98 [ 940.613442] __local_bh_enable_ip+0x12c/0x138 [ 940.617756] ip6_finish_output2+0x220/0xb98 [ 940.621898] __ip6_finish_output+0x1e8/0x2a8 [ 940.626126] ip6_finish_output+0x38/0xd0 [ 940.630010] ip6_output+0x80/0x350 [ 940.633378] bpf_lwt_xmit_reroute+0x2a8/0x4b0 [ 940.637692] bpf_xmit+0x120/0x178 [ 940.640972] lwtunnel_xmit+0xd0/0x210 [ 940.644600] ip_finish_output2+0x488/0xa80 [ 940.648654] __ip_finish_output+0x204/0x318 [ 940.652795] ip_finish_output+0x38/0xd0 [ 940.656592] ip_output+0x108/0x2f8 [ 940.659959] ip_local_out+0x5c/0x98 [ 940.663411] ip_send_skb+0x2c/0xb8 [ 940.666778] ip_push_pending_frames+0x44/0x50 [ 940.671093] raw_sendmsg+0xa7c/0xe20 [ 940.674633] inet_sendmsg+0x4c/0x238 [ 940.678173] sock_sendmsg+0x34/0x50 [ 940.681627] __sys_sendto+0x120/0x150 [ 940.685252] __arm64_sys_sendto+0x30/0x40 [ 940.689223] el0_svc_common.constprop.0+0x7c/0x180 [ 940.693967] el0_svc_handler+0x34/0x90 [ 940.697678] el0_svc+0x8/0xc [ 940.700531] Code: b9001020 f9403fa0 d538d082 f9402400 (f8626813) [ 940.706579] ---[ end trace 8a07ef53f23b6533 ]--- [ 940.711150] Kernel panic - not syncing: Fatal exception in interrupt [ 940.717449] SMP: stopping secondary CPUs [ 940.721536] Kernel Offset: disabled [ 940.724989] CPU features: 0x0002,24006004 [ 940.728957] Memory Limit: none [ 940.731998] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- [1] https://lkft.validation.linaro.org/scheduler/job/760547#L23242 Best regards Naresh Kamboju

6 years

1
0
0 0

BUG: kernel NULL pointer dereference, address: 00000000: memcpy+0x1d/0x30

by Naresh Kamboju

While running selftest bpf: test_maps the kernel BUG found on i386 kernel running on x86_64 machine Linux version 5.2.0-rc3-next-20190604 Full test log can be found in the below link [1] # helper_fill_hashmap(261)FAILfailed to create hashmap err Cannot allocate memory, flags 0x0 to: create_hashmap # # Fork 1024 tasks to 'test_update_delete' 1024: tasks_to # # Fork 1024 tasks to 'test_update_delete' 1024: tasks_to # # Fork 100 tasks to 'test_hashmap' 100: tasks_to # # Fork 100 tasks to 'test_hashmap_percpu' 100: tasks_to # # Fork 100 tasks to 'test_hashmap_sizes' [ 93.249753] BUG: kernel NULL pointer dereference, address: 00000000 [ 93.256586] #PF: supervisor read access in kernel mode [ 93.261714] #PF: error_code(0x0000) - not-present page [ 93.266846] *pde = 00000000 [ 93.269722] Oops: 0000 [#1] SMP [ 93.272859] CPU: 0 PID: 4354 Comm: test_sockmap Not tainted 5.2.0-rc3-next-20190604 #1 [ 93.280763] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 93.288235] EIP: memcpy+0x1d/0x30 [ 93.291547] Code: 59 58 eb 85 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c7 53 89 d6 89 cb c1 e9 02 f3 a5 89 d9 83 e1 03 74 02 <f3> a4 5b 5e 5f 5d c3 8d b6 00 00 00 00 8d bf 00 00 00 00 3e 8d 74 [ 93.310291] EAX: e2ca9000 EBX: 00000001 ECX: 00000001 EDX: 00000000 [ 93.316548] ESI: 00000000 EDI: e2ca9000 EBP: e3d8799c ESP: e3d87990 [ 93.322806] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010202 [ 93.329582] CR0: 80050033 CR2: 00000000 CR3: 20d21000 CR4: 003406d0 [ 93.335841] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 93.342097] DR6: fffe0ff0 DR7: 00000400 [ 93.345929] Call Trace: [ 93.348391] bpf_msg_push_data+0x635/0x660 [ 93.352492] ___bpf_prog_run+0xa0d/0x15a0 [ 93.356529] ? __lock_acquire+0x1fe/0x1360 [ 93.360626] __bpf_prog_run32+0x4b/0x70 [ 93.364461] ? sk_psock_msg_verdict+0x5/0x290 [ 93.368842] sk_psock_msg_verdict+0xad/0x290 [ 93.373105] ? sk_psock_msg_verdict+0xad/0x290 [ 93.377543] ? lockdep_hardirqs_on+0xec/0x1a0 [ 93.381896] ? __local_bh_enable_ip+0x78/0xf0 [ 93.386255] tcp_bpf_send_verdict+0x29c/0x3b0 [ 93.390615] tcp_bpf_sendpage+0x233/0x3d0 [ 93.394629] ? __lock_acquire+0x1fe/0x1360 [ 93.398754] ? __lock_acquire+0x1fe/0x1360 [ 93.402850] ? lock_release+0x8b/0x280 [ 93.406593] ? find_get_entry+0x136/0x300 [ 93.410599] ? touch_atime+0x34/0xd0 [ 93.414177] ? copy_page_to_iter+0x245/0x400 [ 93.418441] ? lockdep_hardirqs_on+0xec/0x1a0 [ 93.422793] ? tcp_bpf_send_verdict+0x3b0/0x3b0 [ 93.427325] inet_sendpage+0x53/0x1f0 [ 93.430981] ? inet_recvmsg+0x1e0/0x1e0 [ 93.434812] ? kernel_sendpage+0x40/0x40 [ 93.438728] kernel_sendpage+0x1e/0x40 [ 93.442474] sock_sendpage+0x24/0x30 [ 93.446054] pipe_to_sendpage+0x59/0xa0 [ 93.449894] ? direct_splice_actor+0x40/0x40 [ 93.454166] __splice_from_pipe+0xde/0x1c0 [ 93.458264] ? direct_splice_actor+0x40/0x40 [ 93.462535] ? direct_splice_actor+0x40/0x40 [ 93.466801] splice_from_pipe+0x59/0x80 [ 93.470641] ? splice_from_pipe+0x80/0x80 [ 93.474652] ? generic_splice_sendpage+0x20/0x20 [ 93.479262] generic_splice_sendpage+0x18/0x20 [ 93.483701] ? direct_splice_actor+0x40/0x40 [ 93.487971] direct_splice_actor+0x2d/0x40 [ 93.492065] splice_direct_to_actor+0x127/0x240 [ 93.496597] ? generic_pipe_buf_nosteal+0x10/0x10 [ 93.501302] do_splice_direct+0x7e/0xc0 [ 93.505134] do_sendfile+0x20d/0x3e0 [ 93.508739] sys_sendfile+0xac/0xd0 [ 93.512232] ? lock_release+0x8b/0x280 [ 93.515984] do_fast_syscall_32+0x8e/0x320 [ 93.520084] entry_SYSENTER_32+0x70/0xc8 [ 93.524009] EIP: 0xb7f9d7a1 [ 93.526807] Code: 8b 98 60 cd ff ff 85 d2 89 c8 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 1c 24 c3 8b 3c 24 c3 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76 [ 93.545542] EAX: ffffffda EBX: 0000001a ECX: 0000001e EDX: 00000000 [ 93.551799] ESI: 00000001 EDI: 0000001a EBP: 00000001 ESP: bfa67a64 [ 93.558057] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000206 [ 93.564836] Modules linked in: tun algif_hash af_alg x86_pkg_temp_thermal fuse [ 93.572082] CR2: 0000000000000000 [ 93.575411] ---[ end trace c106584042e12a8d ]--- [ 93.580046] EIP: memcpy+0x1d/0x30 [ 93.583355] Code: 59 58 eb 85 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c7 53 89 d6 89 cb c1 e9 02 f3 a5 89 d9 83 e1 03 74 02 <f3> a4 5b 5e 5f 5d c3 8d b6 00 00 00 00 8d bf 00 00 00 00 3e 8d 74 [ 93.602092] EAX: e2ca9000 EBX: 00000001 ECX: 00000001 EDX: 00000000 [ 93.608349] ESI: 00000000 EDI: e2ca9000 EBP: e3d8799c ESP: d967e49c [ 93.614607] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010202 [ 93.621408] CR0: 80050033 CR2: 00000000 CR3: 20d21000 CR4: 003406d0 [ 93.627694] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 93.633951] DR6: fffe0ff0 DR7: 00000400 [ 93.637783] BUG: sleeping function called from invalid context at /usr/src/kernel/include/linux/percpu-rwsem.h:34 [ 93.648035] in_atomic(): 1, irqs_disabled(): 1, pid: 4354, name: test_sockmap [ 93.655156] INFO: lockdep is turned off. [ 93.659074] irq event stamp: 1538 [ 93.662408] hardirqs last enabled at (1537): [<d902cadf>] _raw_spin_unlock_irqrestore+0x2f/0x50 [ 93.671200] hardirqs last disabled at (1538): [<d840182c>] trace_hardirqs_off_thunk+0xc/0x10 [ 93.679624] softirqs last enabled at (1532): [<d8d1b849>] lock_sock_nested+0x39/0x90 [ 93.687465] softirqs last disabled at (1530): [<d8d1b83f>] lock_sock_nested+0x2f/0x90 [ 93.695284] CPU: 0 PID: 4354 Comm: test_sockmap Tainted: G D 5.2.0-rc3-next-20190604 #1 [ 93.704573] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 93.712043] Call Trace: [ 93.714490] dump_stack+0x66/0x96 [ 93.717800] ___might_sleep+0x13e/0x230 [ 93.721629] __might_sleep+0x33/0x80 [ 93.725200] exit_signals+0x2a/0x200 [ 93.728771] do_exit+0x8e/0xbb0 [ 93.731910] ? do_fast_syscall_32+0x8e/0x320 [ 93.736182] rewind_stack_do_exit+0x11/0x13 [ 93.740356] EIP: 0xb7f9d7a1 [ 93.743150] Code: 8b 98 60 cd ff ff 85 d2 89 c8 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 1c 24 c3 8b 3c 24 c3 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76 [ 93.761887] EAX: ffffffda EBX: 0000001a ECX: 0000001e EDX: 00000000 [ 93.768142] ESI: 00000001 EDI: 0000001a EBP: 00000001 ESP: bfa67a64 [ 93.774406] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000206 100: tasks_to [ 93.781266] note: test_sockmap[4354] exited with preempt_count 2 # # Fork 100 tasks to 'test_hashmap_walk' 100: tasks_to # # helper_fill_hashmap(261)FAILfailed to create hashmap err Cannot allocate memory, flags 0x0 [1] https://lkft.validation.linaro.org/scheduler/job/760391#L13640 Best regards Naresh Kamboju

6 years

1
0
0 0

bpf: test_btf : kernel Oops: 207 : PC is at memcpy+0xc0/0x330

by Naresh Kamboju

while running kernel selftest bpf: test_btf the following kernel oops detected on beaglebone x15 board. Linux version 5.2.0-rc3-next-20190604 Full test log link can be found below [1] bpf: test_btf_ # # BTF GET_INFO test[3] (Large bpf_btf_info) OK GET_INFO: test[3]_(Large # # BTF GET_INFO test[4] (BTF ID) OK GET_INFO: test[4]_(BTF # [ 341.144885] 8<--- cut here --- [ 341.148164] Unable to handle kernel NULL pointer dereference at virtual address 00000000 [ 341.156443] pgd = b0902156 [ 341.159294] [00000000] *pgd=9655e003, *pmd=ff918003 [ 341.164229] Internal error: Oops: 207 [#1] SMP ARM [ 341.169052] Modules linked in: tun sha1_generic sha1_arm_neon sha1_arm algif_hash af_alg snd_soc_simple_card snd_soc_simple_card_utils snd_soc_core ac97_bus snd_pcm_dmaengine snd_pcm snd_timer snd soundcore fuse [ 341.187962] CPU: 0 PID: 6773 Comm: test_sockmap Not tainted 5.2.0-rc3-next-20190604 #1 [ 341.195923] Hardware name: Generic DRA74X (Flattened Device Tree) [ 341.202058] PC is at memcpy+0xc0/0x330 [ 341.205836] LR is at bpf_msg_push_data+0x70c/0x728 [ 341.210654] pc : [<c12da820>] lr : [<c10ea4a4>] psr: 800b0013 [ 341.216957] sp : e99ad6cc ip : 00000002 fp : e99ad83c [ 341.222212] r10: d1bdc000 r9 : 00000001 r8 : 00000000 [ 341.227467] r7 : cd1de000 r6 : 00000000 r5 : d1bdc000 r4 : 00000000 [ 341.234032] r3 : 00000000 r2 : 80000000 r1 : 00000000 r0 : cd1de000 [ 341.240597] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 341.247771] Control: 30c5387d Table: 91b19880 DAC: fffffffd [ 341.253553] Process test_sockmap (pid: 6773, stack limit = 0x3ad4028c) [ 341.260118] Stack: (0xe99ad6cc to 0xe99ae000) [ 341.264502] d6c0: cd1de000 00000000 c10ea4a4 00000000 00000000 [ 341.272725] d6e0: 00000000 00000000 00000000 00000000 00000000 00000000 ea2759a0 00000001 [ 341.280948] d700: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.289171] d720: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.297394] d740: 00000000 00000000 00000000 00000000 00000000 00000000 e99ad78c d03f0580 [ 341.305615] d760: 00000004 d03f0000 00000007 000003a9 00000000 00000000 00000000 00000000 [ 341.313836] d780: 00000000 00000000 00000000 00000000 d03f0000 c0581f6c 00000060 c1e09fd0 [ 341.322060] d7a0: e99ad85c e99ad7b0 c04c1d1c 00000000 c06c3638 c1dc19b8 e99ad7ec d03f0540 [ 341.330283] d7c0: 00000002 d03f0000 00000007 000003a9 00000001 d03f0560 d03f0000 e3444ce4 [ 341.338506] d7e0: 00000060 c1e09fd0 e99ad8a4 e99ad7f8 cbc66e00 e99ad8a8 c1419868 c059b69c [ 341.346730] d800: 00000000 00000000 e99ad824 e99ad818 c04e3b7c f006b240 e99ad8b8 c1419868 [ 341.354954] d820: c10e9d98 00000000 00000000 c0581ddc e99ad894 e99ad840 c0581f6c c10e9da4 [ 341.363175] d840: 00000000 00000000 00000000 00000000 00000000 00000000 f5388145 290412b8 [ 341.371399] d860: c2432908 00000000 f08d7937 c1e08488 f006b028 00000011 c11cd828 f006b000 [ 341.379620] d880: e99ad9e4 c1fc9e37 e99ad934 e99ad898 c0584910 c0581e48 00000000 00000000 [ 341.387841] d8a0: 00000005 00000004 00000003 00000002 00000001 00000000 cbc66ee8 00000000 [ 341.396063] d8c0: d1bdc000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.404286] d8e0: 00000000 00000000 d1bdc000 00000000 cbc66ee0 00000000 00000007 00000006 [ 341.412509] d900: 00000010 c1fc9e37 e99ad8b8 00000000 cf380840 c10fdef4 c11cd828 9fdbe7c7 [ 341.420732] d920: d1bdc000 d1bdc000 e99ad984 e99ad938 c10fdf18 c05848d0 00000000 00000000 [ 341.428954] d940: c10fde14 c0459978 e99ad97c e99ad958 c056165c e7bdd400 000001ff d1bdc000 [ 341.437178] d960: e7bdd400 00000011 cf380840 00000000 e99ad9e4 c1fc9e37 e99ad9cc e99ad988 [ 341.445407] d980: c11cd828 c10fde20 c11cda3c 00000000 00000000 e99ad9a0 00000000 00000000 [ 341.453631] d9a0: 00000001 e7bdd400 cf380840 eb6d1030 c1e08488 00000000 00000003 c1fc9e37 [ 341.461855] d9c0: e99adcac e99ad9d0 c11cdb60 c11cd518 00000000 00000000 c11cd90c e8577024 [ 341.470078] d9e0: 00000020 00000001 00000000 00000000 00000001 00000001 00000000 00000001 [ 341.478300] da00: 00000000 00000000 00000000 00000000 eb6d1030 00000000 00000001 00000000 [ 341.486522] da20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.494742] da40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.502965] da60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.511184] da80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 341.519406] daa0: 00000000 00000000 00000000 00000000 00000000 00000087 00000001 d03f0500 [ 341.527628] dac0: d03f0000 c1e47f04 00000000 c1e09fd0 e99adb8c e99adae0 c04c1d1c c04c10d0 [ 341.535850] dae0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000078 [ 341.544074] db00: d03f04f0 00000087 00000000 00000000 c2432908 c2638640 00000087 d03f0500 [ 341.552296] db20: c1e08488 c2418b30 406293ec 295bca2f 00000000 00000000 00000000 00000000 [ 341.560517] db40: 00000000 00000000 d03f04f0 00000078 e99adb84 e99adb60 c040e488 00000087 [ 341.568741] db60: 00000001 d03f0500 d03f0000 c1e47f04 00000000 c1e09fd0 e99adc34 e99adb88 [ 341.576961] db80: c04c1d1c c04c10d0 ffffe000 c1fcaf30 c069cddc c1e47f04 e99adbbc e99adba8 [ 341.585182] dba0: c04c19e0 c04c1864 d03f04f0 00000087 00000000 00000000 c2432908 c2638640 [ 341.593405] dbc0: 00000087 d03f0500 c1e08488 c2418b30 406293ec 295bca2f e99adc24 e99adbe8 [ 341.601628] dbe0: c04fe13c c05615d4 00000001 00000000 c069cddc e99adc54 e99adc2c e99adc08 [ 341.609851] dc00: c040e488 c040ce94 c1e08488 00000000 ffffe000 c1fcaf30 c069cddc c1e47f04 [ 341.618073] dc20: e99adc64 e99adc30 d03f0000 c04fe13c ffffe000 c1fcaf30 c069cddc c1e47f04 [ 341.626294] dc40: e99adc64 e99adc50 c04c19e0 c04c1864 c1dc1000 c04fe13c e99adc8c e99adc68 [ 341.634517] dc60: c056165c c04c18d8 c1e47e40 400b0013 00000001 e99adce0 c069cddc 9fdbe7c7 [ 341.642738] dc80: e99adccc cf380840 c11cd90c e776d400 eb6d1030 00000010 00000001 c1938660 [ 341.650959] dca0: e99adcf4 e99adcb0 c119c98c c11cd918 00000000 e3444a98 e99add14 e99adcd0 [ 341.659180] dcc0: c069ce08 c069cd10 5cf61726 c119c908 c10933a0 00000000 00000000 c06b7624 [ 341.667403] dce0: 00000001 c1938660 e99add14 e99adcf8 c1093390 c119c914 00000000 e3444a98 [ 341.675624] dd00: e7cd5110 c1e08488 e99add2c e99add18 c10933d8 c1093368 00000000 0000026d [ 341.683846] dd20: e99add64 e99add30 c06b7694 c10933ac e99add38 00000000 00000000 00000000 [ 341.692067] dd40: c1e08488 9fdbe7c7 e7bdc800 e99adda0 d3b2fcc0 00000018 e99add9c e99add68 [ 341.700289] dd60: c06b8a04 c06b7630 e99ade60 00000000 00000000 c1e08488 d3b2fcc0 c06b7624 [ 341.708510] dd80: e68598c0 00000000 00000001 e99adf20 e99addfc e99adda0 c06b9214 c06b897c [ 341.716731] dda0: 00000001 00000001 00000000 e68598c0 00000000 00000000 00000000 00000000 [ 341.724953] ddc0: 00000000 00000000 00000000 9fdbe7c7 00000000 c06b9240 e99adea0 00000001 [ 341.733176] dde0: 00000000 00000010 00000000 00000001 e99ade14 e99ade00 c06b9270 c06b91a4 [ 341.741398] de00: 00000000 c06b7624 e99ade34 e99ade18 c06b761c c06b924c 00000000 e99adea0 [ 341.749621] de20: 00000001 d3b2fcc0 e99ade9c e99ade38 c06b7ff0 c06b75dc 00000000 c067a2dc [ 341.757842] de40: 00000001 c1e08488 00000000 c06b75d0 00000000 e9949a00 00000010 00000000 [ 341.766065] de60: 00000011 00000000 e99adf1c 9fdbe7c7 00020000 c1e08488 e99adf18 00000010 [ 341.774285] de80: 00000000 e9949a00 e99adf20 e68598c0 e99adef4 e99adea0 c06b8238 c06b7edc [ 341.782507] dea0: 00000001 00000001 00000000 e68598c0 00000010 00000000 e99adf20 00000000 [ 341.790729] dec0: 00000000 00000000 d03f0000 9fdbe7c7 c1e08488 c1e08488 e9949a00 fffff000 [ 341.798952] dee0: 00000fff 00000001 e99adf5c e99adef8 c067ac74 c06b8198 00000001 00000000 [ 341.807174] df00: e776d420 00000000 00000000 00000000 e68598c0 e9949a00 00000010 00000000 [ 341.815397] df20: 00000000 00000000 c1e08488 9fdbe7c7 00000001 c1e08488 00000001 00000000 [ 341.823618] df40: 00000000 c04011c4 0000001e 00000001 e99adfa4 e99adf60 c067c2a4 c067aaa4 [ 341.831841] df60: fffff000 00000fff e99adfac e99adf78 c1dc1000 9fdbe7c7 e99adfac bef7ca44 [ 341.840063] df80: 00000001 00000200 000000bb c04011c4 e99ac000 000000bb 00000000 e99adfa8 [ 341.848285] dfa0: c0401000 c067c1b8 bef7ca44 00000001 0000001a 0000001e 00000000 00000001 [ 341.856508] dfc0: bef7ca44 00000001 00000200 000000bb 00000001 0000001e 0000001a 00000010 [ 341.864729] dfe0: 00045034 bef7c884 000137c0 b6e76d7c 200b0010 0000001a 00000000 00000000 [ 341.872948] Backtrace: [ 341.875425] [<c10e9d98>] (bpf_msg_push_data) from [<c0581f6c>] (___bpf_prog_run+0x130/0x1bbc) [ 341.883999] r10:c0581ddc r9:00000000 r8:00000000 r7:c10e9d98 r6:c1419868 r5:e99ad8b8 [ 341.891869] r4:f006b240 [ 341.894426] [<c0581e3c>] (___bpf_prog_run) from [<c0584910>] (__bpf_prog_run32+0x4c/0x68) [ 341.902649] r10:c1fc9e37 r9:e99ad9e4 r8:f006b000 r7:c11cd828 r6:00000011 r5:f006b028 [ 341.910520] r4:c1e08488 [ 341.913079] [<c05848c4>] (__bpf_prog_run32) from [<c10fdf18>] (sk_psock_msg_verdict+0x104/0x354) [ 341.921909] r4:d1bdc000 [ 341.924470] [<c10fde14>] (sk_psock_msg_verdict) from [<c11cd828>] (tcp_bpf_send_verdict+0x31c/0x400) [ 341.933654] r10:c1fc9e37 r9:e99ad9e4 r8:00000000 r7:cf380840 r6:00000011 r5:e7bdd400 [ 341.941524] r4:d1bdc000 [ 341.944083] [<c11cd50c>] (tcp_bpf_send_verdict) from [<c11cdb60>] (tcp_bpf_sendpage+0x254/0x3c4) [ 341.952914] r10:c1fc9e37 r9:00000003 r8:00000000 r7:c1e08488 r6:eb6d1030 r5:cf380840 [ 341.960784] r4:e7bdd400 [ 341.963343] [<c11cd90c>] (tcp_bpf_sendpage) from [<c119c98c>] (inet_sendpage+0x84/0x294) [ 341.971480] r10:c1938660 r9:00000001 r8:00000010 r7:eb6d1030 r6:e776d400 r5:c11cd90c [ 341.979350] r4:cf380840 [ 341.981906] [<c119c908>] (inet_sendpage) from [<c1093390>] (kernel_sendpage+0x34/0x44) [ 341.989868] r10:c1938660 r9:00000001 r8:c06b7624 r7:00000000 r6:00000000 r5:c10933a0 [ 341.997738] r4:c119c908 [ 342.000290] [<c109335c>] (kernel_sendpage) from [<c10933d8>] (sock_sendpage+0x38/0x40) [ 342.008248] r4:c1e08488 [ 342.010805] [<c10933a0>] (sock_sendpage) from [<c06b7694>] (pipe_to_sendpage+0x70/0xa4) [ 342.018856] [<c06b7624>] (pipe_to_sendpage) from [<c06b8a04>] (__splice_from_pipe+0x94/0x1cc) [ 342.027424] r7:00000018 r6:d3b2fcc0 r5:e99adda0 r4:e7bdc800 [ 342.033122] [<c06b8970>] (__splice_from_pipe) from [<c06b9214>] (splice_from_pipe+0x7c/0xa8) [ 342.041605] r10:e99adf20 r9:00000001 r8:00000000 r7:e68598c0 r6:c06b7624 r5:d3b2fcc0 [ 342.049475] r4:c1e08488 [ 342.052032] [<c06b9198>] (splice_from_pipe) from [<c06b9270>] (generic_splice_sendpage+0x30/0x38) [ 342.060953] r10:00000001 r9:00000000 r8:00000010 r7:00000000 r6:00000001 r5:e99adea0 [ 342.068822] r4:c06b9240 [ 342.071377] [<c06b9240>] (generic_splice_sendpage) from [<c06b761c>] (direct_splice_actor+0x4c/0x54) [ 342.080562] [<c06b75d0>] (direct_splice_actor) from [<c06b7ff0>] (splice_direct_to_actor+0x120/0x2bc) [ 342.089827] r4:d3b2fcc0 [ 342.092383] [<c06b7ed0>] (splice_direct_to_actor) from [<c06b8238>] (do_splice_direct+0xac/0xe4) [ 342.101218] r10:e68598c0 r9:e99adf20 r8:e9949a00 r7:00000000 r6:00000010 r5:e99adf18 [ 342.109088] r4:c1e08488 [ 342.111645] [<c06b818c>] (do_splice_direct) from [<c067ac74>] (do_sendfile+0x1dc/0x420) [ 342.119693] r8:00000001 r7:00000fff r6:fffff000 r5:e9949a00 r4:c1e08488 [ 342.126436] [<c067aa98>] (do_sendfile) from [<c067c2a4>] (sys_sendfile+0xf8/0x11c) [ 342.134048] r10:00000001 r9:0000001e r8:c04011c4 r7:00000000 r6:00000000 r5:00000001 [ 342.141917] r4:c1e08488 [ 342.144475] [<c067c1ac>] (sys_sendfile) from [<c0401000>] (ret_fast_syscall+0x0/0x28) [ 342.152346] Exception stack(0xe99adfa8 to 0xe99adff0) [ 342.157428] dfa0: bef7ca44 00000001 0000001a 0000001e 00000000 00000001 [ 342.165650] dfc0: bef7ca44 00000001 00000200 000000bb 00000001 0000001e 0000001a 00000010 [ 342.173870] dfe0: 00045034 bef7c884 000137c0 b6e76d7c [ 342.178951] r10:000000bb r9:e99ac000 r8:c04011c4 r7:000000bb r6:00000200 r5:00000001 [ 342.186822] r4:bef7ca44 [ 342.189377] Code: e4808004 e480e004 e8bd01e0 e1b02f82 (14d13001) [ 342.195755] ---[ end trace d2353d98cf59813b ]--- [1] https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190604/testru…

6 years

1
0
0 0

[PATCH v2 18/22] docs: move protection-keys.rst to the core-api book

by Mauro Carvalho Chehab

This document is used by multiple architectures: $ echo $(git grep -l pkey_mprotect arch|cut -d'/' -f 2|sort|uniq) alpha arm arm64 ia64 m68k microblaze mips parisc powerpc s390 sh sparc x86 xtensa So, let's move it to the core book and adjust the links to it accordingly. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung(a)kernel.org> --- Documentation/core-api/index.rst | 1 + Documentation/{x86 => core-api}/protection-keys.rst | 0 Documentation/x86/index.rst | 1 - arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 2 +- tools/testing/selftests/x86/protection_keys.c | 2 +- 6 files changed, 4 insertions(+), 4 deletions(-) rename Documentation/{x86 => core-api}/protection-keys.rst (100%) diff --git a/Documentation/core-api/index.rst b/Documentation/core-api/index.rst index ee1bb8983a88..2466a4c51031 100644 --- a/Documentation/core-api/index.rst +++ b/Documentation/core-api/index.rst @@ -34,6 +34,7 @@ Core utilities timekeeping boot-time-mm memory-hotplug + protection-keys Interfaces for kernel debugging diff --git a/Documentation/x86/protection-keys.rst b/Documentation/core-api/protection-keys.rst similarity index 100% rename from Documentation/x86/protection-keys.rst rename to Documentation/core-api/protection-keys.rst diff --git a/Documentation/x86/index.rst b/Documentation/x86/index.rst index ae36fc5fc649..f2de1b2d3ac7 100644 --- a/Documentation/x86/index.rst +++ b/Documentation/x86/index.rst @@ -19,7 +19,6 @@ x86-specific Documentation tlb mtrr pat - protection-keys intel_mpx amd-memory-encryption pti diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig index 1120ff8ac715..e437aa3e78b4 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/core-api/protection-keys.rst If unsure, say y. diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 23de3b9da480..61244bdb886f 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/core-api/protection-keys.rst If unsure, say y. diff --git a/tools/testing/selftests/x86/protection_keys.c b/tools/testing/selftests/x86/protection_keys.c index 5d546dcdbc80..480995bceefa 100644 --- a/tools/testing/selftests/x86/protection_keys.c +++ b/tools/testing/selftests/x86/protection_keys.c @@ -1,6 +1,6 @@ // SPDX-License-Identifier: GPL-2.0 /* - * Tests x86 Memory Protection Keys (see Documentation/x86/protection-keys.txt) + * Tests x86 Memory Protection Keys (see Documentation/core-api/protection-keys.rst) * * There are examples in here of: * * how to set protection keys on memory -- 2.21.0

6 years

1
0
0 0

[PATCH v15 00/17] arm64: untag user pointers passed to the kernel

by Andrey Konovalov

=== Overview arm64 has a feature called Top Byte Ignore, which allows to embed pointer tags into the top byte of each pointer. Userspace programs (such as HWASan, a memory debugging tool [1]) might use this feature and pass tagged user pointers to the kernel through syscalls or other interfaces. Right now the kernel is already able to handle user faults with tagged pointers, due to these patches: 1. 81cddd65 ("arm64: traps: fix userspace cache maintenance emulation on a tagged pointer") 2. 7dcd9dd8 ("arm64: hw_breakpoint: fix watchpoint matching for tagged pointers") 3. 276e9327 ("arm64: entry: improve data abort handling of tagged pointers") This patchset extends tagged pointer support to syscall arguments. As per the proposed ABI change [3], tagged pointers are only allowed to be passed to syscalls when they point to memory ranges obtained by anonymous mmap() or sbrk() (see the patchset [3] for more details). For non-memory syscalls this is done by untaging user pointers when the kernel performs pointer checking to find out whether the pointer comes from userspace (most notably in access_ok). The untagging is done only when the pointer is being checked, the tag is preserved as the pointer makes its way through the kernel and stays tagged when the kernel dereferences the pointer when perfoming user memory accesses. Memory syscalls (mmap, mprotect, etc.) don't do user memory accesses but rather deal with memory ranges, and untagged pointers are better suited to describe memory ranges internally. Thus for memory syscalls we untag pointers completely when they enter the kernel. === Other approaches One of the alternative approaches to untagging that was considered is to completely strip the pointer tag as the pointer enters the kernel with some kind of a syscall wrapper, but that won't work with the countless number of different ioctl calls. With this approach we would need a custom wrapper for each ioctl variation, which doesn't seem practical. An alternative approach to untagging pointers in memory syscalls prologues is to inspead allow tagged pointers to be passed to find_vma() (and other vma related functions) and untag them there. Unfortunately, a lot of find_vma() callers then compare or subtract the returned vma start and end fields against the pointer that was being searched. Thus this approach would still require changing all find_vma() callers. === Testing The following testing approaches has been taken to find potential issues with user pointer untagging: 1. Static testing (with sparse [2] and separately with a custom static analyzer based on Clang) to track casts of __user pointers to integer types to find places where untagging needs to be done. 2. Static testing with grep to find parts of the kernel that call find_vma() (and other similar functions) or directly compare against vm_start/vm_end fields of vma. 3. Static testing with grep to find parts of the kernel that compare user pointers with TASK_SIZE or other similar consts and macros. 4. Dynamic testing: adding BUG_ON(has_tag(addr)) to find_vma() and running a modified syzkaller version that passes tagged pointers to the kernel. Based on the results of the testing the requried patches have been added to the patchset. === Notes This patchset is meant to be merged together with "arm64 relaxed ABI" [3]. This patchset is a prerequisite for ARM's memory tagging hardware feature support [4]. This patchset has been merged into the Pixel 2 & 3 kernel trees and is now being used to enable testing of Pixel phones with HWASan. Thanks! [1] http://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html [2] https://github.com/lucvoo/sparse-dev/commit/5f960cb10f56ec2017c128ef9d16060… [3] https://lkml.org/lkml/2019/3/18/819 [4] https://community.arm.com/processors/b/blog/posts/arm-a-profile-architectur… Changes in v15: - Removed unnecessary untagging from radeon_ttm_tt_set_userptr(). - Removed unnecessary untagging from amdgpu_ttm_tt_set_userptr(). - Moved untagging to validate_range() in userfaultfd code. - Moved untagging to ib_uverbs_(re)reg_mr() from mlx4_get_umem_mr(). - Rebased onto 5.1. Changes in v14: - Moved untagging for most memory syscalls to an arm64 specific implementation, instead of doing that in the common code. - Dropped "net, arm64: untag user pointers in tcp_zerocopy_receive", since the provided user pointers don't come from an anonymous map and thus are not covered by this ABI relaxation. - Dropped "kernel, arm64: untag user pointers in prctl_set_mm*". - Moved untagging from __check_mem_type() to tee_shm_register(). - Updated untagging for the amdgpu and radeon drivers to cover the MMU notifier, as suggested by Felix. - Since this ABI relaxation doesn't actually allow tagged instruction pointers, dropped the following patches: - Dropped "tracing, arm64: untag user pointers in seq_print_user_ip". - Dropped "uprobes, arm64: untag user pointers in find_active_uprobe". - Dropped "bpf, arm64: untag user pointers in stack_map_get_build_id_offset". - Rebased onto 5.1-rc7 (37624b58). Changes in v13: - Simplified untagging in tcp_zerocopy_receive(). - Looked at find_vma() callers in drivers/, which allowed to identify a few other places where untagging is needed. - Added patch "mm, arm64: untag user pointers in get_vaddr_frames". - Added patch "drm/amdgpu, arm64: untag user pointers in amdgpu_ttm_tt_get_user_pages". - Added patch "drm/radeon, arm64: untag user pointers in radeon_ttm_tt_pin_userptr". - Added patch "IB/mlx4, arm64: untag user pointers in mlx4_get_umem_mr". - Added patch "media/v4l2-core, arm64: untag user pointers in videobuf_dma_contig_user_get". - Added patch "tee/optee, arm64: untag user pointers in check_mem_type". - Added patch "vfio/type1, arm64: untag user pointers". Changes in v12: - Changed untagging in tcp_zerocopy_receive() to also untag zc->address. - Fixed untagging in prctl_set_mm* to only untag pointers for vma lookups and validity checks, but leave them as is for actual user space accesses. - Updated the link to the v2 of the "arm64 relaxed ABI" patchset [3]. - Dropped the documentation patch, as the "arm64 relaxed ABI" patchset [3] handles that. Changes in v11: - Added "uprobes, arm64: untag user pointers in find_active_uprobe" patch. - Added "bpf, arm64: untag user pointers in stack_map_get_build_id_offset" patch. - Fixed "tracing, arm64: untag user pointers in seq_print_user_ip" to correctly perform subtration with a tagged addr. - Moved untagged_addr() from SYSCALL_DEFINE3(mprotect) and SYSCALL_DEFINE4(pkey_mprotect) to do_mprotect_pkey(). - Moved untagged_addr() definition for other arches from include/linux/memory.h to include/linux/mm.h. - Changed untagging in strn*_user() to perform userspace accesses through tagged pointers. - Updated the documentation to mention that passing tagged pointers to memory syscalls is allowed. - Updated the test to use malloc'ed memory instead of stack memory. Changes in v10: - Added "mm, arm64: untag user pointers passed to memory syscalls" back. - New patch "fs, arm64: untag user pointers in fs/userfaultfd.c". - New patch "net, arm64: untag user pointers in tcp_zerocopy_receive". - New patch "kernel, arm64: untag user pointers in prctl_set_mm*". - New patch "tracing, arm64: untag user pointers in seq_print_user_ip". Changes in v9: - Rebased onto 4.20-rc6. - Used u64 instead of __u64 in type casts in the untagged_addr macro for arm64. - Added braces around (addr) in the untagged_addr macro for other arches. Changes in v8: - Rebased onto 65102238 (4.20-rc1). - Added a note to the cover letter on why syscall wrappers/shims that untag user pointers won't work. - Added a note to the cover letter that this patchset has been merged into the Pixel 2 kernel tree. - Documentation fixes, in particular added a list of syscalls that don't support tagged user pointers. Changes in v7: - Rebased onto 17b57b18 (4.19-rc6). - Dropped the "arm64: untag user address in __do_user_fault" patch, since the existing patches already handle user faults properly. - Dropped the "usb, arm64: untag user addresses in devio" patch, since the passed pointer must come from a vma and therefore be untagged. - Dropped the "arm64: annotate user pointers casts detected by sparse" patch (see the discussion to the replies of the v6 of this patchset). - Added more context to the cover letter. - Updated Documentation/arm64/tagged-pointers.txt. Changes in v6: - Added annotations for user pointer casts found by sparse. - Rebased onto 050cdc6c (4.19-rc1+). Changes in v5: - Added 3 new patches that add untagging to places found with static analysis. - Rebased onto 44c929e1 (4.18-rc8). Changes in v4: - Added a selftest for checking that passing tagged pointers to the kernel succeeds. - Rebased onto 81e97f013 (4.18-rc1+). Changes in v3: - Rebased onto e5c51f30 (4.17-rc6+). - Added linux-arch@ to the list of recipients. Changes in v2: - Rebased onto 2d618bdf (4.17-rc3+). - Removed excessive untagging in gup.c. - Removed untagging pointers returned from __uaccess_mask_ptr. Changes in v1: - Rebased onto 4.17-rc1. Changes in RFC v2: - Added "#ifndef untagged_addr..." fallback in linux/uaccess.h instead of defining it for each arch individually. - Updated Documentation/arm64/tagged-pointers.txt. - Dropped "mm, arm64: untag user addresses in memory syscalls". - Rebased onto 3eb2ce82 (4.16-rc7). Signed-off-by: Andrey Konovalov <andreyknvl(a)google.com> Andrey Konovalov (17): uaccess: add untagged_addr definition for other arches arm64: untag user pointers in access_ok and __uaccess_mask_ptr lib, arm64: untag user pointers in strn*_user mm: add ksys_ wrappers to memory syscalls arms64: untag user pointers passed to memory syscalls mm: untag user pointers in do_pages_move mm, arm64: untag user pointers in mm/gup.c mm, arm64: untag user pointers in get_vaddr_frames fs, arm64: untag user pointers in copy_mount_options fs, arm64: untag user pointers in fs/userfaultfd.c drm/amdgpu, arm64: untag user pointers drm/radeon, arm64: untag user pointers in radeon_gem_userptr_ioctl IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr() media/v4l2-core, arm64: untag user pointers in videobuf_dma_contig_user_get tee, arm64: untag user pointers in tee_shm_register vfio/type1, arm64: untag user pointers in vaddr_get_pfn selftests, arm64: add a selftest for passing tagged pointers to kernel arch/arm64/include/asm/uaccess.h | 10 +- arch/arm64/kernel/sys.c | 128 ++++++++++++++++- .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 2 + drivers/gpu/drm/radeon/radeon_gem.c | 2 + drivers/infiniband/core/uverbs_cmd.c | 4 + drivers/media/v4l2-core/videobuf-dma-contig.c | 9 +- drivers/tee/tee_shm.c | 1 + drivers/vfio/vfio_iommu_type1.c | 2 + fs/namespace.c | 2 +- fs/userfaultfd.c | 22 +-- include/linux/mm.h | 4 + include/linux/syscalls.h | 22 +++ ipc/shm.c | 7 +- lib/strncpy_from_user.c | 3 +- lib/strnlen_user.c | 3 +- mm/frame_vector.c | 2 + mm/gup.c | 4 + mm/madvise.c | 129 +++++++++--------- mm/mempolicy.c | 21 ++- mm/migrate.c | 1 + mm/mincore.c | 57 ++++---- mm/mlock.c | 20 ++- mm/mmap.c | 30 +++- mm/mprotect.c | 6 +- mm/mremap.c | 27 ++-- mm/msync.c | 35 +++-- tools/testing/selftests/arm64/.gitignore | 1 + tools/testing/selftests/arm64/Makefile | 11 ++ .../testing/selftests/arm64/run_tags_test.sh | 12 ++ tools/testing/selftests/arm64/tags_test.c | 21 +++ 31 files changed, 436 insertions(+), 164 deletions(-) create mode 100644 tools/testing/selftests/arm64/.gitignore create mode 100644 tools/testing/selftests/arm64/Makefile create mode 100755 tools/testing/selftests/arm64/run_tags_test.sh create mode 100644 tools/testing/selftests/arm64/tags_test.c -- 2.21.0.1020.gf2820cf01a-goog

6 years, 1 month

13
98
0 0

Re: [PATCH 22/22] docs: fix broken documentation links

by Michael S. Tsirkin

On Thu, May 30, 2019 at 10:17:32PM +0200, Federico Vaga wrote: > On Thursday, May 30, 2019 1:23:53 AM CEST Mauro Carvalho Chehab wrote: > > Mostly due to x86 and acpi conversion, several documentation > > links are still pointing to the old file. Fix them. > > For the Italian documentation I just send I patch to fix them in a dedicated > patch Acked-by: Michael S. Tsirkin <mst(a)redhat.com> for the vhost change. > > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung(a)kernel.org> > > --- > > Documentation/acpi/dsd/leds.txt | 2 +- > > Documentation/admin-guide/kernel-parameters.rst | 6 +++--- > > Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- > > Documentation/admin-guide/ras.rst | 2 +- > > .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- > > .../bindings/pci/amlogic,meson-pcie.txt | 2 +- > > .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- > > Documentation/devicetree/booting-without-of.txt | 2 +- > > Documentation/driver-api/gpio/board.rst | 2 +- > > Documentation/driver-api/gpio/consumer.rst | 2 +- > > .../firmware-guide/acpi/enumeration.rst | 2 +- > > .../firmware-guide/acpi/method-tracing.rst | 2 +- > > Documentation/i2c/instantiating-devices | 2 +- > > Documentation/sysctl/kernel.txt | 4 ++-- > > .../translations/it_IT/process/howto.rst | 2 +- > > .../it_IT/process/stable-kernel-rules.rst | 4 ++-- > > .../translations/zh_CN/process/4.Coding.rst | 2 +- > > Documentation/x86/x86_64/5level-paging.rst | 2 +- > > Documentation/x86/x86_64/boot-options.rst | 4 ++-- > > .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- > > MAINTAINERS | 6 +++--- > > arch/arm/Kconfig | 2 +- > > arch/arm64/kernel/kexec_image.c | 2 +- > > arch/powerpc/Kconfig | 2 +- > > arch/x86/Kconfig | 16 ++++++++-------- > > arch/x86/Kconfig.debug | 2 +- > > arch/x86/boot/header.S | 2 +- > > arch/x86/entry/entry_64.S | 2 +- > > arch/x86/include/asm/bootparam_utils.h | 2 +- > > arch/x86/include/asm/page_64_types.h | 2 +- > > arch/x86/include/asm/pgtable_64_types.h | 2 +- > > arch/x86/kernel/cpu/microcode/amd.c | 2 +- > > arch/x86/kernel/kexec-bzimage64.c | 2 +- > > arch/x86/kernel/pci-dma.c | 2 +- > > arch/x86/mm/tlb.c | 2 +- > > arch/x86/platform/pvh/enlighten.c | 2 +- > > drivers/acpi/Kconfig | 10 +++++----- > > drivers/net/ethernet/faraday/ftgmac100.c | 2 +- > > .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- > > drivers/vhost/vhost.c | 2 +- > > include/acpi/acpi_drivers.h | 2 +- > > include/linux/fs_context.h | 2 +- > > include/linux/lsm_hooks.h | 2 +- > > mm/Kconfig | 2 +- > > security/Kconfig | 2 +- > > tools/include/linux/err.h | 2 +- > > tools/objtool/Documentation/stack-validation.txt | 4 ++-- > > tools/testing/selftests/x86/protection_keys.c | 2 +- > > 48 files changed, 77 insertions(+), 78 deletions(-) > > > > diff --git a/Documentation/acpi/dsd/leds.txt > > b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644 > > --- a/Documentation/acpi/dsd/leds.txt > > +++ b/Documentation/acpi/dsd/leds.txt > > @@ -96,4 +96,4 @@ where > > > > <URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-da > > ta-extension-UUID-v1.1.pdf>, referenced 2019-02-21. > > > > -[7] Documentation/acpi/dsd/data-node-reference.txt > > +[7] Documentation/firmware-guide/acpi/dsd/data-node-references.rst > > diff --git a/Documentation/admin-guide/kernel-parameters.rst > > b/Documentation/admin-guide/kernel-parameters.rst index > > 0124980dca2d..8d3273e32eb1 100644 > > --- a/Documentation/admin-guide/kernel-parameters.rst > > +++ b/Documentation/admin-guide/kernel-parameters.rst > > @@ -167,7 +167,7 @@ parameter is applicable:: > > X86-32 X86-32, aka i386 architecture is enabled. > > X86-64 X86-64 architecture is enabled. > > More X86-64 boot options can be found in > > - Documentation/x86/x86_64/boot-options.txt > . > > + Documentation/x86/x86_64/boot-options.rst. > > X86 Either 32-bit or 64-bit x86 (same as X86-32+X86-64) > > X86_UV SGI UV support is enabled. > > XEN Xen support is enabled > > @@ -181,10 +181,10 @@ In addition, the following text indicates that the > > option:: Parameters denoted with BOOT are actually interpreted by the boot > > loader, and have no meaning to the kernel directly. > > Do not modify the syntax of boot loader parameters without extreme > > -need or coordination with <Documentation/x86/boot.txt>. > > +need or coordination with <Documentation/x86/boot.rst>. > > > > There are also arch-specific kernel-parameters not documented here. > > -See for example <Documentation/x86/x86_64/boot-options.txt>. > > +See for example <Documentation/x86/x86_64/boot-options.rst>. > > > > Note that ALL kernel parameters listed below are CASE SENSITIVE, and that > > a trailing = on the name of any parameter states that that parameter will > > diff --git a/Documentation/admin-guide/kernel-parameters.txt > > b/Documentation/admin-guide/kernel-parameters.txt index > > 138f6664b2e2..4a02d1346635 100644 > > --- a/Documentation/admin-guide/kernel-parameters.txt > > +++ b/Documentation/admin-guide/kernel-parameters.txt > > @@ -53,7 +53,7 @@ > > ACPI_DEBUG_PRINT statements, e.g., > > ACPI_DEBUG_PRINT((ACPI_DB_INFO, ... > > The debug_level mask defaults to "info". > See > > - Documentation/acpi/debug.txt for more > information about > > + Documentation/firmware-guide/acpi/debug.rst > for more information about > > debug layers and levels. > > > > Enable processor driver info messages: > > @@ -963,7 +963,7 @@ > > for details. > > > > nompx [X86] Disables Intel Memory Protection > Extensions. > > - See Documentation/x86/intel_mpx.txt for > more > > + See Documentation/x86/intel_mpx.rst for > more > > information about the feature. > > > > nopku [X86] Disable Memory Protection Keys CPU > feature found > > @@ -1189,7 +1189,7 @@ > > that is to be dynamically loaded by Linux. > If there are > > multiple variables with the same name but > with different > > vendor GUIDs, all of them will be loaded. > See > > - Documentation/acpi/ssdt-overlays.txt for > details. > > + Documentation/admin-guide/acpi/ssdt- > overlays.rst for details. > > > > > > eisa_irq_edge= [PARISC,HW] > > @@ -2383,7 +2383,7 @@ > > > > mce [X86-32] Machine Check Exception > > > > - mce=option [X86-64] See Documentation/x86/x86_64/boot- > options.txt > > + mce=option [X86-64] See Documentation/x86/x86_64/boot- > options.rst > > > > md= [HW] RAID subsystems devices and level > > See Documentation/admin-guide/md.rst. > > @@ -2439,7 +2439,7 @@ > > set according to the > > CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE > kernel config > > option. > > - See Documentation/memory-hotplug.txt. > > + See Documentation/admin-guide/mm/memory- > hotplug.rst. > > > > memmap=exactmap [KNL,X86] Enable setting of an exact > > E820 memory map, as specified by the user. > > @@ -2528,7 +2528,7 @@ > > mem_encrypt=on: Activate > SME > > mem_encrypt=off: Do not activate SME > > > > - Refer to Documentation/x86/amd-memory- > encryption.txt > > + Refer to Documentation/virtual/kvm/amd- > memory-encryption.rst > > for details on when memory encryption can > be activated. > > > > mem_sleep_default= [SUSPEND] Default system suspend mode: > > @@ -3528,7 +3528,7 @@ > > See Documentation/blockdev/paride.txt. > > > > pirq= [SMP,APIC] Manual mp-table setup > > - See Documentation/x86/i386/IO-APIC.txt. > > + See Documentation/x86/i386/IO-APIC.rst. > > > > plip= [PPT,NET] Parallel port network link > > Format: { parport<nr> | timid | 0 } > > @@ -5054,7 +5054,7 @@ > > Can be used multiple times for multiple > devices. > > > > vga= [BOOT,X86-32] Select a particular video > mode > > - See Documentation/x86/boot.txt and > > + See Documentation/x86/boot.rst and > > Documentation/svga.txt. > > Use vga=ask for menu. > > This is actually a boot loader parameter; > the value is > > diff --git a/Documentation/admin-guide/ras.rst > > b/Documentation/admin-guide/ras.rst index c7495e42e6f4..2b20f5f7380d 100644 > > --- a/Documentation/admin-guide/ras.rst > > +++ b/Documentation/admin-guide/ras.rst > > @@ -199,7 +199,7 @@ Architecture (MCA)\ [#f3]_. > > mode). > > > > .. [#f3] For more details about the Machine Check Architecture (MCA), > > - please read Documentation/x86/x86_64/machinecheck at the Kernel tree. > > + please read Documentation/x86/x86_64/machinecheck.rst at the Kernel tree. > > > > EDAC - Error Detection And Correction > > ************************************* > > diff --git a/Documentation/devicetree/bindings/net/fsl-enetc.txt > > b/Documentation/devicetree/bindings/net/fsl-enetc.txt index > > c812e25ae90f..25fc687419db 100644 > > --- a/Documentation/devicetree/bindings/net/fsl-enetc.txt > > +++ b/Documentation/devicetree/bindings/net/fsl-enetc.txt > > @@ -16,8 +16,8 @@ Required properties: > > In this case, the ENETC node should include a "mdio" sub-node > > that in turn should contain the "ethernet-phy" node describing the > > external phy. Below properties are required, their bindings > > -already defined in ethernet.txt or phy.txt, under > > -Documentation/devicetree/bindings/net/*. > > +already defined in Documentation/devicetree/bindings/net/ethernet.txt or > > +Documentation/devicetree/bindings/net/phy.txt. > > > > Required: > > > > @@ -51,8 +51,7 @@ Example: > > connection: > > > > In this case, the ENETC port node defines a fixed link connection, > > -as specified by "fixed-link.txt", under > > -Documentation/devicetree/bindings/net/*. > > +as specified by Documentation/devicetree/bindings/net/fixed-link.txt. > > > > Required: > > > > diff --git a/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > > b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index > > 12b18f82d441..efa2c8b9b85a 100644 > > --- a/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > > +++ b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > > @@ -3,7 +3,7 @@ Amlogic Meson AXG DWC PCIE SoC controller > > Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCI > > core. It shares common functions with the PCIe DesignWare core driver and > > inherits common properties defined in > > -Documentation/devicetree/bindings/pci/designware-pci.txt. > > +Documentation/devicetree/bindings/pci/designware-pcie.txt. > > > > Additional properties are described here: > > > > diff --git > > a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt > > b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index > > 7ef2dbe48e8a..14d2eee96b3d 100644 > > --- a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt > > +++ b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt > > @@ -97,7 +97,7 @@ Second Level Nodes - Regulators > > sent for this regulator including those which are > for a > > strictly lower power state. > > > > -Other properties defined in Documentation/devicetree/bindings/regulator.txt > > +Other properties defined in > > Documentation/devicetree/bindings/regulator/regulator.txt may also be used. > > regulator-initial-mode and regulator-allowed-modes may be specified for > > VRM regulators using mode values from > > include/dt-bindings/regulator/qcom,rpmh-regulator.h. > > regulator-allow-bypass diff --git > > a/Documentation/devicetree/booting-without-of.txt > > b/Documentation/devicetree/booting-without-of.txt index > > e86bd2f64117..60f8640f2b2f 100644 > > --- a/Documentation/devicetree/booting-without-of.txt > > +++ b/Documentation/devicetree/booting-without-of.txt > > @@ -277,7 +277,7 @@ it with special cases. > > the decompressor (the real mode entry point goes to the same 32bit > > entry point once it switched into protected mode). That entry point > > supports one calling convention which is documented in > > - Documentation/x86/boot.txt > > + Documentation/x86/boot.rst > > The physical pointer to the device-tree block (defined in chapter II) > > is passed via setup_data which requires at least boot protocol 2.09. > > The type filed is defined as > > diff --git a/Documentation/driver-api/gpio/board.rst > > b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 > > 100644 > > --- a/Documentation/driver-api/gpio/board.rst > > +++ b/Documentation/driver-api/gpio/board.rst > > @@ -101,7 +101,7 @@ with the help of _DSD (Device Specific Data), introduced > > in ACPI 5.1:: } > > > > For more information about the ACPI GPIO bindings see > > -Documentation/acpi/gpio-properties.txt. > > +Documentation/firmware-guide/acpi/gpio-properties.rst. > > > > Platform Data > > ------------- > > diff --git a/Documentation/driver-api/gpio/consumer.rst > > b/Documentation/driver-api/gpio/consumer.rst index > > 5e4d8aa68913..fdecb6d711db 100644 > > --- a/Documentation/driver-api/gpio/consumer.rst > > +++ b/Documentation/driver-api/gpio/consumer.rst > > @@ -437,7 +437,7 @@ case, it will be handled by the GPIO subsystem > > automatically. However, if the _DSD is not present, the mappings between > > GpioIo()/GpioInt() resources and GPIO connection IDs need to be provided by > > device drivers. > > > > -For details refer to Documentation/acpi/gpio-properties.txt > > +For details refer to Documentation/firmware-guide/acpi/gpio-properties.rst > > > > > > Interacting With the Legacy GPIO Subsystem > > diff --git a/Documentation/firmware-guide/acpi/enumeration.rst > > b/Documentation/firmware-guide/acpi/enumeration.rst index > > 850be9696931..1252617b520f 100644 > > --- a/Documentation/firmware-guide/acpi/enumeration.rst > > +++ b/Documentation/firmware-guide/acpi/enumeration.rst > > @@ -339,7 +339,7 @@ a code like this:: > > There are also devm_* versions of these functions which release the > > descriptors once the device is released. > > > > -See Documentation/acpi/gpio-properties.txt for more information about the > > +See Documentation/firmware-guide/acpi/gpio-properties.rst for more > > information about the _DSD binding related to GPIOs. > > > > MFD devices > > diff --git a/Documentation/firmware-guide/acpi/method-tracing.rst > > b/Documentation/firmware-guide/acpi/method-tracing.rst index > > d0b077b73f5f..0aa7e2c5d32a 100644 > > --- a/Documentation/firmware-guide/acpi/method-tracing.rst > > +++ b/Documentation/firmware-guide/acpi/method-tracing.rst > > @@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the > > specified > > > > Where: > > 0xXXXXXXXX/0xYYYYYYYY > > - Refer to Documentation/acpi/debug.txt for possible debug layer/level > > + Refer to Documentation/firmware-guide/acpi/debug.rst for possible > > debug layer/level masking values. > > \PPPP.AAAA.TTTT.HHHH > > Full path of a control method that can be found in the ACPI namespace. > > diff --git a/Documentation/i2c/instantiating-devices > > b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c > > 100644 > > --- a/Documentation/i2c/instantiating-devices > > +++ b/Documentation/i2c/instantiating-devices > > @@ -85,7 +85,7 @@ Method 1c: Declare the I2C devices via ACPI > > ------------------------------------------- > > > > ACPI can also describe I2C devices. There is special documentation for this > > -which is currently located at Documentation/acpi/enumeration.txt. +which > > is currently located at Documentation/firmware-guide/acpi/enumeration.rst. > > > > > > Method 2: Instantiate the devices explicitly > > diff --git a/Documentation/sysctl/kernel.txt > > b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644 > > --- a/Documentation/sysctl/kernel.txt > > +++ b/Documentation/sysctl/kernel.txt > > @@ -155,7 +155,7 @@ is 0x15 and the full version number is 0x234, this file > > will contain the value 340 = 0x154. > > > > See the type_of_loader and ext_loader_type fields in > > -Documentation/x86/boot.txt for additional information. > > +Documentation/x86/boot.rst for additional information. > > > > ============================================================== > > > > @@ -167,7 +167,7 @@ The complete bootloader version number. In the example > > above, this file will contain the value 564 = 0x234. > > > > See the type_of_loader and ext_loader_ver fields in > > -Documentation/x86/boot.txt for additional information. > > +Documentation/x86/boot.rst for additional information. > > > > ============================================================== > > > > diff --git a/Documentation/translations/it_IT/process/howto.rst > > b/Documentation/translations/it_IT/process/howto.rst index > > 9903ac7c566b..44e6077730e8 100644 > > --- a/Documentation/translations/it_IT/process/howto.rst > > +++ b/Documentation/translations/it_IT/process/howto.rst > > @@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei > > sorgente del kernel e che "Linux kernel patch submission format" > > http://linux.yyz.us/patch-format.html > > > > - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst > > <it_stable_api_nonsense>` + > > :ref:`Documentation/translations/it_IT/process/stable-api-nonsense.rst > > <it_stable_api_nonsense>` > > > > Questo file descrive la motivazioni sottostanti la conscia decisione di > > non avere un API stabile all'interno del kernel, incluso cose come: diff > > --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst > > b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index > > 48e88e5ad2c5..4f206cee31a7 100644 > > --- a/Documentation/translations/it_IT/process/stable-kernel-rules.rst > > +++ b/Documentation/translations/it_IT/process/stable-kernel-rules.rst > > @@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono > > accettate nei sorgenti - Non deve includere alcuna correzione "banale" > > (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera). > > - Deve rispettare le regole scritte in > > - :ref:`Documentation/translation/it_IT/process/submitting-patches.rst > > <it_submittingpatches>` + > > :ref:`Documentation/translations/it_IT/process/submitting-patches.rst > > <it_submittingpatches>` - Questa patch o una equivalente deve esistere già > > nei sorgenti principali di Linux > > > > @@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable > > > > - Se la patch contiene modifiche a dei file nelle cartelle net/ o > > drivers/net, allora seguite le linee guida descritte in > > - :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst > > <it_netdev-FAQ>`; + > > :ref:`Documentation/translations/it_IT/networking/netdev-FAQ.rst > > <it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la > > patch non sia già in coda: > > > > https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state= > > *&q=&archive= diff --git > > a/Documentation/translations/zh_CN/process/4.Coding.rst > > b/Documentation/translations/zh_CN/process/4.Coding.rst index > > 5301e9d55255..8bb777941394 100644 > > --- a/Documentation/translations/zh_CN/process/4.Coding.rst > > +++ b/Documentation/translations/zh_CN/process/4.Coding.rst > > @@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” > > > > 任何添加新用户空间界面的代码（包括新的sysfs或/proc文件）都应该包含该界面的 > > 文档，该文档使用户空间开发人员能够知道他们在使用什么。请参阅 > > -Documentation/abi/readme，了解如何格式化此文档以及需要提供哪些信息。 > > +Documentation/ABI/README，了解如何格式化此文档以及需要提供哪些信息。 > > > > 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst > > <kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的 > > diff --git a/Documentation/x86/x86_64/5level-paging.rst > > b/Documentation/x86/x86_64/5level-paging.rst index > > ab88a4514163..44856417e6a5 100644 > > --- a/Documentation/x86/x86_64/5level-paging.rst > > +++ b/Documentation/x86/x86_64/5level-paging.rst > > @@ -20,7 +20,7 @@ physical address space. This "ought to be enough for > > anybody" ©. QEMU 2.9 and later support 5-level paging. > > > > Virtual memory layout for 5-level paging is described in > > -Documentation/x86/x86_64/mm.txt > > +Documentation/x86/x86_64/mm.rst > > > > > > Enabling 5-level paging > > diff --git a/Documentation/x86/x86_64/boot-options.rst > > b/Documentation/x86/x86_64/boot-options.rst index > > 2f69836b8445..6a4285a3c7a4 100644 > > --- a/Documentation/x86/x86_64/boot-options.rst > > +++ b/Documentation/x86/x86_64/boot-options.rst > > @@ -9,7 +9,7 @@ only the AMD64 specific ones are listed here. > > > > Machine check > > ============= > > -Please see Documentation/x86/x86_64/machinecheck for sysfs runtime > > tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs > > runtime tunables. > > > > mce=off > > Disable machine check > > @@ -89,7 +89,7 @@ APICs > > Don't use the local APIC (alias for i386 compatibility) > > > > pirq=... > > - See Documentation/x86/i386/IO-APIC.txt > > + See Documentation/x86/i386/IO-APIC.rst > > > > noapictimer > > Don't set up the APIC timer > > diff --git a/Documentation/x86/x86_64/fake-numa-for-cpusets.rst > > b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index > > 74fbb78b3c67..04df57b9aa3f 100644 > > --- a/Documentation/x86/x86_64/fake-numa-for-cpusets.rst > > +++ b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst > > @@ -18,7 +18,7 @@ For more information on the features of cpusets, see > > Documentation/cgroup-v1/cpusets.txt. > > There are a number of different configurations you can use for your needs. > > For more information on the numa=fake command line option and its various > > ways of -configuring fake nodes, see > > Documentation/x86/x86_64/boot-options.txt. +configuring fake nodes, see > > Documentation/x86/x86_64/boot-options.rst. > > > > For the purposes of this introduction, we'll assume a very primitive NUMA > > emulation setup of "numa=fake=4*512,". This will split our system memory > > into diff --git a/MAINTAINERS b/MAINTAINERS > > index 5cfbea4ce575..a38d7273705a 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -3874,7 +3874,7 @@ > > F: Documentation/devicetree/bindings/hwmon/cirrus,lochnagar.txt > > F: Documentation/devicetree/bindings/pinctrl/cirrus,lochnagar.txt > > F: Documentation/devicetree/bindings/regulator/cirrus,lochnagar.txt > > F: Documentation/devicetree/bindings/sound/cirrus,lochnagar.txt > > -F: Documentation/hwmon/lochnagar > > +F: Documentation/hwmon/lochnagar.rst > > > > CISCO FCOE HBA DRIVER > > M: Satish Kharat <satishkh(a)cisco.com> > > @@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER > > M: Rui Miguel Silva <rmfrfs(a)gmail.com> > > L: linux-iio(a)vger.kernel.org > > S: Maintained > > -F: Documentation/devicetree/bindings/iio/gyroscope/fxas21002c.txt > > +F: Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt > > F: drivers/iio/gyro/fxas21002c_core.c > > F: drivers/iio/gyro/fxas21002c.h > > F: drivers/iio/gyro/fxas21002c_i2c.c > > @@ -13043,7 +13043,7 @@ M: Niklas Cassel <niklas.cassel(a)linaro.org> > > L: netdev(a)vger.kernel.org > > S: Maintained > > F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c > > -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt > > +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt > > > > QUALCOMM GENERIC INTERFACE I2C DRIVER > > M: Alok Chauhan <alokc(a)codeaurora.org> > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > > index 8869742a85df..0f220264cc23 100644 > > --- a/arch/arm/Kconfig > > +++ b/arch/arm/Kconfig > > @@ -1263,7 +1263,7 @@ config SMP > > uniprocessor machines. On a uniprocessor machine, the kernel > > will run faster if you say N here. > > > > - See also <file:Documentation/x86/i386/IO-APIC.txt>, > > + See also <file:Documentation/x86/i386/IO-APIC.rst>, > > <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO > available at > > <http://tldp.org/HOWTO/SMP-HOWTO.html>. > > > > diff --git a/arch/arm64/kernel/kexec_image.c > > b/arch/arm64/kernel/kexec_image.c index 07bf740bea91..31cc2f423aa8 100644 > > --- a/arch/arm64/kernel/kexec_image.c > > +++ b/arch/arm64/kernel/kexec_image.c > > @@ -53,7 +53,7 @@ static void *image_load(struct kimage *image, > > > > /* > > * We require a kernel with an unambiguous Image header. Per > > - * Documentation/booting.txt, this is the case when image_size > > + * Documentation/arm64/booting.txt, this is the case when > image_size > > * is non-zero (practically speaking, since v3.17). > > */ > > h = (struct arm64_image_header *)kernel; > > diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig > > index 8c1c636308c8..e868d2bd48b8 100644 > > --- a/arch/powerpc/Kconfig > > +++ b/arch/powerpc/Kconfig > > @@ -898,7 +898,7 @@ config PPC_MEM_KEYS > > page-based protections, but without requiring modification of > the > > page tables when an application changes protection domains. > > > > - For details, see Documentation/vm/protection-keys.rst > > + For details, see Documentation/x86/protection-keys.rst > > > > If unsure, say y. > > > > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig > > index 2bbbd4d1ba31..78fdf2dd71d1 100644 > > --- a/arch/x86/Kconfig > > +++ b/arch/x86/Kconfig > > @@ -395,7 +395,7 @@ config SMP > > Y to "Enhanced Real Time Clock Support", below. The "Advanced > Power > > Management" code will be disabled if you say Y here. > > > > - See also <file:Documentation/x86/i386/IO-APIC.txt>, > > + See also <file:Documentation/x86/i386/IO-APIC.rst>, > > <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO > available at > > <http://www.tldp.org/docs.html#howto>. > > > > @@ -1290,7 +1290,7 @@ config MICROCODE > > the Linux kernel. > > > > The preferred method to load microcode from a detached initrd is > > described - in Documentation/x86/microcode.txt. For that you > need to > > enable + in Documentation/x86/microcode.rst. For that you need to enable > > CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the initrd > > for microcode blobs. > > > > @@ -1329,7 +1329,7 @@ config MICROCODE_OLD_INTERFACE > > It is inadequate because it runs too late to be able to properly > > load microcode on a machine and it needs special tools. Instead, > you > > should've switched to the early loading method with the initrd > or > > - builtin microcode by now: Documentation/x86/microcode.txt > > + builtin microcode by now: Documentation/x86/microcode.rst > > > > config X86_MSR > > tristate "/dev/cpu/*/msr - Model-specific register support" > > @@ -1478,7 +1478,7 @@ config X86_5LEVEL > > A kernel with the option enabled can be booted on machines that > > support 4- or 5-level paging. > > > > - See Documentation/x86/x86_64/5level-paging.txt for more > > + See Documentation/x86/x86_64/5level-paging.rst for more > > information. > > > > Say N if unsure. > > @@ -1626,7 +1626,7 @@ config ARCH_MEMORY_PROBE > > depends on X86_64 && MEMORY_HOTPLUG > > help > > This option enables a sysfs memory/probe interface for testing. > > - See Documentation/memory-hotplug.txt for more information. > > + See Documentation/admin-guide/mm/memory-hotplug.rst for more > > information. If you are unsure how to answer this question, answer N. > > > > config ARCH_PROC_KCORE_TEXT > > @@ -1783,7 +1783,7 @@ config MTRR > > You can safely say Y even if your machine doesn't have MTRRs, > you'll > > just add about 9 KB to your kernel. > > > > - See <file:Documentation/x86/mtrr.txt> for more information. > > + See <file:Documentation/x86/mtrr.rst> for more information. > > > > config MTRR_SANITIZER > > def_bool y > > @@ -1895,7 +1895,7 @@ config X86_INTEL_MPX > > process and adds some branches to paths used during > > exec() and munmap(). > > > > - For details, see Documentation/x86/intel_mpx.txt > > + For details, see Documentation/x86/intel_mpx.rst > > > > If unsure, say N. > > > > @@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS > > page-based protections, but without requiring modification of > the > > page tables when an application changes protection domains. > > > > - For details, see Documentation/x86/protection-keys.txt > > + For details, see Documentation/x86/protection-keys.rst > > > > If unsure, say y. > > > > diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug > > index f730680dc818..59f598543203 100644 > > --- a/arch/x86/Kconfig.debug > > +++ b/arch/x86/Kconfig.debug > > @@ -156,7 +156,7 @@ config IOMMU_DEBUG > > code. When you use it make sure you have a big enough > > IOMMU/AGP aperture. Most of the options enabled by this can > > be set more finegrained using the iommu= command line > > - options. See Documentation/x86/x86_64/boot-options.txt for more > > + options. See Documentation/x86/x86_64/boot-options.rst for more > > details. > > > > config IOMMU_LEAK > > diff --git a/arch/x86/boot/header.S b/arch/x86/boot/header.S > > index 850b8762e889..90d791ca1a95 100644 > > --- a/arch/x86/boot/header.S > > +++ b/arch/x86/boot/header.S > > @@ -313,7 +313,7 @@ start_sys_seg: .word SYSSEG > # obsolete and meaningless, > > but just > > > > type_of_loader: .byte 0 # 0 means ancient > bootloader, newer > > # bootloaders know > to change this. > > - # See > Documentation/x86/boot.txt for > > + # See > Documentation/x86/boot.rst for > > # assigned ids > > > > # flags, unused bits must be zero (RFU) bit within loadflags > > diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S > > index 11aa3b2afa4d..33f9fc38d014 100644 > > --- a/arch/x86/entry/entry_64.S > > +++ b/arch/x86/entry/entry_64.S > > @@ -8,7 +8,7 @@ > > * > > * entry.S contains the system-call and fault low-level handling routines. > > * > > - * Some of this is documented in Documentation/x86/entry_64.txt > > + * Some of this is documented in Documentation/x86/entry_64.rst > > * > > * A note on terminology: > > * - iret frame: Architecture defined interrupt frame from SS to RIP > > diff --git a/arch/x86/include/asm/bootparam_utils.h > > b/arch/x86/include/asm/bootparam_utils.h index f6f6ef436599..101eb944f13c > > 100644 > > --- a/arch/x86/include/asm/bootparam_utils.h > > +++ b/arch/x86/include/asm/bootparam_utils.h > > @@ -24,7 +24,7 @@ static void sanitize_boot_params(struct boot_params > > *boot_params) * IMPORTANT NOTE TO BOOTLOADER AUTHORS: do not simply clear > > * this field. The purpose of this field is to guarantee > > * compliance with the x86 boot spec located in > > - * Documentation/x86/boot.txt . That spec says that the > > + * Documentation/x86/boot.rst . That spec says that the > > * *whole* structure should be cleared, after which only the > > * portion defined by struct setup_header (boot_params->hdr) > > * should be copied in. > > diff --git a/arch/x86/include/asm/page_64_types.h > > b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 > > 100644 > > --- a/arch/x86/include/asm/page_64_types.h > > +++ b/arch/x86/include/asm/page_64_types.h > > @@ -48,7 +48,7 @@ > > > > #define __START_KERNEL_map _AC(0xffffffff80000000, UL) > > > > -/* See Documentation/x86/x86_64/mm.txt for a description of the memory map. > > */ +/* See Documentation/x86/x86_64/mm.rst for a description of the memory > > map. */ > > > > #define __PHYSICAL_MASK_SHIFT 52 > > > > diff --git a/arch/x86/include/asm/pgtable_64_types.h > > b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d > > 100644 > > --- a/arch/x86/include/asm/pgtable_64_types.h > > +++ b/arch/x86/include/asm/pgtable_64_types.h > > @@ -103,7 +103,7 @@ extern unsigned int ptrs_per_p4d; > > #define PGDIR_MASK (~(PGDIR_SIZE - 1)) > > > > /* > > - * See Documentation/x86/x86_64/mm.txt for a description of the memory map. > > + * See Documentation/x86/x86_64/mm.rst for a description of the memory > > map. * > > * Be very careful vs. KASLR when changing anything here. The KASLR address > > * range must not overlap with anything except the KASAN shadow area, which > > diff --git a/arch/x86/kernel/cpu/microcode/amd.c > > b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab > > 100644 > > --- a/arch/x86/kernel/cpu/microcode/amd.c > > +++ b/arch/x86/kernel/cpu/microcode/amd.c > > @@ -61,7 +61,7 @@ static u8 amd_ucode_patch[PATCH_MAX_SIZE]; > > > > /* > > * Microcode patch container file is prepended to the initrd in cpio > > - * format. See Documentation/x86/microcode.txt > > + * format. See Documentation/x86/microcode.rst > > */ > > static const char > > ucode_path[] __maybe_unused = "kernel/x86/microcode/AuthenticAMD.bin"; > > diff --git a/arch/x86/kernel/kexec-bzimage64.c > > b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644 > > --- a/arch/x86/kernel/kexec-bzimage64.c > > +++ b/arch/x86/kernel/kexec-bzimage64.c > > @@ -416,7 +416,7 @@ static void *bzImage64_load(struct kimage *image, char > > *kernel, efi_map_offset = params_cmdline_sz; > > efi_setup_data_offset = efi_map_offset + ALIGN(efi_map_sz, 16); > > > > - /* Copy setup header onto bootparams. Documentation/x86/boot.txt > */ > > + /* Copy setup header onto bootparams. Documentation/x86/boot.rst */ > > setup_header_size = 0x0202 + kernel[0x0201] - setup_hdr_offset; > > > > /* Is there a limit on setup header size? */ > > diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c > > index dcd272dbd0a9..f62b498b18fb 100644 > > --- a/arch/x86/kernel/pci-dma.c > > +++ b/arch/x86/kernel/pci-dma.c > > @@ -70,7 +70,7 @@ void __init pci_iommu_alloc(void) > > } > > > > /* > > - * See <Documentation/x86/x86_64/boot-options.txt> for the iommu kernel > > + * See <Documentation/x86/x86_64/boot-options.rst> for the iommu kernel > > * parameter documentation. > > */ > > static __init int iommu_setup(char *p) > > diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c > > index 7f61431c75fb..400c1ba033aa 100644 > > --- a/arch/x86/mm/tlb.c > > +++ b/arch/x86/mm/tlb.c > > @@ -711,7 +711,7 @@ void native_flush_tlb_others(const struct cpumask > > *cpumask, } > > > > /* > > - * See Documentation/x86/tlb.txt for details. We choose 33 > > + * See Documentation/x86/tlb.rst for details. We choose 33 > > * because it is large enough to cover the vast majority (at > > * least 95%) of allocations, and is small enough that we are > > * confident it will not cause too much overhead. Each single > > diff --git a/arch/x86/platform/pvh/enlighten.c > > b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 > > --- a/arch/x86/platform/pvh/enlighten.c > > +++ b/arch/x86/platform/pvh/enlighten.c > > @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) > > } > > > > /* > > - * See Documentation/x86/boot.txt. > > + * See Documentation/x86/boot.rst. > > * > > * Version 2.12 supports Xen entry point but we will use default > x86/PC > > * environment (i.e. hardware_subarch 0). > > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig > > index 283ee94224c6..2438f37f2ca1 100644 > > --- a/drivers/acpi/Kconfig > > +++ b/drivers/acpi/Kconfig > > @@ -333,7 +333,7 @@ config ACPI_CUSTOM_DSDT_FILE > > depends on !STANDALONE > > help > > This option supports a custom DSDT by linking it into the > kernel. > > - See Documentation/acpi/dsdt-override.txt > > + See Documentation/admin-guide/acpi/dsdt-override.rst > > > > Enter the full path name to the file which includes the AmlCode > > or dsdt_aml_code declaration. > > @@ -355,7 +355,7 @@ config ACPI_TABLE_UPGRADE > > This option provides functionality to upgrade arbitrary ACPI > tables > > via initrd. No functional change if no ACPI tables are passed > via > > initrd, therefore it's safe to say Y. > > - See Documentation/acpi/initrd_table_override.txt for details > > + See Documentation/admin-guide/acpi/initrd_table_override.rst for > details > > > > config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD > > bool "Override ACPI tables from built-in initrd" > > @@ -365,7 +365,7 @@ config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD > > This option provides functionality to override arbitrary ACPI > tables > > from built-in uncompressed initrd. > > > > - See Documentation/acpi/initrd_table_override.txt for details > > + See Documentation/admin-guide/acpi/initrd_table_override.rst for > details > > > > config ACPI_DEBUG > > bool "Debug Statements" > > @@ -374,7 +374,7 @@ config ACPI_DEBUG > > output and increases the kernel size by around 50K. > > > > Use the acpi.debug_layer and acpi.debug_level kernel command- > line > > - parameters documented in Documentation/acpi/debug.txt and > > + parameters documented in Documentation/firmware-guide/acpi/ > debug.rst and > > Documentation/admin-guide/kernel-parameters.rst to control the type and > > amount of debug output. > > > > @@ -445,7 +445,7 @@ config ACPI_CUSTOM_METHOD > > help > > This debug facility allows ACPI AML methods to be inserted and/ > or > > replaced without rebooting the system. For details refer to: > > - Documentation/acpi/method-customizing.txt. > > + Documentation/firmware-guide/acpi/method-customizing.rst. > > > > NOTE: This option is security sensitive, because it allows > arbitrary > > kernel memory to be written to by root (uid=0) users, allowing > them > > diff --git a/drivers/net/ethernet/faraday/ftgmac100.c > > b/drivers/net/ethernet/faraday/ftgmac100.c index b17b79e612a3..ac6280ad43a1 > > 100644 > > --- a/drivers/net/ethernet/faraday/ftgmac100.c > > +++ b/drivers/net/ethernet/faraday/ftgmac100.c > > @@ -1075,7 +1075,7 @@ static int ftgmac100_mii_probe(struct ftgmac100 *priv, > > phy_interface_t intf) } > > > > /* Indicate that we support PAUSE frames (see comment in > > - * Documentation/networking/phy.txt) > > + * Documentation/networking/phy.rst) > > */ > > phy_support_asym_pause(phydev); > > > > diff --git a/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt > > b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index > > 56af3f650fa3..89fb8e14676f 100644 > > --- a/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt > > +++ b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt > > @@ -54,8 +54,8 @@ a limited few common behaviours and properties. This > > allows us to define a simple interface consisting of a character device and > > a set of sysfs files: > > > > See: > > -Documentation/ABI/testing/sysfs-class-fieldbus-dev > > -Documentation/ABI/testing/fieldbus-dev-cdev > > +drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev > > +drivers/staging/fieldbus/Documentation/ABI/fieldbus-dev-cdev > > > > Note that this simple interface does not provide a way to modify adapter > > configuration settings. It is therefore useful only for adapters that get > > their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c > > index 1e3ed41ae1f3..69938dbae2d0 100644 > > --- a/drivers/vhost/vhost.c > > +++ b/drivers/vhost/vhost.c > > @@ -1694,7 +1694,7 @@ EXPORT_SYMBOL_GPL(vhost_dev_ioctl); > > > > /* TODO: This is really inefficient. We need something like get_user() > > * (instruction directly accesses the data, with an exception table entry > > - * returning -EFAULT). See Documentation/x86/exception-tables.txt. > > + * returning -EFAULT). See Documentation/x86/exception-tables.rst. > > */ > > static int set_bit_to_user(int nr, void __user *addr) > > { > > diff --git a/include/acpi/acpi_drivers.h b/include/acpi/acpi_drivers.h > > index de1804aeaf69..98e3db7a89cd 100644 > > --- a/include/acpi/acpi_drivers.h > > +++ b/include/acpi/acpi_drivers.h > > @@ -25,7 +25,7 @@ > > #define ACPI_MAX_STRING 80 > > > > /* > > - * Please update drivers/acpi/debug.c and Documentation/acpi/debug.txt > > + * Please update drivers/acpi/debug.c and > > Documentation/firmware-guide/acpi/debug.rst * if you add to this list. > > */ > > #define ACPI_BUS_COMPONENT 0x00010000 > > diff --git a/include/linux/fs_context.h b/include/linux/fs_context.h > > index 1f966670c8dc..623eb58560b9 100644 > > --- a/include/linux/fs_context.h > > +++ b/include/linux/fs_context.h > > @@ -85,7 +85,7 @@ struct fs_parameter { > > * Superblock creation fills in ->root whereas reconfiguration begins with > > this * already set. > > * > > - * See Documentation/filesystems/mounting.txt > > + * See Documentation/filesystems/mount_api.txt > > */ > > struct fs_context { > > const struct fs_context_operations *ops; > > diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h > > index 47f58cfb6a19..df1318d85f7d 100644 > > --- a/include/linux/lsm_hooks.h > > +++ b/include/linux/lsm_hooks.h > > @@ -77,7 +77,7 @@ > > * state. This is called immediately after commit_creds(). > > * > > * Security hooks for mount using fs_context. > > - * [See also Documentation/filesystems/mounting.txt] > > + * [See also Documentation/filesystems/mount_api.txt] > > * > > * @fs_context_dup: > > * Allocate and attach a security structure to sc->security. This > pointer > > diff --git a/mm/Kconfig b/mm/Kconfig > > index ee8d1f311858..6e5fb81bde4b 100644 > > --- a/mm/Kconfig > > +++ b/mm/Kconfig > > @@ -165,7 +165,7 @@ config MEMORY_HOTPLUG_DEFAULT_ONLINE > > onlining policy (/sys/devices/system/memory/auto_online_blocks) > which > > determines what happens to newly added memory regions. Policy > setting > > can always be changed at runtime. > > - See Documentation/memory-hotplug.txt for more information. > > + See Documentation/admin-guide/mm/memory-hotplug.rst for more > > information. > > > > Say Y here if you want all hot-plugged memory blocks to appear > in > > 'online' state by default. > > diff --git a/security/Kconfig b/security/Kconfig > > index aeac3676dd4d..6d75ed71970c 100644 > > --- a/security/Kconfig > > +++ b/security/Kconfig > > @@ -62,7 +62,7 @@ config PAGE_TABLE_ISOLATION > > ensuring that the majority of kernel addresses are not mapped > > into userspace. > > > > - See Documentation/x86/pti.txt for more details. > > + See Documentation/x86/pti.rst for more details. > > > > config SECURITY_INFINIBAND > > bool "Infiniband Security Hooks" > > diff --git a/tools/include/linux/err.h b/tools/include/linux/err.h > > index 2f5a12b88a86..25f2bb3a991d 100644 > > --- a/tools/include/linux/err.h > > +++ b/tools/include/linux/err.h > > @@ -20,7 +20,7 @@ > > * Userspace note: > > * The same principle works for userspace, because 'error' pointers > > * fall down to the unused hole far from user space, as described > > - * in Documentation/x86/x86_64/mm.txt for x86_64 arch: > > + * in Documentation/x86/x86_64/mm.rst for x86_64 arch: > > * > > * 0000000000000000 - 00007fffffffffff (=47 bits) user space, different per > > mm hole caused by [48:63] sign extension * ffffffffffe00000 - > > ffffffffffffffff (=2 MB) unused hole > > diff --git a/tools/objtool/Documentation/stack-validation.txt > > b/tools/objtool/Documentation/stack-validation.txt index > > 4dd11a554b9b..de094670050b 100644 > > --- a/tools/objtool/Documentation/stack-validation.txt > > +++ b/tools/objtool/Documentation/stack-validation.txt > > @@ -21,7 +21,7 @@ instructions). Similarly, it knows how to follow switch > > statements, for which gcc sometimes uses jump tables. > > > > (Objtool also has an 'orc generate' subcommand which generates debuginfo > > -for the ORC unwinder. See Documentation/x86/orc-unwinder.txt in the > > +for the ORC unwinder. See Documentation/x86/orc-unwinder.rst in the > > kernel tree for more details.) > > > > > > @@ -101,7 +101,7 @@ b) ORC (Oops Rewind Capability) unwind table generation > > band. So it doesn't affect runtime performance and it can be > > reliable even when interrupts or exceptions are involved. > > > > - For more details, see Documentation/x86/orc-unwinder.txt. > > + For more details, see Documentation/x86/orc-unwinder.rst. > > > > c) Higher live patching compatibility rate > > > > diff --git a/tools/testing/selftests/x86/protection_keys.c > > b/tools/testing/selftests/x86/protection_keys.c index > > 5d546dcdbc80..798a5ddeee55 100644 > > --- a/tools/testing/selftests/x86/protection_keys.c > > +++ b/tools/testing/selftests/x86/protection_keys.c > > @@ -1,6 +1,6 @@ > > // SPDX-License-Identifier: GPL-2.0 > > /* > > - * Tests x86 Memory Protection Keys (see > > Documentation/x86/protection-keys.txt) + * Tests x86 Memory Protection Keys > > (see Documentation/x86/protection-keys.rst) * > > * There are examples in here of: > > * * how to set protection keys on memory > > >

6 years, 1 month

1
0
0 0

[PATCH net-next v3 0/1] Allow TX timestamp with UDP GSO

by Fred Klassen

Fixes an issue where TX Timestamps are not arriving on the error queue when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING. Fred Klassen (1): net/udp_gso: Allow TX timestamp with UDP GSO net/ipv4/udp_offload.c | 5 +++++ 1 file changed, 5 insertions(+) -- 2.11.0

6 years, 1 month

2
4
0 0

[PATCH v5 0/3] Fix vDSO clock_getres()

by Vincenzo Frascino

clock_getres in the vDSO library has to preserve the same behaviour of posix_get_hrtimer_res(). In particular, posix_get_hrtimer_res() does: sec = 0; ns = hrtimer_resolution; and hrtimer_resolution depends on the enablement of the high resolution timers that can happen either at compile or at run time. A possible fix is to change the vdso implementation of clock_getres, keeping a copy of hrtimer_resolution in vdso data and using that directly [1]. This patchset implements the proposed fix for arm64, powerpc, s390, nds32 and adds a test to verify that the syscall and the vdso library implementation of clock_getres return the same values. Even if these patches are unified by the same topic, there is no dependency between them, hence they can be merged singularly by each arch maintainer. Note: arm64 and nds32 respective fixes have been merged in 5.2-rc1, hence they have been removed from this series. [1] https://marc.info/?l=linux-arm-kernel&m=155110381930196&w=2 Changes: -------- v5: - Rebased on 5.2-rc2 - Fixed a bug in kselftest. v4: - Address review comments. v3: - Rebased on 5.2-rc1. - Address review comments. v2: - Rebased on 5.1-rc5. - Addressed review comments. Cc: Christophe Leroy <christophe.leroy(a)c-s.fr> Cc: Benjamin Herrenschmidt <benh(a)kernel.crashing.org> Cc: Paul Mackerras <paulus(a)samba.org> Cc: Michael Ellerman <mpe(a)ellerman.id.au> Cc: Martin Schwidefsky <schwidefsky(a)de.ibm.com> Cc: Heiko Carstens <heiko.carstens(a)de.ibm.com> Cc: Shuah Khan <shuah(a)kernel.org> Cc: Thomas Gleixner <tglx(a)linutronix.de> Cc: Arnd Bergmann <arnd(a)arndb.de> Signed-off-by: Vincenzo Frascino <vincenzo.frascino(a)arm.com> Vincenzo Frascino (3): powerpc: Fix vDSO clock_getres() s390: Fix vDSO clock_getres() kselftest: Extend vDSO selftest to clock_getres arch/powerpc/include/asm/vdso_datapage.h | 2 + arch/powerpc/kernel/asm-offsets.c | 2 +- arch/powerpc/kernel/time.c | 1 + arch/powerpc/kernel/vdso32/gettimeofday.S | 7 +- arch/powerpc/kernel/vdso64/gettimeofday.S | 7 +- arch/s390/include/asm/vdso.h | 1 + arch/s390/kernel/asm-offsets.c | 2 +- arch/s390/kernel/time.c | 1 + arch/s390/kernel/vdso32/clock_getres.S | 12 +- arch/s390/kernel/vdso64/clock_getres.S | 10 +- tools/testing/selftests/vDSO/Makefile | 2 + .../selftests/vDSO/vdso_clock_getres.c | 124 ++++++++++++++++++ 12 files changed, 155 insertions(+), 16 deletions(-) create mode 100644 tools/testing/selftests/vDSO/vdso_clock_getres.c -- 2.21.0

6 years, 1 month

2
5
0 0

[PATCH 00/22] Some documentation fixes

by Mauro Carvalho Chehab

Fix several warnings and broken links. This series was generated against linux-next, but was rebased to be applied at docs-next. It should apply cleanly on either tree. There's a git tree with all of them applied on the top of docs/docs-next at: https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v2 Mauro Carvalho Chehab (21): ABI: sysfs-devices-system-cpu: point to the right docs isdn: mISDN: remove a bogus reference to a non-existing doc dt: fix broken references to nand.txt docs: zh_CN: get rid of basic_profiling.txt doc: it_IT: fix reference to magic-number.rst docs: mm: numaperf.rst: get rid of a build warning docs: bpf: get rid of two warnings docs: mark orphan documents as such docs: amd-memory-encryption.rst get rid of warnings gpu: amdgpu: fix broken amdgpu_dma_buf.c references gpu: i915.rst: Fix references to renamed files docs: zh_CN: avoid duplicate citation references docs: vm: hmm.rst: fix some warnings docs: it: license-rules.rst: get rid of warnings docs: gpio: driver.rst: fix a bad tag docs: soundwire: locking: fix tags for a code-block docs: security: trusted-encrypted.rst: fix code-block tag docs: security: core.rst: Fix several warnings docs: net: dpio-driver.rst: fix two codeblock warnings docs: net: sja1105.rst: fix table format docs: fix broken documentation links Otto Sabart (1): mfd: madera: Fix bad reference to pinctrl.txt file .../ABI/testing/sysfs-devices-system-cpu | 3 +- Documentation/accelerators/ocxl.rst | 2 + Documentation/acpi/dsd/leds.txt | 2 +- .../admin-guide/kernel-parameters.rst | 6 +- .../admin-guide/kernel-parameters.txt | 16 ++--- Documentation/admin-guide/mm/numaperf.rst | 5 +- Documentation/admin-guide/ras.rst | 2 +- Documentation/arm/stm32/overview.rst | 2 + .../arm/stm32/stm32f429-overview.rst | 2 + .../arm/stm32/stm32f746-overview.rst | 2 + .../arm/stm32/stm32f769-overview.rst | 2 + .../arm/stm32/stm32h743-overview.rst | 2 + .../arm/stm32/stm32mp157-overview.rst | 2 + Documentation/bpf/btf.rst | 2 + .../bindings/mtd/amlogic,meson-nand.txt | 2 +- .../devicetree/bindings/mtd/gpmc-nand.txt | 2 +- .../devicetree/bindings/mtd/marvell-nand.txt | 2 +- .../devicetree/bindings/mtd/tango-nand.txt | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../regulator/qcom,rpmh-regulator.txt | 2 +- .../devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- Documentation/driver-api/gpio/driver.rst | 2 +- .../driver-api/soundwire/locking.rst | 4 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/gpu/amdgpu.rst | 4 +- Documentation/gpu/i915.rst | 6 +- Documentation/gpu/msm-crash-dump.rst | 2 + Documentation/i2c/instantiating-devices | 2 +- Documentation/interconnect/interconnect.rst | 2 + Documentation/laptops/lg-laptop.rst | 2 + .../freescale/dpaa2/dpio-driver.rst | 4 +- Documentation/networking/dsa/sja1105.rst | 6 +- Documentation/powerpc/isa-versions.rst | 2 + Documentation/security/keys/core.rst | 16 +++-- .../security/keys/trusted-encrypted.rst | 4 +- Documentation/sysctl/kernel.txt | 4 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/license-rules.rst | 28 ++++---- .../it_IT/process/magic-number.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 +- .../translations/zh_CN/basic_profiling.txt | 71 ------------------- .../translations/zh_CN/process/4.Coding.rst | 2 +- .../zh_CN/process/management-style.rst | 4 +- .../zh_CN/process/programming-language.rst | 28 ++++---- .../virtual/kvm/amd-memory-encryption.rst | 5 ++ Documentation/virtual/kvm/vcpu-requests.rst | 2 + Documentation/vm/hmm.rst | 9 ++- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 +- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++--- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +-- drivers/isdn/mISDN/dsp_core.c | 2 - drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 +- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- include/linux/mfd/madera/pdata.h | 3 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- .../Documentation/stack-validation.txt | 4 +- tools/testing/selftests/x86/protection_keys.c | 2 +- 84 files changed, 183 insertions(+), 212 deletions(-) delete mode 100644 Documentation/translations/zh_CN/basic_profiling.txt -- 2.21.0

6 years, 1 month

1
0
0 0

[GIT PULL] Kselftest fixes update for Linux 5.2-rc3

by Shuah Khan

Hi Linus, Please pull the following Kselftest fixes update for Linux 5.2-rc3. This Kselftest update for Linux 5.2-rc3 consists of - Alexandre Belloni's fixes to rtc regressions introduced in kselftest Makefile test run output refactoring work from Kees Cook. - ftrace test checkbashisms fixes from Masami Hiramatsu As a note, it is an usual and expected outcome to see a few regressions when Kselftest run-time scripts are enhanced. No surprises there. I am glad we are finding these problems early on in the rc cycle. diff is attached. thanks, -- Shuah ---------------------------------------------------------------- The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux-kselftest-5.2-rc3 for you to fetch changes up to eff82a263b5cfa3427fd9dbfedd96da94fdc9f19: selftests: rtc: rtctest: specify timeouts (2019-05-24 13:39:58 -0600) ---------------------------------------------------------------- linux-kselftest-5.2-rc3 This Kselftest update for Linux 5.2-rc3 consists of - Alexandre Belloni's fixes to rtc regressions introduced in kselftest Makefile test run output refactoring work from Kees Cook. - ftrace test checkbashisms fixes from Masami Hiramatsu ---------------------------------------------------------------- Alexandre Belloni (2): selftests/harness: Allow test to configure timeout selftests: rtc: rtctest: specify timeouts Masami Hiramatsu (2): selftests/ftrace: Make a script checkbashisms clean selftests/ftrace: Add checkbashisms meta-testcase tools/testing/selftests/ftrace/ftracetest | 1 + .../selftests/ftrace/test.d/kprobe/kprobe_ftrace.tc | 2 +- .../selftests/ftrace/test.d/selftest/bashisms.tc | 21 +++++++++++++++++++++ tools/testing/selftests/kselftest_harness.h | 17 ++++++++++++----- tools/testing/selftests/rtc/rtctest.c | 6 +++--- 5 files changed, 38 insertions(+), 9 deletions(-) create mode 100644 tools/testing/selftests/ftrace/test.d/selftest/bashisms.tc ----------------------------------------------------------------

6 years, 1 month

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-kselftest-mirror