[lkml]   [2009]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic
    KAMEZAWA Hiroyuki wrote:
    > KAMEZAWA Hiroyuki wrote:
    > Then, here is a much easier fix. for trusting cpuset more.
    just a memo about memory hotplug

    _Direct_ use of task->mems_allowed is only in cpuset and mempolicy.
    If no policy is used, it's not checked.
    (See alloc_pages_current())

    memory hotplug's notifier just updates top_cpuset's mems_allowed.
    But it doesn't update each task's ones.
    Then, task's bahavior is

    - tasks which don't use mempolicy will use all nodes, N_HIGH_MEMORY.
    - tasks under cpuset will be controlled under their own cpuset.
    - tasks under mempolicy will use their own policy.
    but no new policy is re-calculated and, then, no new mask.

    Now, even if all memory on nodes a removed, pgdat just remains.
    Then, cpuset/mempolicy will never access NODE_DATA(nid) which is NULL.


     \ /
      Last update: 2009-07-25 05:17    [W:0.044 / U:3.316 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site