linux-um archives
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Lukas Czerner <lczerner@redhat.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml: Error with Linked list debugging on
Date: Mon, 10 May 2010 19:43:53 +0200	[thread overview]
Message-ID: <4BE845D9.40400@web.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1005101719500.21053@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 5982 bytes --]

Lukas Czerner wrote:
> Hi,
> 
> I have got an error when booting uml with Linked list manipulation
> debugging turned on. The crash occurs in the exact moment when the
> consoles are showing up - it just blinks and crush. Here is the
> backtrace:
> 
> 
> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>, 
>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40, 
> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>, 
> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>, 
> v=<value optimized out>) at kernel/notifier.c:191
> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
> at kernel/panic.c:115
> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
> at arch/um/kernel/trap.c:201
> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
> at arch/um/kernel/trap.c:147
> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
> at arch/um/os-Linux/signal.c:226
> #11 0x000000006002151c in handle_signal (sig=<value optimized out>, sc=0x6024fbe8)
>     at arch/um/os-Linux/signal.c:158
> #12 0x0000000060022e9c in hard_handler (sig=<value optimized out>)
> at arch/um/os-Linux/sys-x86_64/signal.c:15
> #13 <signal handler called>
> #14 0x000000006012ecb8 in list_del (entry=0x807bcf00) at lib/list_debug.c:46
> #15 0x0000000060016724 in free_winch (winch=0x807bcf00, free_irq_ok=0) at arch/um/drivers/line.c:731
> #16 0x0000000060016ad7 in winch_interrupt (irq=<value optimized out>, data=0x807bcf00)
> at arch/um/drivers/line.c:760
> #17 0x0000000060055b45 in __free_irq (irq=10, dev_id=0x807bcf00) at kernel/irq/manage.c:937
> #18 0x0000000060055bc0 in free_irq (irq=10, dev_id=0x807bcf00) at kernel/irq/manage.c:986
> #19 0x0000000060016765 in free_winch (winch=0x807bcf00, free_irq_ok=1) at arch/um/drivers/line.c:740
> #20 0x0000000060017211 in unregister_winch (tty=0x8072a800, filp=<value optimized out>)
> at arch/um/drivers/line.c:836
> #21 line_close (tty=0x8072a800, filp=<value optimized out>) at arch/um/drivers/line.c:477
> #22 0x00000000601335d9 in tty_release (inode=0x7eff4190, filp=0x7fc9abc0) at drivers/char/tty_io.c:1580
> #23 0x000000006007e6a8 in __fput (file=0x7fc9abc0) at fs/file_table.c:254
> #24 0x000000006007e79c in fput (file=<value optimized out>) at fs/file_table.c:200
> #25 0x000000006007b995 in filp_close (filp=0x7fc9abc0, id=0x7fc720c0) at fs/open.c:1124
> #26 0x000000006007ba4a in sys_close (fd=3) at fs/open.c:1153
> #27 0x0000000060014c7c in handle_syscall (r=0x7e1ba418) at arch/um/kernel/skas/syscall.c:35
> #28 0x0000000060023e7f in handle_trap (regs=0x7e1ba418) at arch/um/os-Linux/skas/process.c:201
> #29 userspace (regs=0x7e1ba418) at arch/um/os-Linux/skas/process.c:417
> #30 0x000000006001265b in fork_handler () at arch/um/kernel/process.c:181
> 
> 
> Apparently, the winch is not in the list when the free_winch is
> invoked. Kernel version 2.6.34-rc7
> 

You might be lucky: Does the patch below make a difference? It may be
untested as it's part on my half-finished uml cleanup/review queue.

Jan

------

uml: Fix locking around winch_handlers

Manipulation of the winch_handlers list has to be protected by
winch_handler_lock. So we have to add this lock to winch_interrupt which
called free_winch without lock protection and make the other lock sites
IRQ-safe.

---
 arch/um/drivers/line.c |   14 ++++++++------
 1 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/arch/um/drivers/line.c b/arch/um/drivers/line.c
index 7f8f649..dbeaa83 100644
--- a/arch/um/drivers/line.c
+++ b/arch/um/drivers/line.c
@@ -756,7 +756,9 @@ static irqreturn_t winch_interrupt(int irq, void *data)
 				       "read failed, errno = %d\n", -err);
 				printk(KERN_ERR "fd %d is losing SIGWINCH "
 				       "support\n", winch->tty_fd);
+				spin_lock(&winch_handler_lock);
 				free_winch(winch, 0);
+				spin_unlock(&winch_handler_lock);
 				return IRQ_HANDLED;
 			}
 			goto out;
@@ -803,9 +805,9 @@ void register_winch_irq(int fd, int tty_fd, int pid, struct tty_struct *tty,
 		goto out_free;
 	}
 
-	spin_lock(&winch_handler_lock);
+	spin_lock_irq(&winch_handler_lock);
 	list_add(&winch->list, &winch_handlers);
-	spin_unlock(&winch_handler_lock);
+	spin_unlock_irq(&winch_handler_lock);
 
 	return;
 
@@ -823,7 +825,7 @@ static void unregister_winch(struct tty_struct *tty)
 	struct list_head *ele;
 	struct winch *winch;
 
-	spin_lock(&winch_handler_lock);
+	spin_lock_irq(&winch_handler_lock);
 
 	list_for_each(ele, &winch_handlers) {
 		winch = list_entry(ele, struct winch, list);
@@ -832,7 +834,7 @@ static void unregister_winch(struct tty_struct *tty)
 			break;
 		}
 	}
-	spin_unlock(&winch_handler_lock);
+	spin_unlock_irq(&winch_handler_lock);
 }
 
 static void winch_cleanup(void)
@@ -840,14 +842,14 @@ static void winch_cleanup(void)
 	struct list_head *ele, *next;
 	struct winch *winch;
 
-	spin_lock(&winch_handler_lock);
+	spin_lock_irq(&winch_handler_lock);
 
 	list_for_each_safe(ele, next, &winch_handlers) {
 		winch = list_entry(ele, struct winch, list);
 		free_winch(winch, 1);
 	}
 
-	spin_unlock(&winch_handler_lock);
+	spin_unlock_irq(&winch_handler_lock);
 }
 __uml_exitcall(winch_cleanup);
 



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

[-- Attachment #2: Type: text/plain, Size: 80 bytes --]

------------------------------------------------------------------------------


[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2010-05-10 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 15:38 [uml-devel] uml: Error with Linked list debugging on Lukas Czerner
2010-05-10 16:58 ` Lukas Czerner
2010-05-10 17:43 ` Jan Kiszka [this message]
2010-05-16 12:43   ` Paolo Giarrusso
2010-05-16 13:16     ` Jan Kiszka
2010-05-16 14:07       ` Jan Kiszka
2010-05-17  0:30         ` Paolo Giarrusso

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=4BE845D9.40400@web.de \
    --to=jan.kiszka@web.de \
    --cc=lczerner@redhat.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