All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: Rishikesh K Rajak <risrajak@in.ibm.com>,
	"ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>,
	Iranna D Ankad <iranna.ankad@in.ibm.com>
Subject: Re: [LTP] LTP's filecaps test gives false positive results
Date: Thu, 18 Mar 2010 14:55:16 +0530	[thread overview]
Message-ID: <20100318092516.GA16328@linux.vnet.ibm.com> (raw)
In-Reply-To: <364299f41003030114x30e251d6x7cd7993f8f75792f@mail.gmail.com>

On Wed, Mar 03, 2010 at 01:14:12AM -0800, Garrett Cooper wrote:
>     Yes -- and I think this is because the constants no longer have
> the same name:
> 
> http://fxr.watson.org/fxr/source/include/linux/prctl.h?v=linux-2.6#L68
> 
>     Note -- CAP_BSET_DROP should be: PR_CAPBSET_DROP, etc.
> 
>     Which is why I stress _not_ putting these hardcoded constants in
> test files (POLLHDRDUP -- or whatever it was in ppoll01 -- is the only
> real violation I can remember OTOH that I need to clean up
> eventually). We need to be consistent with any and all documentation
> provided to end-developers or we [LTP] are going to shoot ourselves in
> the foot if and when the underlying functionality changes.
>     I'll update the tests this weekend, but I would like it if someone
> test the tests on an outdated distro (RHEL 4.x?) once I provide a

Hi Garret,

Can you please look this again ?

-Rishi

> patch to ensure that nothing's being regressed. Based on some really
> simple inspection it appears that these tests are compatible only with
> libcapability 2.x+, but I could be wrong...
> Thanks,
> -Garrett
> 

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2010-03-18  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 10:11 [LTP] LTP's filecaps test gives false positive results Iranna D Ankad
2010-03-02 15:21 ` Serge E. Hallyn
2010-03-02 16:25   ` Garrett Cooper
2010-03-02 17:35     ` Serge E. Hallyn
2010-03-02 18:25       ` Garrett Cooper
2010-03-03  5:56         ` Rishikesh K Rajak
2010-03-03  9:14           ` Garrett Cooper
2010-03-03  9:23             ` Rishikesh K Rajak
2010-03-03 16:00             ` Serge E. Hallyn
2010-03-18  9:25             ` Rishikesh K Rajak [this message]
2010-03-18 14:55               ` Serge E. Hallyn
2010-03-18 19:13                 ` Garrett Cooper
2010-03-02 16:39 ` Garrett Cooper

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=20100318092516.GA16328@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=iranna.ankad@in.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=risrajak@in.ibm.com \
    --cc=yanegomi@gmail.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.