From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Michael Holzheu <holzheu@de.ibm.com>
Cc: ioe-lkml@rameria.de, linux-kernel@vger.kernel.org,
mschwid2@de.ibm.com, joern@wohnheim.fh-wedel.de
Subject: Re: [PATCH/RFC] s390: Hypervisor File System
Date: Tue, 25 Apr 2006 17:33:01 +0300 [thread overview]
Message-ID: <1145975582.11508.13.camel@localhost> (raw)
In-Reply-To: <20060424191941.7aa6412a.holzheu@de.ibm.com>
On Mon, 2006-04-24 at 19:19 +0200, Michael Holzheu wrote:
> +static int hypfs_create_cpu_files(struct super_block *sb,
> + struct dentry *cpus_dir, void *cpu_info)
> +{
> + struct dentry *cpu_dir;
> + char buffer[TMP_SIZE];
Holy cow! That's 1 KB allocated on the stack! Please use kmalloc()
instead.
> +static int hypfs_create_phys_cpu_files(struct super_block *sb,
> + struct dentry *cpus_dir, void *cpu_info)
> +{
> + struct dentry *cpu_dir;
> + char buffer[TMP_SIZE];
Ditto.
> +static ssize_t hypfs_aio_write(struct kiocb *iocb, const char __user *buf,
> + size_t count, loff_t pos)
> +{
> + int rc;
> +
> + mutex_lock(&hypfs_lock);
> + if (last_update_time == get_seconds()) {
> + rc = -EBUSY;
> + goto out;
> + }
> + hypfs_delete_tree(hypfs_sblk->s_root);
To state what I said earlier: the use of a global hypfs_sblk is
problematic because now we can only have the filesystem mounted once. So
I would really like to see some other way of updating. How do you feel
about the s_ops->fs_remount thing?
Pekka
next prev parent reply other threads:[~2006-04-25 14:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 17:19 [PATCH/RFC] s390: Hypervisor File System Michael Holzheu
2006-04-25 6:58 ` Pekka Enberg
2006-04-25 7:32 ` Pekka Enberg
2006-04-25 7:47 ` Andrew Morton
2006-04-25 8:01 ` Pekka Enberg
2006-04-25 8:52 ` Jörn Engel
2006-04-25 9:00 ` Pekka Enberg
2006-04-25 12:22 ` Michael Holzheu
2006-04-25 14:33 ` Pekka Enberg [this message]
2006-04-25 14:45 ` Jörn Engel
2006-04-26 9:30 ` Michael Holzheu
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 11:35 Michael Holzheu
2006-04-21 11:53 ` Pekka Enberg
2006-04-21 13:56 ` Michael Holzheu
2006-04-21 14:55 ` Arnd Bergmann
2006-04-21 15:31 ` Michael Holzheu
2006-04-21 13:32 ` Pekka Enberg
2006-04-21 14:08 ` Michael Holzheu
2006-04-21 15:38 ` Pekka Enberg
2006-04-21 16:40 ` Martin Schwidefsky
2006-04-25 14:04 ` Pekka Enberg
2006-04-21 14:42 ` Pekka Enberg
2006-04-21 14:59 ` Michael Holzheu
2006-04-21 15:41 ` Pekka Enberg
2006-04-21 15:18 ` Jörn Engel
2006-04-21 15:36 ` Michael Holzheu
2006-04-21 15:46 ` Jörn Engel
2006-04-21 22:30 ` Ingo Oeser
2006-04-24 17:17 ` Michael Holzheu
2006-04-24 19:57 ` Ingo Oeser
2006-04-25 6:27 ` Pekka Enberg
2006-04-24 17:19 ` Michael Holzheu
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=1145975582.11508.13.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=holzheu@de.ibm.com \
--cc=ioe-lkml@rameria.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
/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