From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
Peter <p.repliesignored@rimuhosting.com>
Subject: Re: [uml-devel] 2.6.11 + uml.sf.net patches panic
Date: Fri, 04 Mar 2005 16:08:14 +0100 [thread overview]
Message-ID: <422879DE.6050405@fujitsu-siemens.com> (raw)
In-Reply-To: <42286F4A.30506@fujitsu-siemens.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Bodo Stroesser wrote:
> Jeff Dike wrote:
>
>> The write_ldt just above the segfault in both stacks looks suspicious.
>
>
> Yes. There seems to be a problem with this new stuff.
>
> Peter, could you please send a full call trace? I guess, the ones in your
> mail are truncated, right?
>
> Bodo
Meanwhile I found a problem in arch/um/sys-i386/ldt.c, which causes UML
to panic, if LDT-entry number 8 is written, using modify_ldt-syscall.
This crash is very similar to the one Peter had, so I hope the appended
oneliner will solve the problem.
Bodo
[-- Attachment #2: fix-skas-ldt.patch --]
[-- Type: text/x-diff, Size: 616 bytes --]
---
diff -puN arch/um/sys-i386/ldt.c~fix-skas-ldt arch/um/sys-i386/ldt.c
--- linux-2.6.11-rc3-mm2/arch/um/sys-i386/ldt.c~fix-skas-ldt 2005-03-04 15:51:04.000000000 +0100
+++ linux-2.6.11-rc3-mm2-root/arch/um/sys-i386/ldt.c 2005-03-04 15:51:27.000000000 +0100
@@ -208,7 +208,7 @@ static int write_ldt(void __user * ptr,
goto out_unlock;
if(ldt_info.entry_number >= ldt->entry_count &&
- ldt_info.entry_number > LDT_DIRECT_ENTRIES){
+ ldt_info.entry_number >= LDT_DIRECT_ENTRIES){
for(i=ldt->entry_count/LDT_ENTRIES_PER_PAGE;
i*LDT_ENTRIES_PER_PAGE <= ldt_info.entry_number;
i++){
_
next prev parent reply other threads:[~2005-03-04 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 2:53 [uml-devel] 2.6.11 + uml.sf.net patches panic Peter
2005-03-03 18:53 ` Jeff Dike
2005-03-04 14:23 ` Bodo Stroesser
2005-03-04 15:08 ` Bodo Stroesser [this message]
2005-03-05 23:24 ` [uml-devel] 2.6.11 + uml.sf.net patches panic (now fixed, replaced by CPU problem) Peter
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=422879DE.6050405@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=p.repliesignored@rimuhosting.com \
--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