[Crackerjack-users 00060] Re: [LTP] Crackerjack and Linux Test Project

[Michael K. <mtk...@go...>]

>> For this to happen, we need to make our test cases ready when the
>> corresponding kernel features are in -mm tree. Let me know your ideas on
>> this.
>
>
> Part of the problem here is knowing when interface changes have occurred.
> Seeing new system calls in a release is easy. But, for the project to be
> truly effective, all kernel-userland interfacechanges need to be checked
> for, including
>
> system calls
> ioctl()s
> netlink
> /proc
> /sys (okay -- that's a big ask at the moment)
> virtual /dev interfaces used for kernel-uerland communication
> And probably other things I forgot right now.

An afterthought: for each man-pages release, I publish a changelog,
and also mail the changlelog out to a list of people that I (manually)
maintain.  Many items in the change log relate to new/changed features
in the latest, or a recent, kernel, so that it can be a good source
for finding out what to test.  It's online here:

http://www.kernel.org/doc/man-pages/changelog.html

And if anyone wants to be subscribed to my release changelog mailout,
let me know.

Cheers,

Michael