Hi,
> Hmm. I used an old set of patches to avoid filtering out local changes
> again. Try the enclosed up to date patches.
Hmmm.
Fresh -current, fresh patch.
(Hunk 2 still doesnt apply cleanly, but this seems to be irrelevant
for the problem)
Old symptom:
...
mounting root from ufs:/dev/ad0s3a
I made a kernel module that logs execve system calls by intercepting the
execve syscall, log it and then execute the original syscall. This was
pretty straightforward to do, and it works beautifully on STABLE, but on
CURRENT it bombs on this line:
uid = p->p_cred->pc_ucred->cr_uid;
So, my questi
On 10-Jan-02 Emiel Kollof wrote:
> I made a kernel module that logs execve system calls by intercepting the
> execve syscall, log it and then execute the original syscall. This was
> pretty straightforward to do, and it works beautifully on STABLE, but on
> CURRENT it bombs on this line:
>
> uid
I've recently committed a series of changes which affect the way
modules are built. Since I can't test *every* module, please let me
know immediately if you run into problems with modules refusing to
load due to undefined symbols, or not working "quite right". I've
tried hard to make sure it's
* Mike Smith <[EMAIL PROTECTED]> [020110 17:36] wrote:
>
> Questions and comments welcome.
Looks really cool, nice job.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Mike Smith wrote:
> In order to deal with this problem, I have changed the module build
> process so that symbols global to the module are converted to local
> symbols when the module is linked into the .kld/,ko file. In order
> to allow modules that intentionally export symbols to continue to do
> In the book "Writing Linux DEvice Drivers", there is a neat bit
> on how Linux does this. Effectively, they export all symbols
> within the module load if there is no explicit symbol table
> export call, and they export only the symbols that are requested,
> if there is.
I considered this appr
