public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error
Date: Thu, 13 Jun 2013 20:41:56 +0200	[thread overview]
Message-ID: <20130613184156.GE27760@1wt.eu> (raw)
In-Reply-To: <alpine.DEB.2.10.1306132028230.24569@aurora.sdinet.de>

On Thu, Jun 13, 2013 at 08:31:08PM +0200, Sven-Haegar Koch wrote:
> 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).

Great, thanks for the report!

> (But I did not try rebooting the server yet)

no pb, usually on that old kernels, we get build failure reports in the week of
the release and boot issues during the next month because it seems that not that
many people use them on machines where unplanned reboots are permitted :-)

Thanks !
Willy


  reply	other threads:[~2013-06-13 18:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 10:15 Linux 2.6.32.61 Willy Tarreau
2013-06-10 15:11 ` Sven-Haegar Koch
2013-06-10 16:04   ` Willy Tarreau
2013-06-13 17:53   ` Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error Willy Tarreau
2013-06-13 18:31     ` Sven-Haegar Koch
2013-06-13 18:41       ` Willy Tarreau [this message]
2013-06-14  6:23     ` Christoph Biedl
2013-06-14  6:36       ` Willy Tarreau
2013-06-14  4:11 ` Linux 2.6.32.61 Ben Hutchings
2013-06-14  5:54   ` 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=20130613184156.GE27760@1wt.eu \
    --to=w@1wt.eu \
    --cc=haegar@sdinet.de \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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