canonical-ubuntu-qa team mailing list archive

[Manuel Diewald <2072989@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

  === Ftrace unit tests ===
  [1] Kprobe event parser error log check	[FAIL]
  execute: /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc

...

  + tail -n 1 error_log
  + wc -c
  + N=30
  + expr 13 + 17
  + test 30 -eq 30
  + check_error r vfs_read ^$arg*
  + ftrace_errlog_check trace_kprobe r vfs_read ^$arg* kprobe_events
  + printf %s r vfs_read 
  + wc -c
  + pos=11
  + printf %s r vfs_read ^$arg*
  + tr -d ^
  + command=r vfs_read $arg*
  + echo Test command: r vfs_read $arg*
  Test command: r vfs_read $arg*
  + echo
  + grep trace_kprobe: error: -A 3 error_log
  [  337.950203] trace_kprobe: error: $arg* can be used only on function entry
    Command: r vfs_read $arg*
                        ^
  + tail -n 1 error_log
  + wc -c
  + N=24
  + expr 13 + 11
  + test 24 -eq 24
  + check_error p vfs_read+8 ^$arg*
  + ftrace_errlog_check trace_kprobe p vfs_read+8 ^$arg* kprobe_events
  + printf %s p vfs_read+8 
  + wc -c
  + pos=13
  + printf %s p vfs_read+8 ^$arg*
  + tr -d ^
  + command=p vfs_read+8 $arg*
  + echo Test command: p vfs_read+8 $arg*
  Test command: p vfs_read+8 $arg*
  + echo
  
  
  # of passed:  0
  # of failed:  1
  # of unresolved:  0
  # of untested:  0
  # of unsupported:  0
  # of xfailed:  0
  # of undefined(test bug):  0

The test seems to die on this line:

kprobe_syntax_errors.tc:112: check_error 'p vfs_read+8 ^$arg*'   #
NOFENTRY_ARGS

check_error is basically a wrapper around this function:

 # Since probe event command may include backslash, explicitly use printf "%s"    
 # to NOT interpret it.                                                           
 ftrace_errlog_check() { # err-prefix command-with-error-pos-by-^ command-file    
     pos=$(printf "%s" "${2%^*}" | wc -c) # error position                        
     command=$(printf "%s" "$2" | tr -d ^)                                        
     echo "Test command: $command"                                                
     echo > error_log                                                             
     (! printf "%s" "$command" >> "$3" ) 2> /dev/null                             
     grep "$1: error:" -A 3 error_log                                             
     N=$(tail -n 1 error_log | wc -c)                                             
     # "  Command: " and "^\n" => 13                                              
     test $(expr 13 + $pos) -eq $N                                                
 }

The last line executed is:
  echo > error_log

Observed on ppc64el.9/ppc64el.10 metal instances with noble:linux in
s2024.06.10. The issue is present since we started testing noble in SRU
cycle 2024.04.29 at least.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2072989

Title:
  kselftests_ftrace.ftrace:test.d--kprobe--kprobe_syntax_errors.tc fails
  on ppc64el

Status in ubuntu-kernel-tests:
  New

Bug description:
    === Ftrace unit tests ===
    [1] Kprobe event parser error log check	[FAIL]
    execute: /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_syntax_errors.tc

  ...

    + tail -n 1 error_log
    + wc -c
    + N=30
    + expr 13 + 17
    + test 30 -eq 30
    + check_error r vfs_read ^$arg*
    + ftrace_errlog_check trace_kprobe r vfs_read ^$arg* kprobe_events
    + printf %s r vfs_read 
    + wc -c
    + pos=11
    + printf %s r vfs_read ^$arg*
    + tr -d ^
    + command=r vfs_read $arg*
    + echo Test command: r vfs_read $arg*
    Test command: r vfs_read $arg*
    + echo
    + grep trace_kprobe: error: -A 3 error_log
    [  337.950203] trace_kprobe: error: $arg* can be used only on function entry
      Command: r vfs_read $arg*
                          ^
    + tail -n 1 error_log
    + wc -c
    + N=24
    + expr 13 + 11
    + test 24 -eq 24
    + check_error p vfs_read+8 ^$arg*
    + ftrace_errlog_check trace_kprobe p vfs_read+8 ^$arg* kprobe_events
    + printf %s p vfs_read+8 
    + wc -c
    + pos=13
    + printf %s p vfs_read+8 ^$arg*
    + tr -d ^
    + command=p vfs_read+8 $arg*
    + echo Test command: p vfs_read+8 $arg*
    Test command: p vfs_read+8 $arg*
    + echo
    
    
    # of passed:  0
    # of failed:  1
    # of unresolved:  0
    # of untested:  0
    # of unsupported:  0
    # of xfailed:  0
    # of undefined(test bug):  0

  The test seems to die on this line:

  kprobe_syntax_errors.tc:112: check_error 'p vfs_read+8 ^$arg*'   #
  NOFENTRY_ARGS

  check_error is basically a wrapper around this function:

   # Since probe event command may include backslash, explicitly use printf "%s"    
   # to NOT interpret it.                                                           
   ftrace_errlog_check() { # err-prefix command-with-error-pos-by-^ command-file    
       pos=$(printf "%s" "${2%^*}" | wc -c) # error position                        
       command=$(printf "%s" "$2" | tr -d ^)                                        
       echo "Test command: $command"                                                
       echo > error_log                                                             
       (! printf "%s" "$command" >> "$3" ) 2> /dev/null                             
       grep "$1: error:" -A 3 error_log                                             
       N=$(tail -n 1 error_log | wc -c)                                             
       # "  Command: " and "^\n" => 13                                              
       test $(expr 13 + $pos) -eq $N                                                
   }

  The last line executed is:
    echo > error_log

  Observed on ppc64el.9/ppc64el.10 metal instances with noble:linux in
  s2024.06.10. The issue is present since we started testing noble in
  SRU cycle 2024.04.29 at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2072989/+subscriptions