Hello,
Eric W. Biederman wrote:Daniel Lezcano <dlezcano@xxxxxxxxxx> writes:
The kobject events are sent through a netlink message which is not currently perGrumble. I have been conveniently been forgetting about that socket.
network namespace. Shouldn't be useful to have a way to retrieve from the
kobject the network namespace or the uevent socket associated with it ? IMHO
having idr in the kobject + netns pointer associated may help to handle the
sysfs isolation and makes the uevent per namespace trivial, no ?
Similarly we have the user mode helpers to deal with.
For this conversation there is a simple answer. All of that is in the
kobject layer, and works even when you compile sysfs out of your kernel.
Therefore it is a separate problem. And sysfs idr tags have nothing
to do with it.
It is most definitely something we need to come back to. I bet there
are some interesting interactions when you have multiple network devices
with the same name generating events.
Related delta: I've been thinking that uevents should be part of sysfs
not kobject as that's what the userland is gonna associate the event
with. Would that solve the problem you're thinking about?