Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755820AbYFLC4f (ORCPT ); Wed, 11 Jun 2008 22:56:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751839AbYFLC42 (ORCPT ); Wed, 11 Jun 2008 22:56:28 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:39577 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750837AbYFLC42 (ORCPT ); Wed, 11 Jun 2008 22:56:28 -0400 X-Sasl-enc: vU8CuXRTY+HZBr2bMrZStD8945IkPMmTX27IW24Hm7Wi 1213239386 Subject: Re: [PATCH] autofs4: fix 32-bit userspace vs 64-bit kernel communications From: Ian Kent To: Mikael Pettersson Cc: Pavel Emelyanov , autofs mailing list , Linux Kernel Mailing List , Konstantin Khlebnikov In-Reply-To: <18511.57661.944934.513223@harpo.it.uu.se> References: <484FA0B8.2000002@openvz.org> <1213187579.4994.25.camel@raven.themaw.net> <484FC94E.1000209@openvz.org> <1213190100.4994.54.camel@raven.themaw.net> <18511.57661.944934.513223@harpo.it.uu.se> Content-Type: text/plain Date: Thu, 12 Jun 2008 10:52:28 +0800 Message-Id: <1213239148.4994.70.camel@raven.themaw.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-4.fc8) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 742 Lines: 21 On Wed, 2008-06-11 at 16:29 +0200, Mikael Pettersson wrote: > Ian Kent writes: > > What about other arches offer 32-bit within a 64-bit environment (has > > this been the case on sparc64 at some point)? > > What about the compiler padding on these? > > Both ppc64 and sparc64 commonly have 32-bit userspaces. > But 64-bit and mixed 32/64-bit userspaces are of course possible. I believe that both these archs have the same alignment characteristics a x86_64. Can anyone confirm that? Ian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/