From: Marius Gedminas <mgedmin@centras.lt>
To: linux-kernel@vger.kernel.org
Subject: Re: Hard lock when mounting loopback file
Date: Sun, 13 Jan 2002 13:52:30 +0200 [thread overview]
Message-ID: <20020113115230.GB1955@gintaras> (raw)
In-Reply-To: <3C3F3267.7050103@actarg.com> <3C413BF0.24576AEC@zip.com.au>
In-Reply-To: <3C413BF0.24576AEC@zip.com.au>
On Sat, Jan 12, 2002 at 11:49:04PM -0800, Andrew Morton wrote:
> I don't know a thing about fat layout, but it appears that it uses a
> linked list of blocks, and if that list ends up pointing back onto
> itself, the kernel goes into an infinite loop in several places chasing
> its way to the end of the list.
>
> The below patch fixed it for me, and I was able to mount and read
> your filesystem image.
>
> Unless someone has a smarter fix, I'll send this to the kernel
> maintainers in a week or two.
It seems to me that this patch will find only those infinite loops where
the last link of the chain points to itself. But there could be loops
where the last link points to the middle of the chain.
Additional check on the number of followed links could be useful there.
No chain should be longer than the number of clusters on the fs.
Although on large FAT32 filesystems the number of clusters can be high,
a very long loop is still better than an infinite one. (In cases where
we know the file size, this limit can be reduced to
file_size/cluster_size + 1 links).
Marius Gedminas
--
This company has performed an illegal operation and will be shut down. If
the problem persists, contact your vendor or appeal to a higher court.
next prev parent reply other threads:[~2002-01-13 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 18:43 Kyle
2002-01-13 7:49 ` Andrew Morton
2002-01-13 11:52 ` Marius Gedminas [this message]
2002-01-13 20:35 ` Andrew Morton
2002-01-14 10:26 ` OGAWA Hirofumi
2002-01-14 10:42 ` Andrew Morton
2002-01-14 15:22 ` OGAWA Hirofumi
2002-01-14 10:58 ` Prof. Brand
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=20020113115230.GB1955@gintaras \
--to=mgedmin@centras.lt \
--cc=linux-kernel@vger.kernel.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®