Re: cpumap infinite loop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 05 Mar 2024 at 06:08 PM, Toke Høiland-Jørgensen wrote:
> Tobias Böhm <tobias@xxxxxxxx> writes:
> 
> > Hello,
> >
> > I was playing around a bit with cpumaps and wondered what happens when
> > the attached program just does another CPU redirect to itself.
> >
> > I ended up having an infinite loop. The working example can be found
> > here: https://github.com/aibor/cpumap-loop
> >
> > Now, I wonder if there is a way to detect and break this loop. I took a
> > look at the xdp_md->rx_queue_index values. When executed by a NIC event,
> > the value is the NIC ID, so a fairly low number. After CPU redirection
> > the values I saw were far above the range of NIC queue IDs. I couldn't
> > figure out if it is just a random memory value or if this value still 
> > has a (maybe different) meaning after CPU redirection. Maybe somehow
> > related to the CPU queue?
> 
> It's random. The rxq data structure is not initialised on the stack, so
> it's basically whatever was in that memory. Interestingly, there's a
> TODO comment in there to fix this:
> 
> https://elixir.bootlin.com/linux/latest/source/kernel/bpf/cpumap.c#L195
> 
> Not sure what the intention was here. +Lorenzo, who wrote that code.
> Returning the contents of a random uninitialised stack variable is
> probably not a good idea, though, we should zero out the data structure.
> I'll send a patch for that.

Thank you for the explanation and the patch. :)

> > If the field is set to a meaningful value I can make assumptions about
> > it and would be able to detect previous CPU redirection, I guess.
> >
> > I'd appreciate any pointers and tips how I could detect such a loop. Or
> > maybe there is a way to prevent it in the first place other than "just
> > being careful"?
> 
> Well, you kinda have to go out of your way to construct a loop like
> this. How are you envisioning this would happen accidentally? :)

I totally agree that it is pretty unlikely to create such a loop by accident.
Especially since the map programs usually are rather simple.
My example was driven by pure curiosity, exploring the possibilities of
redirect map programs. And since I saw infinite recursion is possible I
was looking for options for reliable termination conditions. This made me
wonder if I can detect if the program was invoked by the device or by map
redirection.




[Index of Archives]     [Linux Networking Development]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Campsites]

  Powered by Linux