From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
Andreas Dilger <adilger@sun.com>,
Ron Johnson <ron.l.johnson@cox.net>,
linux-ext4@vger.kernel.org
Subject: Re: ioctl32
Date: Sat, 25 Jul 2009 10:46:10 -0400 [thread overview]
Message-ID: <20090725144610.GA9609@infradead.org> (raw)
In-Reply-To: <87k51y11yn.fsf@basil.nowhere.org>
On Fri, Jul 24, 2009 at 06:26:56PM +0200, Andi Kleen wrote:
> > /* pointer to compatible structure or no argument */
> > #define COMPATIBLE_IOCTL(cmd) \
> > { (cmd), do_ioctl32_pointer },
>
>
> The modern way to do this is to use the ->compat_ioctl VFS
> method. COMPATIBLE_IOCTL etc are all obsolete.
>
> > I think adding COMPATIBLE_IOCTL(FS_IOC_FIEMAP); to fs/compat_ioctl.c
> > should be enough, I'll try to get it tested tomorrow.
>
> Nope, add a ->compat_ioctl
>
> When your ioctl is already a unlocked_ioctl you can just use
> the same function. If not convert to unlocked_ioctl first.
fiemap is handled in generic code and never enters ->whatever_ioctl.
Because of that there are only two ways to handle it:
(1) add it to the static translation table in fs/compat_ioctl.c
(2) add a special case to compat_sys_ioctl
Number one is the much simpler solution for a fully compatible ioctl.
prev parent reply other threads:[~2009-07-25 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 21:49 filefrag abort Ron Johnson
2009-07-20 22:16 ` Eric Sandeen
2009-07-21 2:03 ` Theodore Tso
2009-07-22 0:33 ` ioctl32 (was Re: filefrag abort) Ron Johnson
2009-07-22 0:57 ` Eric Sandeen
2009-07-22 17:01 ` Andreas Dilger
2009-07-23 4:51 ` Eric Sandeen
2009-07-24 0:34 ` Ron Johnson
2009-07-24 2:38 ` Eric Sandeen
2009-07-24 16:26 ` ioctl32 Andi Kleen
2009-07-24 16:28 ` ioctl32 Eric Sandeen
2009-07-25 14:46 ` Christoph Hellwig [this message]
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=20090725144610.GA9609@infradead.org \
--to=hch@infradead.org \
--cc=adilger@sun.com \
--cc=andi@firstfloor.org \
--cc=linux-ext4@vger.kernel.org \
--cc=ron.l.johnson@cox.net \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).