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 for Android: free password hash cracker in your pocket

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

Message-Id: <20091118.102434.160976750.davem@davemloft.net>
Date:	Wed, 18 Nov 2009 10:24: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:22:54 -0800

> So is this a bug or a feature?

It definitely seems intentional.

> When I call setsockopt() to set this option on a NETLINK socket,
> setsockopt() appears to return 0 to indicate success. If it's not
> going to be supported, shouldn't setsockopt() return -1 with
> ENOPROTOOPT in errno in this case?

There are a lot of socket option values that can be set but which
are not used by the protocol in question.

I don't think any changes need to be made.
--
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