netdev - Re: Why return E2BIG from bpf map update?

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: <55AD7514.7040906@plumgrid.com>
Date:	Mon, 20 Jul 2015 15:24:20 -0700
From:	Alexei Starovoitov <ast@...mgrid.com>
To:	Alex Gartrell <alexgartrell@...il.com>, daniel@...earbox.net
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: Why return E2BIG from bpf map update?

On 7/20/15 3:15 PM, Alex Gartrell wrote:
> The ship has probably sailed on this one, but it seems like ENOSPC
> makes more sense than E2BIG.  Any chance of changing it so that poor
> ebpf library maintainers in the future don't have to wonder how their
> argument list got too big?

sorry, too late.
It's in tests and even document in bpf manpage:
"E2BIG - indicates that the number of elements in the map reached the
max_entries limit specified at map creation time."
I read E2BIG as "too big" and not as "argument list is too long" :)

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