linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <groeck@google.com>
To: Jeff Xu <jeffxu@google.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
	linux-security-module@vger.kernel.org,
	"Jorge Lucangeli Obes" <jorgelo@chromium.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Kees Cook" <keescook@chromium.org>
Subject: Re: [PATCH] selftests/landlock: skip ptrace_test when YAMA is enabled
Date: Wed, 13 Jul 2022 17:30:28 -0700	[thread overview]
Message-ID: <CABXOdTf=o1zSSDUPNubHxAnF=1dOwOuxKfrViPHAD-tV_4x=Ww@mail.gmail.com> (raw)
In-Reply-To: <CALmYWFvfRFfZbk=9P-=RNtjhXoR0ToQKnVVEZwmXB9yxLEHotg@mail.gmail.com>

On Wed, Jul 13, 2022 at 4:44 PM Jeff Xu <jeffxu@google.com> wrote:
>
> > > a correction:
> > >
> > >     =====================================
> > >     case 0 - classic ptrace permissions: a process can PTRACE_ATTACH to
> > >     any other
> > >          process running under the same uid, as long as it is dumpable (i.e.
> > >          did not transition uids, start privileged, or have called
> > >          prctl(PR_SET_DUMPABLE...) already). Similarly, PTRACE_TRACEME is
> > >          unchanged.
> > >
> > >     Test: All passing
> > >
> > > // Base_test: 7/7 pass.
> > > // Fs_test 46/48 pass
> > > //.   not ok 47 layout2_overlay.no_restriction
> > > //.   not ok 48 layout2_overlay.same_content_different_file
> > > //  Ptrace 8/8 pass
>
>
> > Hmm, well, it is not related to Yama then. Could it be linked to other
> > Chromium OS non-upstream patches?
>
>
> fs_test.c 47 and 48 are failing in chromeOS because OVERLAYFS is not
> enabled in chromeOS.
> If there is a reliable way of detecting OVERLAYFS (checking mount
> overlayfs is successful ? ), this is a good candidate to add SKIP.
>

IS_ENABLED(CONFIG_OVERLAY_FS) ?

> Overall, all the failure of landlock selftest seen in chromeOS are
> expected, we just need to modify the test.
>
> Thanks
> Best Regards
> Jeff
>
>
>
> On Thu, Jul 7, 2022 at 7:25 AM Mickaël Salaün <mic@digikod.net> wrote:
> >
> >
> > On 07/07/2022 01:35, Jeff Xu wrote:
> > > a correction:
> > >
> > >     =====================================
> > >     case 0 - classic ptrace permissions: a process can PTRACE_ATTACH to
> > >     any other
> > >          process running under the same uid, as long as it is dumpable (i.e.
> > >          did not transition uids, start privileged, or have called
> > >          prctl(PR_SET_DUMPABLE...) already). Similarly, PTRACE_TRACEME is
> > >          unchanged.
> > >
> > >     Test: All passing
> > >
> > > // Base_test: 7/7 pass.
> > > // Fs_test 46/48 pass
> > > //.   not ok 47 layout2_overlay.no_restriction
> > > //.   not ok 48 layout2_overlay.same_content_different_file
> > > //  Ptrace 8/8 pass
> >
> > Hmm, well, it is not related to Yama then. Could it be linked to other
> > Chromium OS non-upstream patches?

  reply	other threads:[~2022-07-14  0:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 22:29 [PATCH] selftests/landlock: skip ptrace_test when YAMA is enabled Jeff Xu
2022-06-30 15:09 ` Mickaël Salaün
2022-06-30 15:31 ` Mickaël Salaün
2022-07-05 21:49   ` Jeff Xu
2022-07-06 23:41     ` Jeff Xu
2022-07-07 14:24     ` Mickaël Salaün
     [not found]     ` <CALmYWFvcSn_wks0bXo3_DUyYGtVW_MHrrO1dRoYcxY4uiB1KEA@mail.gmail.com>
2022-07-07 14:25       ` Mickaël Salaün
2022-07-13 23:44         ` Jeff Xu
2022-07-14  0:30           ` Guenter Roeck [this message]
2022-07-14 18:36             ` Jeff Xu
2022-07-14 20:39               ` Guenter Roeck
2022-07-15  0:35                 ` Jeff Xu
2022-07-15 21:41                   ` Jeff Xu
2022-07-15 22:42                     ` Guenter Roeck
2022-07-16  0:16                       ` Jeff Xu
2022-07-16 21:45                         ` Guenter Roeck
2022-07-18 21:24                           ` Mickaël Salaün

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='CABXOdTf=o1zSSDUPNubHxAnF=1dOwOuxKfrViPHAD-tV_4x=Ww@mail.gmail.com' \
    --to=groeck@google.com \
    --cc=groeck@chromium.org \
    --cc=jeffxu@google.com \
    --cc=jorgelo@chromium.org \
    --cc=keescook@chromium.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.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;
as well as URLs for NNTP newsgroup(s).