-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[syzbot] WARNING in __mptcp_move_skbs_from_subflow
#513
Comments
@cpaasch : thank you for this reminder. By chance, do you have a reproducer? Did you get it while validating the |
No reproducer yet. |
Some occurrence of the reported splats should be fixed by the following commit commit 68cc924
According to the syzbot status, syzkaller was able to reproduce the splat on top of linux@6a0e38264012 which includes the above commit, so there should be something more. |
The splat is caused by a somewhat bad mapping: the current data mapping covers only partially the current skb contents. In theory we could 'downgrade' the warning to a dbg message and/or a mib count increase, as an evil/bad pear could trigger this at will, but syzkaller is observing the splat when the peer is the in-tree mptcp implementation: we need to dig the root cause. |
Yes, that is something that can happen, so downgrading to dbg with a MIB-counter would be good. |
Raising awareness here to this issue: https://syzkaller.appspot.com/bug?id=e1909b42f954d6302231753e99ff2fef6d763447
We are hitting this as well in our deployment.
The text was updated successfully, but these errors were encountered: