From: Christoph Hellwig <hch@lst.de>
To: Toralf F?rster <toralf.foerster@gmx.de>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Fwd: Re: UML kernel crash of v2.6.36-rcX kernel
Date: Sun, 17 Oct 2010 22:18:37 +0200 [thread overview]
Message-ID: <20101017201837.GA16458@lst.de> (raw)
In-Reply-To: <201010171555.40453.toralf.foerster@gmx.de>
On Sun, Oct 17, 2010 at 03:55:39PM +0200, Toralf F?rster wrote:
> I bisected it again w/ a fixed test script, got the same bad commit script and
> double checked, that this commit is really the culprit which crashes a user
> mode linux kernel at my 32bix x86 stable Gentoo running 2.6.35.6 vanilla kernel
> as host system and 2/ gcc version 4.4.3 (Gentoo 4.4.3-r2 p1.2) and
> glibc-2.11.2-r1 in the tool chain.
I really can't see any relation to the patch. Can you try the some
things in the following order, please:
(1) git-revert 365b18189789bfa1acd9939e6312b8a4b4577b28 on current
Linus tree and see it it works.
If it works try the next, else the bisect must have been a weird
conicidence and I can't really help more.
(2) re-apply only the changes to include/asm-generic/statfs.h from
365b18189789bfa1acd9939e6312b8a4b4577b28 and see if that still
boots.
(3) re-apply the arch/mips/include/asm/statfs.h and
arch/s390/include/asm/statfs.h changes and see if it still boots
(4) re-apply the include/linux/statfs.h changes and see if it still
boots
(5) re-apply the fs/statfs.c changes, and by now it really shouldn't
boot anymore
(6) verify the code really is the same again as in current Linus' tree
next prev parent reply other threads:[~2010-10-17 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 11:28 Toralf Förster
2010-10-15 9:33 ` Toralf Förster
2010-10-15 17:46 ` Richard Weinberger
2010-10-16 8:55 ` Toralf Förster
2010-10-16 11:12 ` Richard Weinberger
2010-10-17 13:55 ` Toralf Förster
2010-10-17 20:18 ` Christoph Hellwig [this message]
2010-10-18 8:43 ` Toralf Förster
2010-10-18 8:48 ` richard -rw- weinberger
2010-10-18 9:08 ` Geert Uytterhoeven
2010-10-18 9:05 ` Toralf Förster
2010-10-18 9:09 ` [uml-devel] " Geert Uytterhoeven
2010-10-18 9:16 ` richard -rw- weinberger
2010-10-18 9:31 ` richard -rw- weinberger
2010-10-18 11:14 ` Toralf Förster
2010-10-18 11:22 ` Richard Weinberger
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=20101017201837.GA16458@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=toralf.foerster@gmx.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome