2003-07-21 07:48:48 +04:00
/*
* Copyright ( C ) 2003 Greg Kroah - Hartman < greg @ kroah . com >
2006-08-28 02:29:11 +04:00
* Copyright ( C ) 2004 - 2006 Kay Sievers < kay . sievers @ vrfy . org >
2003-07-21 07:48:48 +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 . ,
2006-08-28 02:29:11 +04:00
* 51 Franklin Street , Fifth Floor , Boston , MA 02110 - 1301 , USA .
2003-07-21 07:48:48 +04:00
*
*/
# include <stdlib.h>
# include <string.h>
# include <stdio.h>
2006-01-09 23:18:00 +03:00
# include <stddef.h>
2003-07-21 07:48:48 +04:00
# include <fcntl.h>
# include <unistd.h>
# include <errno.h>
2006-02-03 15:52:37 +03:00
# include <grp.h>
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
# include <dirent.h>
2003-10-23 06:39:54 +04:00
# include <sys/stat.h>
2003-11-24 07:56:18 +03:00
# include <sys/types.h>
2003-07-21 07:48:48 +04:00
# include "udev.h"
2005-03-13 00:36:32 +03:00
# include "udev_rules.h"
2005-02-04 23:38:26 +03:00
# include "udev_selinux.h"
2004-10-06 10:39:05 +04:00
2007-06-21 04:28:09 +04:00
# define TMP_FILE_EXT ".udev-tmp"
2003-07-21 07:48:48 +04:00
2006-04-06 00:29:33 +04:00
int udev_node_mknod ( struct udevice * udev , const char * file , dev_t devt , mode_t mode , uid_t uid , gid_t gid )
2004-02-17 08:44:28 +03:00
{
2007-06-21 04:28:09 +04:00
char file_tmp [ PATH_SIZE + sizeof ( TMP_FILE_EXT ) ] ;
2004-04-03 10:16:38 +04:00
struct stat stats ;
2008-07-11 01:54:28 +04:00
int preserve = 0 ;
int err = 0 ;
2004-04-03 10:16:38 +04:00
2006-01-09 23:18:00 +03:00
if ( major ( devt ) ! = 0 & & strcmp ( udev - > dev - > subsystem , " block " ) = = 0 )
2005-06-18 12:57:10 +04:00
mode | = S_IFBLK ;
2006-01-09 23:18:00 +03:00
else
2005-06-18 12:57:10 +04:00
mode | = S_IFCHR ;
2007-06-21 04:28:09 +04:00
if ( lstat ( file , & stats ) = = 0 ) {
2008-07-11 01:54:28 +04:00
if ( ( ( stats . st_mode & S_IFMT ) = = ( mode & S_IFMT ) ) & & ( stats . st_rdev = = devt ) ) {
2008-04-20 23:07:06 +04:00
info ( " preserve file '%s', because it has correct dev_t \n " , file ) ;
2008-07-11 01:54:28 +04:00
preserve = 1 ;
selinux_setfilecon ( file , udev - > dev - > kernel , mode ) ;
} else {
info ( " atomically replace existing file '%s' \n " , file ) ;
strlcpy ( file_tmp , file , sizeof ( file_tmp ) ) ;
strlcat ( file_tmp , TMP_FILE_EXT , sizeof ( file_tmp ) ) ;
unlink ( file_tmp ) ;
selinux_setfscreatecon ( file_tmp , udev - > dev - > kernel , mode ) ;
err = mknod ( file_tmp , mode , devt ) ;
selinux_resetfscreatecon ( ) ;
if ( err ! = 0 ) {
err ( " mknod(%s, %#o, %u, %u) failed: %s \n " ,
file_tmp , mode , major ( devt ) , minor ( devt ) , strerror ( errno ) ) ;
goto exit ;
}
err = rename ( file_tmp , file ) ;
if ( err ! = 0 ) {
err ( " rename(%s, %s) failed: %s \n " ,
file_tmp , file , strerror ( errno ) ) ;
unlink ( file_tmp ) ;
}
2007-06-21 04:28:09 +04:00
}
2007-06-21 11:00:35 +04:00
} else {
2008-07-11 01:54:28 +04:00
info ( " mknod(%s, %#o, (%u,%u)) \n " , file , mode , major ( devt ) , minor ( devt ) ) ;
2007-06-21 11:00:35 +04:00
selinux_setfscreatecon ( file , udev - > dev - > kernel , mode ) ;
2008-07-11 01:54:28 +04:00
err = mknod ( file , mode , devt ) ;
2007-06-21 11:00:35 +04:00
selinux_resetfscreatecon ( ) ;
2008-07-11 01:54:28 +04:00
if ( err ! = 0 ) {
err ( " mknod(%s, %#o, (%u,%u) failed: %s \n " ,
file , mode , major ( devt ) , minor ( devt ) , strerror ( errno ) ) ;
goto exit ;
}
2004-02-17 08:44:28 +03:00
}
2008-07-11 01:54:28 +04:00
if ( ! preserve | | stats . st_mode ! = mode ) {
info ( " chmod(%s, %#o) \n " , file , mode ) ;
err = chmod ( file , mode ) ;
if ( err ! = 0 ) {
err ( " chmod(%s, %#o) failed: %s \n " , file , mode , strerror ( errno ) ) ;
goto exit ;
}
2004-02-17 08:44:28 +03:00
}
2008-07-11 01:54:28 +04:00
if ( ! preserve | | stats . st_uid ! = uid | | stats . st_gid ! = gid ) {
info ( " chown(%s, %u, %u) \n " , file , uid , gid ) ;
err = chown ( file , uid , gid ) ;
if ( err ! = 0 ) {
err ( " chown(%s, %u, %u) failed: %s \n " , file , uid , gid , strerror ( errno ) ) ;
[PATCH] netdev - udevdb+dev.d changes
Here is a patch to change the netdev handling in the database and for
the dev.d/ calls. I applies on top of the udevd.patch, cause klibc has
no sysinfo().
o netdev's are also put into our database now. I want this for the
udevruler gui to get a list of all handled devices.
All devices in the db are stamped with the system uptime value at
the creation time. 'udevinfo -d' prints it.
o the DEVPATH value is the key for udevdb, but if we rename
a netdev, the name is replaced in the kernel, so we add
the changed name to the db to match with the remove event.
NOTE: The dev.d/ scripts still get the original name from the
hotplug call. Should we replace DEVPATH with the new name too?
o We now only add a device to the db, if we have successfully created
the main node or successfully renamed a netdev. This is the main part
of the patch, cause I needed to clean the retval passing trough all
the functions used for node creation.
o DEVNODE sounds a bit ugly for netdev's so I exported DEVNAME too.
Can we change the name?
o I've added a UDEV_NO_DEVD to possibly skip the script execution
and used it in udev-test.pl.
udevstart is the same horror now, if you have scripts with logging
statements in dev.d/ it takes minutes to finish, can we skip the
scripts here too?
o The get_device_type() function is changed to be more strict, cause
'udevinfo -a -p /block/' gets a class device for it and tries to
print the major/minor values.
o bugfix, the RESULT value has now a working newline removal and a test
for this case.
2004-04-01 11:12:57 +04:00
goto exit ;
2004-02-17 08:44:28 +03:00
}
}
[PATCH] netdev - udevdb+dev.d changes
Here is a patch to change the netdev handling in the database and for
the dev.d/ calls. I applies on top of the udevd.patch, cause klibc has
no sysinfo().
o netdev's are also put into our database now. I want this for the
udevruler gui to get a list of all handled devices.
All devices in the db are stamped with the system uptime value at
the creation time. 'udevinfo -d' prints it.
o the DEVPATH value is the key for udevdb, but if we rename
a netdev, the name is replaced in the kernel, so we add
the changed name to the db to match with the remove event.
NOTE: The dev.d/ scripts still get the original name from the
hotplug call. Should we replace DEVPATH with the new name too?
o We now only add a device to the db, if we have successfully created
the main node or successfully renamed a netdev. This is the main part
of the patch, cause I needed to clean the retval passing trough all
the functions used for node creation.
o DEVNODE sounds a bit ugly for netdev's so I exported DEVNAME too.
Can we change the name?
o I've added a UDEV_NO_DEVD to possibly skip the script execution
and used it in udev-test.pl.
udevstart is the same horror now, if you have scripts with logging
statements in dev.d/ it takes minutes to finish, can we skip the
scripts here too?
o The get_device_type() function is changed to be more strict, cause
'udevinfo -a -p /block/' gets a class device for it and tries to
print the major/minor values.
o bugfix, the RESULT value has now a working newline removal and a test
for this case.
2004-04-01 11:12:57 +04:00
exit :
2008-07-11 01:54:28 +04:00
return err ;
2004-02-17 08:44:28 +03:00
}
2007-03-15 05:54:12 +03:00
static int node_symlink ( const char * node , const char * slink )
2006-06-14 18:32:52 +04:00
{
2007-06-21 04:28:09 +04:00
struct stat stats ;
2007-03-15 05:54:12 +03:00
char target [ PATH_SIZE ] = " " ;
2007-06-21 04:28:09 +04:00
char slink_tmp [ PATH_SIZE + sizeof ( TMP_FILE_EXT ) ] ;
2007-03-15 05:54:12 +03:00
int i = 0 ;
int tail = 0 ;
2006-06-14 18:32:52 +04:00
int len ;
2007-06-21 04:28:09 +04:00
int retval = 0 ;
2006-06-14 18:32:52 +04:00
2007-03-15 05:54:12 +03:00
/* use relative link */
while ( node [ i ] & & ( node [ i ] = = slink [ i ] ) ) {
if ( node [ i ] = = ' / ' )
tail = i + 1 ;
i + + ;
}
while ( slink [ i ] ! = ' \0 ' ) {
if ( slink [ i ] = = ' / ' )
strlcat ( target , " ../ " , sizeof ( target ) ) ;
i + + ;
}
strlcat ( target , & node [ tail ] , sizeof ( target ) ) ;
2007-06-21 04:28:09 +04:00
/* preserve link with correct target, do not replace node of other device */
if ( lstat ( slink , & stats ) = = 0 ) {
if ( S_ISBLK ( stats . st_mode ) | | S_ISCHR ( stats . st_mode ) ) {
struct stat stats2 ;
2008-04-20 23:07:06 +04:00
info ( " found existing node instead of symlink '%s' \n " , slink ) ;
2007-06-21 04:28:09 +04:00
if ( lstat ( node , & stats2 ) = = 0 ) {
if ( ( stats . st_mode & S_IFMT ) = = ( stats2 . st_mode & S_IFMT ) & &
stats . st_rdev = = stats2 . st_rdev ) {
2008-04-20 23:07:06 +04:00
info ( " replace device node '%s' with symlink to our node '%s' \n " , slink , node ) ;
2007-06-21 04:28:09 +04:00
} else {
2008-04-20 23:07:06 +04:00
err ( " device node '%s' already exists, link to '%s' will not overwrite it \n " , slink , node ) ;
2007-06-21 04:28:09 +04:00
goto exit ;
}
}
} else if ( S_ISLNK ( stats . st_mode ) ) {
char buf [ PATH_SIZE ] ;
2008-04-20 23:07:06 +04:00
info ( " found existing symlink '%s' \n " , slink ) ;
2007-06-21 04:28:09 +04:00
len = readlink ( slink , buf , sizeof ( buf ) ) ;
if ( len > 0 ) {
buf [ len ] = ' \0 ' ;
if ( strcmp ( target , buf ) = = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " preserve already existing symlink '%s' to '%s' \n " , slink , target ) ;
2007-06-21 04:28:09 +04:00
selinux_setfilecon ( slink , NULL , S_IFLNK ) ;
goto exit ;
}
}
2006-06-14 18:32:52 +04:00
}
2007-06-21 11:00:35 +04:00
} else {
2008-04-20 23:07:06 +04:00
info ( " creating symlink '%s' to '%s' \n " , slink , target ) ;
2007-06-21 11:00:35 +04:00
selinux_setfscreatecon ( slink , NULL , S_IFLNK ) ;
retval = symlink ( target , slink ) ;
selinux_resetfscreatecon ( ) ;
if ( retval = = 0 )
goto exit ;
2006-06-14 18:32:52 +04:00
}
2008-04-20 23:07:06 +04:00
info ( " atomically replace '%s' \n " , slink ) ;
2007-06-21 04:28:09 +04:00
strlcpy ( slink_tmp , slink , sizeof ( slink_tmp ) ) ;
strlcat ( slink_tmp , TMP_FILE_EXT , sizeof ( slink_tmp ) ) ;
2007-06-25 18:03:11 +04:00
unlink ( slink_tmp ) ;
2008-03-13 17:54:21 +03:00
selinux_setfscreatecon ( slink , NULL , S_IFLNK ) ;
2007-06-21 04:28:09 +04:00
retval = symlink ( target , slink_tmp ) ;
selinux_resetfscreatecon ( ) ;
if ( retval ! = 0 ) {
2008-04-20 23:07:06 +04:00
err ( " symlink(%s, %s) failed: %s \n " , target , slink_tmp , strerror ( errno ) ) ;
2007-06-21 04:28:09 +04:00
goto exit ;
}
retval = rename ( slink_tmp , slink ) ;
if ( retval ! = 0 ) {
2008-04-20 23:07:06 +04:00
err ( " rename(%s, %s) failed: %s \n " , slink_tmp , slink , strerror ( errno ) ) ;
2007-06-21 04:28:09 +04:00
unlink ( slink_tmp ) ;
goto exit ;
}
2006-06-14 18:32:52 +04:00
exit :
2007-06-21 04:28:09 +04:00
return retval ;
2006-06-14 18:32:52 +04:00
}
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
static int update_link ( struct udevice * udev , const char * name )
{
LIST_HEAD ( name_list ) ;
char slink [ PATH_SIZE ] ;
char node [ PATH_SIZE ] ;
struct udevice * udev_db ;
struct name_entry * device ;
char target [ PATH_MAX ] = " " ;
int count ;
int priority = 0 ;
int rc = 0 ;
strlcpy ( slink , udev_root , sizeof ( slink ) ) ;
strlcat ( slink , " / " , sizeof ( slink ) ) ;
strlcat ( slink , name , sizeof ( slink ) ) ;
count = udev_db_get_devices_by_name ( name , & name_list ) ;
2008-04-20 23:07:06 +04:00
info ( " found %i devices with name '%s' \n " , count , name ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
2007-03-21 13:55:26 +03:00
/* if we don't have a reference, delete it */
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
if ( count < = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " no reference left, remove '%s' \n " , name ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
if ( ! udev - > test_run ) {
unlink ( slink ) ;
delete_path ( slink ) ;
}
goto out ;
}
/* find the device with the highest priority */
list_for_each_entry ( device , & name_list , node ) {
2008-04-20 23:07:06 +04:00
info ( " found '%s' for '%s' \n " , device - > name , name ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
/* did we find ourself? we win, if we have the same priority */
if ( strcmp ( udev - > dev - > devpath , device - > name ) = = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " compare (our own) priority of '%s' %i >= %i \n " ,
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
udev - > dev - > devpath , udev - > link_priority , priority ) ;
2007-09-20 21:38:58 +04:00
if ( strcmp ( udev - > name , name ) = = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " '%s' is our device node, database inconsistent, skip link update \n " , udev - > name ) ;
2007-09-20 21:38:58 +04:00
} else if ( target [ 0 ] = = ' \0 ' | | udev - > link_priority > = priority ) {
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
priority = udev - > link_priority ;
strlcpy ( target , udev - > name , sizeof ( target ) ) ;
}
continue ;
}
2007-09-20 21:38:58 +04:00
/* another device, read priority from database */
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
udev_db = udev_device_init ( NULL ) ;
if ( udev_db = = NULL )
continue ;
if ( udev_db_get_device ( udev_db , device - > name ) = = 0 ) {
2007-09-12 02:21:53 +04:00
if ( strcmp ( udev_db - > name , name ) = = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " '%s' is a device node of '%s', skip link update \n " , udev_db - > name , device - > name ) ;
2007-09-12 02:21:53 +04:00
} else {
2008-04-20 23:07:06 +04:00
info ( " compare priority of '%s' %i > %i \n " ,
2007-09-12 02:21:53 +04:00
udev_db - > dev - > devpath , udev_db - > link_priority , priority ) ;
if ( target [ 0 ] = = ' \0 ' | | udev_db - > link_priority > priority ) {
priority = udev_db - > link_priority ;
strlcpy ( target , udev_db - > name , sizeof ( target ) ) ;
}
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
}
}
udev_device_cleanup ( udev_db ) ;
}
name_list_cleanup ( & name_list ) ;
if ( target [ 0 ] = = ' \0 ' ) {
2008-04-20 23:07:06 +04:00
info ( " no current target for '%s' found \n " , name ) ;
2007-09-12 02:21:53 +04:00
rc = 1 ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
goto out ;
}
/* create symlink to the target with the highest priority */
strlcpy ( node , udev_root , sizeof ( node ) ) ;
strlcat ( node , " / " , sizeof ( node ) ) ;
strlcat ( node , target , sizeof ( node ) ) ;
2008-04-20 23:07:06 +04:00
info ( " '%s' with target '%s' has the highest priority %i, create it \n " , name , target , priority ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
if ( ! udev - > test_run ) {
create_path ( slink ) ;
node_symlink ( node , slink ) ;
}
out :
return rc ;
}
void udev_node_update_symlinks ( struct udevice * udev , struct udevice * udev_old )
{
struct name_entry * name_loop ;
char symlinks [ PATH_SIZE ] = " " ;
list_for_each_entry ( name_loop , & udev - > symlink_list , node ) {
2008-04-20 23:07:06 +04:00
info ( " update symlink '%s' of '%s' \n " , name_loop - > name , udev - > dev - > devpath ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
update_link ( udev , name_loop - > name ) ;
strlcat ( symlinks , udev_root , sizeof ( symlinks ) ) ;
strlcat ( symlinks , " / " , sizeof ( symlinks ) ) ;
strlcat ( symlinks , name_loop - > name , sizeof ( symlinks ) ) ;
strlcat ( symlinks , " " , sizeof ( symlinks ) ) ;
}
/* export symlinks to environment */
remove_trailing_chars ( symlinks , ' ' ) ;
if ( symlinks [ 0 ] ! = ' \0 ' )
setenv ( " DEVLINKS " , symlinks , 1 ) ;
/* update possible left-over symlinks (device metadata changed) */
if ( udev_old ! = NULL ) {
struct name_entry * link_loop ;
struct name_entry * link_old_loop ;
int found ;
/* remove current symlinks from old list */
2007-03-21 13:55:26 +03:00
list_for_each_entry ( link_old_loop , & udev_old - > symlink_list , node ) {
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
found = 0 ;
list_for_each_entry ( link_loop , & udev - > symlink_list , node ) {
if ( strcmp ( link_old_loop - > name , link_loop - > name ) = = 0 ) {
found = 1 ;
break ;
}
}
if ( ! found ) {
/* link does no longer belong to this device */
2008-04-20 23:07:06 +04:00
info ( " update old symlink '%s' no longer belonging to '%s' \n " ,
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
link_old_loop - > name , udev - > dev - > devpath ) ;
update_link ( udev , link_old_loop - > name ) ;
}
}
2007-03-19 13:57:54 +03:00
2007-03-21 13:55:26 +03:00
/*
* if the node name has changed , delete the node ,
* or possibly restore a symlink of another device
*/
if ( strcmp ( udev - > name , udev_old - > name ) ! = 0 )
update_link ( udev , udev_old - > name ) ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
}
}
int udev_node_add ( struct udevice * udev )
2004-03-02 10:31:06 +03:00
{
2005-03-07 06:29:43 +03:00
char filename [ PATH_SIZE ] ;
2005-03-10 04:46:26 +03:00
uid_t uid ;
gid_t gid ;
2005-03-05 07:35:31 +03:00
int i ;
2006-04-06 00:29:33 +04:00
int retval = 0 ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
strlcpy ( filename , udev_root , sizeof ( filename ) ) ;
strlcat ( filename , " / " , sizeof ( filename ) ) ;
strlcat ( filename , udev - > name , sizeof ( filename ) ) ;
2007-03-15 05:54:12 +03:00
create_path ( filename ) ;
2003-11-12 14:48:01 +03:00
2005-03-10 04:46:26 +03:00
if ( strcmp ( udev - > owner , " root " ) = = 0 )
uid = 0 ;
else {
2003-11-12 14:47:57 +03:00
char * endptr ;
2005-03-10 04:46:26 +03:00
unsigned long id ;
2005-02-09 10:43:18 +03:00
2005-03-10 04:46:26 +03:00
id = strtoul ( udev - > owner , & endptr , 10 ) ;
2004-01-20 06:44:24 +03:00
if ( endptr [ 0 ] = = ' \0 ' )
2003-11-12 14:47:57 +03:00
uid = ( uid_t ) id ;
2005-03-06 08:16:52 +03:00
else
uid = lookup_user ( udev - > owner ) ;
2003-11-12 14:47:57 +03:00
}
2005-03-10 04:46:26 +03:00
if ( strcmp ( udev - > group , " root " ) = = 0 )
gid = 0 ;
else {
2003-11-12 14:47:57 +03:00
char * endptr ;
2005-03-10 04:46:26 +03:00
unsigned long id ;
2005-02-09 10:43:18 +03:00
2005-03-10 04:46:26 +03:00
id = strtoul ( udev - > group , & endptr , 10 ) ;
2004-01-20 06:44:24 +03:00
if ( endptr [ 0 ] = = ' \0 ' )
2003-11-12 14:47:57 +03:00
gid = ( gid_t ) id ;
2005-03-06 08:16:52 +03:00
else
2005-03-18 12:00:25 +03:00
gid = lookup_group ( udev - > group ) ;
2003-11-12 14:47:57 +03:00
}
2008-04-20 23:07:06 +04:00
info ( " creating device node '%s', major=%d, minor=%d, mode=%#o, uid=%d, gid=%d \n " ,
2006-01-25 04:18:13 +03:00
filename , major ( udev - > devt ) , minor ( udev - > devt ) , udev - > mode , uid , gid ) ;
if ( ! udev - > test_run )
2006-04-06 00:29:33 +04:00
if ( udev_node_mknod ( udev , filename , udev - > devt , udev - > mode , uid , gid ) ! = 0 ) {
retval = - 1 ;
goto exit ;
}
2006-01-25 04:18:13 +03:00
setenv ( " DEVNAME " , filename , 1 ) ;
2004-02-17 08:44:28 +03:00
[PATCH] netdev - udevdb+dev.d changes
Here is a patch to change the netdev handling in the database and for
the dev.d/ calls. I applies on top of the udevd.patch, cause klibc has
no sysinfo().
o netdev's are also put into our database now. I want this for the
udevruler gui to get a list of all handled devices.
All devices in the db are stamped with the system uptime value at
the creation time. 'udevinfo -d' prints it.
o the DEVPATH value is the key for udevdb, but if we rename
a netdev, the name is replaced in the kernel, so we add
the changed name to the db to match with the remove event.
NOTE: The dev.d/ scripts still get the original name from the
hotplug call. Should we replace DEVPATH with the new name too?
o We now only add a device to the db, if we have successfully created
the main node or successfully renamed a netdev. This is the main part
of the patch, cause I needed to clean the retval passing trough all
the functions used for node creation.
o DEVNODE sounds a bit ugly for netdev's so I exported DEVNAME too.
Can we change the name?
o I've added a UDEV_NO_DEVD to possibly skip the script execution
and used it in udev-test.pl.
udevstart is the same horror now, if you have scripts with logging
statements in dev.d/ it takes minutes to finish, can we skip the
scripts here too?
o The get_device_type() function is changed to be more strict, cause
'udevinfo -a -p /block/' gets a class device for it and tries to
print the major/minor values.
o bugfix, the RESULT value has now a working newline removal and a test
for this case.
2004-04-01 11:12:57 +04:00
/* create all_partitions if requested */
2005-02-14 08:03:06 +03:00
if ( udev - > partitions ) {
2005-12-17 18:20:51 +03:00
char partitionname [ PATH_SIZE ] ;
2006-01-09 23:18:00 +03:00
char * attr ;
2005-02-09 10:43:18 +03:00
int range ;
/* take the maximum registered minor range */
2006-01-09 23:18:00 +03:00
attr = sysfs_attr_get_value ( udev - > dev - > devpath , " range " ) ;
2007-06-03 02:01:46 +04:00
if ( attr ! = NULL ) {
2006-01-09 23:18:00 +03:00
range = atoi ( attr ) ;
2005-02-09 10:43:18 +03:00
if ( range > 1 )
udev - > partitions = range - 1 ;
}
2008-04-20 23:07:06 +04:00
info ( " creating device partition nodes '%s[1-%i]' \n " , filename , udev - > partitions ) ;
2004-10-19 06:11:51 +04:00
if ( ! udev - > test_run ) {
for ( i = 1 ; i < = udev - > partitions ; i + + ) {
2005-02-21 15:44:39 +03:00
dev_t part_devt ;
2005-03-07 06:29:43 +03:00
snprintf ( partitionname , sizeof ( partitionname ) , " %s%d " , filename , i ) ;
partitionname [ sizeof ( partitionname ) - 1 ] = ' \0 ' ;
[PATCH] fix stupid all_partitions bug
> On Mon, 2005-04-11 at 14:55 +0200, Norbert Preining wrote:
> > On Mon, 11 Apr 2005, Kay Sievers wrote:
> > > > brw-rw---- 1 root root 8, 0 2005-04-10 14:58 /dev/sdcard
> > > > brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard1
> > > > brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard2
> > > > brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard3
> > >
> > > This looks broken.
> >
> > Good to hear.
Yeah, I guess it's broken. In create_node() in udev_add.c there is
always added 1 to the minor number, thus the error. The attached patch
should fix this.
2005-04-12 03:05:03 +04:00
part_devt = makedev ( major ( udev - > devt ) , minor ( udev - > devt ) + i ) ;
2006-04-06 00:29:33 +04:00
udev_node_mknod ( udev , partitionname , part_devt , udev - > mode , uid , gid ) ;
2004-02-17 08:58:25 +03:00
}
2004-02-17 08:44:28 +03:00
}
2003-12-07 20:12:07 +03:00
}
2006-04-06 00:29:33 +04:00
exit :
return retval ;
2003-07-21 07:48:48 +04:00
}
2006-04-13 00:08:05 +04:00
int udev_node_remove ( struct udevice * udev )
{
char filename [ PATH_SIZE ] ;
char partitionname [ PATH_SIZE ] ;
struct stat stats ;
2007-03-21 13:55:26 +03:00
int retval = 0 ;
2006-04-13 00:08:05 +04:00
int num ;
priority based symlink handling
Symlinks can have priorities now, the priority is assigned to the device
and specified with OPTIONS="link_priority=100". Devices with higher
priorities overwrite the symlinks of devices with lower priorities.
If the device, that currently owns the link goes away, the symlink
will be removed, and recreated, pointing to the next device with the
highest actual priority.
This should solve the issue, that inserting an USB-stick may overwrite the
/dev/disk/by-id/-link of another disk, and removes the entire link after the
USB-stick is disconnected. If no priorities are specified, the new link will
overwrite the current one, and if the device goes away, it will restore
the old link. It should be possible to assign lower priorities to removable
devices, if needed.
In multipath setups, we see several devices, which all connect to the same
volume, and therefore all try to create the same metadata-links. The
different path-devices are combined into one device-mapper device, which also
contains the same metadata. It should be possible, to assign multipath-table
device-mapper devices a higher priority, so path-devices that appear and
disappear, will not overwrite or delete the device-mapper device links.
2007-03-18 14:51:57 +03:00
strlcpy ( filename , udev_root , sizeof ( filename ) ) ;
strlcat ( filename , " / " , sizeof ( filename ) ) ;
strlcat ( filename , udev - > name , sizeof ( filename ) ) ;
2006-04-06 00:29:33 +04:00
if ( stat ( filename , & stats ) ! = 0 ) {
2008-04-20 23:07:06 +04:00
info ( " device node '%s' not found \n " , filename ) ;
2007-12-29 19:19:06 +03:00
return 0 ;
2006-04-06 00:29:33 +04:00
}
if ( udev - > devt & & stats . st_rdev ! = udev - > devt ) {
2008-04-20 23:07:06 +04:00
info ( " device node '%s' points to a different device, skip removal \n " , filename ) ;
2006-04-06 00:29:33 +04:00
return - 1 ;
}
2008-04-20 23:07:06 +04:00
info ( " removing device node '%s' \n " , filename ) ;
2007-03-21 13:55:26 +03:00
if ( ! udev - > test_run )
retval = unlink_secure ( filename ) ;
2006-04-06 00:29:33 +04:00
if ( retval )
return retval ;
setenv ( " DEVNAME " , filename , 1 ) ;
num = udev - > partitions ;
if ( num > 0 ) {
2006-04-13 00:08:05 +04:00
int i ;
2008-04-20 23:07:06 +04:00
info ( " removing all_partitions '%s[1-%i]' \n " , filename , num ) ;
2007-03-16 23:15:54 +03:00
if ( num > 255 )
2006-04-06 00:29:33 +04:00
return - 1 ;
for ( i = 1 ; i < = num ; i + + ) {
snprintf ( partitionname , sizeof ( partitionname ) , " %s%d " , filename , i ) ;
partitionname [ sizeof ( partitionname ) - 1 ] = ' \0 ' ;
2007-03-21 13:55:26 +03:00
if ( ! udev - > test_run )
unlink_secure ( partitionname ) ;
2004-10-19 06:28:39 +04: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
}
2007-03-15 05:54:12 +03:00
delete_path ( filename ) ;
2003-07-21 07:48:48 +04:00
return retval ;
}