Hello,
I apologize in advance if this is a dummy question. My web search turned
up nothing, so I'm trying it here.
We came across the following error message:
Kernelpanic - not syncing: fs/proc/
Generic.c:521: spin_lock(fs/file_table.c:ffffffff80420280)
Already locked by fs/file_table.c/204
This shows a locking problem with the files_lock on a UP kernel with
spinlock debugging enabled.
I noticed that files_lock is only protected with spin_lock()
(file_list_lock(), include/linux/fs.h). Is it possible that this should
be changed to spin_lock_irq()) or spin_lock_irqsave()? Or am I misssing
something obvious?
Thanks
Martin
--
Martin Wilck Phone: +49 5251 8 15113
Fujitsu Siemens Computers Fax: +49 5251 8 20409
Heinz-Nixdorf-Ring 1 mailto:[email protected]
D-33106 Paderborn http://www.fujitsu-siemens.com/primergy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |