lkml.org 
[lkml]   [2003]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [CHECKER] 12 potential leaks in kernel 2.5.69
    From
    Date
    > >             schedule();
    > > barrier();
    >
    > Iirc, the above will leak 4 bytes (plus overhead) once per kernel
    > boot and controller. This only happens for broken hardware and the
    > alternative is memory corruption, depending on how broken the hardware
    > is. Wontfix.
    >
    > Alan, was that correct?

    It should only leak in the error path case. If the controller didnt reply
    then it still owns that ram and for the sake of a few bytes its better to
    play safe yes

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:35    [W:0.022 / U:29.696 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site