From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: backing_dev_info == 8?!
Date: Wed, 08 Dec 2004 09:18:26 +1100 [thread overview]
Message-ID: <1102457906.5879.7.camel@desktop.cunninghams> (raw)
Hi all.
Running 2.6.9, I sometimes get oopses in what I think is called VFS
related code (struct inode, dentry and so on). Last night, for example,
I saw an oops in file_ra_state_init which occurred because the
backing_dev_info being dereferenced was set to 0x8. Everything else in
the struct looked normal, and related structs with backing_dev_info also
had the value set to 8. (The oops occurred in process locate, called via
sys_open). My question, then, is "Does anyone know if any bugs related
to this have been found/fixed since 2.6.9?". I'm considering running BK
for a while and seeing if it's still there.
The kernel isn't vanilla, but I don't think any of the additions
(Win4Lin, kgdb, suspend2, bootsplash) are affecting this.
Regards,
Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6
reply other threads:[~2004-12-07 22:22 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=1102457906.5879.7.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=linux-kernel@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