On Tue, Feb 02, 2010 at 02:57:14PM -0800, Greg KH (email@example.com) wrote:
> > There are at least two ways to fix it: using a big cannon and a small
> > one. The former way is to disable notification registration, since it is
> > not used by anyone at all. Second way is to check whether calling
> > process is root and its destination group is -1 (kind of priveledged
> > one) before command is dispatched to workqueue.
> Well if no one is using it, removing it makes the most sense, right?
> No objection from me, care to make up a patch either way for this?
Getting it is not used, let's drop support for notifications about
(un)registered events from connector.
Another option was to check credentials on receiving, but we can always
restore it without bugs if needed, but genetlink has a wider code base
and none complained, that userspace can not get notification when some
other clients were (un)registered.
Kudos for Sebastian Krahmer <firstname.lastname@example.org>, who found a bug in the
Signed-off-by: Evgeniy Polyakov <email@example.com>
Acked-by: Greg Kroah-Hartman <firstname.lastname@example.org>
Signed-off-by: David S. Miller <email@example.com>