aboutsummaryrefslogtreecommitdiffstats
path: root/.hgignore
diff options
context:
space:
mode:
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-06-30 14:41:13 +0100
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-06-30 14:41:13 +0100
commite110434e9117f90917d1c41d9cddf3d6c712c408 (patch)
treef191662ef58d6e04b349a9aeaee54ea5bf659592 /.hgignore
parent4509ffb83c9a82528bb2988868210af8c73eeebe (diff)
downloadxen-e110434e9117f90917d1c41d9cddf3d6c712c408.tar.gz
xen-e110434e9117f90917d1c41d9cddf3d6c712c408.tar.bz2
xen-e110434e9117f90917d1c41d9cddf3d6c712c408.zip
[NET]: Update net-gso.patch. Remove net-tso.patch.
New changeset merged upstream: [TCP]: Reset gso_segs if packet is dodgy I wasn't paranoid enough in verifying GSO information. A bogus gso_segs could upset drivers as much as a bogus header would. Let's reset it in the per-protocol gso_segment functions. I didn't verify gso_size because that can be verified by the source of the dodgy packets. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to '.hgignore')
0 files changed, 0 insertions, 0 deletions