From: Joel Reardon <joel@clambassador.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: mtdchar kernel oops
Date: Sun, 15 Apr 2012 13:58:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1204151350450.13924@eristoteles.iwoars.net> (raw)
I think that this patch:
"mtdchar: kill persistently held vfsmount"
http://permalink.gmane.org/gmane.linux.kernel.commits.head/314175
has started causing kernel oops's when running ubiformat. The oops is
occuring in fs/namespace.c's mnt_add_count() line:
this_cpu_add(mnt->mnt_pcp->mnt_count, n);
with the stack trace:
mntget()
simple_pin_fs()
mtdchar_open()
Cheers,
Joel
next reply other threads:[~2012-04-15 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 11:58 Joel Reardon [this message]
2012-04-15 14:19 ` mtdchar kernel oops Fabio Estevam
2012-04-19 0:51 ` Fabio Estevam
2012-04-15 15:32 ` Al Viro
2012-04-15 17:57 ` Joel Reardon
2012-04-15 21:53 ` Al Viro
2012-04-16 12:37 ` Joel Reardon
2012-04-16 19:17 ` Al Viro
2012-04-18 12:55 ` Joel Reardon
2012-04-18 13:12 ` Artem Bityutskiy
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=alpine.DEB.2.00.1204151350450.13924@eristoteles.iwoars.net \
--to=joel@clambassador.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).