kernel-packages team mailing list archive

[Colin Ian King <1526811@xxxxxxxxxxxxxxxxxx>]

Fix will land in Linux 4.4 Ubuntu Xenial automatically, commit
c6ff5268293ef98e48a99597e765ffc417e39fa5

Wily SRU submitted to kernel team mailing list,
https://lists.ubuntu.com/archives/kernel-team/2015-December/067287.html

** Description changed:

  [SRU Justification][Wily]  + [Xenial]
  
  While stress testing with the stress-ng procfs stressor I hit a walker
  list bug.  This has been recently fixed by Herbert Xu in commit:
  
  The commit ba7c95ea3870fe7b847466d39a049ab6f156aa2c ("rhashtable: Fix
  sleeping inside RCU critical section in walk_stop") introduced a new
  spinlock for the walker list.  However, it did not convert all existing
  users of the list over to the new spin lock.  Some continued to use the
  old mutex for this purpose.  This obviously led to corruption of the
  list.
  
  [Fix]
- See: http://marc.info/?l=linux-netdev&m=145027458131396&w=2
- Probably will wait until this officially lands in 4.4 or 4.5.
+ Clean upstream cherry pick, commit c6ff5268293ef98e48a99597e765ffc417e39fa5
+ Will land in Xenial automatically (4.4)
+ 
  
  [Testcase]
  Run multiple instances of the attached code on a multicore system.  Alternatively, run stress-ng --procfs 0 on a multi-core system
  
  Fix will stop the above code corrupting the list and crashing.

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

Title:
  SRU: walker list corruption while being intensively stressed

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [SRU Justification][Wily]  + [Xenial]

  While stress testing with the stress-ng procfs stressor I hit a walker
  list bug.  This has been recently fixed by Herbert Xu in commit:

  The commit ba7c95ea3870fe7b847466d39a049ab6f156aa2c ("rhashtable: Fix
  sleeping inside RCU critical section in walk_stop") introduced a new
  spinlock for the walker list.  However, it did not convert all
  existing users of the list over to the new spin lock.  Some continued
  to use the old mutex for this purpose.  This obviously led to
  corruption of the list.

  [Fix]
  Clean upstream cherry pick, commit c6ff5268293ef98e48a99597e765ffc417e39fa5
  Will land in Xenial automatically (4.4)

  
  [Testcase]
  Run multiple instances of the attached code on a multicore system.  Alternatively, run stress-ng --procfs 0 on a multi-core system

  Fix will stop the above code corrupting the list and crashing.

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