From: Eric Sandeen <sandeen@sandeen.net>
To: Mark Lord <lkml@rtr.ca>
Cc: Eric Sandeen <sandeen@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fs/compat_ioctl.c: add missing FS_IOC_FIEMAP support
Date: Mon, 03 Aug 2009 17:21:30 -0500 [thread overview]
Message-ID: <4A7762EA.5070701@sandeen.net> (raw)
In-Reply-To: <4A775FB9.80600@rtr.ca>
Mark Lord wrote:
> Eric Sandeen wrote:
>> Mark Lord wrote:
>>> (resending, no ack from anyone first time around).
>> I had previously sent a fix for this to the ext4 list as well, although
>> w/o the added case for compat_ioctl or the extra #include.
>>
>> Because this ioctl should be 100% compat everywhere, I don't -think-
>> it's needed, and
>>
>> http://marc.info/?l=linux-ext4&m=124872536713005&w=2
>>
>> suffices....
> ..
>
> Well, whichever of the two works best for the maintainers.
>
> We need *something* for it upstream, and probably back in -stable too.
> Otherwise this prevents using 64-bit kernels on 32-bit userland,
> as Linus likes to recommend so often. ;)
>
> Cheers
>
Heh, it's probably far from the only ioctl missing a compat handler, but
yeah. :)
-Eric
next prev parent reply other threads:[~2009-08-03 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 14:59 [PATCH] fs/compat_ioctl.c: add missing FS_IOC_FIEMAP support Mark Lord
2009-08-01 15:17 ` Mark Lord
2009-08-03 17:48 ` Mark Lord
2009-08-03 18:00 ` Arnd Bergmann
2009-08-03 18:00 ` Eric Sandeen
2009-08-03 22:07 ` Mark Lord
2009-08-03 22:21 ` Eric Sandeen [this message]
2009-08-03 23:22 ` Andrew Morton
2009-08-04 10:39 ` Arnd Bergmann
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=4A7762EA.5070701@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--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 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.