From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: vfs whitebox test Date: 24 Nov 2003 16:29:22 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1069716562.4649.14.camel@patrh9> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:10219 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S261660AbTKXX3y (ORCPT ); Mon, 24 Nov 2003 18:29:54 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 2854922AB for ; Mon, 24 Nov 2003 16:29:54 -0700 (MST) To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Anybody already pull together some more closely interactive way of trying creative patterns of calls thru the vfs layer? I ask because I'm still hung up on my demo that udf.ko can't reliably write more than one file at a time: http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106676214111422 List: linux-fsdevel Subject: Re: zeroes read back more often than appended Date: 2003-10-21 18:44:54 I'm guessing what makes that demo tough to analyse is that I wrote it up at the high level of fopen/ fwrite/ fclose/ hexdump. I'm guessing translating that demo down to the more verbose level of open/ write/ read/ close actually won't make the demo significantly easier to analyse. I'm thinking I have to drop down to the vfs level. Can I somehow drop down to the vfs level? Maybe I could run the fs as a .so? Can I help in any way quicker than deciphering the source of udf.ko? Pat LaVarre