I'm going to be mounting a filesystem that uses a block device from inside
the kernel. This mount will not be visible from userland nor can it be
unmounted from userland. Is anyone else doing something like this so we can
coordinate on the changes needed to fs/super.c?
John
On Mon, 27 Nov 2000, John Zielinski wrote:
> I'm going to be mounting a filesystem that uses a block device from inside
> the kernel. This mount will not be visible from userland nor can it be
> unmounted from userland. Is anyone else doing something like this so we can
> coordinate on the changes needed to fs/super.c?
No changes needed. Check kern_mount().
> On Mon, 27 Nov 2000, John Zielinski wrote:
>
> > I'm going to be mounting a filesystem that uses a block device from
inside
> > the kernel. This mount will not be visible from userland nor can it be
> > unmounted from userland. Is anyone else doing something like this so we
can
> > coordinate on the changes needed to fs/super.c?
>
> No changes needed. Check kern_mount().
Oops. Should have said 'physical' block device. The kern_mount() function
calls get_unnamed_dev(). I want to modify it so that it also takes an 'char
* dev_name' and does the same thing as the code in do_mount() which picks
which get_sb_???() functions to call.
I'll just make a kern_mount2() until all the other code that calls
kern_mount is changed so that it passes a "none" or something as the second
parameter.
John