From: Andries.Brouwer@cwi.nl
To: akpm@osdl.org, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [uPATCH] refuse plain ufs mount
Date: Sun, 25 Jan 2004 01:17:47 +0100 (MET) [thread overview]
Message-ID: <UTC200401250017.i0P0Hlc09374.aeb@smtp.cwi.nl> (raw)
Installed some machine with a reiserfs rootfs.
The boot messages contain a lot of garbage spouted by Intermezzo
and ufs_read_super caused by the fact that the kernel tried lots
of other filesystems before hitting on reiserfs.
On the one hand this is solved by "rootfstype=reiserfs".
But on the other hand, the kernel should not complain about the
guessing it does itself. There is a parameter "silent" for this
purpose, but in this case I think it cleaner just to remove the
complaint and tighten the requirement.
Andries
--- /linux/2.6/linux-2.6.1/linux/fs/ufs/super.c 2003-12-18 03:57:57.000000000 +0100
+++ super.c 2004-01-25 01:05:47.000000000 +0100
@@ -516,14 +516,10 @@
printk("wrong mount options\n");
goto failed;
}
- if (!(sbi->s_mount_opt & UFS_MOUNT_UFSTYPE)) {
- printk("You didn't specify the type of your ufs filesystem\n\n"
- "mount -t ufs -o ufstype="
- "sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...\n\n"
- ">>>WARNING<<< Wrong ufstype may corrupt your filesystem, "
- "default is ufstype=old\n");
- ufs_set_opt (sbi->s_mount_opt, UFSTYPE_OLD);
- }
+
+ /* "old" used to be default - now: always specify type */
+ if (!(sbi->s_mount_opt & UFS_MOUNT_UFSTYPE))
+ goto failed;
sbi->s_uspi = uspi =
kmalloc (sizeof(struct ufs_sb_private_info), GFP_KERNEL);
next reply other threads:[~2004-01-25 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 0:17 Andries.Brouwer [this message]
2004-01-27 1:43 ` GOTO Masanori
2004-01-27 1:56 Andries.Brouwer
2004-01-27 2:09 ` Linus Torvalds
2004-01-27 4:07 Andries.Brouwer
2004-01-27 5:04 ` GOTO Masanori
2004-01-27 6:15 ` Linus Torvalds
2004-01-28 22:24 Example
2004-01-29 0:13 ` GOTO Masanori
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=UTC200401250017.i0P0Hlc09374.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®