From: Colin Leroy <colin@colino.net>
To: Colin Leroy <colin@colino.net>
Cc: Roman Zippel <zippel@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hfsplus: don't oops on bad FS
Date: Tue, 26 Apr 2005 09:14:03 +0200 [thread overview]
Message-ID: <20050426091403.099cee53@colin.toulouse> (raw)
In-Reply-To: <20050426085914.2b278856@colin.toulouse>
On Tue, 26 Apr 2005 08:59:14 +0200
Colin Leroy <colin@colino.net> wrote:
> cleanup:
> + kfree(sb->s_fs_info);
> + sb->s_fs_info = NULL;
> +
Also, that may be wrong: maybe hfsplus_put_super has a job to do if
mounting fails later than "no hfs+ fs found".
My understanding of the driver is limited, that's why my initial patch
did the less possible functionality change. But I'd like to remember
you (maybe you forgot) that my initial patch wasn't about fixing the
s_fs_info leak, but rather fixing an oops that happens in
hfsplus_put_super. That's why I don't think we can run the current code
in hfsplus_put_super from hfsplus_fill_super cleanup part :
HFS+-fs: unable to find HFS+ superblock
Oops: kernel access of bad area, sig: 11 [#1]
NIP: EA4707F4 LR: EA470AC8 SP: CC91DAA0 REGS: cc91d9f0 TRAP: 0300 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000004, DSISR: 40000000
TASK = ce48cdf0[20295] 'mount' THREAD: cc91c000
Last syscall: 21
GPR00: 00000000 CC91DAA0 CE48CDF0 CB2FF200 C0373ECC 00000004 E756CD60 3B9ACA00
GPR08: C2B71F60 C0360000 00000000 BE932A74 0000D903 1002957C 10020000 10026810
GPR16: 100267E0 10026840 7FF3F4DD 100267D0 7FF3F4B3 00000000 10026820 10026820
GPR24: 7FF3EF70 EA4709EC EA105714 00000000 00000000 C9341000 C2B71F60 CB2FF200
NIP [ea4707f4] hfsplus_put_super+0x9c/0x114 [hfsplus]
LR [ea470ac8] hfsplus_fill_super+0xdc/0x5a8 [hfsplus]
Call trace:
[ea470ac8] hfsplus_fill_super+0xdc/0x5a8 [hfsplus]
[c00644e4] get_sb_bdev+0x14c/0x1d4
[ea471018] hfsplus_get_sb+0x18/0x28 [hfsplus]
[c0064824] do_kern_mount+0x5c/0x130
[c007c774] do_mount+0x46c/0x6cc
[c007ce18] sys_mount+0x98/0xe8
[c0004840] ret_from_syscall+0x0/0x44
--
Colin
next prev parent reply other threads:[~2005-04-26 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050425211915.126ddab5@jack.colino.net>
2005-04-25 19:53 ` Roman Zippel
2005-04-25 20:03 ` Colin Leroy
2005-04-25 20:07 ` Christoph Hellwig
2005-04-25 20:12 ` Colin Leroy
2005-04-25 20:26 ` Roman Zippel
2005-04-26 6:59 ` Colin Leroy
2005-04-26 7:14 ` Colin Leroy [this message]
2005-04-25 20:29 ` Jesper Juhl
2005-05-01 5:08 ` Chris Wedgwood
2005-05-01 9:12 ` Colin Leroy
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=20050426091403.099cee53@colin.toulouse \
--to=colin@colino.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®