Re: [PATCH bpf-next 1/2] bpf: Preserve stack frame number for commuted arithmetic

[Yiyang Chen]

Hi Eduard,

Totally agree.

I'll respin v2 to preserve the full pointer state instead of copying only selected fields, and use a temporary scalar offset register for the commuted `scalar += pointer` case as you suggested.

I also re-checked the history before adding the `Fixes:` tag. The tightest candidate I found is:

`Fixes: f1174f77b50c ("bpf/verifier: rework value tracking")`

That commit introduced the unified `scalar += pointer` handling and the pointer-state inheritance path. `f4d7e40a5b15` added the multi-frame stack model later, so it is related but less precise as a `Fixes:` target.

Will send v2 soon.

Thanks!