* Filesystem as a module?
@ 2004-03-12 23:02 Vineet Joglekar
2004-03-13 12:07 ` Jan-Benedict Glaw
0 siblings, 1 reply; 4+ messages in thread
From: Vineet Joglekar @ 2004-03-12 23:02 UTC (permalink / raw)
To: linux-c-programming
Hi all,
I am trying to add some functionalities to ext2 filesystem, and use it as a module. Till now what I did is:
1: Copied the ext2 files and made the approprate changes
2: Copied files from usr/src/linux/fs/ directory
3: Copied relevant header files in /include/linux directory
The module gets compiled properly, but when I try to insert it using insmod, I am getting following errors like:
my_extv2.o: unresolved symbol generic_file_read_Rsmp_106b3732
my_extv2.o: unresolved symbol __get_free_pages_Rsmp_4784e424
my_extv2.o: unresolved symbol try_inc_mod_count_Rsmp_e6105b23
my_extv2.o: unresolved symbol blk_size_Rsmp_a2e0a082
my_extv2.o: unresolved symbol pidhash_Rsmp_4439d880
my_extv2.o: unresolved symbol floppy_eject
my_extv2.o: unresolved symbol smp_num_siblings
etc... and many more on the similar lines.
Whats wrong with my approach or do I need to add / modify few things?
Thanks and regards,
Vineet
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Filesystem as a module?
2004-03-12 23:02 Filesystem as a module? Vineet Joglekar
@ 2004-03-13 12:07 ` Jan-Benedict Glaw
0 siblings, 0 replies; 4+ messages in thread
From: Jan-Benedict Glaw @ 2004-03-13 12:07 UTC (permalink / raw)
To: linux-c-programming
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
On Fri, 2004-03-12 18:02:57 -0500, Vineet Joglekar <vintya@excite.com>
wrote in message <20040312230257.B06123DE6@xprdmailfe11.nwk.excite.com>:
> Hi all,
>
> I am trying to add some functionalities to ext2 filesystem, and use it as a module. Till now what I did is:
> 1: Copied the ext2 files and made the approprate changes
> 2: Copied files from usr/src/linux/fs/ directory
> 3: Copied relevant header files in /include/linux directory
Better create another directory below ./linux/fs/ and place your sources
there.
> The module gets compiled properly, but when I try to insert it using insmod, I am getting following errors like:
>
> my_extv2.o: unresolved symbol generic_file_read_Rsmp_106b3732
> my_extv2.o: unresolved symbol __get_free_pages_Rsmp_4784e424
> my_extv2.o: unresolved symbol try_inc_mod_count_Rsmp_e6105b23
> my_extv2.o: unresolved symbol blk_size_Rsmp_a2e0a082
> my_extv2.o: unresolved symbol pidhash_Rsmp_4439d880
> my_extv2.o: unresolved symbol floppy_eject
> my_extv2.o: unresolved symbol smp_num_siblings
You've mixed up your symbol versioning settings, most probably because
you're not building within the kernel's sources. That should all go away
automatically if you build within the kernel:)
> Whats wrong with my approach or do I need to add / modify few things?
Just copy all the sources back into the kernel tree and you're most
probably done.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Filesystem as a module?
@ 2004-03-13 19:47 Vineet Joglekar
2004-03-13 23:52 ` Jan-Benedict Glaw
0 siblings, 1 reply; 4+ messages in thread
From: Vineet Joglekar @ 2004-03-13 19:47 UTC (permalink / raw)
To: linux-c-programming
> Better create another directory below ./linux/fs/ and place your sources there.
Thanks for the prompt reply. I'll try to do it. I have 1 more question regarding this approach. In which make files do I need to make changes / additions so that while building the kernel, my newly added directory will be compiled too?
Thanks and regards
Vineet
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Filesystem as a module?
2004-03-13 19:47 Vineet Joglekar
@ 2004-03-13 23:52 ` Jan-Benedict Glaw
0 siblings, 0 replies; 4+ messages in thread
From: Jan-Benedict Glaw @ 2004-03-13 23:52 UTC (permalink / raw)
To: linux-c-programming
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Sat, 2004-03-13 14:47:21 -0500, Vineet Joglekar <vintya@excite.com>
wrote in message <20040313194721.EB5123DC2@xprdmailfe6.nwk.excite.com>:
> > Better create another directory below ./linux/fs/ and place your sources there.
>
> Thanks for the prompt reply. I'll try to do it. I have 1 more question regarding this approach. In which make files do I need to make changes / additions so that while building the kernel, my newly added directory will be compiled too?
Well, for 2.4.x, you'll need to touch ./linux/fs/Makefile,
./linux/fs/Config.in and ./linux/Documentation/Configure.help. In 2.6.x,
you need to modify ./linux/fs/Makefile and ./linux/fs/Kconfig.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-03-13 23:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-12 23:02 Filesystem as a module? Vineet Joglekar
2004-03-13 12:07 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-03-13 19:47 Vineet Joglekar
2004-03-13 23:52 ` Jan-Benedict Glaw
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).