Ubuntu Raring Kernel - pull patch block/partitions: optimize memory allocation in check_partition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Tim Gardner | ||
Saucy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We have a Ubuntu Raring server running kernel 3.8.13-
We use iscsi to consume LUNs out of a storage array in the backend. When the server is loaded we run into the issue of iSCSI device discovery failing to scan partitions on LUNs with
Jul 30 12:12:01 srv1 kernel: [101661.119322] kworker/u:20: page allocation failure: order:4, mode:0x10c0d0
Jul 30 12:12:01 srv1 kernel: [101661.119327] Pid: 32539, comm: kworker/u:20 Tainted: GF W O 3.8.13-
Jul 30 12:12:01 srv1 kernel: [101661.119329] Call Trace:
Jul 30 12:12:01 srv1 kernel: [101661.119340] [<ffffffff8113a
Jul 30 12:12:01 srv1 kernel: [101661.119345] [<ffffffff8113e
Jul 30 12:12:01 srv1 kernel: [101661.119350] [<ffffffff810bc
Jul 30 12:12:01 srv1 kernel: [101661.119354] [<ffffffff8113e
Jul 30 12:12:01 srv1 kernel: [101661.119359] [<ffffffff8117a
Jul 30 12:12:01 srv1 kernel: [101661.119363] [<ffffffff81139
Jul 30 12:12:01 srv1 kernel: [101661.119367] [<ffffffff81184
Jul 30 12:12:01 srv1 kernel: [101661.119373] [<ffffffff8133a
Jul 30 12:12:01 srv1 kernel: [101661.119376] [<ffffffff8133a
Jul 30 12:12:01 srv1 kernel: [101661.119381] [<ffffffff811d5
Jul 30 12:12:01 srv1 kernel: [101661.119386] [<ffffffff8107f
Jul 30 12:12:01 srv1 kernel: [101661.119389] [<ffffffff811d5
Jul 30 12:12:01 srv1 kernel: [101661.119393] [<ffffffff81337
Jul 30 12:12:01 srv1 kernel: [101661.119396] [<ffffffff81338
Jul 30 12:12:01 srv1 kernel: [101661.119403] [<ffffffff814bb
Jul 30 12:12:01 srv1 kernel: [101661.119407] [<ffffffff81087
Jul 30 12:12:01 srv1 kernel: [101661.119410] [<ffffffff81078
Jul 30 12:12:01 srv1 kernel: [101661.119413] [<ffffffff81079
Jul 30 12:12:01 srv1 kernel: [101661.119416] [<ffffffff81079
Jul 30 12:12:01 srv1 kernel: [101661.119419] [<ffffffff8107f
Jul 30 12:12:01 srv1 kernel: [101661.119423] [<ffffffff8107e
Jul 30 12:12:01 srv1 kernel: [101661.119429] [<ffffffff816f6
Jul 30 12:12:01 srv1 kernel: [101661.119432] [<ffffffff8107e
We see this issue is fixed in 3.9 kernels with the following commit
https:/
Kindly request you to pull this patch into Ubuntu raring stable 3.8 kernel version as detailed in
http://
Thank You
CVE References
tags: | added: cherry-pick |
tags: | added: bot-stop-nagging |
Changed in linux (Ubuntu Saucy): | |
status: | Confirmed → Fix Released |
Changed in linux (Ubuntu Raring): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → Fix Committed |
Changed in linux (Ubuntu Raring): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Saucy): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed-raring |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1206837
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.