public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	Hugh Dickins <hughd@google.com>, Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: commit 0fc9d10 : chroot under kernel 3.4.x core dumps
Date: Tue, 05 Jun 2012 14:55:59 +0400	[thread overview]
Message-ID: <4FCDE5BF.6000905@openvz.org> (raw)
In-Reply-To: <4FCDE2ED.8010501@gmx.de>

Toralf Förster wrote:
>
> When I try under kernel versions 3.4.[01] to chroot into a user mode
> linux image, I often get this :
>
> + mount -o loop /home/tfoerste/virtual/uml/gentoo_unstable /mnt/loop
> + mount -t proc none /mnt/loop/proc
> + mount -o bind /dev /mnt/loop/dev
> + mount -o bind /dev/pts /mnt/loop/dev/pts
> + mount -o bind /usr/portage /mnt/loop/usr/portage
> + mount -o bind /usr/local/portage /mnt/loop/usr/local/portage
> + mount -o bind /tmp/uml_portage /mnt/loop/var/tmp/portage
> + chroot /mnt/loop /bin/bash
> /home/tfoerste/workspace/bin/chr_uml.sh: line 55:  4143 Segmentation
> fault      (core dumped) chroot /mnt/loop /bin/bash
>
>
> The core file itself is only 400 KB in size and the back trace with gbd
> is meaningless :
>
> Core was generated by `/bin/bash'.
> Program terminated with signal 11, Segmentation fault.
> #0  0xb75cac00 in ?? ()
> (gdb) bt
> #0  0xb75cac00 in ?? ()
> #1  0xb76f4ff4 in ?? ()
> Cannot access memory at address 0xffffffdc
>
> In the rare cases, where the chroot doesn't crash, all subsequent
> commands cores instead. Furthermore it seems, that the boinc grid
> software has problems too under kernel 3.4.1.
> All kernel 3.3.x works fine.
>
> I bisected it to :
>
> commit 0fc9d1040313047edf6a39fd4d7c7defdca97c62
> Author: Konstantin Khlebnikov<khlebnikov@openvz.org>
> Date:   Wed Mar 28 14:42:54 2012 -0700
>
>      radix-tree: use iterators in find_get_pages* functions
>
>

I have two reports about this, and NFS is mentioned in both. Did you use it?

  parent reply	other threads:[~2012-06-05 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 21:30 chroot under kernel 3.4.x gives core dumps Toralf Förster
2012-06-04 21:41 ` richard -rw- weinberger
2012-06-05 10:43 ` commit 0fc9d10 : chroot under kernel 3.4.x " Toralf Förster
2012-06-05 10:49   ` richard -rw- weinberger
2012-06-05 10:55   ` Konstantin Khlebnikov [this message]
2012-06-05 13:59     ` Toralf Förster

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=4FCDE5BF.6000905@openvz.org \
    --to=khlebnikov@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=toralf.foerster@gmx.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