All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [RFC PATCH] regression test for 64bit sendfile capped at 2G
Date: Tue, 15 Jul 2014 12:10:31 +0200	[thread overview]
Message-ID: <20140715101030.GB27102@rei> (raw)
In-Reply-To: <53BB90C6.9020101@cn.fujitsu.com>

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
chrubis@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

      parent reply	other threads:[~2014-07-15 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  3:16 [LTP] [RFC PATCH] regression test for 64bit sendfile capped at 2G Han Pingtian
2014-07-07 12:14 ` Jan Stancek
2014-07-08  7:23   ` Han Pingtian
2014-07-08 10:36     ` Jan Stancek
2014-07-08 11:55       ` Jan Stancek
2014-07-08 12:30         ` Jan Stancek
2014-07-08 14:42           ` Han Pingtian
2014-07-14  7:40             ` Jan Stancek
2014-07-08  6:33 ` Xiaoguang Wang
2014-07-07  6:51   ` Han Pingtian
2014-07-08  7:46     ` Xiaoguang Wang
2014-07-07 11:44       ` Han Pingtian
2014-07-15 10:10   ` chrubis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140715101030.GB27102@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=wangxg.fnst@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.