linux-um archives
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	Richard Weinberger <richard@nod.at>,
	serge.hallyn@canonical.com, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: shm updates broke UML
Date: Thu, 4 Aug 2011 13:04:40 +0200	[thread overview]
Message-ID: <201108041304.41135.toralf.foerster@gmx.de> (raw)
In-Reply-To: <20110801172452.GA26190@albatros>

issue solved for the UML, tested linux-v3.0-7347-g288d5ab whcih works fine.

BTW is there a special commit id dealing with this bug or was it solved as a 
side effect of another commit ?

Vasiliy Kulikov wrote at 19:24:52
> On Mon, Aug 01, 2011 at 19:19 +0200, Marc Zyngier wrote:
> > Here you go (sorry about the line wrapping, damned webmail...):
> Thank you!  Now I see that the problem is rw_mutex is not initialized:
> 
> 	down_write(&shm_ids(ns).rw_mutex);
> 
> void __sched __down_write_nested(struct rw_semaphore *sem, int subclass)
> {
>     ...
> 	if (sem->activity == 0 && list_empty(&sem->wait_list)) {
>                                          ^^^^^^^^^^^^^^^ is NULL
> 
> Wtf - ipc namespace should be fully initialized for the moment of
> threads run...
> 
> > Calibrating local timer... 104.99MHz.
> > CPU1: Booted secondary processor
> > CPU1: Unknown IPI message 0x1
> > CPU2: Booted secondary processor
> > CPU2: Unknown IPI message 0x1
> > CPU3: Booted secondary processor
> > CPU3: Unknown IPI message 0x1
> > Brought up 4 CPUs
> > SMP: Total of 4 processors activated (333.41 BogoMIPS).
> > ns = c0447474, ids = c04474d0
> > ns = c0447474, ids = c04474d0
> > wait_list = c04474e0
> > next =   (null)
> 
>            ^^^^^^


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


  parent reply	other threads:[~2011-08-04 11:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 13:41 shm updates broke UML Richard Weinberger
2011-08-01 13:49 ` Vasiliy Kulikov
2011-08-01 14:04   ` [uml-devel] " Richard Weinberger
2011-08-01 16:01   ` Marc Zyngier
2011-08-01 17:10     ` Vasiliy Kulikov
2011-08-01 17:19       ` Marc Zyngier
2011-08-01 17:24         ` [uml-devel] " Vasiliy Kulikov
2011-08-01 17:32           ` Vasiliy Kulikov
2011-08-01 17:43             ` Marc Zyngier
2011-08-04 11:04           ` Toralf Förster [this message]
2011-08-04 11:16             ` [uml-devel] " Vasiliy Kulikov
2011-08-01 17:20       ` 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=201108041304.41135.toralf.foerster@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=richard@nod.at \
    --cc=segoon@openwall.com \
    --cc=serge.hallyn@canonical.com \
    --cc=torvalds@linux-foundation.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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