From: Peter Kundrat <kundrat@kundrat.sk>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: MS_RDONLY patch (do_remount_sb and cramfs/inode.c)
Date: Tue, 15 May 2001 13:16:49 +0200 [thread overview]
Message-ID: <20010515131649.A8151@napri.sk> (raw)
In-Reply-To: <20010515112726.A28961@napri.sk> <20010515122406.A4564@napri.sk>
In-Reply-To: <20010515122406.A4564@napri.sk>; from kundrat on Tue, May 15, 2001 at 12:24:06PM +0200
On Tue, May 15, 2001 at 12:24:06PM +0200, Peter Kundrat wrote:
> On Tue, May 15, 2001 at 11:27:26AM +0200, Peter Kundrat wrote:
> > This patch does:
> > - set MS_RDONLY flag in cramfs superblock
> > - doesnt allow -w remount in do_remount_sb
> > if the filesystem has MS_RDONLY set.
>
> Oh, ignore the second part. Seems i'd have to supply remount_fs super
> op to prevent that.
How about this one ? Similar thing could be done to other fs as well.
pkx
diff -ur -x *~ -x *.o -x .* Linux-2.4.3.orig/fs/cramfs/inode.c Linux-2.4.3.isdn.kgdb/fs/cramfs/inode.c
--- Linux-2.4.3.orig/fs/cramfs/inode.c Fri Apr 6 08:09:07 2001
+++ Linux-2.4.3.isdn.kgdb/fs/cramfs/inode.c Tue May 15 12:56:32 2001
@@ -192,6 +192,8 @@
goto out;
}
+ sb->s_flags |= MS_RDONLY;
+
/* Set it all up.. */
sb->s_op = &cramfs_ops;
sb->s_root = d_alloc_root(get_cramfs_inode(sb, &super.root));
@@ -212,6 +214,14 @@
return 0;
}
+static int cramfs_remount (struct super_block * sb, int * flags, char * data)
+{
+ if (*flags & MS_RDONLY)
+ return 0;
+ else
+ return -EROFS;
+}
+
/*
* Read a cramfs directory entry.
*/
@@ -358,6 +368,7 @@
static struct super_operations cramfs_ops = {
statfs: cramfs_statfs,
+ remount_fs: cramfs_remount,
};
static DECLARE_FSTYPE_DEV(cramfs_fs_type, "cramfs", cramfs_read_super);
--
Peter Kundrat
peter@kundrat.sk
prev parent reply other threads:[~2001-05-15 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 9:27 MS_RDONLY patch (do_remount_sb and cramfs/inode.c) Peter Kundrat
2001-05-15 10:24 ` Peter Kundrat
2001-05-15 11:16 ` Peter Kundrat [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=20010515131649.A8151@napri.sk \
--to=kundrat@kundrat.sk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).