netdev - Re: Suggestions for TC Rust Projects

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]

Date: Wed, 24 Jan 2024 00:10:34 -0600
From: Trevor Gross <tmgross@...ch.edu>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, 
	Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: Suggestions for TC Rust Projects

On Tue, Jan 23, 2024 at 3:23 PM Jamal Hadi Salim <jhs@...atatu.com> wrote:
> [...]
>
> I think a good starting point would be tc actions. You can write a
> simple hello world action.
> Actions will put to test your approach for implementing netlink and
> skbs which are widely used in the net stack for both control(by
> netlink) and the runtime datapath. If you can jump that hoop it will
> open a lot of doors for you into the network stack.
> Here's a simple action:
> https://elixir.bootlin.com/linux/v6.8-rc1/source/net/sched/act_simple.c
> Actually that one may be hiding a lot of abstractions - but if you
> look at it we can discuss what it is hiding.

That sounds great, getting an OOT equivalent should be a feasible
first step. I will pass the information along.

> Note: We have written user space netlink code using rust and it was
> fine but the kernel side is more complex.

Would that be the code at https://github.com/rust-netlink? Seems like
a good reference in any case.

Thanks for the information,
Trevor

> cheers,
> jamal
>
> > We are getting more contributors interested in doing Rust work that
> > are looking for projects, so just collecting some ideas we can point
> > them at.
> >
> > Thanks,
> > Trevor