diff options
| author | Pu Lehui <pulehui@huawei.com> | 2022-05-30 17:28:10 +0800 |
|---|---|---|
| committer | Andrii Nakryiko <andrii@kernel.org> | 2022-06-02 16:25:57 -0700 |
| commit | 2cd008522707a59bf38c1f45d5c654eddbb86c20 (patch) | |
| tree | f51f86d7deecd218b8c3a109892787d2de0fab5e /arch | |
| parent | 21f1481a8db4caae4f935ef37aa29e5b3ceebc56 (diff) | |
| download | linux-stable-2cd008522707a59bf38c1f45d5c654eddbb86c20.tar.gz linux-stable-2cd008522707a59bf38c1f45d5c654eddbb86c20.tar.bz2 linux-stable-2cd008522707a59bf38c1f45d5c654eddbb86c20.zip | |
bpf: Unify data extension operation of jited_ksyms and jited_linfo
We found that 32-bit environment can not print BPF line info due to a data
inconsistency between jited_ksyms[0] and jited_linfo[0].
For example:
jited_kyms[0] = 0xb800067c, jited_linfo[0] = 0xffffffffb800067c
We know that both of them store BPF func address, but due to the different
data extension operations when extended to u64, they may not be the same.
We need to unify the data extension operations of them.
Signed-off-by: Pu Lehui <pulehui@huawei.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/CAEf4BzZ-eDcdJZgJ+Np7Y=V-TVjDDvOMqPwzKjyWrh=i5juv4w@mail.gmail.com
Link: https://lore.kernel.org/bpf/20220530092815.1112406-2-pulehui@huawei.com
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions