Hi! > > Please review this patch. Thanks. > > > > There is a bug on 64bit sendfile() with large file, please see > > https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-June/118128.html > > for details. > > I'd like to ask an irrelevant question about that where can we get such bug > report or similar issues > about syscalls from a stable place(url), or how did you found this issue, > thanks.
This is IMHO most problematic part of producing LTP testcases. There is no single place to pickup kernel regression/bug reports and produce testcases for them. This is partly caused by the nature of how the community works and partly because nobody cared about this (this happens to change slowly now). > Give that currently there are 1039 test cases about syscalls in LTP(cat > runtest/syscalls | grep -v "^#" | sed -e '/^$/d' | wc -l), > we can tell that syscalls is a very big test suite in LTP, so I'd like to add > all similar regression test about > syscalls to LTP, which will expand ltp's test coverage, thanks. And we don't have 100% coverage either, there are numerous syscalls/ioctls/... that are not even documented properly. But at least new syscalls along with documentation and example source code are starting to appear on linux-api mailing list. See also: https://www.kernel.org/doc/man-pages/maintaining.html which lists various sources where to get information about kernel/libc interfaces. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
