2005-04-27 07:59:47 +04:00
/*
* udev . c
*
* Userspace devfs
*
2004-01-27 06:23:11 +03:00
* Copyright ( C ) 2003 , 2004 Greg Kroah - Hartman < greg @ kroah . com >
2005-04-27 07:59:47 +04:00
*
* This program is free software ; you can redistribute it and / or modify it
* under the terms of the GNU General Public License as published by the
* Free Software Foundation version 2 of the License .
*
* This program is distributed in the hope that it will be useful , but
* WITHOUT ANY WARRANTY ; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE . See the GNU
* General Public License for more details .
*
* You should have received a copy of the GNU General Public License along
* with this program ; if not , write to the Free Software Foundation , Inc . ,
* 675 Mass Ave , Cambridge , MA 0213 9 , USA .
*
*/
2004-03-23 09:22:20 +03:00
# include <stdio.h>
# include <stddef.h>
2005-04-27 07:59:47 +04:00
# include <stdlib.h>
# include <string.h>
2003-12-03 12:08:46 +03:00
# include <ctype.h>
2004-03-23 09:22:20 +03:00
# include <errno.h>
2003-12-30 12:21:06 +03:00
# include <signal.h>
2003-04-10 21:53:46 +04:00
2004-02-24 06:07:25 +03:00
# include "libsysfs/sysfs/libsysfs.h"
2005-04-27 07:59:47 +04:00
# include "udev.h"
2004-03-23 09:22:20 +03:00
# include "udev_lib.h"
2005-04-27 07:59:47 +04:00
# include "udev_version.h"
[PATCH] add udev logging to info log
On Thu, Jan 15, 2004 at 05:14:16AM +0100, Kay Sievers wrote:
> On Wed, Jan 14, 2004 at 01:10:43PM -0800, Greg KH wrote:
> > On Wed, Jan 14, 2004 at 02:34:26PM -0600, Clay Haapala wrote:
> > > On Wed, 14 Jan 2004, Chris Friesen spake thusly:
> > > >
> > > > Maybe for ones with a matching rule, you could print something like:
> > > >
> > > >
> > > Is the act of printing/syslogging a rule in an of itself?
> >
> > No, as currently the only way stuff ends up in the syslog is if
> > DEBUG=true is used on the build line.
> >
> > But it's sounding like we might want to change that... :)
>
> How about this in the syslog after connect/disconnect?
>
> Jan 15 05:07:45 pim udev[28007]: configured rule in '/etc/udev/udev.rules' at line 17 applied, 'video*' becomes 'video/webcam%n'
> Jan 15 05:07:45 pim udev[28007]: creating device node '/udev/video/webcam0'
> Jan 15 05:07:47 pim udev[28015]: removing device node '/udev/video/webcam0'
Here is a slightly better version. I've created a logging.h file and
moved the debug macros from udev.h in there.
If you type:
'make' - you will get a binary that prints one or two lines to syslog
if a device node is created or deleted
'make LOG=false' - you get a binary that prints asolutely nothing
'make DEBUG=true' - the same as today, it will print all debug lines
2004-01-16 08:53:20 +03:00
# include "logging.h"
2003-07-17 12:24:51 +04:00
# include "namedev.h"
2003-10-15 10:20:53 +04:00
# include "udevdb.h"
2005-04-27 07:59:47 +04:00
2003-10-22 07:19:09 +04:00
/* global variables */
char * * main_argv ;
char * * main_envp ;
2004-02-13 05:57:06 +03:00
# ifdef LOG
2004-03-04 11:57:29 +03:00
unsigned char logname [ LOGNAME_SIZE ] ;
2004-02-27 06:40:40 +03:00
void log_message ( int level , const char * format , . . . )
2004-02-12 09:10:26 +03:00
{
2004-02-27 06:40:32 +03:00
va_list args ;
2004-02-13 05:57:06 +03:00
if ( ! udev_log )
return ;
va_start ( args , format ) ;
vsyslog ( level , format , args ) ;
va_end ( args ) ;
2004-02-12 09:10:26 +03:00
}
2004-02-13 05:57:06 +03:00
# endif
2004-02-12 09:10:26 +03:00
2004-06-07 13:56:47 +04:00
__attribute__ ( ( regparm ( 0 ) ) ) static void sig_handler ( int signum )
2003-12-30 12:21:06 +03:00
{
switch ( signum ) {
case SIGINT :
case SIGTERM :
udevdb_exit ( ) ;
exit ( 20 + signum ) ;
default :
2004-06-07 13:56:47 +04:00
dbg ( " unhandled signal %d " , signum ) ;
2003-12-30 12:21:06 +03:00
}
}
2004-01-04 19:08:26 +03:00
static char * subsystem_blacklist [ ] = {
" scsi_host " ,
" scsi_device " ,
2004-01-15 09:55:24 +03:00
" usb_host " ,
" pci_bus " ,
2004-03-03 10:49:04 +03:00
" pcmcia_socket " ,
2004-03-04 11:57:29 +03:00
" "
2004-01-04 19:08:26 +03:00
} ;
2004-02-27 06:40:40 +03:00
static int udev_hotplug ( void )
2003-12-31 09:31:37 +03:00
{
char * action ;
char * devpath ;
char * subsystem ;
int retval = - EINVAL ;
2004-01-04 19:08:26 +03:00
int i ;
2004-02-12 09:29:15 +03:00
struct sigaction act ;
[PATCH] hmm, handle net devices with udev?
Hmm, Arndt Bergmann sent a patch like this one a few weeks ago and
I want to bring the question back, if we want to handle net device
naming with udev.
With this patch it is actually possible to specify something like this
in udev.rules:
KERNEL="dummy*", SYSFS{address}="00:00:00:00:00:00", SYSFS{features}="0x0", NAME="blind%n"
KERNEL="eth*", SYSFS{address}="00:0d:60:77:30:91", NAME="private"
and you will get:
[root@pim udev.kay]# cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1500 30 0 0 0 0 0 0 1500 30 0 0 0 0 0 0
private: 278393 1114 0 0 0 0 0 0 153204 1468 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
blind0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The udevinfo program is also working:
[root@pim udev.kay]# ./udevinfo -a -p /sys/class/net/private
looking at class device '/sys/class/net/private':
SYSFS{addr_len}="6"
SYSFS{address}="00:0d:60:77:30:91"
SYSFS{broadcast}="ff:ff:ff:ff:ff:ff"
SYSFS{features}="0x3a9"
SYSFS{flags}="0x1003"
SYSFS{ifindex}="2"
SYSFS{iflink}="2"
SYSFS{mtu}="1500"
SYSFS{tx_queue_len}="1000"
SYSFS{type}="1"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0':
BUS="pci"
ID="0000:02:01.0"
SYSFS{class}="0x020000"
SYSFS{detach_state}="0"
SYSFS{device}="0x101e"
SYSFS{irq}="11"
SYSFS{subsystem_device}="0x0549"
SYSFS{subsystem_vendor}="0x1014"
SYSFS{vendor}="0x8086"
The matching device will be renamed to the given name. The device name
will not be put into the udev database, cause the kernel renames the
device and the sysfs name disappears.
I like it, cause it plugs in nicely. We have all the naming features
and sysfs queries and walks inside of udev. The sysfs timing races
are already solved and the management tools are working for net devices
too. nameif can only match the MAC address now. udev can match any sysfs
value of the device tree the net device is connected to.
But right, net devices do not have device nodes :)
2004-03-25 10:19:39 +03:00
const int nofake = 0 ;
2003-12-31 09:31:37 +03:00
2004-01-27 06:23:11 +03:00
action = get_action ( ) ;
if ( ! action ) {
2004-02-24 06:31:14 +03:00
dbg ( " no action? " ) ;
2004-01-27 06:23:11 +03:00
goto exit ;
}
2003-07-21 07:48:48 +04:00
2003-10-22 07:19:09 +04:00
devpath = get_devpath ( ) ;
if ( ! devpath ) {
2004-02-24 06:31:14 +03:00
dbg ( " no devpath? " ) ;
2003-07-19 16:06:55 +04:00
goto exit ;
}
2003-11-25 09:27:17 +03:00
dbg ( " looking at '%s' " , devpath ) ;
2003-07-17 12:24:51 +04:00
2003-07-19 16:06:55 +04:00
/* we only care about class devices and block stuff */
2003-10-22 07:19:09 +04:00
if ( ! strstr ( devpath , " class " ) & &
! strstr ( devpath , " block " ) ) {
2003-11-25 09:27:17 +03:00
dbg ( " not a block or class device " ) ;
2003-07-19 16:06:55 +04:00
goto exit ;
}
2003-07-17 07:18:06 +04:00
2004-01-04 19:08:26 +03:00
/* skip blacklisted subsystems */
2004-02-27 06:40:40 +03:00
subsystem = get_subsystem ( main_argv [ 1 ] ) ;
2004-02-24 06:31:14 +03:00
if ( ! subsystem ) {
dbg ( " no subsystem? " ) ;
goto exit ;
}
2004-01-04 19:08:26 +03:00
i = 0 ;
while ( subsystem_blacklist [ i ] [ 0 ] ! = ' \0 ' ) {
if ( strcmp ( subsystem , subsystem_blacklist [ i ] ) = = 0 ) {
dbg ( " don't care about '%s' devices " , subsystem ) ;
goto exit ;
}
i + + ;
2003-07-21 07:48:48 +04:00
}
2005-04-27 07:59:47 +04:00
2003-10-15 10:20:53 +04:00
/* initialize udev database */
retval = udevdb_init ( UDEVDB_DEFAULT ) ;
if ( retval ! = 0 ) {
2003-11-25 09:27:17 +03:00
dbg ( " unable to initialize database " ) ;
2004-03-25 08:11:13 +03:00
goto exit ;
2003-10-15 10:20:53 +04:00
}
2004-06-07 13:56:47 +04:00
/* set signal handlers */
2004-02-12 09:29:15 +03:00
act . sa_handler = sig_handler ;
sigemptyset ( & act . sa_mask ) ;
act . sa_flags = SA_RESTART ;
sigaction ( SIGINT , & act , NULL ) ;
sigaction ( SIGTERM , & act , NULL ) ;
2003-12-30 12:29:16 +03:00
2004-03-24 05:54:34 +03:00
if ( strcmp ( action , " add " ) = = 0 ) {
namedev_init ( ) ;
[PATCH] hmm, handle net devices with udev?
Hmm, Arndt Bergmann sent a patch like this one a few weeks ago and
I want to bring the question back, if we want to handle net device
naming with udev.
With this patch it is actually possible to specify something like this
in udev.rules:
KERNEL="dummy*", SYSFS{address}="00:00:00:00:00:00", SYSFS{features}="0x0", NAME="blind%n"
KERNEL="eth*", SYSFS{address}="00:0d:60:77:30:91", NAME="private"
and you will get:
[root@pim udev.kay]# cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1500 30 0 0 0 0 0 0 1500 30 0 0 0 0 0 0
private: 278393 1114 0 0 0 0 0 0 153204 1468 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
blind0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The udevinfo program is also working:
[root@pim udev.kay]# ./udevinfo -a -p /sys/class/net/private
looking at class device '/sys/class/net/private':
SYSFS{addr_len}="6"
SYSFS{address}="00:0d:60:77:30:91"
SYSFS{broadcast}="ff:ff:ff:ff:ff:ff"
SYSFS{features}="0x3a9"
SYSFS{flags}="0x1003"
SYSFS{ifindex}="2"
SYSFS{iflink}="2"
SYSFS{mtu}="1500"
SYSFS{tx_queue_len}="1000"
SYSFS{type}="1"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0':
BUS="pci"
ID="0000:02:01.0"
SYSFS{class}="0x020000"
SYSFS{detach_state}="0"
SYSFS{device}="0x101e"
SYSFS{irq}="11"
SYSFS{subsystem_device}="0x0549"
SYSFS{subsystem_vendor}="0x1014"
SYSFS{vendor}="0x8086"
The matching device will be renamed to the given name. The device name
will not be put into the udev database, cause the kernel renames the
device and the sysfs name disappears.
I like it, cause it plugs in nicely. We have all the naming features
and sysfs queries and walks inside of udev. The sysfs timing races
are already solved and the management tools are working for net devices
too. nameif can only match the MAC address now. udev can match any sysfs
value of the device tree the net device is connected to.
But right, net devices do not have device nodes :)
2004-03-25 10:19:39 +03:00
retval = udev_add_device ( devpath , subsystem , nofake ) ;
goto action_done ;
}
if ( strcmp ( action , " remove " ) = = 0 ) {
retval = udev_remove_device ( devpath , subsystem ) ;
goto action_done ;
2003-10-15 10:20:53 +04:00
}
2004-03-24 05:54:34 +03:00
[PATCH] hmm, handle net devices with udev?
Hmm, Arndt Bergmann sent a patch like this one a few weeks ago and
I want to bring the question back, if we want to handle net device
naming with udev.
With this patch it is actually possible to specify something like this
in udev.rules:
KERNEL="dummy*", SYSFS{address}="00:00:00:00:00:00", SYSFS{features}="0x0", NAME="blind%n"
KERNEL="eth*", SYSFS{address}="00:0d:60:77:30:91", NAME="private"
and you will get:
[root@pim udev.kay]# cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1500 30 0 0 0 0 0 0 1500 30 0 0 0 0 0 0
private: 278393 1114 0 0 0 0 0 0 153204 1468 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
blind0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The udevinfo program is also working:
[root@pim udev.kay]# ./udevinfo -a -p /sys/class/net/private
looking at class device '/sys/class/net/private':
SYSFS{addr_len}="6"
SYSFS{address}="00:0d:60:77:30:91"
SYSFS{broadcast}="ff:ff:ff:ff:ff:ff"
SYSFS{features}="0x3a9"
SYSFS{flags}="0x1003"
SYSFS{ifindex}="2"
SYSFS{iflink}="2"
SYSFS{mtu}="1500"
SYSFS{tx_queue_len}="1000"
SYSFS{type}="1"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0':
BUS="pci"
ID="0000:02:01.0"
SYSFS{class}="0x020000"
SYSFS{detach_state}="0"
SYSFS{device}="0x101e"
SYSFS{irq}="11"
SYSFS{subsystem_device}="0x0549"
SYSFS{subsystem_vendor}="0x1014"
SYSFS{vendor}="0x8086"
The matching device will be renamed to the given name. The device name
will not be put into the udev database, cause the kernel renames the
device and the sysfs name disappears.
I like it, cause it plugs in nicely. We have all the naming features
and sysfs queries and walks inside of udev. The sysfs timing races
are already solved and the management tools are working for net devices
too. nameif can only match the MAC address now. udev can match any sysfs
value of the device tree the net device is connected to.
But right, net devices do not have device nodes :)
2004-03-25 10:19:39 +03:00
dbg ( " unknown action '%s' " , action ) ;
retval = - EINVAL ;
action_done :
2003-10-15 10:20:53 +04:00
udevdb_exit ( ) ;
2003-04-10 21:53:46 +04:00
2003-12-08 20:40:40 +03:00
exit :
[PATCH] hmm, handle net devices with udev?
Hmm, Arndt Bergmann sent a patch like this one a few weeks ago and
I want to bring the question back, if we want to handle net device
naming with udev.
With this patch it is actually possible to specify something like this
in udev.rules:
KERNEL="dummy*", SYSFS{address}="00:00:00:00:00:00", SYSFS{features}="0x0", NAME="blind%n"
KERNEL="eth*", SYSFS{address}="00:0d:60:77:30:91", NAME="private"
and you will get:
[root@pim udev.kay]# cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1500 30 0 0 0 0 0 0 1500 30 0 0 0 0 0 0
private: 278393 1114 0 0 0 0 0 0 153204 1468 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
blind0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The udevinfo program is also working:
[root@pim udev.kay]# ./udevinfo -a -p /sys/class/net/private
looking at class device '/sys/class/net/private':
SYSFS{addr_len}="6"
SYSFS{address}="00:0d:60:77:30:91"
SYSFS{broadcast}="ff:ff:ff:ff:ff:ff"
SYSFS{features}="0x3a9"
SYSFS{flags}="0x1003"
SYSFS{ifindex}="2"
SYSFS{iflink}="2"
SYSFS{mtu}="1500"
SYSFS{tx_queue_len}="1000"
SYSFS{type}="1"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0':
BUS="pci"
ID="0000:02:01.0"
SYSFS{class}="0x020000"
SYSFS{detach_state}="0"
SYSFS{device}="0x101e"
SYSFS{irq}="11"
SYSFS{subsystem_device}="0x0549"
SYSFS{subsystem_vendor}="0x1014"
SYSFS{vendor}="0x8086"
The matching device will be renamed to the given name. The device name
will not be put into the udev database, cause the kernel renames the
device and the sysfs name disappears.
I like it, cause it plugs in nicely. We have all the naming features
and sysfs queries and walks inside of udev. The sysfs timing races
are already solved and the management tools are working for net devices
too. nameif can only match the MAC address now. udev can match any sysfs
value of the device tree the net device is connected to.
But right, net devices do not have device nodes :)
2004-03-25 10:19:39 +03:00
return retval ;
2005-04-27 07:59:47 +04:00
}
2003-12-31 09:31:37 +03:00
2004-03-04 11:57:29 +03:00
int main ( int argc , char * argv [ ] , char * envp [ ] )
2003-12-31 09:31:37 +03:00
{
main_argv = argv ;
main_envp = envp ;
2004-02-02 19:19:41 +03:00
init_logging ( " udev " ) ;
2004-02-27 06:40:40 +03:00
/* initialize our configuration */
udev_init_config ( ) ;
2003-12-31 09:31:37 +03:00
dbg ( " version %s " , UDEV_VERSION ) ;
2004-02-27 06:40:40 +03:00
return udev_hotplug ( ) ;
2003-12-31 09:31:37 +03:00
}