Mdthbs

I have found a mistake on someone's code published online: what is the protocol?

Authorship dispute on a paper that came out of a final report of a course?

Manager asking me to eat breakfast from now on

How to interpret a promising preprint that was never published in peer-review?

Should I have shared a document with a former employee?

Real orthogonal and sign

Align the contents of a numerical matrix when you have minus signs

"This used to be my phone number"

Can error correction and detection be done without adding extra bits?

What is the name for the average of the largest and the smallest values in a given data set?

The most secure way to handle someone forgetting to verify their account?

/bin/sh: 0: Can't open sh

How to not confuse readers with simultaneous events?

Is encryption still applied if you ignore the SSL certificate warning for self-signed certs?

Symbolic integration of logmultinormal distribution

Can't install anything via terminal

How many opportunity attacks can you make per turn before becoming exhausted?

What could make large expeditions ineffective for exploring territory full of dangers and valuable resources?

In this iconic lunar orbit rendezvous photo of John Houbolt, why do arrows #5 and #6 point the "wrong" way?

Why is an object not defined as identity morphism?

Inscriptio Labyrinthica

Why would word of Princess Leia's capture generate sympathy for the Rebellion in the Senate?

How was Luke's prosthetic hand in Episode V filmed?

Transistor power dissipation rating

Distributing a Module.symvers

Compile Linux kernel module without Module.symversHow is Module.symvers generated?Compile Linux kernel module without Module.symvers

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I'm creating a set of kernel modules. Each module is its own project. One of these modules provides an interface to many child modules. ie. One parent module has exports and the child modules import.

Since the kernel code being compiled against already has a Module.symvers, I have no problems compiling and inserting the parent module. However, the child modules include a header file (describing the exports) from the parent. I've created the header in such a way it can just be copied into the a child project's include directory. My aim is for one day this parent module be part of the kernel tree.

When inserting the child modules, dmesg complains about unverified function signatures (can't remember the exact error message). To work around this I also copied the Module.symvers generated while building the parent into the build directories of the children.

While copying the Module.symvers works, the Module.symvers file contains full paths to the built module containing the exported functions. Therefore, sharing Module.symvers on github/gitlab would cause problems for anybody cloning the project.

What is the best/preferred way of handling this situation?

kernel-modules git

share|improve this question

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

add a comment | 

0

I'm creating a set of kernel modules. Each module is its own project. One of these modules provides an interface to many child modules. ie. One parent module has exports and the child modules import.

Since the kernel code being compiled against already has a Module.symvers, I have no problems compiling and inserting the parent module. However, the child modules include a header file (describing the exports) from the parent. I've created the header in such a way it can just be copied into the a child project's include directory. My aim is for one day this parent module be part of the kernel tree.

When inserting the child modules, dmesg complains about unverified function signatures (can't remember the exact error message). To work around this I also copied the Module.symvers generated while building the parent into the build directories of the children.

While copying the Module.symvers works, the Module.symvers file contains full paths to the built module containing the exported functions. Therefore, sharing Module.symvers on github/gitlab would cause problems for anybody cloning the project.

What is the best/preferred way of handling this situation?

kernel-modules git

share|improve this question

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

add a comment | 

I'm creating a set of kernel modules. Each module is its own project. One of these modules provides an interface to many child modules. ie. One parent module has exports and the child modules import.

Since the kernel code being compiled against already has a Module.symvers, I have no problems compiling and inserting the parent module. However, the child modules include a header file (describing the exports) from the parent. I've created the header in such a way it can just be copied into the a child project's include directory. My aim is for one day this parent module be part of the kernel tree.

When inserting the child modules, dmesg complains about unverified function signatures (can't remember the exact error message). To work around this I also copied the Module.symvers generated while building the parent into the build directories of the children.

While copying the Module.symvers works, the Module.symvers file contains full paths to the built module containing the exported functions. Therefore, sharing Module.symvers on github/gitlab would cause problems for anybody cloning the project.

What is the best/preferred way of handling this situation?

kernel-modules git

share|improve this question

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

share|improve this question

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

share|improve this question

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

asked 50 mins ago

TwiftyTwifty

12155 bronze badges

asked 50 mins ago

TwiftyTwifty

12155 bronze badges