On Mon, Jan 24 2005, Andrew Morton wrote: > Jens Axboe <[EMAIL PROTECTED]> wrote: > > > > Here is the output of your program (somewhat modified, I cut the runtime > > by 19/20 killing the 1-byte reads :-) after 10 hours of use with > > bk-current as of this morning. > > hmm.. > > 62130 times: Page allocated via order 0 > [0xffffffff80173d6e] pipe_writev+574 > [0xffffffff8017402a] pipe_write+26 > [0xffffffff80168b47] vfs_write+199 > [0xffffffff80168cb3] sys_write+83 > [0xffffffff8011e4f3] cstar_do_call+27 > > 55552 times: Page allocated via order 0 > [0xffffffff80173d6e] pipe_writev+574 > [0xffffffff8017402a] pipe_write+26 > [0xffffffff8038b88d] thread_return+41 > [0xffffffff80168b47] vfs_write+199 > [0xffffffff80168cb3] sys_write+83 > [0xffffffff8011e4f3] cstar_do_call+27 > > Would indicate that the new pipe code is leaking.
I suspected that, I even tried backing out the new pipe patches but it still seemed to leak. And the test cases I tried to come up with could not provoke a pipe leak. But yeah, it certainly is the most likely culprit and the leak did start in the period when it was introduced. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
