linux-kernel - Re: TCP_MAXSEG vs TCP/generic segmentation offload (tso/gso)

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: <874ob55rcm.fsf@gmail.com>
Date:	Thu, 25 Nov 2010 10:56:57 -0500
From:	Ben Gamari <bgamari@...il.com>
To:	Niels Möller <nisse@...ator.liu.se>,
	linux-kernel@...r.kernel.org
Subject: Re: TCP_MAXSEG vs TCP/generic segmentation offload (tso/gso)

> I have spent some time searching the documentation and the net for
> answers, without result, hence I'm posting to this list. I'm not
> subscribed, so please cc any replies.
> 
You may find that responses are more forthcoming if you include the
maintainers for the tcp subsystem and a few of the relevant
drivers. This will ensure that they see your message. The LKML is a
pretty high-traffic list and it is frequently that messages simply
aren't seen. Also, I would definitely start by filing bug reports
against individual drivers; as you said producing packets larger than
the maximum segment size definitely seems like buggy behavior. A bug
report will ensure that the problem doesn't fall through the cracks.
Good luck,

- Ben
--
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/