Re: [syzbot] [mptcp?] general protection fault in proc_scheduler

[Matthieu Baerts]

Hi Al,

On 04/01/2025 21:21, Al Viro wrote:
> The real issue (and the one that affects more than just this scenario) is
> the use of current->nsproxy->net to get to the damn thing.
> 
> Why not something like

(...)

> seeing that the data object you really want to access is
> mptcp_get_pernet(net)->scheduler and you have that pointer
> stored in table->data at the registration time?

Good point, thank you for the suggestion! :)

I will do this modification.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.