stress-inode-flags reports errno 13 but does not report a failure in termination

Bug #1841900 reported by Colin Ian King
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stress-ng (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

stress-ng-inode-flags reports, variously, the following errors:

stress-ng: 12:27:12.67 error: [32322] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-32322-3/stress-ng-inode-flags-32322-3-2060495061: errno=13 (Permission denied)

stress-ng: 16:38:13.65 error: [9810] stress-ng-inode-flags: cannot open ./tmp-stress-ng
-inode-flags-9810-0/stress-ng-inode-flags-9810-0-3340326306: errno=13 (Permission denied)
stress-ng: 16:38:13.65 error: [9810] stress-ng-inode-flags: cannot open ./tmp-stress-ng
-inode-flags-9810-0/stress-ng-inode-flags-9810-0-3340326306: errno=13 (Permission denied)
stress-ng: 16:38:13.65 error: [9810] stress-ng-inode-flags: cannot open ./tmp-stress-ng
-inode-flags-9810-0/stress-ng-inode-flags-9810-0-3340326306: errno=13 (Permission denied)
stress-ng: 16:38:13.65 error: [9810] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-9810-0/stress-ng-inode-flags-9810-0-3340326306: errno=13 (Permission denied)

stress-ng: 16:39:29.62 error: [31148] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-31148-0/stress-ng-inode-flags-31148-0-1846194840: errno=1 (Operation not permitted)
stress-ng: 16:39:29.62 error: [31148] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-31148-0/stress-ng-inode-flags-31148-0-1846194840: errno=1 (Operation not permitted)
stress-ng: 16:39:29.62 error: [31148] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-31148-0/stress-ng-inode-flags-31148-0-1846194840: errno=1 (Operation not permitted)
stress-ng: 16:39:29.62 error: [31148] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-31148-0/stress-ng-inode-flags-31148-0-1846194840: errno=1 (Operation not permitted)
stress-ng: 16:39:29.62 error: [31148] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-31148-0/stress-ng-inode-flags-31148-0-1846194840: errno=1 (Operation not permitted)

stress-ng: 18:16:19.73 error: [30507] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-30507-1/stress-ng-inode-flags-30507-1-1821874951: errno=1 (Operation not permitted)

stress-ng: 18:28:15.68 error: [32528] stress-ng-inode-flags: cannot open ./tmp-stress-ng-inode-flags-32528-1/stress-ng-inode-flags-32528-1-1344360964: errno=1 (Operation not permitted)

(Having separated by spaces the messages from different runs.)

If I understand correctly, in stress-ng's terminology, "error:" means something more like a bug in stress-ng itself, rather than a problem it found with the system?

Using stress-ng-0.10

Changed in stress-ng (Ubuntu):
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in stress-ng (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package stress-ng - 0.10.04-1

---------------
stress-ng (0.10.04-1) unstable; urgency=medium

  * Makefile: bump version
  * Remove execute bit on bash completion script
  * debian: rules: workaround dwz failures on arm64

 -- Colin King <email address hidden> Mon, 2 Sep 2019 18:43:41 +0100

Changed in stress-ng (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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