linux-ext4 - Re: i_size error with the latest patchqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 31 Jul 2008 11:41:39 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
CC:	Theodore Tso <tytso@....edu>, ext4 <linux-ext4@...r.kernel.org>
Subject: Re: i_size error with the latest patchqueue

Aneesh Kumar K.V wrote:
> Hi Ted,
> 
> I haven't yet looked at whether it is kernel or e2fsck bug.
> But I am having this with the latest patch queue when running
> fsstress. The fsstress have falloc added as a supported operation.
> So it is mostly to do with fallocate. Architecture is x86.
> 
> The tests performed are
> 
>                chown 3/39 write op
>                creat 4/39 write op
>                dread 4/39  
>            fdatasync 1/39 write op
>                fsync 1/39 write op
>             getdents 1/39  
>                 link 1/39 write op
>                mkdir 2/39 write op
>                mknod 2/39 write op
>                 read 1/39  
>             readlink 1/39  
>               rename 2/39 write op
>                rmdir 1/39 write op
>                 stat 1/39  
>              symlink 2/39 write op
>                 sync 1/39  
>             truncate 2/39 write op
>               unlink 1/39 write op
>                write 4/39 write op
>            fallocate 4/39 write op
> 
> seed = 1218256896
> 
> 
> /usr/local/e2fsprogs/sbin/e2fsck -fnv /dev/sdb1
> e2fsck 1.41.0 (10-Jul-2008)
> Pass 1: Checking inodes, blocks, and sizes
> Inode 10093, i_size is 974599, should be 999424.  Fix? no

are those due to blocks beyond EOF, I assume?  How is fallocate being
called in fsstress?

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html