Re: [uml-devel] why does index in truncate_inode_pages_range() grows so much ?

2013-12-13 Thread Jan Kara
On Fri 13-12-13 14:01:34, Toralf Förster wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12/13/2013 11:51 AM, Richard Weinberger wrote: > > On Fri, Dec 13, 2013 at 10:52 AM, Toralf Förster > > wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA256 > >> > >> On 12/11/2

Re: [uml-devel] why does index in truncate_inode_pages_range() grows so much ?

2013-12-13 Thread Toralf Förster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/13/2013 11:51 AM, Richard Weinberger wrote: > On Fri, Dec 13, 2013 at 10:52 AM, Toralf Förster > wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 12/11/2013 09:26 PM, Jan Kara wrote: >>> Thanks! So this works more or less

Re: [uml-devel] why does index in truncate_inode_pages_range() grows so much ?

2013-12-13 Thread Richard Weinberger
On Fri, Dec 13, 2013 at 10:52 AM, Toralf Förster wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12/11/2013 09:26 PM, Jan Kara wrote: >> Thanks! So this works more or less as expected - trinity issued a >> read at absurdly high offset so we created pagecache page a that >> offset

Re: why does index in truncate_inode_pages_range() grows so much ?

2013-12-13 Thread Toralf Förster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/11/2013 09:26 PM, Jan Kara wrote: > Thanks! So this works more or less as expected - trinity issued a > read at absurdly high offset so we created pagecache page a that > offset and tried to read data into it. That failed. We left the > page in

Re: why does index in truncate_inode_pages_range() grows so much ?

2013-12-11 Thread Jan Kara
On Sat 07-12-13 19:06:01, Toralf Förster wrote: > On 12/04/2013 02:06 PM, Jan Kara wrote: > > One idea: Can you add > > WARN_ON(offset > 1000); > > into mm/filemap.c:add_to_page_cache_locked() ? That should tell us > > whether someone is indeed inserting pages with strange indices into page

Re: why does index in truncate_inode_pages_range() grows so much ?

2013-12-07 Thread Toralf Förster
On 12/04/2013 02:06 PM, Jan Kara wrote: > One idea: Can you add > WARN_ON(offset > 1000); > into mm/filemap.c:add_to_page_cache_locked() ? That should tell us > whether someone is indeed inserting pages with strange indices into page > cache or if page->index got somehow corrupted. > >

Re: why does index in truncate_inode_pages_range() grows so much ?

2013-12-03 Thread Jan Kara
On Sun 24-11-13 16:14:21, Toralf Förster wrote: > 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) > { > ... > > >

why does index in truncate_inode_pages_range() grows so much ?

2013-11-24 Thread Toralf Förster
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++; prin