function to zero out module ref count so module can be unloaded in 2.6 kernel?
In 2.4 kernel one could check MOD_IN_USE and repeatedly call MOD_DEC_USE_COUNT until the ref count drops to zero. Is there a function in 2.6 kernel that would zero out the ref count so that module can be unloaded ? Need to implement ioctl for a driver to zero out the ref count. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
function to zero out module ref count so module can be unloaded in 2.6 kernel?
In 2.4 kernel one could check MOD_IN_USE and repeatedly call MOD_DEC_USE_COUNT until the ref count drops to zero. Is there a function in 2.6 kernel that would zero out the ref count so that module can be unloaded ? Need to implement ioctl for a driver to zero out the ref count. Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Ramdisk root filesystem strangeness
Hi
I m sorry if this question doesn't belong to this list. But I couldn't
access the linux-admin list.
Is there support for using RAMDISK as the final root file system
in 2.2.x versions, or is it there in the 2.4.x versions.
I am trying to bring up linux on a diskless server which initially mounts
root FS thru NFS. Then I want to load HDD image to a RAMDISK and use it as
the final root filesystem.
I am not sure whether it is a ready supported or any kernel change will be
required for this?
Any pointers would be helpful.
thanks
vivek
-Original Message-
From: Justin Carlson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 07, 2000 11:52 AM
To: [EMAIL PROTECTED]
Subject: Ramdisk root filesystem strangeness
Am in the midst of bringing up the kernel on a new MIPS variant, and I'm
tryingthe mount a statically linked ramdisk as the root filesystem.
Note, this is NOT using initrd support, I really want to use a ramdisk as my
final filesystem, not as an intermediate step in booting the system.
In blkdev_get(), called from mount_root(), there's some code that grabs
an empty inode, sets up i_rdev, and calls open() for the root device
with the caveat that open() must not examine anything except i_rdev.
in rd_open, though, there's this code snippet:
/*
* Immunize device against invalidate_buffers() and prune_icache().
*/
if (rd_inode[DEVICE_NR(inode->i_rdev)] == NULL) {
if (!inode->i_bdev)
return -ENXIO;
I'm hitting the -ENXIO return, which is based on an uninitialized field of
the
inode structure.
Being relatively new to the code base, I'm not sure what this code is trying
to
do, nor how to fix it. Any suggestions?
The code involved is from the MIPS CVS repository at oss.sgi.com, which was
synced in the past couple days from 2.4.0test11
-Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
---
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
RE: Ramdisk root filesystem strangeness
Hi
I m sorry if this question doesn't belong to this list. But I couldn't
access the linux-admin list.
Is there support for using RAMDISK as the final root file system
in 2.2.x versions, or is it there in the 2.4.x versions.
I am trying to bring up linux on a diskless server which initially mounts
root FS thru NFS. Then I want to load HDD image to a RAMDISK and use it as
the final root filesystem.
I am not sure whether it is a ready supported or any kernel change will be
required for this?
Any pointers would be helpful.
thanks
vivek
-Original Message-
From: Justin Carlson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 07, 2000 11:52 AM
To: [EMAIL PROTECTED]
Subject: Ramdisk root filesystem strangeness
Am in the midst of bringing up the kernel on a new MIPS variant, and I'm
tryingthe mount a statically linked ramdisk as the root filesystem.
Note, this is NOT using initrd support, I really want to use a ramdisk as my
final filesystem, not as an intermediate step in booting the system.
In blkdev_get(), called from mount_root(), there's some code that grabs
an empty inode, sets up i_rdev, and calls open() for the root device
with the caveat that open() must not examine anything except i_rdev.
in rd_open, though, there's this code snippet:
/*
* Immunize device against invalidate_buffers() and prune_icache().
*/
if (rd_inode[DEVICE_NR(inode-i_rdev)] == NULL) {
if (!inode-i_bdev)
return -ENXIO;
I'm hitting the -ENXIO return, which is based on an uninitialized field of
the
inode structure.
Being relatively new to the code base, I'm not sure what this code is trying
to
do, nor how to fix it. Any suggestions?
The code involved is from the MIPS CVS repository at oss.sgi.com, which was
synced in the past couple days from 2.4.0test11
-Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
---
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
