From: Signal9 <signal9@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: possible bug in VFS ?
Date: Sat, 13 Oct 2001 01:50:31 +0000 [thread overview]
Message-ID: <01101301503101.00295@apocalipsis> (raw)
When i tried bestcrypt (a crypto-fs) with the new 2.4.12 kernel, i got a
ooops when mounting a device. The oops was in this line:
(in bcrypt-0.8-6/mod/bc_dev24.c)
root = current->fs->rootmnt;
list_for_each(ptr, &root->mnt_list) {
mnt = list_entry(ptr, struct vfsmount, mnt_list);
sb = mnt ? mnt->mnt_sb : NULL;
if (NULL != sb && dev == sb->s_dev) <============
mntget(mnt);
}
The oops was a pointer dereference to 0x9. I added some printk's to see the
values of the pointers. I did see that in the last 'struct vfsmount' linked
inside root->mnt_list, the mnt_sb field is '0x1', so when it tries to access
sb->sb_dev it dereferences a pointer to 0x9. The field mnt_devname was NULL.
¿Is this a bug in the kernel or a bug in bestcrypt?
Cheers,
- Doing
PD: Please send replies with CC to me, since i'm not subscribed to the list :)
next reply other threads:[~2001-10-12 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 1:50 Signal9 [this message]
2001-10-13 0:06 ` possible bug in VFS ? Alexander Viro
2001-10-13 12:32 ` Signal9
2001-10-13 15:35 ` Alexander Viro
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=01101301503101.00295@apocalipsis \
--to=signal9@gmx.net \
--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 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.