Re: [PATCH ftrace/core v6 5/5] kselftest, ftrace: Add ftrace IPMODIFY flag test

Steven Rostedt
2014-11-24T15:07:41Z

On Mon, 24 Nov 2014 23:11:12 +0900
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:

> So, if your server directory is mounted with noexec, it's an environmental
> problem. I guess you can not build any kernel drivers on that testbox, can you?
>

You're right about the noexec, even though my fstab has "exec" in it ??

I use a custom distcc build to build the kernel, and I don't waste time
setting up that environment for a testbox, which means I can't build a
module for the test kernels because it would be using a different
compiler in that case.

> Anyway, this gives us a good question, "should test binaries be made by
> server or client(testbox) environment?" This ipmodify driver is a binary
> and it should be built with the kernel binary (by server) I think.
> But yes, I missed the Makefile didn't allow that (this always referred
> installed running kernel builddir).
>
> I hope to have CONFIG_KSELFTEST_BINARIES for Kconfig, or make prep_kselftest
> target to build these binaries with kernel...

Is that what this would need? I would think we could add a
CONFIG_KSELFTEST_MODULES, that would build any modules needed for
selftests and have them in /lib/modules just like any other module.

-- Steve

>
> Shuah, what would you think about this?
>
> > make[4]: *** [ipmodify.ko] Error 2
> > make[3]: *** [sub-make] Error 2
> > make[2]: *** [__sub-make] Error 2
> > make[2]: Leaving directory `/home/rostedt/work/git/nobackup/bxtest/trace'
> > make[1]: *** [ipmodify.ko] Error 2
> > make[1]: Leaving directory `/work/git/linux-trace.git/tools/testing/selftests/ftrace/ipmodify'
> > make: *** [all] Error 2
> >
> >
> > Thanks (on my way to bed),
>
> Thank you :),
>
>