From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Morris Subject: Refactor Netlink connector? Date: Fri, 26 May 2006 16:04:53 -0400 (EDT) Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Evgeniy Polyakov , "David S. Miller" Return-path: Received: from mail5.sea5.speakeasy.net ([69.17.117.7]:20389 "EHLO mail5.sea5.speakeasy.net") by vger.kernel.org with ESMTP id S1751413AbWEZUEz (ORCPT ); Fri, 26 May 2006 16:04:55 -0400 Received: from megaweapon.nightmoose.net (HELO d.namei) ([66.92.66.197]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 26 May 2006 20:04:54 -0000 To: netdev@vger.kernel.org Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org I've been looking through the kernel for new subsytems which might need LSM hooks, and we've got a proliferation of Netlink abstractions: generic Netlink, nfnetlink, connector and kobject_uevent. I think we should look at consolidating some of these schemes, and if possible, into a unififed Netlink API. As a first step, what would it take to adapt the single user of connector (the w1 driver) to use generic Netlink? I suspect that some of the nfnetlink infrastructure can be used more generically, and that a simple API for the common case of kernel->user event notifications could be also be provided. Thoughts? - James -- James Morris