On Fri, Jun 27, 2014 at 5:21 PM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > On Fri, Jun 27, 2014 at 5:06 PM, Alexei Starovoitov <ast@xxxxxxxxxxxx> wrote: >> this socket filter example does: >> >> - creates a hashtable in kernel with key 4 bytes and value 8 bytes >> >> - populates map[6] = 0; map[17] = 0; // 6 - tcp_proto, 17 - udp_proto >> >> - loads eBPF program: >> r0 = skb[14 + 9]; // load one byte of ip->proto >> *(u32*)(fp - 4) = r0; >> value = bpf_map_lookup_elem(map_id, fp - 4); >> if (value) >> (*(u64*)value) += 1; > > In the code below, this is XADD. Is there anything that validates > that shared things like this can only be poked at by atomic > operations? Correct. The asm code uses xadd to increment packet stats. It's up to the program itself to decide what it's doing. Some programs may prefer speed vs accuracy when counting and they will be using regular "ld, add, st", instead of xadd. Verifier checks that programs can only access a valid memory region. The program itself needs to do something sensible with it. Theoretically I can add a check to verifier that shared map elements are read-only and xadd-only, but that limits usability and unnecessary. We actually do have a use case when we do a regular add, since 'lock add' is too costly at high event rates. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
