Public bug reported:

SRU Justification:

[Impact]

* bpf selftest do not compile. See the error below.
Commit "bpf: Allow reads from uninit stack" introduced the usage of '__failure',
without bringing the commit where this is defined.
This prevents us from running other tests and it also affects the netselfts 
because they are dependant on it.

Logs:

17242             progs/test_global_func10.c:24:17: error: expected parameter 
declarator
17243             __failure __msg("invalid indirect access to stack")
17244                             ^
17245             progs/test_global_func10.c:24:17: error: expected ')'
17246             progs/test_global_func10.c:24:16: note: to match this '('
17247             __failure __msg("invalid indirect access to stack")
17248                            ^
17249             progs/test_global_func10.c:24:52: error: expected ';' after 
top level declarator
17250             __failure __msg("invalid indirect access to stack")
17251                                                                ^

[Fix]

* While discussing with upstream a revert of this commit will be the fix
for now.

[Test Plan]

* Revert, build the kernel, run the ubuntu_bpf_selftests and see it they
build.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux (Ubuntu Jammy)
     Importance: High
     Assignee: Roxana Nicolescu (roxanan)
         Status: In Progress

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
       Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
     Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu)
       Status: New => Invalid

** Description changed:

- RU Justification:
+ SRU Justification:
  
  [Impact]
  
  * bpf selftest do not compile. See the error below.
  Commit "bpf: Allow reads from uninit stack" introduced the usage of 
'__failure',
  without bringing the commit where this is defined.
- This prevents us from running other tests and it also affects the netselfts 
because they are dependant on it. 
+ This prevents us from running other tests and it also affects the netselfts 
because they are dependant on it.
  
  Logs:
-    
+ 
  17242                   progs/test_global_func10.c:24:17: error: expected 
parameter declarator
  17243                   __failure __msg("invalid indirect access to stack")
  17244                                   ^
  17245                   progs/test_global_func10.c:24:17: error: expected ')'
  17246                   progs/test_global_func10.c:24:16: note: to match this 
'('
  17247                   __failure __msg("invalid indirect access to stack")
  17248                                  ^
  17249                   progs/test_global_func10.c:24:52: error: expected ';' 
after top level declarator
  17250                   __failure __msg("invalid indirect access to stack")
  17251                                                                      ^
  
  [Fix]
  
  * While discussing with upstream a revert of this commit will be the fix
  for now.
  
  [Test Plan]
  
  * Revert, build the kernel, run the ubuntu_bpf_selftests and see it they
  build.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076334

Title:
  jammy:linux bpfk selftest do not build

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  * bpf selftest do not compile. See the error below.
  Commit "bpf: Allow reads from uninit stack" introduced the usage of 
'__failure',
  without bringing the commit where this is defined.
  This prevents us from running other tests and it also affects the netselfts 
because they are dependant on it.

  Logs:

  17242                   progs/test_global_func10.c:24:17: error: expected 
parameter declarator
  17243                   __failure __msg("invalid indirect access to stack")
  17244                                   ^
  17245                   progs/test_global_func10.c:24:17: error: expected ')'
  17246                   progs/test_global_func10.c:24:16: note: to match this 
'('
  17247                   __failure __msg("invalid indirect access to stack")
  17248                                  ^
  17249                   progs/test_global_func10.c:24:52: error: expected ';' 
after top level declarator
  17250                   __failure __msg("invalid indirect access to stack")
  17251                                                                      ^

  [Fix]

  * While discussing with upstream a revert of this commit will be the
  fix for now.

  [Test Plan]

  * Revert, build the kernel, run the ubuntu_bpf_selftests and see it
  they build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076334/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to