On 25/08/09 05:40 PM, Yunsong (Roamer) Lu wrote:
Darren Reed wrote:
Yunsong (Roamer) Lu wrote:
...
The simplest way to fix the CR is let snoop to check the LSO
information with the packet and avoid warning it. But I'm not sure
it's enough.
Is that enough?
Even though the system shouldn't do it, if an mblk_t is marked with
LSO information and delivered to a driver that doesn't support it, it
will then attempt to transmit the packet as-is, correct?
I don't think snoop is supposed to do all sanity check for the driver.
Actually it's simple for the snoop users to figure out such
misbehavior without seeing a warning.
Really?
If I send a packet using a raw socket, to a network interface, that
looks just like the one that comes from inside the kernel, how is snoop
going to know the difference?
Mind you, the one from the application won't have the checksum flags set
on the mblk_t and will thus be transmitted "as is" - if at all possible.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
