Based on the last recent conversation (and comment #9) I am closing this ticket
for now as Invalid.
If the upstream work succeeded and BPF got stabilized and tested again and
further issues occur, a new LP bug can be opened any time.
** Changed in: linux (Ubuntu Focal)
Status: In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507
Ti
** Description changed:
- We need to run BPF filters to analyse and monitor network traffic. The
- BPF filters are created by skydive (http://skydive.network). Currently
- skydive fails to install BPF filters on s390x (using Ubuntu 18.04
- currently, soon moving to Ubuntu 20.04).
+ [Impact]
+ Some
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Hi.
So if I understand correctly, this will be 18.04 userspace on top of a
20.04 kernel, that is, 5.4. I noticed 5.4 also lacks probe_read_user. I
will keep working on a backport of this to 5.4 kernel, then. Let me know
if there is anything else missing here.
Thanks.
Cascardo.
--
You received t
Hi.
So, we clarified that some of the problems were not caused by the kernel
at all. The only thing missing is support to probe_read_kernel and
probe_read_user on 4.15 kernels. Is that needed for the offering?
If I didn't get it right, I am sorry. So, in order for us to meet your
expectations, I'
Yep, and the commit that first fixes up these probe_read vs
probe_read_kernel/probe_read_user problems is:
6ae08ae3dea2cfa03dd3665a3c8475c2d429ef47 "bpf: Add probe_read_{user,
kernel} and probe_read_{user, kernel}_str helpers"
So, these helpers are not available until 5.5. We may consider this a
After some investigation, I found out that failures caused by "invalid
relo for insn[4].code 0x85" are due to a small typo in some headers.
That has caused LLVM to emit relocations (thinking those missing macro
calls were external function calls) that are not supported by the
loader. This is all i
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507
Title:
[UBUNTU 18.04] BPF programs fail on Ubuntu s390x
To manage notificatio
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notific
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Assignee:
11 matches
Mail list logo