I've gotten some time to start working with this code again and I'm
looking for some review on my first couple patches. After these two
patches the code does little more than print out lots of details
about the binary being run to the syslog and then fail with -ENOEXEC,
but it's a start. I'm currently fixing up my icky memory-mapping
code to avoid allocating big chunks of kernel memory for tables in
the binary, and once I make some progress on that I'll submit it too.
I'd appreciate any information on what is required in the load_binary
function in my binfmt. In particular, if there's anything which fs/
binfmt_elf.c does do which is *NOT* required, I'd be interested to
know what and why. Thanks for all your assistance.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
