From: orjan.friberg@axis.com (Orjan Friberg)
To: linux-mtd@lists.infradead.org
Subject: [PATCH] Oops on umount/mount (JFFS 1)
Date: Wed, 12 Mar 2003 15:17:26 +0100 [thread overview]
Message-ID: <3E6F4176.E49F1450@axis.com> (raw)
In-Reply-To: 3E6CB695.CF72E9BC@axis.com
Orjan Friberg wrote:
>
> The patch below takes care of a umount/mount-related oops I had. It happens when a JFFS 1 file
> system is mounted for the second time if CONFIG_JFFS_PROC_FS is on, due to jffs_proc_root being
> freed on a umount, but only being allocated once (at init). The patch below allocates
> jffs_proc_root each time the proc entry is registered. (In my case, besides corrupting a node, the
> bug also manifested itself by /proc/fs/jffs not showing up after the second mount.)
Is this ok to commit?
--
Orjan Friberg
Axis Communications AB
prev parent reply other threads:[~2003-03-12 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 16:00 [PATCH] Oops on umount/mount (JFFS 1) Orjan Friberg
2003-03-12 14:17 ` Orjan Friberg [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=3E6F4176.E49F1450@axis.com \
--to=orjan.friberg@axis.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.