All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: Linus Test Project <ltp-list@lists.sourceforge.net>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails
Date: Thu, 6 May 2010 12:55:12 -0500	[thread overview]
Message-ID: <20100506175512.GA25514@us.ibm.com> (raw)
In-Reply-To: <j2v364299f41005061038ucdbdaf19hcdad19491344e76d@mail.gmail.com>

Quoting Garrett Cooper (yanegomi@gmail.com):
> On Thu, May 6, 2010 at 6:53 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Quoting Garrett Cooper (yanegomi@gmail.com):
> >> On May 5, 2010, at 11:56 PM, Subrata Modak wrote:
> >>
> >> > Subject: LTPś sysctl03 test fails
> >> >
> >> > Issues Description Below:
> >> > =====================================
> >> > # ./runltp -s sysctl03
> >> > <<<test_output>>>
> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> >> > sysctl03    2  TFAIL  :  Expected EPERM, got 13
> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> >> > <<<execution_status>>>
> >> > initiation_status="ok"
> >> > duration=0 termination_type=exited termination_id=1 corefile=no
> >> > cutime=0 cstime=0
> >> > <<<test_end>>>
> >>
> >>       Already known and recently discussed.
> >
> > Not only can things move glacially in kernel-land, but decisions not
> > yet implemented can be changed.
> >
> > In the meantime, the sysctl's sit there as a potential subject for
> > exploitation.
> >
> > So not meaning to be argumentative for its own sake, I nevertheless
> > think it's better to fix the test than either to ignore or remove
> > it.  Two untested patches below - the one just replaces EPERM with
> > EACCESS.  The other removes the (imo misuided) notion that we can
> > guess at the failing errno.
> 
> Except that the documentation (manpages) should explicitly state what
> the failing conditions are for any given libcall and syscall. If not,
> the Linux kernel devs and documentation team have failed to do their
> job.

So since we're all member of the doc team, send a patch for sysctl(2)
manpage ERRORS section :)

(mtk cc:d as this is probably news to him)

> > An LSM could choose to return -EPERM
> > after all, or perhaps even something different.  The thing that
> > should scare us is if the call succeeds.  If we give any false
> > positives, then true positives will seem less scary.
> 
> This will fail on older kernels as sysctl(2) always returned EPERM due

Sorry - what will fail?

I think you're saying the first patch will, and I agree, which is why
I advocate the second one i pasted in.

> to the way it was improperly designed. Please see the previous thread
> for more info: http://lkml.org/lkml/2010/3/4/354
> 
> Thanks,
> -Garrett

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-05-06 17:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  6:55 [LTP] [00/12 FAILURE] Reporting LTP run issues on Fedora 13 ppc6 Subrata Modak
2010-05-06  6:56 ` [01/12 FAILURE] LTPX Memory CGROUP test creates Call Trace and Badness at mm/oom_kill.c:393 Subrata Modak
2010-05-06  6:56 ` [02/12 FAILURE] LTPX File Capabilities tests becomes defunct and does not complete beyond 12 hours Subrata Modak
2010-05-06  6:56 ` [03/12 FAILURE] LTPX Memory Conroller test fails and hangs system for more than " Subrata Modak
2010-05-06  6:56 ` [04/12 FAILURE] LTPX sysctl03 test fails Subrata Modak
2010-05-06  8:05   ` [LTP] [04/12 FAILURE] LTP? " Garrett Cooper
2010-05-06 13:53     ` Serge E. Hallyn
2010-05-06 17:38       ` Garrett Cooper
2010-05-06 17:55         ` Serge E. Hallyn [this message]
2010-05-06 17:59           ` Garrett Cooper
2010-05-06 18:39             ` Serge E. Hallyn
2010-05-07  9:05               ` Subrata Modak
2010-05-07  9:22               ` Garrett Cooper
2010-05-06  6:57 ` [05/12 FAILURE] LTPX proc01 " Subrata Modak
2010-05-06  8:04   ` [LTP] [05/12 FAILURE] LTP? " Garrett Cooper
2010-07-27 17:37     ` Subrata Modak
2010-07-27 17:38     ` Subrata Modak
2010-05-06  6:57 ` [LTP] [06/12 FAILURE] Many CONTAINER tests of LTP fail Subrata Modak
2010-05-06 17:53   ` Garrett Cooper
2010-05-06 17:59     ` Dan Smith
2010-07-27 17:40     ` Subrata Modak
2010-05-06  6:57 ` [07/12 FAILURE] LTPX MEMORY CGROUP FUNCTION tests fails Subrata Modak
2010-07-28 17:34   ` [LTP] [07/12 FAILURE] LTPE " Subrata Modak
2010-05-06  6:58 ` [08/12 FAILURE] LTPX clock gettime03 fails Subrata Modak
2010-05-06  7:04   ` [LTP] [08/12 FAILURE] LTPE " Suzuki Poulose
2010-05-06  7:55     ` Garrett Cooper
2010-05-06  9:03       ` Suzuki Poulose
2010-05-06 17:42         ` Garrett Cooper
2010-05-07  8:53           ` Subrata Modak
2010-06-01 15:40         ` Suzuki Poulose
2010-06-02 12:57           ` Subrata Modak
2010-07-27 18:03             ` Subrata Modak
2010-05-06  6:58 ` [09/12 FAILURE] LTPX timer create04 fails Subrata Modak
2010-05-07  2:12   ` [LTP] [09/12 FAILURE] LTP " Henry xu
2010-07-28 12:46   ` [LTP] [09/12 FAILURE] LTPE " Subrata Modak
2010-05-06  6:58 ` [10/12 FAILURE] LTPX ar01 fails Subrata Modak
2010-05-06  6:58 ` [11/12 FAILURE] LTPX file test fails Subrata Modak
2010-05-06  8:01   ` [LTP] [11/12 FAILURE] LTP? " Garrett Cooper
2010-05-06  6:59 ` [12/12 FAILURE] LTPX cron tests fails Subrata Modak

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=20100506175512.GA25514@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mtk.manpages@gmail.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.