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]
next reply other threads:[~2005-08-19 12:16 UTC|newest]
Thread overview: 41+ 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
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 3:08 Is this a bug? Peter Teoh
2013-02-19 9:32 David Wade
2013-02-19 9:42 ` Andreas Ericsson
2013-02-19 9:47 ` Erik Faye-Lund
2013-02-19 11:02 ` Duy Nguyen
2013-02-22 19:29 ` Phil Hord
2013-02-22 21:48 ` Junio C Hamano
2011-06-21 21:57 Is this a Bug? Christian Deussen
2011-06-21 22:49 ` Greg Freemyer
2011-06-22 7:28 ` Wilson Felipe
2011-06-22 19:50 ` julie Sullivan
2011-06-22 21:21 ` julie Sullivan
2011-06-23 12:16 ` Christian D.
2011-06-23 13:03 ` Jonathan Neuschäfer
2011-06-23 18:49 ` Jonathan Neuschäfer
2011-04-02 8:05 Is this a bug? Ding Dinghua
2011-04-02 16:32 ` Amir Goldstein
2011-04-03 9:24 ` Ding Dinghua
2011-04-03 14:51 ` Yongqiang Yang
2011-04-03 15:44 ` Amir Goldstein
2011-03-24 0:46 is " Jay
2011-03-25 15:18 ` Steven Rostedt
2002-07-15 13:57 Is " Tisserand Patrice
2002-07-15 14:08 ` Takashi Iwai
2001-08-07 11:51 is " Thodoris Pitikaris
2001-08-07 13:51 ` Andrzej Krzysztofowicz
2001-08-08 2:19 ` Dr. Kelsey Hudson
2001-08-08 3:15 ` J Sloan
2001-08-08 3:45 ` Dr. Kelsey Hudson
2001-08-08 10:53 ` David Weinehall
2001-08-08 11:05 ` Alan Cox
2001-08-08 12:59 ` Ron Flory
2001-08-08 16:51 ` jury gerold
2001-08-10 9:12 ` Eric W. Biederman
2001-08-10 12:22 ` jury gerold
2001-08-10 16:22 ` Eric W. Biederman
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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.