From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Arjan van de Ven <arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"Yan,
Zheng" <zheng.z.yan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 1/5] add metadata_incore ioctl in vfs
Date: Thu, 6 Jan 2011 08:38:48 +0100 [thread overview]
Message-ID: <201101060838.49359.arnd@arndb.de> (raw)
In-Reply-To: <1294276437.1949.578.camel@sli10-conroe>
On Thursday 06 January 2011, Shaohua Li wrote:
> I don't understand. adding a case statement in compat_sys_ioctl, so we will do
> compat_ioctl_check_table(). If I add COMPATIBLE_IOCTL(), then the check
> will success, we will go to the found_handler code path and execute
> do_vfs_ioctl, which is what we want. if not adding COMPATIBLE_IOCTL(),
> the check will fail, and in any case, we will go to the out_fput code
> path, so our ioctl does nothing.
You are correct, I misremembered the code and did not check properly.
> > Two more general comments:
> >
> > - You probably want to add the ioctls to file_ioctl instead of do_vfs_ioctl,
> > so you don't add another case statement to the common path.
> >
> > - I don't know if there are any rules for what should be an ioctl or an
> > fcntl, we're rather inconsistent about this. If you have found a good
> > reason for making it an ioctl, just put that into the changelog so we
> > can refer to it next time.
> it can be applied to a directory too. I thought file_ioctl or fcntl is
> for file.
Right again, good point!
Arnd
next prev parent reply other threads:[~2011-01-06 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 5:40 [PATCH v2 1/5] add metadata_incore ioctl in vfs Shaohua Li
2011-01-04 9:40 ` Arnd Bergmann
[not found] ` <201101041040.31482.arnd-r2nGTMty4D4@public.gmane.org>
2011-01-05 2:17 ` Shaohua Li
2011-01-05 9:42 ` Arnd Bergmann
[not found] ` <201101051042.37181.arnd-r2nGTMty4D4@public.gmane.org>
2011-01-06 1:13 ` Shaohua Li
2011-01-06 7:38 ` Arnd Bergmann [this message]
[not found] ` <201101060838.49359.arnd-r2nGTMty4D4@public.gmane.org>
2011-01-06 7:45 ` Shaohua Li
2011-01-07 14:15 ` Arnd Bergmann
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=201101060838.49359.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=zheng.z.yan-VuQAYsv1563Yd54FQh9/CA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.