public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ashwin Chaugule <ashwinc@aftek.com>
To: linux-mtd@lists.infradead.org
Subject: is this a bug ?
Date: Sat, 20 Aug 2005 05:44:35 +0530	[thread overview]
Message-ID: <430675EB.9030905@aftek.com> (raw)

 Hi,
      Im using 2.4.19-rmk7-pxa1, on a pxa255. Recently I mounted jffs2 
as rootfs. While doing this the conventional way, I found that
it was being mounted readonly. Since I'm using M28W640 (ST flash) which 
needs to be unlocked upon every reboot, I thought the readonly
was because of this locking thing. So, I integrated the flash_unlock 
code into the mtd subsystem, but I still got the readonly mount.
After digging into init/do_mounts.c , I found  root_mountflags was by 
default readonly, and is sent to mount_block_root("/dev/root", 
root_mountflags);  only to be later reassigned somewhere in fs/super.c ! 
(s->s_flags = flags;)

The following addition to do_mounts.c , did the trick.

+ root_mountflags &= ~MS_RDONLY;
   mount_block_root("/dev/root", root_mountflags);

Now jffs2 mounts nice and clean, with readwrite !

I know you guys have dropped support for 2.4.x, but just for 
clarification, might even help several others struggling to get jffs2 
working as rootfs :)

Cheers,
Ashwin Chaugule
Embedded Systems Engineer
Aftek Infosys Ltd.
[Embedded Division]

             reply	other threads:[~2005-08-19 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20  0:14 Ashwin Chaugule [this message]
2005-08-19 13:19 ` is this a bug ? Thomas Gleixner
2005-08-20  1:36   ` Ashwin Chaugule
2005-08-19 18:25     ` Thomas Gleixner
2005-08-19 19:31       ` ashwinc

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=430675EB.9030905@aftek.com \
    --to=ashwinc@aftek.com \
    --cc=linux-mtd@lists.infradead.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