From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] gethostbyname_r01: check whether a system is vulnerable or not.
Date: Thu, 26 Feb 2015 14:39:25 +0100 [thread overview]
Message-ID: <20150226133925.GA16136@rei.suse.de> (raw)
In-Reply-To: <1152905776.19309335.1424957443988.JavaMail.zimbra@redhat.com>
Hi!
> > > If you want to go ahead and start runtest/libc, testcases/libc and move
> > > all the libc tests there I'm all for it.
> >
> > On the other hand, I'm not sure where to draw the line.
>
> For this particular regression test it seemed clear cut, but in general
> for functional and stress tests I don't a have good answer.
The most reasonable definition to me seems to call things that have very
thin wrapper in glibc or are called by syscall() to be syscall testcases
and the rest, even when they end up calling particular syscall to be
libc tests. But that is still wrong as any other simple definition.
The other simple and wrong option is to move everything that is
implemented purely in userspace to testcases/libc/.
Or we can stop pretending that there is a clear line between kernel and
libc and rename the syscalls to something else. The question is what
should be the new name, I do not have a good idea for that.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-02-26 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 7:46 [LTP] [PATCH] gethostbyname_r01: check whether a system is vulnerable or not Zeng Linggang
2015-02-26 9:00 ` Cyril Hrubis
[not found] ` <1449902344.19156887.1424942209488.JavaMail.zimbra@redhat.com>
2015-02-26 9:23 ` Cyril Hrubis
2015-02-26 9:26 ` Cyril Hrubis
[not found] ` <1152905776.19309335.1424957443988.JavaMail.zimbra@redhat.com>
2015-02-26 13:39 ` Cyril Hrubis [this message]
[not found] ` <1425016398.11179.22.camel@G08JYZSD130126.localdomain>
2015-03-02 15:13 ` [LTP] [PATCH v2] " Cyril Hrubis
[not found] ` <741733497.21023393.1425309844772.JavaMail.zimbra@redhat.com>
2015-03-02 15:41 ` Cyril Hrubis
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=20150226133925.GA16136@rei.suse.de \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox