[Bug 36944] software_resume()->read_suspend_image() can fail at get_zeroed_page()

[Paul Sladen]

Hi Pavel,

I have the following backtrace recorded in an Ubuntu bug-report:

  https://launchpad.net/bugs/36944

  swsusp: Reading pagedir (125 pages)
  busybox: page allocation failure. order:0, mode:0x8020
   [__alloc_pages+494/736] __alloc_pages+0x1ee/0x2e0
   [get_zeroed_page+34/80] get_zeroed_page+0x22/0x50
   [alloc_data_pages+55/208] alloc_data_pages+0x37/0xd0
   [read_suspend_image+155/192] read_suspend_image+0x9b/0xc0
   [swsusp_read+21/64] swsusp_read+0x15/0x40
   [software_resume+119/224] software_resume+0x77/0xe0
   [resume_store+161/164] resume_store+0xa1/0xa4
   [flush_write_buffer+39/48] flush_write_buffer+0x27/0x30
   [sysfs_write_file+63/96] sysfs_write_file+0x3f/0x60
   [vfs_write+150/336] vfs_write+0x96/0x150
   [sys_write+56/128] sys_write+0x38/0x80
   [syscall_call+7/11] syscall_call+0x7/0xb

This is using a initiated from an initramfs (that's what the busybox process
is) with:

  if [ -e /sys/power/resume ]; then
      major=$((0x$(stat -c%t ${resume})))
      minor=$((0x$(stat -c%T ${resume})))
      echo ${major}:${minor} >/sys/power/resume
  fi

Any idea how swsusp can end up in this state?  The affect of this is that
the syscall fails and bootup proceeds normally.

Many Thanks,

	-Paul
-- 
Britain is just cold, in a pesky way.  Southampton, GB


-- 
software_resume()->read_suspend_image() can fail at get_zeroed_page()
https://launchpad.net/malone/bugs/36944