From: Christoph Hellwig <hch@infradead.org>
To: An?bal Monsalve Salazar <anibal@debian.org>
Cc: Ron Johnson <ron.l.johnson@cox.net>,
debian-amd64@lists.debian.org, xfs@oss.sgi.com
Subject: Re: ia32 userland and XFS
Date: Tue, 2 Dec 2008 04:52:44 -0500 [thread overview]
Message-ID: <20081202095244.GA18292@infradead.org> (raw)
In-Reply-To: <20081202093350.GC20730@debianrules.debiancolombia.org>
On Tue, Dec 02, 2008 at 08:33:50PM +1100, An?bal Monsalve Salazar wrote:
> On Mon, Dec 01, 2008 at 07:37:16PM -0600, Ron Johnson wrote:
> >According to this (seemingly 2+ year old) web page, the XFS file system
> >chokes on the combination of 32 bit userland and 64 bit kernel.
> >
> >Is this still true, and why should a low-level driver hidden under a
> >virtual fs care what user apps access it via the vfs?
XFS as in the plain posix filesystem works perfectly fine with a 64 bit
kernel and 32 bit userspace.
But various advance capabilities or administration interfaces which are
used by tools from xfsprogs are implemented as ioctls, and unfortunately
most of them have been designed very badly and aren't wordsize clean.
There have been handlers for a few of them for a while, but only as of
today a full set of compat handlers has been commited. That code will be
release with 2.6.29, but could also be backported.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-02 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4934914C.7050707@cox.net>
2008-12-02 9:33 ` ia32 userland and XFS Aníbal Monsalve Salazar
2008-12-02 9:52 ` 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=20081202095244.GA18292@infradead.org \
--to=hch@infradead.org \
--cc=anibal@debian.org \
--cc=debian-amd64@lists.debian.org \
--cc=ron.l.johnson@cox.net \
--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