Message ID | 20190627194250.91296-1-maheshb@google.com |
---|---|
Headers | show |
Series | blackhole device to invalidate dst | expand |
On Thu, Jun 27, 2019 at 12:42 PM Mahesh Bandewar <maheshb@google.com> wrote: > However, Michael Chan <michael.chan@broadcom.com> had a setup > where these fixes helped him mitigate the issue and not cause > the crash. > Our lab has finished testing these patches. The patches work in the sense that no oversize packets are now passed to the driver with the patches applied. But I'm not seeing these bad packets reaching the blackhole device and getting dropped there. So they get dropped in some other code paths. I believe we saw the same results with your earlier patches. Thanks.
On Fri, Jun 28, 2019 at 11:22 AM Michael Chan <michael.chan@broadcom.com> wrote: > > On Thu, Jun 27, 2019 at 12:42 PM Mahesh Bandewar <maheshb@google.com> wrote: > > > However, Michael Chan <michael.chan@broadcom.com> had a setup > > where these fixes helped him mitigate the issue and not cause > > the crash. > > > > Our lab has finished testing these patches. The patches work in the > sense that no oversize packets are now passed to the driver with the > patches applied. But I'm not seeing these bad packets reaching the > blackhole device and getting dropped there. So they get dropped in > some other code paths. I believe we saw the same results with your > earlier patches. > Thanks Michael for confirmation. I would say that is WAI. With the MTU that low, I don't think .ndo_xmit for this device would ever be triggered.