linux-toradex.git/fs/nilfs2/page.c, branch v3.4.2

nilfs2: remove the second argument of k[un]map_atomic()

2012-03-20T13:48:24+00:00

Acked-by: Ryusuke Konishi 
Signed-off-by: Cong Wang

nilfs2: use mark_buffer_dirty to mark btnode or meta data dirty

2011-05-10T13:21:57+00:00

This replaces nilfs_mdt_mark_buffer_dirty and nilfs_btnode_mark_dirty
macros with mark_buffer_dirty and gets rid of nilfs_mark_buffer_dirty,
an own mark buffer dirty function.

Signed-off-by: Ryusuke Konishi

nilfs2: always set back pointer to host inode in mapping->host

2011-05-10T13:21:57+00:00

In the current nilfs, page cache for btree nodes and meta data files
do not set a valid back pointer to the host inode in mapping->host.

This will change it so that every address space in nilfs uses
mapping->host to hold its host inode.

Signed-off-by: Ryusuke Konishi

nilfs2: get rid of private page allocator

2011-05-10T13:21:44+00:00

Previously, nilfs was cloning pages for mmapped region to freeze their
data and ensure consistency of checksum during writeback cycles.  A
private page allocator was used for this page cloning.  But, we no
longer need to do that since clear_page_dirty_for_io function sets up
pte so that vm_ops->page_mkwrite function is called right before the
mmapped pages are modified and nilfs_page_mkwrite function can safely
wait for the pages to be written back to disk.

So, this stops making a copy of mmapped pages during writeback, and
eliminates the private page allocation and deallocation functions from
nilfs.

Signed-off-by: Ryusuke Konishi

fs: export empty_aops

2011-04-05T21:51:48+00:00

With the ->sync_page() hook gone, we have a few users that
add their own static address_space_operations without any
functions defined.

fs/inode.c already has an empty_aops that it uses for init
purposes. Lets export that and use it in the places where
an otherwise empty aops was defined.

Signed-off-by: Jens Axboe

nilfs2: fix oops due to a bad aops initialization

2011-03-30T08:39:25+00:00

Nilfs in 2.6.39-rc1 hit the following oops:

 BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
 IP: [] try_to_release_page+0x2a/0x3d
 PGD 234cb6067 PUD 234c72067 PMD 0
 Oops: 0000 [#1] SMP
 
 Process truncate (pid: 10995, threadinfo ffff8802353c2000, task ffff880234cfa000)
 Stack:
  ffff8802333c77b8 ffffffff810b64b0 0000000000003802 ffffffffa0052cca
  0000000000000000 ffff8802353c3b58 0000000000000000 ffff8802353c3b58
  0000000000000001 0000000000000000 ffffea0007b92308 ffffea0007b92308
 Call Trace:
  [] ? invalidate_inode_pages2_range+0x15f/0x273
  [] ? nilfs_palloc_get_block+0x2d/0xaf [nilfs2]
  [] ? bit_waitqueue+0x14/0xa1
  [] ? wake_up_bit+0x10/0x20
  [] ? nilfs_forget_buffer+0x66/0x7a [nilfs2]
  [] ? nilfs_btree_concat_left+0x5c/0x77 [nilfs2]
  [] ? nilfs_btree_delete+0x395/0x3cf [nilfs2]
  [] ? nilfs_bmap_do_delete+0x6e/0x79 [nilfs2]
  [] ? nilfs_btree_last_key+0x14b/0x15e [nilfs2]
  [] ? nilfs_bmap_truncate+0x2f/0x83 [nilfs2]
  [] ? nilfs_bmap_last_key+0x35/0x62 [nilfs2]
  [] ? nilfs_truncate_bmap+0x6b/0xc7 [nilfs2]
  [] ? nilfs_truncate+0x79/0xe4 [nilfs2]
  [] ? vmtruncate+0x33/0x3b
  [] ? nilfs_setattr+0x4d/0x8c [nilfs2]
  [] ? do_page_fault+0x31b/0x356
  [] ? notify_change+0x17d/0x262
  [] ? do_truncate+0x65/0x80
  [] ? sys_ftruncate+0xf1/0xf6
  [] ? system_call_fastpath+0x16/0x1b
 Code: c3 48 83 ec 08 48 8b 17 48 8b 47 18 80 e2 01 75 04 0f 0b eb fe 48 8b 17 80 e6 20 74 05 31 c0 41 59 c3 48 85 c0 74 11 48 8b 40 58
  8b 40 48 48 85 c0 74 04 41 58 ff e0 59 e9 b1 b5 05 00 41 54
 RIP  [] try_to_release_page+0x2a/0x3d
  RSP 
 CR2: 0000000000000048

This oops was brought in by the change "block: remove per-queue
plugging" (commit: 7eaceaccab5f40bb).  It initializes mapping->a_ops
with a NULL pointer for some pages in nilfs (e.g. btree node pages),
but mm code doesn't NULL pointer checks against mapping->a_ops. (the
check is done for each callback function)

This corrects the aops initialization and fixes the oops.

Signed-off-by: Ryusuke Konishi 
Acked-by: Jens Axboe

Merge branch 'for-2.6.39/stack-plug' into for-2.6.39/core

2011-03-10T07:58:35+00:00

Conflicts:
	block/blk-core.c
	block/blk-flush.c
	drivers/md/raid1.c
	drivers/md/raid10.c
	drivers/md/raid5.c
	fs/nilfs2/btnode.c
	fs/nilfs2/mdt.c

Signed-off-by: Jens Axboe

block: remove per-queue plugging

2011-03-10T07:52:07+00:00

Code has been converted over to the new explicit on-stack plugging,
and delay users have been converted to use the new API for that.
So lets kill off the old plugging along with aops->sync_page().

Signed-off-by: Jens Axboe

mm: prevent concurrent unmap_mapping_range() on the same inode

2011-02-24T03:52:52+00:00

Michael Leun reported that running parallel opens on a fuse filesystem
can trigger a "kernel BUG at mm/truncate.c:475"

Gurudas Pai reported the same bug on NFS.

The reason is, unmap_mapping_range() is not prepared for more than
one concurrent invocation per inode.  For example:

  thread1: going through a big range, stops in the middle of a vma and
     stores the restart address in vm_truncate_count.

  thread2: comes in with a small (e.g. single page) unmap request on
     the same vma, somewhere before restart_address, finds that the
     vma was already unmapped up to the restart address and happily
     returns without doing anything.

Another scenario would be two big unmap requests, both having to
restart the unmapping and each one setting vm_truncate_count to its
own value.  This could go on forever without any of them being able to
finish.

Truncate and hole punching already serialize with i_mutex.  Other
callers of unmap_mapping_range() do not, and it's difficult to get
i_mutex protection for all callers.  In particular ->d_revalidate(),
which calls invalidate_inode_pages2_range() in fuse, may be called
with or without i_mutex.

This patch adds a new mutex to 'struct address_space' to prevent
running multiple concurrent unmap_mapping_range() on the same mapping.

[ We'll hopefully get rid of all this with the upcoming mm
  preemptibility series by Peter Zijlstra, the "mm: Remove i_mmap_mutex
  lockbreak" patch in particular.  But that is for 2.6.39 ]

Signed-off-by: Miklos Szeredi 
Reported-by: Michael Leun 
Reported-by: Gurudas Pai 
Tested-by: Gurudas Pai 
Acked-by: Hugh Dickins 
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds

nilfs2: fix a checkpatch error in page.c

2011-01-10T05:05:46+00:00

Will correct the following checkpatch error:

 ERROR: trailing whitespace
 #494: FILE: page.c:494:
 + $

Signed-off-by: Ryusuke Konishi