[lkml]   [2009]   [Aug]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()
    On Tue, 2009-08-11 at 09:32 +0200, Ingo Molnar wrote:
    > * Catalin Marinas <> wrote:
    > > I tried similar config and with the mainline kernel I get some
    > > lockups (several seconds) with CONFIG_PREEMPT disabled on ARM
    > > machines or x86 during a scanning episode but it eventually
    > > completes the scanning. With the kmemleak patches for the next
    > > merging window, I don't get any lockups as it has more
    > > cond_resched() calls.
    > How big are those patches? Kmemleak is new in .31 so if it fixes a
    > real problem it might still be acceptable.

    My patches for -next were posted here - - but the relevant ones are pretty
    small (review/ack is welcomed): - allow rescheduling during object
    scanning - inform kmemleak about kernel stack
    allocation (needs ack by the x86 people) - always scan the task stacks


     \ /
      Last update: 2009-08-11 13:59    [W:0.037 / U:111.600 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site