netdev - Re: NETLINK sockets dont honor SO

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: <20091118.104434.185425439.davem@davemloft.net>
Date:	Wed, 18 Nov 2009 10:44:34 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jharan@...cade.COM
Cc:	netdev@...r.kernel.org
Subject: Re: NETLINK sockets dont honor SO_RCVLOWAT?

From: Jeff Haran <jharan@...cade.COM>
Date: Wed, 18 Nov 2009 10:41:06 -0800

> The operative term is "shall". The RFCs define "shall" to be
> required behavior. I realize the RFCs do not dictate how Linux
> works, but even the common English language usage of the word
> "shall" conveys this meaning.

The low water mark can be seen as a hint, therefore we can
apply the term "support" loosely here.

And the errors are advisory, just like things like -EFAULT.

Look, I'm not going to add a feature flag or some callback just to
handle this.

You have to know what kind of protocol you are working with, and
therefore which socket options make any sense for it.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html