← Back to team overview

kernel-packages team mailing list archive

[Bug 1567064] [NEW] tipc: missing linearization of sk_buff

 

Public bug reported:

The TIPC binding table sometimes fails to update correctly between nodes
because we don't linearize nonlinear buffers at two places where it is
needed in the code.

In the upstream kernel at kernel.org, the following commit was applied
on Nov 19th 2015:

commit c7cad0d6f70cd4ce8644ffe528a4df1cdc2e77f5   ("tipc: move
linearization of buffers to generic code") that fixes this issue.

This crucial fix made it into kernel 4.5, but unfortunately not into 4.4
that is used in Xenial, and makes TIPC in Xenial almost unusable as it
is now.

Now I am uncertain about how to proceed with this, since I am new with dealing with the Ubuntu kernel. 
-  Do you apply such fixes from kernel.org if I post a new one to kernel.org/stable? (The one referred to above won't apply cleanly to 4.4).  
- Or should I issue a new one directly to Ubuntu's kernel team ? 
- Or do you fix it yourself (it it pretty trivial and safe if you take a look at the original commit I refer to) ?

BR
Jon Maloy
Ericsson Canada Inc

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

-- 
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/1567064

Title:
  tipc: missing linearization of sk_buff

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The TIPC binding table sometimes fails to update correctly between
  nodes because we don't linearize nonlinear buffers at two places where
  it is needed in the code.

  In the upstream kernel at kernel.org, the following commit was applied
  on Nov 19th 2015:

  commit c7cad0d6f70cd4ce8644ffe528a4df1cdc2e77f5   ("tipc: move
  linearization of buffers to generic code") that fixes this issue.

  This crucial fix made it into kernel 4.5, but unfortunately not into
  4.4 that is used in Xenial, and makes TIPC in Xenial almost unusable
  as it is now.

  Now I am uncertain about how to proceed with this, since I am new with dealing with the Ubuntu kernel. 
  -  Do you apply such fixes from kernel.org if I post a new one to kernel.org/stable? (The one referred to above won't apply cleanly to 4.4).  
  - Or should I issue a new one directly to Ubuntu's kernel team ? 
  - Or do you fix it yourself (it it pretty trivial and safe if you take a look at the original commit I refer to) ?

  BR
  Jon Maloy
  Ericsson Canada Inc

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


Follow ups