From: Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Some nilfs comments
Date: Tue, 06 Jan 2009 14:55:09 -0500 [thread overview]
Message-ID: <1231271709.4888.27.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>
On Mon, 2008-12-22 at 18:07 +0900, Ryusuke Konishi wrote:
> > I haven't dug too deeply in yet, but if there are parts you're most
> > interested in comments on, please let me know.
>
> Well, I feel that the following two matters are particularlly
> questionable and need to be checked:
>
> - ioctl:
> Ioctl interface (routines and structures) were implemented in an
> own way. These seems to be checked whether to comply with the rules
> of ioctl design.
>
It took me far too long to look at this, I'm sorry. But, looking
through the ioctl code I think you'll have a few (easy to fix) problems.
struct nilfs_argv {
void *v_base;
size_t v_nmembs; /* number of members */
size_t v_size; /* size of members */
int v_index;
int v_flags;
};
The structs that get passed from userland to kernel should use fixed
sized types.
I get around this by using u64s (and __u64s) everywhere. It looks like
you have compat ioctls to fix this too, I find it easier to use the
fixed types.
Otherwise the ioctl code looks pretty reasonable.
-chris
next prev parent reply other threads:[~2009-01-06 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:52 Some nilfs comments Chris Mason
[not found] ` <1229568775.27170.134.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-22 9:07 ` Ryusuke Konishi
[not found] ` <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-22 13:01 ` Reinoud Zandijk
[not found] ` <20081222130152.GA23725-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-12-23 17:23 ` Ryusuke Konishi
[not found] ` <20081224.022337.30445207.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-23 20:49 ` Chris Mason
2008-12-23 1:47 ` Chris Mason
[not found] ` <1229996820.4812.7.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-23 15:57 ` Ryusuke Konishi
2009-01-06 19:55 ` Chris Mason [this message]
[not found] ` <1231271709.4888.27.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2009-01-07 5:20 ` Ryusuke Konishi
[not found] ` <20090107.142009.106620982.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-07 14:16 ` Chris Mason
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=1231271709.4888.27.camel@think.oraclecorp.com \
--to=chris.mason-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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