On Fri, Oct 9, 2020 at 2:07 PM Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > On Fri, Oct 09, 2020 at 01:49:14PM -0700, John Fastabend wrote: > > Jakub Kicinski wrote: > > > On Thu, 08 Oct 2020 16:08:57 +0200 Jesper Dangaard Brouer wrote: > > > > V3: Drop enforcement of MTU in net-core, leave it to drivers > > > > > > Sorry for being late to the discussion. > > > > > > I absolutely disagree. We had cases in the past where HW would lock up > > > if it was sent a frame with bad geometry. > > > > > > We will not be sprinkling validation checks across the drivers because > > > some reconfiguration path may occasionally yield a bad packet, or it's > > > hard to do something right with BPF. > > > > This is a driver bug then. As it stands today drivers may get hit with > > skb with MTU greater than set MTU as best I can tell. Generally I > > expect drivers use MTU to configure RX buffers not sure how it is going > > to be used on TX side? Any examples? I just poked around through the > > driver source to see and seems to confirm its primarily for RX side > > configuration with some drivers throwing the event down to the firmware > > for something that I can't see in the code? > > > > I'm not suggestiong sprinkling validation checks across the drivers. > > I'm suggesting if the drivers hang we fix them. > > +1 > > I've seen HW that hangs when certain sizes of the packet. > Like < 68 byte TX where size is one specific constant. > I don't think it's a job of the stack or the driver to deal with that. > It's firmware/hw bug. +1 It's not the job of the core stack, but it *is* the job of the driver to deal with firmware/hw bugs like this. Sure fix in hw when you can (next rev), in fw if you can't (and have fw, can release it, rev it, distribute it), but ultimately that's why drivers have quirks for various revisions of hw/fw... so you very much fix bugs like this in driver if needed.
