public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Richard Weinberger <richard@nod.at>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel
	<user-mode-linux-devel@lists.sourceforge.net>,
	sahne@0x90.at
Subject: Re: "resource: provide new functions to walk through resources" breaks UML
Date: Mon, 11 Aug 2014 08:22:29 -0400	[thread overview]
Message-ID: <20140811122229.GA26869@redhat.com> (raw)
In-Reply-To: <53E7A42E.4090702@nod.at>

On Sun, Aug 10, 2014 at 06:56:14PM +0200, Richard Weinberger wrote:
> Hi Vivek,
> 
> Daniel Walter reported that UML is currently broken.
> The offending commit is:
> 

Hi Richard,

Thanks for pointing it out. I will look into it.

Would you have link to the report Daniel sent. I am interested in 
looking at backtrace.

Thanks
Vivek

> commit 8c86e70acead629aacb4afcd818add66bf6844d9
> Author: Vivek Goyal <vgoyal@redhat.com>
> Date:   Fri Aug 8 14:25:50 2014 -0700
> 
>     resource: provide new functions to walk through resources
> 
> It dies in next_resource():
>         /* Caller wants to traverse through siblings only */
>         if (sibling_only)
>                 return p->sibling;
> 
> because p is NULL.
> Please note that UML has no iomem, maybe this is the problem...
> 
> Thanks,
> //richard

  reply	other threads:[~2014-08-11 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 16:56 "resource: provide new functions to walk through resources" breaks UML Richard Weinberger
2014-08-11 12:22 ` Vivek Goyal [this message]
2014-08-11 12:25   ` Richard Weinberger
2014-08-11 18:44     ` Vivek Goyal
2014-08-11 19:18       ` Richard Weinberger
2014-08-11 19:25       ` [uml-devel] " Toralf Förster
2014-08-11 19:48       ` Daniel Walter

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=20140811122229.GA26869@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=sahne@0x90.at \
    --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