linux-kernel - Re: Honoring SO_RCVLOWAT in proto

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-next>] [day] [month] [year] [list]

Message-ID: <20080921211337.74e8f1f1@lxorguk.ukuu.org.uk>
Date:	Sun, 21 Sep 2008 21:13:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	vcaputo@...garu.com, linux-kernel@...r.kernel.org
Subject: Re: Honoring SO_RCVLOWAT in proto_ops.poll methods

Thats a gloriously insane way of trying to do HTTP/1.1, and one I'm not
sure is actually viable in the real world because the TCP window may be
smaller than the number of bytes required to find a Host: header - so you
may simply not be able to receive it via MSG_PEEK. In particular mobile
phone gateways have a nasty habit of using very small windows.

> I just don't see a good solution for what I'm doing other than MSG_PEEK
> and SO_RCVLOWAT, any ideas?

I don't either, and while I don't agree that what you are doing for
HTTP/1.1 is remotely sane there are probably other cases this would be
both sane and useful which does suggest fixing it would be beneficial
--
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/