From: "Jan Beulich" <jbeulich@novell.com>
To: <odie@cs.aau.dk>, "Ingo Molnar" <mingo@elte.hu>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, <tglx@linutronix.de>,
"Chuck Ebbert" <cebbert@redhat.com>,
<linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Please revert 709f744 (x86: bitops asm constraint fixes)
Date: Wed, 07 May 2008 08:27:11 +0100 [thread overview]
Message-ID: <482175EF.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20080506120155.GG32591@elte.hu>
>>> Ingo Molnar <mingo@elte.hu> 06.05.08 14:01 >>>
>
>* Simon Holm Thøgersen <odie@cs.aau.dk> wrote:
>
>> [CC'ing all that commented on the patch on LKML]
>>
>> 709f744 causes my computer to freeze during the start up of X and my
>> login manger (GDM). It gets to the point where it has shown the
>> default X mouse cursor logo (a big X / cross) and does not respond to
>> anything from that point on.
>>
>> This worked fine before 709f744, and it works fine with 709f744
>> reverted on top of Linus' current tree (f74d505). The revert had
>> conflicts, as far as I can tell due to white space changes. The diff I
>> ended up with is below.
>>
>> It is 100% reproducible.
>
>thanks Simon for tracking this down.
>
>I've applied your revert (see the patch below), we'll do it unless the
>real bug is found and confirmed by you. What exact compiler version are
>you using to build the kernel?
>
>Jan, any ideas what's wrong with your commit?
No, I have no idea at all (apart from considering mis-compilation as you
did. The best path I could suggest is to try and nail this down to one
(or more, if that happens to be the case) function(s) having been
changed - this is mostly because part of the changes are really
tightening things (which therefore I would think ought to be kept),
while the change to __test_and_change_bit() really weakens things
(which I nevertheless continue to think is correct and consistent with
other functions, but which then would be the primary suspect). Of
course, since no-one else has seen this so far, this would need to be
done by Simon.
Once down to a single (hopefully) function, it might be possible to just
statically compare the two vmlinux-es to perhaps spot whether this
indeed is mis-compilation.
Jan
next prev parent reply other threads:[~2008-05-07 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 13:45 Please revert 709f744 (x86: bitops asm constraint fixes) Simon Holm Thøgersen
2008-05-06 12:01 ` Ingo Molnar
2008-05-06 12:45 ` Simon Holm Thøgersen
2008-05-07 7:27 ` Jan Beulich [this message]
2008-05-07 7:43 ` Thomas Gleixner
2008-05-07 7:50 ` Jan Beulich
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=482175EF.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=cebbert@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=odie@cs.aau.dk \
--cc=tglx@linutronix.de \
/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