From: Jiri Slaby <jslaby@suse.cz>
To: Willy Tarreau <w@1wt.eu>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Tony Luck <tony.luck@intel.com>,
Jiri Slaby <jirislaby@gmail.com>,
raven@themaw.net
Subject: Re: Build broken on s390 and ia64 [was: Linux 2.6.32.58]
Date: Thu, 08 Mar 2012 12:06:25 +0100 [thread overview]
Message-ID: <4F5892B1.3070008@suse.cz> (raw)
In-Reply-To: <20120305223338.GE2930@1wt.eu>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On 03/05/2012 11:33 PM, Willy Tarreau wrote:
> Hi,
>
> On Mon, Mar 05, 2012 at 01:48:24PM +0100, Jiri Slaby wrote:
>>>>> Linus Torvalds (2): Fix autofs compile without CONFIG_COMPAT
>>>>
>>>> But who defines is_compat_task *with* CONFIG_COMPAT on ia64?
>>>>
>>>> fs/autofs4/inode.c: In function 'autofs4_fill_super':
>>>> fs/autofs4/inode.c:345: error: implicit declaration of function
>>>> 'is_compat_task'
>>>
>>> The ia64 compat code got entirely removed, since it was broken:
>>>
>>> 32974ad4907cdde6c9de612cd1b2ee0568fb9409 "[IA64] Remove COMPAT_IA32 support"
>>
>> Yes, but that is even in 2.6.34. So the fix for autofs is incomplete in
>> .32 as it breaks build on configs which used to work.
>
> So in the end, does anybody have an idea what is missing from this patch ?
> I'm not sure that reverting the autofs fix is a right solution either :-/
Nobody relevant? Hmm... I use the attached patch. If there are no
objections, I will add a header there and send to Willy.
thanks,
--
js
suse labs
[-- Attachment #2: ia64-is_compat_task-fix.patch --]
[-- Type: text/x-patch, Size: 437 bytes --]
---
arch/ia64/include/asm/compat.h | 5 +++++
1 file changed, 5 insertions(+)
--- a/arch/ia64/include/asm/compat.h
+++ b/arch/ia64/include/asm/compat.h
@@ -204,4 +204,9 @@ arch_compat_alloc_user_space (long len)
return (void __user *) (((regs->r12 & 0xffffffff) & -16) - len);
}
+/* for !COMPAT this is defined in linux/compat.h */
+#ifdef CONFIG_COMPAT
+#define is_compat_task() (0)
+#endif
+
#endif /* _ASM_IA64_COMPAT_H */
next prev parent reply other threads:[~2012-03-08 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 18:09 Linux 2.6.32.58 Greg KH
2012-03-04 18:09 ` Greg KH
2012-03-04 23:22 ` Willy Tarreau
2012-03-05 11:32 ` Build broken on s390 and ia64 [was: Linux 2.6.32.58] Jiri Slaby
2012-03-05 12:02 ` Heiko Carstens
2012-03-05 12:48 ` Jiri Slaby
2012-03-05 12:54 ` Willy Tarreau
2012-03-05 12:56 ` Jiri Slaby
2012-03-05 13:13 ` Heiko Carstens
2012-03-05 13:18 ` Willy Tarreau
2012-03-05 22:33 ` Willy Tarreau
2012-03-08 11:06 ` Jiri Slaby [this message]
2012-03-08 11:47 ` Willy Tarreau
2012-03-09 5:29 ` Ben Hutchings
2012-03-09 6:57 ` Willy Tarreau
2012-03-09 8:23 ` Jiri Slaby
2012-03-09 8:41 ` Willy Tarreau
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=4F5892B1.3070008@suse.cz \
--to=jslaby@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=raven@themaw.net \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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).