public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: why does index in truncate_inode_pages_range() grows so much ?
Date: Sun, 24 Nov 2013 16:14:21 +0100	[thread overview]
Message-ID: <529217CD.1000204@gmx.de> (raw)

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

             reply	other threads:[~2013-11-24 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 15:14 Toralf Förster [this message]
2013-12-03 14:02 ` why does index in truncate_inode_pages_range() grows so much ? Jan Kara
2013-12-03 19:43   ` Toralf Förster
2013-12-03 23:00     ` Jan Kara
2013-12-04 13:06       ` Jan Kara
2013-12-07 18:06         ` Toralf Förster
2013-12-11 20:26           ` Jan Kara
2013-12-13  9:52             ` Toralf Förster
2013-12-13 10:51               ` [uml-devel] " Richard Weinberger
2013-12-13 13:01                 ` Toralf Förster
2013-12-13 19:10                   ` Jan Kara
2013-12-05 23:23       ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=529217CD.1000204@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox