Hi, On 11/16/2022 1:43 PM, Alexei Starovoitov wrote: > On Tue, Nov 15, 2022 at 6:40 PM Hou Tao <houtao@xxxxxxxxxxxxxxx> wrote: >>> Also pls target this kind of change to bpf-next especially >>> when there is a consideration to revert other fixes. >>> This kind of questionable fixes are not suitable for bpf tree >>> regardless of how long the "bug" was present. >> The reason to post the fix to bpf tree instead bpf-next is that cgroup iterator >> is merged in v6.1 and I think it is better to merge the fix into v6.1 instead of >> v6.2. And patchset v1 is not a questionable fixes, because iterator link has >> already acquired the reference of the start cgroup. > These "fixes are not suitable for bpf tree regardless of how long the > "bug" was present". I see. Should I include the revert patches in v3 and resend it to bpf-next tree ? Or the patchset will be merged to bpf-next and I just need to send a follow-up revert patchset to bpf-next ? > .
