On Tue, Oct 10, 2017 at 01:15:11PM +0530, Pintu Kumar wrote:
> Hi All,
>
> Is anybody familiar with ktests of selftests framework under: tool/testing/ ?
> I have some queries.
>
> 1) What is the difference between ktests and selftests ? How to choose ?
It depends on what you want to do, but
Hi,
I am actually interested in kselftests.
My requirement is:
I have a sub folders for test. Example: tools/testing/selftests//
I have my own Makefile, and some set of C source files under folder1
I also have a test script under folder1, that tests 2 executable
generated out of 7 C files.
I
On Tue, Oct 10, 2017 at 09:08:30AM +0200, Greg KH wrote:
> On Tue, Oct 10, 2017 at 10:17:09AM +1100, Tobin C. Harding wrote:
> > Hi,
> >
> > I would like to create a boot time variable i.e a variable that is set once
> > at boot time. Variable
> > does not need to be globally accessible.
On Tue, 10 Oct 2017 10:17:09 +1100, "Tobin C. Harding" said:
> I would like to create a boot time variable i.e a variable that is set once
> at boot time. Variable
> does not need to be globally accessible. (actually I am using two variables).
The canonical way to have stuff happen at boot is
Hi guys.
I want to write a code (or library) which it used AFL and QEMU in order to
monitor functions which called by an executable.
I have worked with AFL for binary instrumentation and fuzzing. Also, I
could find out multiple vulnerabilities in third-party libraries but I
can't realize how is
Hi All,
Is anybody familiar with ktests of selftests framework under: tool/testing/ ?
I have some queries.
1) What is the difference between ktests and selftests ? How to choose ?
2) How to invoke a test under ktests?
For example:
I have some user space C program, that tests some kernel
On Tue, Oct 10, 2017 at 10:17:09AM +1100, Tobin C. Harding wrote:
> Hi,
>
> I would like to create a boot time variable i.e a variable that is set once
> at boot time. Variable
> does not need to be globally accessible. (actually I am using two variables).
static foo = 42;
should be all you
