All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Ron Johnson <ron.l.johnson@cox.net>, linux-ext4@vger.kernel.org
Subject: Re: ioctl32 (was Re: filefrag abort)
Date: Wed, 22 Jul 2009 23:51:07 -0500	[thread overview]
Message-ID: <4A67EC3B.9060503@redhat.com> (raw)
In-Reply-To: <20090722170152.GN4231@webber.adilger.int>

Andreas Dilger wrote:
> On Jul 21, 2009  19:57 -0500, Eric Sandeen wrote:
>> Ron Johnson wrote:
>>> On 2009-07-20 21:03, Theodore Tso wrote:
>>>> On Mon, Jul 20, 2009 at 04:49:04PM -0500, Ron Johnson wrote:
>>>>> Hi,
>>>>>
>>>>> (Is this OT?  http://sourceforge.net/forum/forum.php?forum_id=7052  
>>>>> doesn't show much activity...)
>>>>>
>>>>> Debian Sid, e2fsprogs 1.41.8-1
>>>>> Home-rolled 64-bit 2.6.30 with 32-bit userland
>>>> Should be fixed in e2fsprogs 1.41.8-2
>>> ff seems to work now, but I still get this in dmesg:
>>>
>>> [188883.274547] ioctl32(filefrag:7086): Unknown cmd fd(3) 
>>> cmd(c020660b){t:'f';sz:32} arg(ffacb808) on /some/large/file
>> Huh, did we miss a compat ioctl for fiemap.... looks like so.  I'll look
>> into that tomorrow, thanks.
> 
> Sigh, I wish there was some sort of automatic ioctl parser tool that
> would report if the ioctl will need compat handling or not.  I thought
> the fiemap structs didn't need any compat handling because they are
> properly sized/aligned and w/o pointers...

They are properly sized yep but I think they still have to be flagged:

/* pointer to compatible structure or no argument */
#define COMPATIBLE_IOCTL(cmd) \
        { (cmd), do_ioctl32_pointer },

I have to remind myself how this all works, despite doing a bunch of
ioctl32 work for xfs last year :)

I think adding COMPATIBLE_IOCTL(FS_IOC_FIEMAP); to fs/compat_ioctl.c
should be enough, I'll try to get it tested tomorrow.

-Eric

-Eric

  reply	other threads:[~2009-07-23  4:51 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 [this message]
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             ` ioctl32 Christoph Hellwig

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=4A67EC3B.9060503@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ron.l.johnson@cox.net \
    /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.