Re: __hardcfr_check_fail and BPF

2023-11-07 Thread Jose E. Marchesi
> Hi, > > On Oct 31, 2023, "Jose E. Marchesi" wrote: > >> As you may know, in BPF we have to live (for now) with the constant pain >> from being limited to functions whose arguments can be compiled to get >> their arguments in five or less registers. > > Ugh. I had no idea. > >> The recently in

Re: __hardcfr_check_fail and BPF

2023-11-07 Thread Alexandre Oliva
Hi, On Oct 31, 2023, "Jose E. Marchesi" wrote: > As you may know, in BPF we have to live (for now) with the constant pain > from being limited to functions whose arguments can be compiled to get > their arguments in five or less registers. Ugh. I had no idea. > The recently introduced __hardc

__hardcfr_check_fail and BPF

2023-10-31 Thread Jose E. Marchesi
Hi Alex. As you may know, in BPF we have to live (for now) with the constant pain from being limited to functions whose arguments can be compiled to get their arguments in five or less registers. The recently introduced __hardcfr_check_fail in the run-time component of hardcfr breaks the bpf-un