RE: [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RE: [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64
From: <Kenta.Tada@xxxxxxxx>
Date: Tue, 11 Jan 2022 01:04:49 +0000
Accept-language: ja-JP, en-US
Cc: <andrii@xxxxxxxxxx>, <bpf@xxxxxxxxxxxxxxx>, <ast@xxxxxxxxxx>, <daniel@xxxxxxxxxxxxx>, <kafai@xxxxxx>, <songliubraving@xxxxxx>, <yhs@xxxxxx>, <john.fastabend@xxxxxxxxx>, <kpsingh@xxxxxxxxxx>
In-reply-to: <CAEf4BzYWueWzBzVfW62augyDmLTN0ZW=mtE0xPFX7UrtG2BMPw@mail.gmail.com>
Thread-index: AdgDbmTY/BRuEK6oR7OS3JTt6yRDPQAl5y6AAJ/QBkA=
Thread-topic: [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64

I'll reconsider whether we need CORE variants when I create selftests and fix the problem you pointed out.
I'm sorry but my response might be a little late due to my personal reason.

References:
- [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64
  - From: Kenta.Tada
- Re: [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64
  - From: Andrii Nakryiko

Prev by Date: [PATCH bpf-next v5 1/2] Add skb_store_bytes() for BPF_PROG_TYPE_CGROUP_SKB
Next by Date: Re: [PATCH RFC bpf-next v1 0/8] Pinning bpf objects outside bpffs
Previous by thread: Re: [PATCH v2] libbpf: Fix the incorrect register read for syscalls on x86_64
Next by thread: [syzbot] KMSAN: uninit-value in ip_fast_csum (2)
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux