[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <8B32DE36-9AD0-4418-86D8-4E453AA910DB@whamcloud.com>
Date: Sat, 20 Aug 2011 00:23:24 -0600
From: Andreas Dilger <adilger@...mcloud.com>
To: Ted Ts'o <tytso@....edu>
Cc: Bernd Schubert <bernd.schubert@...m.fraunhofer.de>,
linux-nfs@...r.kernel.org, linux-ext4@...r.kernel.org,
bfields@...ldses.org, bernd.schubert@...tmail.fm,
hch@...radead.org, yong.fan@...mcloud.com,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 3 2/4] Return 32/64-bit dir name hash according to usage type
On 2011-08-19, at 4:29 PM, Ted Ts'o wrote:
> On Tue, Aug 16, 2011 at 01:54:14PM +0200, Bernd Schubert wrote:
>> +static inline int is_32bit_api(void)
>> +{
>> +#ifdef HAVE_IS_COMPAT_TASK
>> + return is_compat_task();
>> +#else
>> + return (BITS_PER_LONG == 32);
>> +#endif
>
> I assume is_compat_task() is coming from another patch? What is the
> status of that change?
No, is_compat_task() is upstream for most (all?) of the architectures
that support hybrid 32-/64-bit operation. It is set at 32-bit syscall
entry when running on 64-bit architectures.
The only minor error in this patch (fixed with a new version from Bernd)
is that this should be under CONFIG_COMPAT instead of HAVE_IS_COMPAT_TASK.
> In the case where is_compat_task() is not defined, we can't just test
> based on BITS_PER_LONG == 32, since even on an x86_64 machine, it's
> possible we're running a 32-bit binary in compat mode....
It is definitely available on x86_64.
Cheers, Andreas
--
Andreas Dilger
Principal Engineer
Whamcloud, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists