From: Alexander Aring <alex.aring@gmail.com>
To: barebox@lists.infradead.org
Subject: [RFC 1/3] ramfs: add foofs for testing
Date: Fri, 28 Feb 2014 08:44:26 +0100 [thread overview]
Message-ID: <1393573468-31105-2-git-send-email-alex.aring@gmail.com> (raw)
In-Reply-To: <1393573468-31105-1-git-send-email-alex.aring@gmail.com>
Signed-off-by: Alexander Aring <alex.aring@gmail.com>
---
fs/ramfs.c | 69 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
diff --git a/fs/ramfs.c b/fs/ramfs.c
index f45a454..4b93c2e 100644
--- a/fs/ramfs.c
+++ b/fs/ramfs.c
@@ -608,6 +608,48 @@ static int ramfs_probe(struct device_d *dev)
return 0;
}
+static int foofs_read(struct device_d *_dev, FILE *f, void *buf, size_t insize)
+{
+ if (f->pos == strlen("Hello World!\n"))
+ return 0;
+
+ return sprintf(buf, "%s", "Hello World!\n");
+}
+
+static int foofs_probe(struct device_d *dev)
+{
+ struct ramfs_inode *n;
+ struct ramfs_priv *priv = xzalloc(sizeof(struct ramfs_priv));
+
+ dev->priv = priv;
+
+ priv->root.name = "/";
+ priv->root.mode = S_IFDIR | S_IRWXU | S_IRWXG | S_IRWXO;
+ priv->root.parent = &priv->root;
+ n = ramfs_get_inode();
+ n->name = strdup(".");
+ n->mode = S_IFDIR;
+ n->parent = &priv->root;
+ n->child = n;
+ priv->root.child = n;
+ n = ramfs_get_inode();
+ n->name = strdup("..");
+ n->mode = S_IFDIR | S_IRWXU | S_IRWXG | S_IRWXO;
+ n->parent = &priv->root;
+ n->child = priv->root.child;
+ priv->root.child->next = n;
+
+ /* just for test zero file read */
+ n = ramfs_get_inode();
+ n->name = strdup("foobar");
+ n->mode = S_IFREG | S_IRWXU | S_IRWXG | S_IRWXO;
+ n->parent = &priv->root;
+ n->child = priv->root.child;
+ priv->root.child->next = n;
+
+ return 0;
+}
+
static void ramfs_remove(struct device_d *dev)
{
free(dev->priv);
@@ -638,8 +680,35 @@ static struct fs_driver_d ramfs_driver = {
}
};
+static struct fs_driver_d foofs_driver = {
+ .create = ramfs_create,
+ .unlink = ramfs_unlink,
+ .open = ramfs_open,
+ .close = ramfs_close,
+ .truncate = ramfs_truncate,
+ .read = foofs_read,
+ .write = ramfs_write,
+ .lseek = ramfs_lseek,
+ .mkdir = ramfs_mkdir,
+ .rmdir = ramfs_rmdir,
+ .opendir = ramfs_opendir,
+ .readdir = ramfs_readdir,
+ .closedir = ramfs_closedir,
+ .stat = ramfs_stat,
+ .symlink = ramfs_symlink,
+ .readlink = ramfs_readlink,
+ .flags = FS_DRIVER_NO_DEV,
+ .drv = {
+ .probe = foofs_probe,
+ .remove = ramfs_remove,
+ .name = "foofs",
+ }
+};
+
+
static int ramfs_init(void)
{
+ register_fs_driver(&foofs_driver);
return register_fs_driver(&ramfs_driver);
}
--
1.9.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-02-28 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 7:44 [RFC 0/3] current read implementation and POSIX Alexander Aring
2014-02-28 7:44 ` Alexander Aring [this message]
2014-02-28 7:56 ` [RFC 1/3] ramfs: add foofs for testing Alexander Aring
2014-03-03 8:36 ` Sascha Hauer
2014-03-03 9:08 ` Alexander Aring
2014-02-28 7:44 ` [RFC 2/3] fs: read: handle zero files Alexander Aring
2014-02-28 7:44 ` [RFC 3/3] libbb: read_full: use read return instead size Alexander Aring
2014-02-28 8:03 ` Alexander Aring
2014-02-28 14:21 ` Sascha Hauer
2014-02-28 17:12 ` Alexander Aring
2014-02-28 17:58 ` Alexander Aring
2014-03-03 8:30 ` Sascha Hauer
2014-03-03 9:04 ` Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1393573468-31105-2-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox