Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1197169

Re: Revisit AF_BUS: is it a better way to implement KDBUS?

Show all headers | View raw

2015-07-31 2:12 GMT+08:00 Andy Lutomirski <luto@amacapital.net>:
>
> I find myself wondering whether an in-kernel *bus* is a good idea at
> all.  Creating a bus that unprivileged programs are allowed to
> broadcast on (which is kind of the point) opens up big cans of worms.

This can be solved in this AF_BUS like this:
* Becoming a bus master needs a proper CAP.
* Impose a bus endpoint to join multicast address "maddr1" first, if
it wants to send to multicast address "maddr2".

The bus endpoint sends the request of joining maddr1, and the bus
master grants it with replying a cmsg(control message) and setting up
a proper eBPF.

Next time, the bus endpoint sends to maddr2, the kernel will allow this if:
1) maddr1 & maddr2 == maddr1
And 2) the eBPF allows it.
 (i.e. the same multicast match logic in this AF_BUS)



-- 
Regards,

- cee1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: Revisit AF_BUS: is it a better way to implement KDBUS? cee1 <fykcee1@gmail.com> - 2015-07-31 18:30 +0200
  Re: Revisit AF_BUS: is it a better way to implement KDBUS? cee1 <fykcee1@gmail.com> - 2015-08-01 04:10 +0200

csiph-web