From: Shaya Potter <spotter@yucs.org>
To: linux-fsdevel@vger.kernel.org
Subject: oops in fs_may_remount_ro()
Date: 25 Jun 2003 16:57:23 -0400 [thread overview]
Message-ID: <1056574643.1094.8.camel@zaphod> (raw)
I'm somehow causing an oops in fs_may_remount_ro() (triggered by
rebooting when it tries to remount / ) in that the list of files off the
superblock either points to an invalid entry of some sort. It's either
invalid because the dentry is null, or because it doesn't exist
evidence seems to point in the not existent direction, as I stuck in an
if (!dentry)
{
printk("bad dentry\n");
continue;
}
in the loop, and it went nuts printing out data. I dont know enough
about this, so trying to figure out what could cause this problem? The
only things I modify are tty device related, so shouldn't have any
affect on the ext3 root (well seen w/ both an ext3 based /dev and a
devfs based dev)
anyways, any help/ideas/pointers would be appreciated.
thanks,
shaya
reply other threads:[~2003-06-25 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1056574643.1094.8.camel@zaphod \
--to=spotter@yucs.org \
--cc=linux-fsdevel@vger.kernel.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