Bug 103365 - [GLK] gem_fd_exhaustion produces file-max limit 377904 reached
Summary: [GLK] gem_fd_exhaustion produces file-max limit 377904 reached
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-19 20:58 UTC by Luis Botello
Modified: 2018-10-11 19:42 UTC (History)
1 user (show)

See Also:
i915 platform: GLK
i915 features: GEM/Other


Attachments

Description Luis Botello 2017-10-19 20:58:45 UTC
Steps:
======================================
1. Execute commands:
# ./gem_fd_exhaustion 

Actual result:
======================================
Test is failing

Expected result:
======================================
Test is Pass

             Software
======================================
kernel version              : 4.14.0-rc5-drm-intel-qa-ww42-commit-3f1f8a0+
architecture                : x86_64
os version                  : Ubuntu 16.10
kernel driver               : i915
bios revision               : 62.30
ksc                         : 1.41

        Graphic drivers
======================================
libdrm                      : 2.4.84
cairo                       : 1.15.9
intel-gpu-tools (tag)       : intel-gpu-tools-1.19-430-gabc08cb
intel-gpu-tools (commit)    : abc08cb

             Hardware
======================================
platform                   : Geminilake
motherboard id             : GLKRVP1DDR4(05)
cpu information            : Genuine Intel(R) CPU @ 1.10GHz
gpu card                   : Intel Corporation Device 3185 (rev 03) (prog-if 00 [VGA controller])
memory ram                 : 3.7 GB
max memory ram             : 16 GB

             Firmware
======================================
dmc fw loaded             : yes
guc version found         : wanted 10.56, found 10.56


dmesg
============================================
[23610.339799] [IGT] gem_fd_exhaustion: executing
[23612.951353] VFS: file-max limit 377904 reached
[23613.177938] [IGT] gem_fd_exhaustion: exiting, ret=99


IGT output
=============================================
./gem_fd_exhaustion
IGT-Version: 1.20-gabc08cb (x86_64) (Linux: 4.14.0-rc5-drm-intel-qa-ww42-commit-3f1f8a0+ x86_64)
System limit for open files is 377904
(gem_fd_exhaustion:6761) CRITICAL: Test assertion failure function __real_main61, file gem_fd_exhaustion.c:87:
(gem_fd_exhaustion:6761) CRITICAL: Failed assertion: handle == 0
Stack trace:
  #0 [<unknown>+0x1a69]
  #1 [<unknown>+0x1a69]
  #2 [<unknown>+0x1a69]
  #3 [<unknown>+0x1a69]
  #4 [<unknown>+0x1a69]
child 0 failed with exit status 99
Test gem_fd_exhaustion failed.
**** DEBUG ****
(gem_fd_exhaustion:6760) igt-core-INFO: IGT-Version: 1.20-gabc08cb (x86_64) (Linux: 4.14.0-rc5-drm-intel-qa-ww42-commit-3f1f8a0+ x86_64)
(gem_fd_exhaustion:6760) INFO: System limit for open files is 377904
(gem_fd_exhaustion:6760) DEBUG: Test requirement passed: allow_unlimited_files()
(gem_fd_exhaustion:6760) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_fd_exhaustion:6760) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
****  END  ****
FAIL (2.828s)
Comment 1 Chris Wilson 2017-10-25 10:51:56 UTC
commit 07f515979e06d4fdc6d09daa19335e91083a96f8 (HEAD, upstream/master)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Oct 20 11:18:01 2017 +0100

    igt/gem_fd_exhaustion: Remove stale assert
    
    __gem_create() doesn't touch the outparam *handle on failure, so we can
    no longer assert that it zero. This is reasonable to remove as it is just
    testing the library itself and not the kernel, so no loss in coverage.
    We already had to remove the false assertion that gem_create() must fail
    following fd exhaustion (as we can not prevent the kernel from freeing
    VFS fdspace in between calls).
Comment 2 Lakshmi 2018-10-11 19:42:27 UTC
This bug is fixed, closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.