From: Andrew Morton <akpm@osdl.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, oliver@neukum.org
Subject: Re: OOps in HFS was: 2.6.0-test4-mm3
Date: Tue, 16 Sep 2003 14:40:12 -0700 [thread overview]
Message-ID: <20030916144012.0ab9b009.akpm@osdl.org> (raw)
In-Reply-To: <20030916214105.GA3490@matchmail.com>
Mike Fedyk <mfedyk@matchmail.com> wrote:
>
> Just reading a hfs floppy...
It's not an oops - it's a warning.
> Sep 15 10:10:49 mis-mike-wstn kernel: inserting floppy driver for 2.6.0-test4-mm3-1-mdfail
> Sep 15 10:10:49 mis-mike-wstn kernel: Floppy drive(s): fd0 is 1.44M
> Sep 15 10:10:49 mis-mike-wstn kernel: FDC 0 is a post-1991 82077
> Sep 15 10:10:49 mis-mike-wstn kernel: PM: Adding info for platform:floppy0
> Sep 15 10:11:14 mis-mike-wstn kernel: Debug: sleeping function called from invalid context at mm/slab.c:1833
> Sep 15 10:11:14 mis-mike-wstn kernel: Call Trace:
> Sep 15 10:11:14 mis-mike-wstn kernel: [__might_sleep+99/104] __might_sleep+0x63/0x68
> Sep 15 10:11:15 mis-mike-wstn kernel: [kmem_cache_alloc+37/324] kmem_cache_alloc+0x25/0x144
> Sep 15 10:11:15 mis-mike-wstn kernel: [_end+340461616/1068932160] grow_entries+0x24/0xa0 [hfs]
> Sep 15 10:11:15 mis-mike-wstn kernel: [_end+340462938/1068932160] get_new_entry+0x1e/0x460 [hfs]
get_entry() does disk I/O under spin_lock(&entry_lock). Deadlock country.
A simple fix would be to convert entry_lock into a semaphore.
> Sep 15 10:21:11 mis-mike-wstn kernel: hfs_cat_put: trying to free free entry: c261451c
> Sep 15 10:21:11 mis-mike-wstn kernel: hfs_cat_put: trying to free free entry: cc08f104
> Sep 15 10:21:11 mis-mike-wstn kernel: hfs_cat_put: trying to free free entry: c7997ccc
> Sep 15 10:21:11 mis-mike-wstn kernel: hfs_cat_put: trying to free free entry: c6cb9728
Well that's not very good. Can you make an image of that floppy available for download?
Does 2.4's HFS driver work OK?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-16 21:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 6:56 2.6.0-test4-mm3 Andrew Morton
2003-08-29 7:45 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:42 ` 2.6.0-test4-mm3 Ed Sweetman
2003-08-29 15:57 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:59 ` 2.6.0-test4-mm3 Felipe Alfaro Solana
2003-08-30 1:43 ` OOps in 2.6.0-test4-mm3-1 Mike Fedyk
2003-09-10 18:53 ` 2.6.0-test4-mm3 Mike Fedyk
2003-09-10 18:55 ` ide-scsi oops was: 2.6.0-test4-mm3 Mike Fedyk
2003-09-10 18:43 ` Andrew Morton
2003-09-10 19:10 ` Mike Fedyk
2003-09-11 15:24 ` Alan Cox
2003-09-10 20:04 ` Martin J. Bligh
2003-09-10 20:53 ` Paul Larson
2003-09-11 8:20 ` Jens Axboe
2003-09-11 15:12 ` Gerhard Mack
2003-09-11 21:52 ` Jens Axboe
2003-09-11 15:27 ` Alan Cox
2003-09-11 21:50 ` Jens Axboe
2003-09-11 18:13 ` Martin J. Bligh
2003-09-11 18:30 ` Mike Fedyk
2003-09-11 21:52 ` Jens Axboe
2003-09-16 21:41 ` OOps in HFS " Mike Fedyk
2003-09-16 21:40 ` Andrew Morton [this message]
2003-09-16 23:59 ` Mike Fedyk
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=20030916144012.0ab9b009.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mfedyk@matchmail.com \
--cc=oliver@neukum.org \
/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