linux-toradex.git/drivers/md/bitmap.c, branch v3.10.78

md/bitmap: always wait for writes on unplug.

2015-01-08T17:58:15+00:00

commit 4b5060ddae2b03c5387321fafc089d242225697a upstream.

If two threads call bitmap_unplug at the same time, then
one might schedule all the writes, and the other might
decide that it doesn't need to wait.  But really it does.

It rarely hurts to wait when it isn't absolutely necessary,
and the current code doesn't really focus on 'absolutely necessary'
anyway.  So just wait always.

This can potentially lead to data corruption if a crash happens
at an awkward time and data was written before the bitmap was
updated.  It is very unlikely, but this should go to -stable
just to be safe.  Appropriate for any -stable.

Signed-off-by: NeilBrown 
Signed-off-by: Greg Kroah-Hartman

md: use set_bit_le and clear_bit_le

2013-04-24T01:42:41+00:00

The value returned by test_and_set_bit_le() drivers/md/bitmap.c is not used.
So just use set_bit_le(). The same goes for test_and_clear_bit_le().

Signed-off-by: Akinobu Mita 
Cc: Neil Brown 
Cc: linux-raid@vger.kernel.org
Signed-off-by: NeilBrown

new helper: file_inode(file)

2013-02-23T04:31:31+00:00

Signed-off-by: Al Viro

md/bitmap:Don't use IS_ERR to judge alloc_page().

2012-10-11T02:45:36+00:00

Signed-off-by: Jianpeng Ma 
Signed-off-by: NeilBrown

raid: replace list_for_each_continue_rcu with new interface

2012-10-11T02:43:21+00:00

This patch replaces list_for_each_continue_rcu() with
list_for_each_entry_continue_rcu() to save a few lines
of code and allow removing list_for_each_continue_rcu().

Reviewed-by: Paul E. McKenney 
Signed-off-by: Michael Wang 
Signed-off-by: NeilBrown

md/raid1: submit IO from originating thread instead of md thread.

2012-08-01T22:33:20+00:00

queuing writes to the md thread means that all requests go through the
one processor which may not be able to keep up with very high request
rates.

So use the plugging infrastructure to submit all requests on unplug.
If a 'schedule' is needed, we fall back on the old approach of handing
the requests to the thread for it to handle.

Signed-off-by: NeilBrown

md/bitmap: record the space available for the bitmap in the superblock.

2012-05-22T03:55:34+00:00

Now that bitmaps can grow and shrink it is best if we record
how much space is available.  This means that when
we reduce the size of the bitmap we won't "lose" the space
for late when we might want to increase the size of the bitmap
again.

Signed-off-by: NeilBrown

md/bitmap: make sure reshape request are reflected in superblock.

2012-05-22T03:55:26+00:00

As a reshape may change the sync_size and/or chunk_size, we need
to update these whenever we write out the bitmap superblock.

Signed-off-by: NeilBrown

md/bitmap: add bitmap_resize function to allow bitmap resizing.

2012-05-22T03:55:25+00:00

This function will allocate the new data structures and copy
bits across from old to new, allowing for the possibility that the
chunksize has changed.

Use the same function for performing the initial allocation
of the structures.  This improves test coverage.

When bitmap_resize is used to resize an existing bitmap, it
only copies '1' bits in, not '0' bits.
So when allocating the bitmap, ensure everything is initialised
to ZERO.

Signed-off-by: NeilBrown

md/bitmap: use DIV_ROUND_UP instead of open-code

2012-05-22T03:55:25+00:00

Also take the opportunity to simplify CHUNK_BLOCK_RATIO.

Signed-off-by: NeilBrown