> > > > Hi, the attachment is a reproducer. Enjoy it. > > Please do not top-post. > Forwarding a syzbot reproducer with zero effort to analyze > what's going on is kinda lame. Hi, I am sorry for that. > Maybe try harder and come up with a fix? > Or at least try git bisect and based on a commit find and > cc an author so it can be fixed (assuming issue still exists > in bpf-next) ? > Thank you for your suggestions. I spent a few days on git bisect and locked the bad commit, the commit is d635a69dd4981cc51f90293f5f64268620ed1565. The commit is a Merge tag 'net-next-5.11' and Contains multiple commits, currently not locked to a single commit. Regards, but3rflyh4ck. -- Active Defense Lab of Venustech
