From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: favourite vfs globals
Date: 28 Nov 2003 15:42:57 -0700 [thread overview]
Message-ID: <1070059377.2328.1.camel@patrh9> (raw)
In-Reply-To: <1070056276.3518.13.camel@patrh9>
> > > > Which vfs globals are the most fun, in lk like 2.6.0-test11?
"That question I can't yet answer, but":
> > > > ... we ... see the global variables of modules ...
> > > ... when the modules share those variables with non-module code
Success! Thanks again for the hints.
(gdb) print /x udf_gdb
$1 = 0xcafefacf
(gdb) #
(gdb) print udf_gdb_fstype
$3 = (struct file_system_type *) 0xdf9639c0
(gdb) #
(gdb) print *udf_gdb_fstype
$4 = {name = 0xdf95fc65 "udf", fs_flags = 1, get_sb = 0xdf9592d4,
kill_sb = 0xc0153d9c <kill_block_super>, owner = 0xdf963e80, next = 0x0,
fs_supers = {next = 0xd5fa7d5c, prev = 0xd5fa7d5c}}
(gdb)
diff -Nur linux-2.6.0-test11/fs/udf/super.c linux/fs/udf/super.c
--- linux-2.6.0-test11/fs/udf/super.c 2003-11-26 13:44:41.000000000 -0700
+++ linux/fs/udf/super.c 2003-11-28 15:23:55.000000000 -0700
@@ -189,10 +189,19 @@
struct nls_table *nls_map;
};
+extern int udf_gdb;
+extern struct file_system_type * udf_gdb_fstype;
+
static int __init init_udf_fs(void)
{
int err;
printk(KERN_NOTICE "udf: registering filesystem\n");
+
+ printk(KERN_NOTICE "udf: before incrementing hello_gdb\n");
+ udf_gdb_fstype = &udf_fstype;
+ ++udf_gdb;
+ printk(KERN_NOTICE "udf: after incrementing hello_gdb\n");
+
err = init_inodecache();
if (err)
goto out1;
diff -Nur linux-2.6.0-test11/drivers/block/scsi_ioctl.c linux/drivers/block/scsi_ioctl.c
diff -Nur linux-2.6.0-test11/drivers/block/ll_rw_blk.c linux/drivers/block/ll_rw_blk.c
--- linux-2.6.0-test11/drivers/block/ll_rw_blk.c 2003-11-26 13:42:58.000000000 -0700
+++ linux/drivers/block/ll_rw_blk.c 2003-11-28 15:24:06.000000000 -0700
@@ -2445,6 +2445,11 @@
}
}
+int udf_gdb = 0xCAFEFACE;
+struct file_system_type * udf_gdb_fstype;
+EXPORT_SYMBOL(udf_gdb);
+EXPORT_SYMBOL(udf_gdb_fstype);
+
static int __end_that_request_first(struct request *req, int uptodate,
int nr_bytes)
{
prev parent reply other threads:[~2003-11-28 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 21:05 favourite vfs globals Pat LaVarre
2003-11-28 21:22 ` Pat LaVarre
2003-11-28 21:43 ` Pat LaVarre
2003-11-28 21:51 ` Pat LaVarre
2003-11-28 22:42 ` Pat LaVarre [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=1070059377.2328.1.camel@patrh9 \
--to=p.lavarre@ieee.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 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.