All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs compat_ioctl?
Date: Mon, 31 Aug 2009 08:57:10 -0400	[thread overview]
Message-ID: <4A9BC8A6.20503@rtr.ca> (raw)
In-Reply-To: <20090831123010.GA2368@infradead.org>

Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 11:02:51AM +0400, Michael Tokarev wrote:
>> Hello!
>>
>> I tried to resize an xfs filesystem on 64bit 2.6.30 kernel
>> using 32bit userland, and that does not work, in dmesg I see:
>>
>> ioctl32(xfs_growfs:24426): Unknown cmd fd(3) cmd(400c586e){t:'X';sz:12} arg(ffa56df4) on /mnt
>> ioctl32(xfs_growfs:24427): Unknown cmd fd(3) cmd(400c586e){t:'X';sz:12} arg(ff991254) on /mnt
>>
>> so apparently there's no compat_ioctl layer for these ioctls.
>>
>> Are there any plans to add these? :)
> 
> Are you sure you're testing 2.6.30?  The copat ioctls were added in 2.6.28.
..

What command-line flags were you using, Michael ?

I just tried a simple "xfs_growfs -d" here, and it worked fine.
This is 2.6.31-rc7-64bit on top of a 32-bit userland.

Cheers

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Mark Lord <lkml@rtr.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs compat_ioctl?
Date: Mon, 31 Aug 2009 08:57:10 -0400	[thread overview]
Message-ID: <4A9BC8A6.20503@rtr.ca> (raw)
In-Reply-To: <20090831123010.GA2368@infradead.org>

Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 11:02:51AM +0400, Michael Tokarev wrote:
>> Hello!
>>
>> I tried to resize an xfs filesystem on 64bit 2.6.30 kernel
>> using 32bit userland, and that does not work, in dmesg I see:
>>
>> ioctl32(xfs_growfs:24426): Unknown cmd fd(3) cmd(400c586e){t:'X';sz:12} arg(ffa56df4) on /mnt
>> ioctl32(xfs_growfs:24427): Unknown cmd fd(3) cmd(400c586e){t:'X';sz:12} arg(ff991254) on /mnt
>>
>> so apparently there's no compat_ioctl layer for these ioctls.
>>
>> Are there any plans to add these? :)
> 
> Are you sure you're testing 2.6.30?  The copat ioctls were added in 2.6.28.
..

What command-line flags were you using, Michael ?

I just tried a simple "xfs_growfs -d" here, and it worked fine.
This is 2.6.31-rc7-64bit on top of a 32-bit userland.

Cheers

  reply	other threads:[~2009-08-31 12:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  7:02 xfs compat_ioctl? Michael Tokarev
2009-08-31 12:30 ` Christoph Hellwig
2009-08-31 12:30   ` Christoph Hellwig
2009-08-31 12:57   ` Mark Lord [this message]
2009-08-31 12:57     ` Mark Lord
2009-08-31 12:59     ` Michael Tokarev
2009-08-31 12:59       ` Michael Tokarev
2009-08-31 18:14   ` Torsten Kaiser
2009-08-31 18:14     ` Torsten Kaiser
2009-08-31 18:27     ` Christoph Hellwig
2009-08-31 18:27       ` Christoph Hellwig
2009-08-31 18:42       ` Torsten Kaiser
2009-08-31 18:42         ` Torsten Kaiser
2009-09-01 17:00       ` Torsten Kaiser
2009-09-01 17:00         ` Torsten Kaiser
2009-09-01 17:55         ` Eric Sandeen
2009-09-01 17:55           ` Eric Sandeen
2009-08-31 18:37   ` Tim Walberg
2009-08-31 18:37     ` Tim Walberg
2009-08-31 18:48     ` Christoph Hellwig
2009-08-31 18:48       ` Christoph Hellwig
2009-08-31 18:48       ` Christoph Hellwig
2009-08-31 18:49       ` Christoph Hellwig
2009-08-31 18:49         ` Christoph Hellwig
2009-08-31 18:49         ` Christoph Hellwig
2009-08-31 19:02         ` Tim Walberg
2009-08-31 19:02           ` Tim Walberg
2009-09-02 11:51           ` Tim Walberg
2009-09-02 11:51             ` Tim Walberg

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=4A9BC8A6.20503@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=xfs@oss.sgi.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 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.