Btrfs: use a worker thread to do caching

Browse source

A user reported a deadlock when copying a bunch of files.  This is because they
were low on memory and kthreadd got hung up trying to migrate pages for an
allocation when starting the caching kthread.  The page was locked by the person
starting the caching kthread.  To fix this we just need to use the async thread
stuff so that the threads are already created and we don't have to worry about
deadlocks.  Thanks,

Reported-by: Roman Mamedov <rm@romanrm.ru>
Signed-off-by: Josef Bacik <josef@redhat.com>

...

This commit is contained in:

Josef Bacik 2011-06-30 14:42:28 -04:00 • committed by Chris Mason

parent df98b6e2c5

commit bab39bf998

3 changed files with 27 additions and 29 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

fs/btrfs/ctree.h

View file

6

fs/btrfs/disk-io.c

View file

46

fs/btrfs/extent-tree.c

View file