From: Stefano Takekawa <take@libero.it>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alexander Galanin <agalanin@mera.ru>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
benh@kernel.crashing.org, Greg Kroah-Hartman <gregkh@suse.de>,
Zhang Yanmin <yanmin.zhang@intel.com>,
bugme-daemon@kernel-bugs.osdl.org
Subject: Re: [Bug 7505] Linux-2.6.19 fails to boot on AMD64 machine
Date: Sat, 02 Dec 2006 09:54:37 +0100 [thread overview]
Message-ID: <1165049677.12073.9.camel@proton.twominds.it> (raw)
In-Reply-To: <m1odqohak7.fsf@ebiederm.dsl.xmission.com>
> Il giorno gio, 30/11/2006 alle 14.46 -0700, Eric W. Biederman ha
> scritto:
> bugme-daemon@bugzilla.kernel.org writes:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=7505
>
> > one. I think this was a better bisection and I got this
>
> > Bisecting: 1 revisions left to test after this
> > [d71374dafbba7ec3f67371d3b7e9f6310a588808] PCI: fix race with pci_walk_bus and
> > pci_destroy_dev
> > d71374dafbba7ec3f67371d3b7e9f6310a588808 is first bad commit
> > commit d71374dafbba7ec3f67371d3b7e9f6310a588808
> > Author: Zhang Yanmin <yanmin.zhang@intel.com>
> > Date: Fri Jun 2 12:35:43 2006 +0800
> >
> > [PATCH] PCI: fix race with pci_walk_bus and pci_destroy_dev
> >
> > pci_walk_bus has a race with pci_destroy_dev. When cb is called
> > in pci_walk_bus, pci_destroy_dev might unlink the dev pointed by next.
> > Later on in the next loop, pointer next becomes NULL and cause
> > kernel panic.
> >
> > Below patch against 2.6.17-rc4 fixes it by changing pci_bus_lock (spin_lock)
> > to pci_bus_sem (rw_semaphore).
> >
> > Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
> > :040000 040000 570ec0423dac5f57a4b7db859e4f502fab422b4d
> > 3fbe35bcc512418894e9ae3862f44363b8b0ab4e M drivers
> >
>
> Let's try and discussing this someplace where people are watching. Bugzilla
> seems to be a horrible medium for tracking down bugs.
>
> Does reverting the above commit allow later kernels to boot? Or do you
> still get the impossible oops?
>
> Eric
I tried to revert the commit:
$ git revert d71374dafbba7ec3f67371d3b7e9f6310a588808
First trying simple merge strategy to revert.
Simple revert fails; trying Automatic revert.
Auto-merging drivers/pci/bus.c
merge: warning: conflicts during merge
ERROR: Merge conflict in drivers/pci/bus.c
Auto-merging drivers/pci/pci.h
Auto-merging drivers/pci/probe.c
Auto-merging drivers/pci/remove.c
Auto-merging drivers/pci/search.c
fatal: merge program failed
Automatic revert failed. After resolving the conflicts,
mark the corrected paths with 'git-update-index <paths>'
and commit the result.
I don't know how to go on. Could someone help me?
(I'm leaving tomorrow, I'll be back in 4 days.)
--
Stefano Takekawa <take@libero.it>
prev parent reply other threads:[~2006-12-02 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611302111.kAULBugP011242@fire-2.osdl.org>
2006-11-30 21:46 ` Eric W. Biederman
2006-12-01 7:09 ` Andrew Morton
2006-12-02 8:54 ` Stefano Takekawa [this message]
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=1165049677.12073.9.camel@proton.twominds.it \
--to=take@libero.it \
--cc=agalanin@mera.ru \
--cc=ak@suse.de \
--cc=benh@kernel.crashing.org \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin.zhang@intel.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
all inboxes | Powered by JetHome®