From: Torsten Kaiser <just.for.lkml@googlemail.com>
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 20:42:55 +0200 [thread overview]
Message-ID: <64bb37e0908311142y4f9b6a8ex4918ac4dea09a4d2@mail.gmail.com> (raw)
In-Reply-To: <20090831182754.GA3620@infradead.org>
On Mon, Aug 31, 2009 at 8:27 PM, Christoph Hellwig<hch@infradead.org> wrote:
> I think you are right, the constant used is incorrect. Does the small
> patch below fix it for you?
Thanks, I will try it tomorrow.
Torsten
> Index: linux-2.6/fs/xfs/linux-2.6/xfs_ioctl32.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/linux-2.6/xfs_ioctl32.c 2009-08-31 15:25:06.093044591 -0300
> +++ linux-2.6/fs/xfs/linux-2.6/xfs_ioctl32.c 2009-08-31 15:25:10.856544216 -0300
> @@ -619,7 +619,7 @@ xfs_file_compat_ioctl(
> case XFS_IOC_GETVERSION_32:
> cmd = _NATIVE_IOC(cmd, long);
> return xfs_file_ioctl(filp, cmd, p);
> - case XFS_IOC_SWAPEXT: {
> + case XFS_IOC_SWAPEXT_32: {
> struct xfs_swapext sxp;
> struct compat_xfs_swapext __user *sxu = arg;
>
>
next prev parent reply other threads:[~2009-08-31 18:48 UTC|newest]
Thread overview: 14+ 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:57 ` Mark Lord
2009-08-31 12:59 ` Michael Tokarev
2009-08-31 18:14 ` Torsten Kaiser
2009-08-31 18:27 ` Christoph Hellwig
2009-08-31 18:42 ` Torsten Kaiser [this message]
2009-09-01 17:00 ` Torsten Kaiser
2009-09-01 17:55 ` Eric Sandeen
2009-08-31 18:37 ` Tim Walberg
2009-08-31 18:48 ` Christoph Hellwig
2009-08-31 18:49 ` Christoph Hellwig
2009-08-31 19:02 ` 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=64bb37e0908311142y4f9b6a8ex4918ac4dea09a4d2@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--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 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).