From: Richard Weinberger <richard@nod.at>
To: Vivek Goyal <vgoyal@redhat.com>
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 21:18:08 +0200 [thread overview]
Message-ID: <53E916F0.80308@nod.at> (raw)
In-Reply-To: <20140811184401.GE1863@redhat.com>
Am 11.08.2014 20:44, schrieb Vivek Goyal:
> On Mon, Aug 11, 2014 at 02:25:56PM +0200, Richard Weinberger wrote:
>> Hi Vivek,
>>
>> Am 11.08.2014 14:22, schrieb Vivek Goyal:
>>> 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.
>>
>> he reported it on IRC to me.
>>
>> Here is a backtrace:
>> RIP: 0033:[<0000000060039b9f>]
>> RSP: 0000000081459da0 EFLAGS: 00010202
>> RAX: 0000000000000000 RBX: 00000000219b3fff RCX: 000000006010d1d9
>> RDX: 0000000000000001 RSI: 00000000602dfb94 RDI: 0000000081459df8
>> RBP: 0000000081459de0 R08: 00000000601b59f4 R09: ffffffff0000ff00
>> R10: ffffffff0000ff00 R11: 0000000081459e88 R12: 0000000081459df8
>> R13: 00000000219b3fff R14: 00000000602dfb94 R15: 0000000000000000
>> Kernel panic - not syncing: Segfault with no mm
>> CPU: 0 PID: 1 Comm: swapper Not tainted 3.16.0-10454-g58d08e3 #13
>> Stack:
>> 00000000 000080d0 81459df0 219b3fff
>> 81459e70 6010d1d9 ffffffff 6033e010
>> 81459e50 6003a269 81459e30 00000000
>> Call Trace:
>> [<6010d1d9>] ? kclist_add_private+0x0/0xe7
>> [<6003a269>] walk_system_ram_range+0x61/0xb7
>> [<6000e859>] ? proc_kcore_init+0x0/0xf1
>> [<6010d574>] kcore_update_ram+0x4c/0x168
>> [<6010d72e>] ? kclist_add+0x0/0x2e
>> [<6000e943>] proc_kcore_init+0xea/0xf1
>> [<6000e859>] ? proc_kcore_init+0x0/0xf1
>> [<6000e859>] ? proc_kcore_init+0x0/0xf1
>> [<600189f0>] do_one_initcall+0x13c/0x204
>> [<6004ca46>] ? parse_args+0x1df/0x2e0
>> [<6004c82d>] ? parameq+0x0/0x3a
>> [<601b5990>] ? strcpy+0x0/0x18
>> [<60001e1a>] kernel_init_freeable+0x240/0x31e
>> [<6026f1c0>] kernel_init+0x12/0x148
>> [<60019fad>] new_thread_handler+0x81/0xa3
>>
>> RIP is at kernel/resource.c:66.
>
> Hi Richard,
>
> Can you please give the attached patch a try and see if it fixes the UML
> issue.
>
> I noticed that previous code had a for() loop which will not execute
> if p was null. I have resorted back to same code now.
Looks good!
Reported-by: Daniel Walter <sahne@0x90.at>
Tested-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
next prev parent reply other threads:[~2014-08-11 19:18 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
2014-08-11 12:25 ` Richard Weinberger
2014-08-11 18:44 ` Vivek Goyal
2014-08-11 19:18 ` Richard Weinberger [this message]
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=53E916F0.80308@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sahne@0x90.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=vgoyal@redhat.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