From: Frank v Waveren <fvw@var.cx>
To: linux-kernel@vger.kernel.org
Subject: isofs forcing cruft on volset# > 1
Date: Tue, 24 Sep 2002 07:23:06 +0200 [thread overview]
Message-ID: <1032843561MGN.fvw@jareth.var.cx> (raw)
Currently the isofs driver forces the 'cruft' option (which does some
nasty stuff like setting maximum filesize to 16mb to salvage malformed
filesystems) on filesystems that have a volume set sequence number
which is not 0 or 1. (linux/fs/isofs/inode.c:1273)
This has been brought up twice here, and gotten no replies. Could
someone please give a reason why we can't accept volume set sequence
numbers, even if we're not exporting them to userspace in any way?
If no-one has a any reasons why not I'll ask hpa to remove the check
or as Stanislav Brabec (utx@penguin.cz) suggested replace it by
testing if the highest byte of the sequence number is set, if this
helps detect some broken images (though I am hesitant to mark any
valid filesystem as cruft just on some heuristic that may be wrong,
even though having more than 16777215 CD's in a set does seem unlikely).
--
Frank v Waveren Fingerprint: 0EDB 8787
fvw@[var.cx|stack.nl|dse.nl|chello.nl] ICQ#10074100 09B9 6EF5 6425 B855
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7179 3036 E136 B85D
reply other threads:[~2002-09-24 5:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1032843561MGN.fvw@jareth.var.cx \
--to=fvw@var.cx \
--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®