linux-kernel - Re: How to mount own file system in linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <84144f020607190156q1de9893ek3e5b800ee181e1a@mail.gmail.com>
Date:	Wed, 19 Jul 2006 11:56:25 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	chinmaya@...omedia.soft.net
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: How to mount own file system in linux

Hi,

On 7/19/06, Chinmaya Mishra <chinmaya4@...il.com> wrote:
> Can you suggest me where I can get some good documents to proceed or any
> dummy code if any.

See fs/ramfs/ for an example. There's also Documentation/filesystems/vfs.txt.

On 7/19/06, Chinmaya Mishra <chinmaya4@...il.com> wrote:
> I have tried this with the following code but it gives some warning
> messages during compilation. The file system is registered but during
> the mount command segmentation fault occurs.

So maybe pay attention to the warnings?

> static struct super_block *rfs_read_super( struct super_block *sb, void
> *buf, int size);
> static struct file_system_type rfs = {"rfs", 0, rfs_read_super, NULL};

There's no read_super in struct file_system_type. See
include/linux/fs.h for details.

> int init_module(void) {

[snip]

> void cleanup_module(void) {

[snip]

This is the old way. You really want to be using module_init and
module_exit macros.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/