Florian Westphal <fw@xxxxxxxxx> writes: > Toke Høiland-Jørgensen <toke@xxxxxxxxxx> wrote: >> >> It seems a bit odd to include the file path in the kernel as well. >> > >> > Its needed to be able to re-load the ruleset. >> >> How does that work, exactly? Is this so that the userspace binary can >> query the current ruleset, and feed it back to the kernel expecting it >> to stay the same? > > Yes. > >> Because in that case, if the pinned object goes away >> in the meantime (or changes to a different program), this could lead to >> some really hard to debug errors, where a reload subtly changes the >> behaviour because the BPF program is not in fact the same. > > Correct, but thats kind of expected when the user changes programs > logic. > > Same with a 'nft list ruleset > /etc/nft.txt', reboot, > 'nft -f /etc/nft.txt' fails because user forgot to load/pin the program > first. Right, so under what conditions is the identifier expected to survive, exactly? It's okay if it fails after a reboot, but it should keep working while the system is up? >> > This way was the most simple solution. >> >> My point here was more that if it's just a label for human consumption, >> the comment field should be fine, didn't realise it was needed for the >> tool operation (and see above re: that). > > Yes, this is unfortunate. I would like to avoid introducing an > asymmetry between input and output (as in "... add rule ebpf pinned > bla', but 'nft list ruleset' showing 'ebpf id 42') or similar, UNLESS we > can somehow use that alternate output to reconstruct that was originally > intended. And so far I can only see that happening with storing some > label in the kernel for userspace to consume (elf filename, pinned name, > program name ... ). > > To give an example: > > With 'ebpf id 42', we might be able to let this get echoed back as if > user would have said 'ebpf progname myfilter' (I am making this up!), > just to have a more 'stable' identifier. > > This would make it necessary to also support load-by-program-name, of > course. Seems like this kind of mapping can be done in userspace without involving the kernel? For example, the 'progname' thing could be implemented by defining an nft-specific pinning location so that 'ebpf progname myfilter' is equivalent to 'ebpf pinned /sys/bpf/nft/myfilter' and when nft receives an ID from the kernel it goes looking in /sys/bpf/nft to see if it can find the program with that ID and echoes it with the appropriate progname if it does exist? This could also be extended, so that if a user does '... add rule ebpf file /usr/lib/bpf/myrule.o' the nft binary stashes the id -> .o file mapping somewhere (in /run for instance) so that it can echo back where it got it from later? In either case I'm not really sure that there's much to be gained from asking the kernel to store an additional label with the program rule? -Toke
