Uploaded image for project: 'RHEL Testing'
  1. RHEL Testing
  2. RHELTEST-2417

[ltp - cifs] : io_pgetevents01 and io_pgetevents02 fail over cifs

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • rhel-se-kernel

      This happened on 9.2 :

      https://beaker.engineering.redhat.com/recipes/20235808#task208394322

      tag=io_pgetevents01 stime=1765791080
      cmdline="io_pgetevents01"
      contacts=""
      analysis=exit
      <<<test_output>>>
      tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
      io_pgetevents01.c:28: TINFO: Testing variant: syscall with old kernel spec
      io_pgetevents01.c:64: TFAIL: io_pgetevents() failed: SUCCESS (0)
      tag=io_pgetevents02 stime=1765791080
      cmdline="io_pgetevents02"
      contacts=""
      analysis=exit
      <<<test_output>>>
      tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
      io_pgetevents02.c:57: TINFO: Testing variant: syscall with old kernel spec
      io_pgetevents02.c:114: TPASS: invalid ctx: io_pgetevents() failed as expected: EINVAL (22)
      io_pgetevents02.c:114: TPASS: invalid min_nr: io_pgetevents() failed as expected: EINVAL (22)
      io_pgetevents02.c:114: TPASS: invalid max_nr: io_pgetevents() failed as expected: EINVAL (22)
      io_pgetevents02.c:109: TFAIL: invalid events: io_pgetevents() should fail with EFAULT: SUCCESS (0)
      io_pgetevents02.c:114: TPASS: invalid timeout: io_pgetevents() failed as expected: EFAULT (14)
      io_pgetevents02.c:114: TPASS: invalid sigmask: io_pgetevents() failed as expected: EFAULT (14) 

      AIO events seem to have troble with CIFS, this is likely a filesystem limitation, not something related to the code being tested.

              rhn-support-rbergant Roberto Bergantinos Corpas
              rhn-support-rbergant Roberto Bergantinos Corpas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: