linux-kernel - Re: Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1306132028230.24569@aurora.sdinet.de>
Date:	Thu, 13 Jun 2013 20:31:08 +0200 (CEST)
From:	Sven-Haegar Koch <haegar@...net.de>
To:	Willy Tarreau <w@....eu>
cc:	Christoph Biedl <linux-kernel.bfrz@...chmal.in-ulm.de>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error

On Thu, 13 Jun 2013, Willy Tarreau wrote:

> Sven-Haegar, Christoph,
> 
> concerning the issue below, I could reproduce both Sven-Haegar's error (running
> make headers_check with the patch applied) and Christoph's build error with gcc
> 4.7 on i686 without the patch.
> 
> I noticed that neither syscall_trace_enter() nor syscall_trace_leave() were
> called from C code, all were from pure asm. So I simply reverted the first
> patch then removed the two function prototypes and everything is OK for me
> now using gcc 4.7, i686 and x86_64.
> 
> I'm attaching the two patches here to be appled on top of 2.6.32.61, I would
> like it if you could try in your environment to confirm that they correctly
> fix the issue.

hello Willy,

With your two new patches applied on top I was able to build my kernel 
package both using gcc 4.7 (Debian Wheezy) and gcc 4.4 (Debian Squeeze).

(But I did not try rebooting the server yet)

Thanks for the fix!
Haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/