[lkml]   [2011]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: list corruption in the last few days. (block ? crypto ?)
    On Fri, 5 Aug 2011, Dave Jones wrote:
    >>  > Argh another debugging code issue. Anyone who sees this please verify that
    >>  > it also occurs with debugging off. I ran this code for 9 months in
    >>  > various configs but only sporadically with debugging support since that
    >>  > switches the lockless stuff.
    >> This started turning up immediately as soon as it got merged to mainline.
    >> Which leads me to believe no-one is running -next with debugging on either.
    >> Perhaps we should force debugging on for a week once per release cycle.

    On Fri, Aug 5, 2011 at 9:14 PM, Christoph Lameter <> wrote:
    > I have run some tests over the last hours with kvm and
    > CONFIG_SLUB_DEBUG_ON as well as CONFIG_DEBUG_LIST set but (aside from
    > other unrelated backtraces in other subsystems) did not see this issue.
    > Can I get a .config? Maybe that will help.

    I haven't been able to reproduce the problem on hardware either.
    However, I don't have CONFIG_PREEMPT enabled like Dave and our RCU
    options seem to be different:

    $ diff -u adamo.config ../linux/.config | grep RCU
    # RCU Subsystem
    +# CONFIG_PREEMPT_RCU is not set
    # CONFIG_RCU_TRACE is not set
    # CONFIG_RCU_FANOUT_EXACT is not set
    +# CONFIG_RCU_FAST_NO_HZ is not set
    # CONFIG_TREE_RCU_TRACE is not set
    # CONFIG_RCU_TORTURE_TEST is not set

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-08-07 22:39    [W:0.063 / U:11.996 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site