linux-kernel - Re: [PATCH] lro: IP fragment checking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081201.131810.158631503.davem@davemloft.net>
Date:	Mon, 01 Dec 2008 13:18:10 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	gallatin@...i.com
Cc:	ossthema@...ibm.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, tklein@...ibm.com, raisch@...ibm.com,
	jb.billaud@...il.com, hering2@...ibm.com
Subject: Re: [PATCH] lro: IP fragment checking

From: Andrew Gallatin <gallatin@...i.com>
Date: Mon, 01 Dec 2008 12:50:15 -0500

> As to whether or not to do it in the drivers/hardware or in the
> LRO code, I favor doing it in the LRO code just so that it is not
> missed in some driver.

Then there is no point in the hardware doing the check, if
we're going to check it anyways.

That's part of my point about why this check doesn't belong
here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/