From: Horms <horms@verge.net.au>
To: Colin Leroy <colin@colino.net>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH] hfs, hfsplus: don't leak s_fs_info and fix an oops
Date: Tue, 29 Nov 2005 13:16:08 +0900 [thread overview]
Message-ID: <20051129041606.GA9575@verge.net.au> (raw)
In-Reply-To: <20051007071008.CAC4E10334@paperstreet.colino.net>
On Fri, Oct 07, 2005 at 09:10:05AM +0200, Colin Leroy wrote:
> On 07 Oct 2005 at 13h10, Horms wrote:
>
> Hi,
>
> > I took a look at making a backport, and it seems that
> > some of the problems are there, but without a deeper inspection
> > of the code its difficult to tell if the problems manifest or not.
>
> That was easy to get the oops:
>
> $ dd if=/dev/zero of=im_not_hfsplus count=10 #for example
> $ mkdir test_dir
> $ sudo mount -o loop -t hfsplus ./im_not_hfsplus ./testdir
> $ dmesg
After an extended delay I have been able to confirm that the above
commands do not cause 2.4 (Debian's 2.4.27) to do anything unusal.
Mount just reports:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
or too many mounted file systems
And there is nothing exciting in dmsg:
loop: loaded (max 8 devices)
HFS+-fs: unable to find HFS+ superblock
HFS+-fs: unable to find HFS+ superblock
HFS+-fs: unable to find HFS+ superblock
Thus it seems that 2.4 does not suffer from this bug.
--
Horms
prev parent reply other threads:[~2005-11-29 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 4:39 [PATCH] hfs, hfsplus: don't leak s_fs_info and fix an oops Horms
2005-10-07 7:10 ` Colin Leroy
2005-10-07 7:31 ` Horms
2005-11-29 4:16 ` Horms [this message]
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=20051129041606.GA9575@verge.net.au \
--to=horms@verge.net.au \
--cc=colin@colino.net \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--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