public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander van Heukelum" <heukelum@fastmail.fm>
To: sedat.dilek@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-next <linux-next@vger.kernel.org>,
	psomas@cslab.ece.ntua.gr, Jan Beulich <JBeulich@novell.com>,
	"H. Peter Anvin" <hpa@zytor.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: linux-next: Tree for March 8 (BROKEN: arch/x86/kernel/entry_32.S? Debian's binutils/as?)
Date: Tue, 08 Mar 2011 21:25:39 +0100	[thread overview]
Message-ID: <1299615939.25628.1427572905@webmail.messagingengine.com> (raw)
In-Reply-To: <AANLkTi=6YstJxad41knR4Q9WN3wYKikPv-g1i3kg3HS1@mail.gmail.com>

On Tue, 08 Mar 2011 18:53 +0100, "Sedat Dilek" <sedat.dilek@googlemail.com> wrote:
> On Tue, Mar 8, 2011 at 6:27 PM, Alexander van Heukelum
> <heukelum@fastmail.fm> wrote:
> > On Tue, 08 Mar 2011 16:42 +0100, "Sedat Dilek" <sedat.dilek@googlemail.com> wrote:
> >> On 3/8/11, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> >> > On 3/8/11, H.J. Lu <hjl.tools@gmail.com> wrote:
> >> >> On Tue, Mar 8, 2011 at 2:44 AM, Sedat Dilek <sedat.dilek@googlemail.com>
> >> >> wrote:
> >> >>> Hi,
> >> >>>
> >> >>> my build of linux-next (next-20110308, the same with the one from
> >> >>> yesterday) is broken.
> >> >>> (I translated the German output.)
> >> >>>
> >> >>> [ build.log ]
> >> >>>  AS      arch/x86/kernel/entry_32.o
> >> >>> /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:
> >> >>> Assembler messages:
> >> >>> /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:1421:
> >> >>> Error: .size expression does not evaluate to a constant
> >> >>> make[6]: *** [arch/x86/kernel/entry_32.o] Fehler 1 (Error 1)
> >> >>> make[5]: *** [arch/x86/kernel] Fehler 2 (Error 2)
> >> >>> make[4]: *** [arch/x86] Fehler 2 (Error 2)
> >> >>> make[4]: *** Warte auf noch nicht beendete Prozesse... (Waiting for
> >> >>> unfinished jobs...)
> >> >>>
> >> >>
> >> >> This is a kernel bug.  Please use the latest binutils from CVS.
> >> >> It will tell you which symbol causes this.
> >> >>
> >> >>
> >> >> --
> >> >> H.J.
> >> >>
> >> >
> >> > Yeah, I have cherry-picked these two upstream commits before you have
> >> > mentionned it...
> >> >
> >> > 0001-Mention-symbol-name-in-non-constant-.size-expression.patch
> >> >        (Cherry-picked from commit b9521fc0be7945fc842ce1197e241a023378125d)
> >> > 0002-Revert-the-last-change-on-gas-elf-bad-size.err.patch
> >> >        (Cherry-picked from commit cbd141bb69f791de7ea1581abe7afb34f0c61288)
> >> >
> >> > ... and have built with them a new binutils Debian package.
> >> >
> >> > The error looks now like this (sorry for the German output):
> >> > ...
> >> >   AS      arch/x86/kernel/entry_32.o
> >> > /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:
> >> > Assembler messages:
> >> > /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/entry_32.S:1421:
> >> > Error: .size expression with symbol `apf_page_fault' does not evaluate
> >> > to a constant
> >> > make[6]: *** [arch/x86/kernel/entry_32.o] Fehler 1
> >> > make[5]: *** [arch/x86/kernel] Fehler 2
> >> > make[5]: *** Warte auf noch nicht beendete Prozesse...
> >> >
> >> > Anyway, before more riddling around it would be very helpful to have a
> >> > clear pointer if there is a fix around... That building, testing and
> >> > installing took me now several hours.
> >> > And... yeah, backports to 2.21-branch appreciated.
> >> >
> >> > - Sedat -
> >> >
> >>
> >> After a quick look into the source, it seems attached patch fixes the
> >> issue.
> >> Is that OK?
> >
> > Hi Sedat,
> >
> > The patch ( https://lkml.org/lkml/2011/3/8/203 ) is ok, feel free to add
> > Acked-by: Alexander van Heukelum <heukelum@fastmail.fm>
> >
> > Better description might be something like:
> >
> > i386: Fix mismatched ENTRY/END pair.
> >
> > Under CONFIG_KVM_GUEST=y, the following part of entry_32.S causes a compile failure.
> >
> > 1409 #ifdef CONFIG_KVM_GUEST
> > 1410 ENTRY(async_page_fault)
> > 1411         RING0_EC_FRAME
> > 1412         pushl $do_async_page_fault
> > 1413         CFI_ADJUST_CFA_OFFSET 4
> > 1414         jmp error_code
> > 1415         CFI_ENDPROC
> > 1416 END(apf_page_fault)
> > 1417 #endif
> >
> > Replace apf_page_fault with async_page_fault, as intended.
> >
> > Greetings,
> >    Alexander
> >
> >> - Sedat -
> >>
> >> Email had 1 attachment:
> >> + 0001-x86-Fix-build-failure-with-binutils-as-from-upstream.patch
> >>   1k (text/x-patch)
> >
> 
> As I said, quick view on the code, quick fix :-).
> 
> Your description is definitive more meaningful.
> I can refresh my patch and add your ACK.
> 
> Anyway, I continued after dinner and with the above patch I ran into
> the next problem:
> [ build.log ]
> ...
>   AS      arch/x86/kernel/acpi/wakeup_rm.o
> /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/acpi/wakeup_rm.S:
> Assembler messages:
> /home/sd/src/linux-2.6/linux-2.6.38-rc7/debian/build/source_i386_none/arch/x86/kernel/acpi/wakeup_rm.S:12:
> Error: .size expression with symbol `wakeup_code_start' does not
> evaluate to a constant

No idea what's wrong there. But my version of wakeup_rm.S has only 10 lines...

     1  /*
     2   * Wrapper script for the realmode binary as a transport object
     3   * before copying to low memory.
     4   */
     5          .section ".rodata","a"
     6          .globl  wakeup_code_start, wakeup_code_end
     7  wakeup_code_start:
     8          .incbin "arch/x86/kernel/acpi/realmode/wakeup.bin"
     9  wakeup_code_end:
    10          .size   wakeup_code_start, .-wakeup_code_start

And it compiles just fine.
The fix for entry_32.S is valid, though, and necessary for mainline.

Greetings,
    Alexander

> I am unsure how to fix that and open for feedback.
> 
> - Sedat -
> 

  reply	other threads:[~2011-03-08 20:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 10:44 linux-next: Tree for March 8 (BROKEN: arch/x86/kernel/entry_32.S? Debian's binutils/as?) Sedat Dilek
2011-03-08 12:44 ` Sedat Dilek
2011-03-08 14:55 ` H.J. Lu
2011-03-08 15:28   ` Sedat Dilek
2011-03-08 15:42     ` Sedat Dilek
2011-03-08 17:27       ` Alexander van Heukelum
2011-03-08 17:53         ` Sedat Dilek
2011-03-08 20:25           ` Alexander van Heukelum [this message]
2011-03-08 20:33             ` Sedat Dilek
2011-03-08 20:45               ` H.J. Lu
2011-03-08 20:59                 ` Alexander van Heukelum
2011-03-08 21:25                   ` Sedat Dilek
2011-03-09  8:51                 ` Ingo Molnar
2011-03-09 10:16                   ` Sedat Dilek
2011-03-09 11:51                     ` Ingo Molnar
2011-03-09 15:40                   ` H.J. Lu
2011-03-09 16:02                     ` Ingo Molnar
2011-03-09 19:04                       ` H.J. Lu
2011-03-10  7:17                         ` Ingo Molnar
2011-03-10 15:54                           ` H.J. Lu
2011-03-12  8:25                             ` Ingo Molnar
2011-03-09 11:53 ` Sedat Dilek

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=1299615939.25628.1427572905@webmail.messagingengine.com \
    --to=heukelum@fastmail.fm \
    --cc=JBeulich@novell.com \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=psomas@cslab.ece.ntua.gr \
    --cc=sedat.dilek@gmail.com \
    /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