kernel-packages team mailing list archive

[Philipp Hahn <hahn@xxxxxxxxxxxxx>]

Reverting the patch "unix: avoid use-after-free in ep_remove_wait_queue"
in 4.1 fixes my problem (for now). The original patch went into 4.4, but
was back-ported to several stable trees:

v3.2: a3b0f6e8a21ef02f69a15abac440572d8cde8c2a
v3.18: 72032798034d921ed565e3bf8dfdc3098f6473e2
v4.1: 5c77e26862ce604edea05b3442ed765e9756fe0f
v4.2: bad967fdd8ecbdd171f5f243657be033d2d081a7
v4.3: 58a6a46a036ce81a2a8ecaa6fc1537c894349e3f
v4.4: 7d267278a9ece963d77eefec61630223fce08c6c

See <https://lkml.org/lkml/2016/2/2/474>

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

Title:
  Kernel 3.13.0-77 crashes (can be triggered by Samba)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Ubuntu 14.04.3 LTS

  After updating to kernel 3.13.0-77 system crashes.
  First, network dies, then the whole system.
  There are several kernel crashes in the logs.

  --- snip ---
  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be restarted.
  Date: Wed Feb 10 09:20:35 2016
  Failure: oops
  OopsText:
   BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908]
  --- snap ---

  Followed by kernel stack traces.

  After some investigation, it turned out that the crash can be triggered by Samba.
  It's easily reproducible by running the following commands in the Samba master branch:
  ./configure.developer
  TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 TESTS="samba3.raw.composite"

  Downgrading to kernel 3.13.0-76 solves this problem.

  Please let me know if we can provide more information or help testing.

  Thanks!

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