Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262186AbTKUGSK (ORCPT ); Fri, 21 Nov 2003 01:18:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262319AbTKUGSK (ORCPT ); Fri, 21 Nov 2003 01:18:10 -0500 Received: from sv1.valinux.co.jp ([210.128.90.2]:11498 "EHLO sv1.valinux.co.jp") by vger.kernel.org with ESMTP id S262186AbTKUGSI (ORCPT ); Fri, 21 Nov 2003 01:18:08 -0500 Date: Fri, 21 Nov 2003 15:18:06 +0900 From: IWAMOTO Toshihiro To: linux-kernel@vger.kernel.org Subject: O_DIRECT leaks memory on linux-2.6.0-test9 User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Message-Id: <20031121061806.6A65F7007C@sv1.valinux.co.jp> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1378 Lines: 38 Hi, recently I noticed that direct IO causes memory leaks with linux-2.6.0-test9. The program that causes memory leaks is "fsstress", which is testcases/kernel/fs/fsstress in ltp-full-20031106.tgz (ftp from http://sourceforge.net/projects/ltp/). fsstress does various file operations, and I found that the problem is with the combination of write and dread (O_DIRECT read). You should be able to reproduce the bug with the following command line. $ while true; do ./fsstress -c -d /usr/src/test -z -f write=1 \ -f dread=1 -f creat=1 -S -n 1000 -p 32; done The test machine is a quad P3 machine with the following file systems. /usr/src is an ext3 file system but mounted as an ext2 using mount -t ext2. $ mount -v /dev/rd/c0d0p2 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/rd/c0d0p5 on /usr/src type ext2 (rw) I didn't see memory leaks with the other three combinations of read+write (dread+dwrite, read+dwrite, and read+write). Any ideas? I'll try to debug this next week, but rather like to see the fix in the meanwhile. :) -- IWAMOTO Toshihiro - 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/