linux-kernel - why does index in truncate_inode_pages

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-next>] [day] [month] [year] [list]

Message-ID: <529217CD.1000204@gmx.de>
Date:	Sun, 24 Nov 2013 16:14:21 +0100
From:	Toralf Förster <toralf.foerster@....de>
To:	UML devel <user-mode-linux-devel@...ts.sourceforge.net>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: why does index in truncate_inode_pages_range() grows so much ?

At a 32 bit guest UML with current kernel git tree I putted a printk
into that function :

void truncate_inode_pages_range(struct address_space *mapping,
                                loff_t lstart, loff_t lend)
{
...


                cond_resched();
                index++;
		printk ("            <------------




and got (while fuzzying the UML guest with trinity) this output in the
UML guest:


Nov 24 12:06:53 trinity kernel: index:42 end:4294967295
Nov 24 12:06:53 trinity kernel: index:43 end:4294967295
Nov 24 12:06:53 trinity kernel: index:5 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1035468800 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:16 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:4 end:4294967295
Nov 24 12:06:53 trinity kernel: index:2 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:4184867847 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295
Nov 24 12:06:53 trinity kernel: index:3 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1727 end:4294967295
Nov 24 12:06:53 trinity kernel: index:1 end:4294967295


I'm wondering if index is expected to become sometimes so big.

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/