On 10/15/26 2:53 PM, [email protected] wrote: > Hi! > > This is an automated message. This series looks like a fix, but its > commit messages seem to be missing some information: > > - How the issue was discovered, e.g. hit in production, hit during > development, syzbot report, manual code inspection, LLM or static > analysis tool scan.
Sashiko report while reviewing another patch, IIRC. > > - Whether the issue was actually triggered, or is only theoretical > (e.g. found by code inspection). If it was triggered please include > the symptoms, like the stack trace or error messages. It can be triggered manually, but should not be triggerable in any real OVS setups, as ovs-vswitchd always has the fragmentation bits exactly matched and will not produce set(tcp/udp) actions for later fragments. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
