1. 28 Oct, 2015 2 commits
  2. 16 Oct, 2015 1 commit
  3. 14 Oct, 2015 2 commits
    • Ulf Hansson's avatar
      PM / Domains: Fix validation of latency constraints in genpd governor · a98f1b78
      Ulf Hansson authored
      Commit ba2bbfbf (PM / Domains: Remove intermediate states from the
      power off sequence) changed the power off sequence in genpd. That also
      required some updates regarding the validation of latency constraints in
      the genpd governor. Unfortunate that wasn't covered, so let's fix this.
      
      From a runtime PM and latency point of view, we need to consider the worst
      case scenario while validating latency constraints. That's typically when
      a call to pm_runtime_get_sync() needs to wait for a ongoing runtime
      suspend operation to be carried out, as it then also needs to wait for the
      device to be runtime resumed again.
      
      The above mentioned commit made the genpd governor's ->stop_ok() callback
      responsible of validating genpd's device's runtime suspend/resume latency.
      In other words, the constraint needs to be validated towards the relevant
      latencies present in genpd's ->runtime_suspend|resume() callbacks.
      
      Earlier, that included latencies from the ->stop|start() callbacks, but as
      ->save|restore_state() are now also being invoked from genpd's
      ->runtime_suspend|resume() and to comply with the worst case scenario,
      let's take also those latencies into account.
      
      Fixes: ba2bbfbf (PM / Domains: Remove intermediate states from the power off sequence)
      Signed-off-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      a98f1b78
    • Ulf Hansson's avatar
      PM / Domains: Rename *pm_genpd_poweron|poweroff() · 7420aa4f
      Ulf Hansson authored
      This is another step to get consistent names of functions in genpd. Let's
      rename the internal *pm_genpd_poweron|poweroff() into
      *genpd_poweron|poweroff().
      Signed-off-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      7420aa4f
  4. 12 Oct, 2015 4 commits
  5. 11 Oct, 2015 8 commits
  6. 10 Oct, 2015 12 commits
  7. 09 Oct, 2015 10 commits
  8. 08 Oct, 2015 1 commit
    • Mikulas Patocka's avatar
      crash in md-raid1 and md-raid10 due to incorrect list manipulation · a452744b
      Mikulas Patocka authored
      The commit 55ce74d4 (md/raid1: ensure
      device failure recorded before write request returns) is causing crash in
      the LVM2 testsuite test shell/lvchange-raid.sh. For me the crash is 100%
      reproducible.
      
      The reason for the crash is that the newly added code in raid1d moves the
      list from conf->bio_end_io_list to tmp, then tests if tmp is non-empty and
      then incorrectly pops the bio from conf->bio_end_io_list (which is empty
      because the list was alrady moved).
      
      Raid-10 has a similar bug.
      
      Kernel Fault: Code=15 regs=000000006ccb8640 (Addr=0000000100000000)
      CPU: 3 PID: 1930 Comm: mdX_raid1 Not tainted 4.2.0-rc5-bisect+ #35
      task: 000000006cc1f258 ti: 000000006ccb8000 task.ti: 000000006ccb8000
      
           YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
      PSW: 00001000000001001111111000001111 Not tainted
      r00-03  000000ff0804fe0f 000000001059d000 000000001059f818 000000007f16be38
      r04-07  000000001059d000 000000007f16be08 0000000000200200 0000000000000001
      r08-11  000000006ccb8260 000000007b7934d0 0000000000000001 0000000000000000
      r12-15  000000004056f320 0000000000000000 0000000000013dd0 0000000000000000
      r16-19  00000000f0d00ae0 0000000000000000 0000000000000000 0000000000000001
      r20-23  000000000800000f 0000000042200390 0000000000000000 0000000000000000
      r24-27  0000000000000001 000000000800000f 000000007f16be08 000000001059d000
      r28-31  0000000100000000 000000006ccb8560 000000006ccb8640 0000000000000000
      sr00-03  0000000000249800 0000000000000000 0000000000000000 0000000000249800
      sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
      
      IASQ: 0000000000000000 0000000000000000 IAOQ: 000000001059f61c 000000001059f620
       IIR: 0f8010c6    ISR: 0000000000000000  IOR: 0000000100000000
       CPU:        3   CR30: 000000006ccb8000 CR31: 0000000000000000
       ORIG_R28: 000000001059d000
       IAOQ[0]: call_bio_endio+0x34/0x1a8 [raid1]
       IAOQ[1]: call_bio_endio+0x38/0x1a8 [raid1]
       RP(r2): raid_end_bio_io+0x88/0x168 [raid1]
      Backtrace:
       [<000000001059f818>] raid_end_bio_io+0x88/0x168 [raid1]
       [<00000000105a4f64>] raid1d+0x144/0x1640 [raid1]
       [<000000004017fd5c>] kthread+0x144/0x160
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Fixes: 55ce74d4 ("md/raid1: ensure device failure recorded before write request returns.")
      Fixes: 95af587e ("md/raid10: ensure device failure recorded before write request returns.")
      Signed-off-by: default avatarNeilBrown <neilb@suse.com>
      a452744b