prctl07 from ubuntu_ltp_syscalls failed on T-4.4

Bug #1839064 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Triaged
Undecided
Unassigned
linux-signed-lts-xenial (Ubuntu)
New
Undecided
Unassigned

Bug Description

Test failed with:
  FAIL: PR_CAP_AMBIENT_RAISE succeeded unexpectedly because of NO_RAISE_SECBIT set

Step to reproduce:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "prctl07 prctl07" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

<<<test_output>>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
prctl07.c:180: INFO: kernel supports PR_CAP_AMBIENT
prctl07.c:64: PASS: At the beginning, CapAmb in /proc/self/status doesn't have CAP_NET_BIND_SERVICE
prctl07.c:86: PASS: PR_CAP_AMBIENT_RAISE failed with EPERM on non-inheritable cap
prctl07.c:86: PASS: PR_CAP_AMBIENT_RAISE failed with EPERM on non-permitted cap
prctl07.c:83: FAIL: PR_CAP_AMBIENT_RAISE succeeded unexpectedly because of NO_RAISE_SECBIT set
prctl07.c:74: PASS: PR_CAP_AMBIENT_RAISE CAP_NET_BIND_SERVICE succeeded
prctl07.c:74: PASS: PR_CAP_AMBIENT_RAISE CAP_NET_BIND_SERIVCE twice succeeded
prctl07.c:60: PASS: After PR_CAP_AMBIENT_RAISE, CapAmb in /proc/self/status has CAP_NET_BIND_SERVICE
prctl07.c:99: PASS: PR_CAP_AMBIENT_IS_SET CAP_NET_BIND_SERVICE was in AmbientCap
prctl07.c:102: PASS: PR_CAP_AMBIENT_IS_SET CAP_NET_RAW was not in AmbientCap
prctl07.c:114: PASS: PR_CAP_AMBIENT_LOWER CAP_NET_RAW(it wasn't in ambient set) succeeded
prctl07.c:114: PASS: PR_CAP_AMBIENT_LOWER CAP_NET_BIND_SERVICE(it was in ambient set) succeeded
prctl07.c:64: PASS: After PR_CAP_AMBIENT_LORWER, CapAmb in /proc/self/status doesn't have CAP_NET_BIND_SERVICE
prctl07.c:161: INFO: raise cap for clear
prctl07.c:164: PASS: PR_CAP_AMBIENT_CLEAR ALL succeeded
prctl07.c:50: PASS: After PR_CAP_AMBIENT_CLEAN_ALL, /proc/self/status CapAmb has been clear as 0

Summary:
passed 13
failed 1
skipped 0
warnings 0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1
ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Tue Aug 6 07:43:30 2019
SourcePackage: linux-signed-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
tags: added: 4.4 sru-20190722 ubuntu-ltp-syscalls
Changed in ubuntu-kernel-tests:
assignee: nobody → Kai-Heng Feng (kaihengfeng)
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

- The issue doesn't happen under X-4.4.

- After upgrading the toolchain (gcc, binutils, libelf, etc) from Trusty's to Xenial's and rebuild the kernel with the new toolchain, I can still reproduce the issue. I am not sure where to investigate further though...

Changed in ubuntu-kernel-tests:
assignee: Kai-Heng Feng (kaihengfeng) → nobody
Revision history for this message
Sean Feole (sfeole) wrote :

4.15.0-1066.71~14.04.1 linux-azure

10019. 12/14 04:45:23 DEBUG| utils:0153| [stdout] prctl07.c:83: FAIL: PR_CAP_AMBIENT_RAISE succeeded unexpectedly because of NO_RAISE_SECBIT set

Changed in ubuntu-kernel-tests:
status: New → Triaged
tags: added: sru-20191202
Po-Hsu Lin (cypressyew)
tags: added: sru-20200316
Po-Hsu Lin (cypressyew)
tags: added: sru-20200720
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

still visible on 4.4.0-1082.86 aws

tags: added: sru-20201109
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

Found with trusty/linux-azure 4.15.0-1114.127~14.04.1.

tags: added: 4.15 azure sru-20210412
Revision history for this message
Guilherme G. Piccoli (gpiccoli) wrote :

Observed in T-4.15/Azure, cycle sru-20210531 .

tags: added: sru-20210531
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Found on T-azure 4.15.0-1124.137~14.04.1

tags: added: sru-20210906
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.