linux-toradex.git/mm/backing-dev.c, branch v2.6.31-rc4

Fix congestion_wait() sync/async vs read/write confusion

2009-07-10T18:31:53+00:00

Commit 1faa16d22877f4839bd433547d770c676d1d964c accidentally broke
the bdi congestion wait queue logic, causing us to wait on congestion
for WRITE (== 1) when we really wanted BLK_RW_ASYNC (== 0) instead.

Signed-off-by: Jens Axboe

block: change the request allocation/congestion logic to be sync/async based

2009-04-06T15:04:53+00:00

This makes sure that we never wait on async IO for sync requests, instead
of doing the split on writes vs reads.

Signed-off-by: Jens Axboe 
Signed-off-by: Linus Torvalds

Move the default_backing_dev_info out of readahead.c and into backing-dev.c

2009-03-26T10:01:33+00:00

It really makes no sense to have it in readahead.c, so move it where
it belongs.

Signed-off-by: Jens Axboe

Merge branch 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

2009-01-07T01:10:04+00:00

* 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
  rcu: fix rcutorture bug
  rcu: eliminate synchronize_rcu_xxx macro
  rcu: make treercu safe for suspend and resume
  rcu: fix rcutree grace-period-latency bug on small systems
  futex: catch certain assymetric (get|put)_futex_key calls
  futex: make futex_(get|put)_key() calls symmetric
  locking, percpu counters: introduce separate lock classes
  swiotlb: clean up EXPORT_SYMBOL usage
  swiotlb: remove unnecessary declaration
  swiotlb: replace architecture-specific swiotlb.h with linux/swiotlb.h
  swiotlb: add support for systems with highmem
  swiotlb: store phys address in io_tlb_orig_addr array
  swiotlb: add hwdev to swiotlb_phys_to_bus() / swiotlb_sg_to_bus()

mm: change dirty limit type specifiers to unsigned long

2009-01-06T23:59:02+00:00

The background dirty and dirty limits are better defined with type
specifiers of unsigned long since negative writeback thresholds are not
possible.

These values, as returned by get_dirty_limits(), are normally compared
with ZVC values to determine whether writeback shall commence or be
throttled.  Such page counts cannot be negative, so declaring the page
limits as signed is unnecessary.

Acked-by: Peter Zijlstra 
Cc: Dave Chinner 
Cc: Christoph Lameter 
Signed-off-by: David Rientjes 
Cc: Andrea Righi 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branches 'core/futexes', 'core/locking', 'core/rcu' and 'linus' into core/urgent

2009-01-06T08:32:11+00:00

locking, percpu counters: introduce separate lock classes

2008-12-29T12:43:00+00:00

Impact: fix lockdep false positives

Classify percpu_counter instances similar to regular lock objects --
that is, per instantiation site.

The networking code has increased its use of percpu_counters, which
leads to false positives if they are treated as a single class.

Signed-off-by: Peter Zijlstra 
Signed-off-by: Ingo Molnar

mm/backing-dev.c: remove recently-added WARN_ON()

2008-12-10T16:01:52+00:00

On second thoughts, this is just going to disturb people while telling us
things which we already knew.

Cc: Peter Korsgaard 
Cc: Peter Zijlstra 
Cc: Kay Sievers 
Cc: David Woodhouse 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

bdi: register sysfs bdi device only once per queue

2008-12-02T23:50:40+00:00

Devices which share the same queue, like floppies and mtd devices, get
registered multiple times in the bdi interface, but bdi accounts only the
last registered device of the devices sharing one queue.

On remove, all earlier registered devices leak, stay around in sysfs, and
cause "duplicate filename" errors if the devices are re-created.

This prevents the creation of multiple bdi interfaces per queue, and the
bdi device will carry the dev_t name of the block device which is the
first one registered, of the pool of devices using the same queue.

[akpm@linux-foundation.org: add a WARN_ON so we know which drivers are misbehaving]
Tested-by: Peter Korsgaard 
Acked-by: Peter Zijlstra 
Signed-off-by: Kay Sievers 
Cc: David Woodhouse 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm: bdi: fix race in bdi_class device creation

2008-05-20T20:31:53+00:00

There is a race from when a device is created with device_create() and
then the drvdata is set with a call to dev_set_drvdata() in which a
sysfs file could be open, yet the drvdata will be NULL, causing all
sorts of bad things to happen.

This patch fixes the problem by using the new function,
device_create_vargs().

Many thanks to Arthur Jones  for reporting the bug,
and testing patches out.

Cc: Kay Sievers 
Cc: Arthur Jones 
Cc: Peter Zijlstra 
Cc: Miklos Szeredi 
Signed-off-by: Greg Kroah-Hartman