-------- Original Message --------
Subject: Re: [PATCH] Btrfs: fix task hang under heavy compressed write
From: Chris Mason <c...@fb.com>
To: Liu Bo <bo.li....@oracle.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Date: 2014年08月12日 22:57
On 08/12/2014 03:44 AM, Liu Bo wrote:
This has been reported and discussed for a long time, and this hang occurs in
both 3.15 and 3.16.
Btrfs now migrates to use kernel workqueue, but it introduces this hang problem.
Btrfs has a kind of work queued as an ordered way, which means that its
ordered_func() must be processed in the way of FIFO, so it usually looks like --
This definitely explains some problems, and I overlooked the part where
all of our workers use the same normal_work()
Oh, all my faults, it didn't occur to me that it is possible that other
process can alloc the same address of memory :(
And same normal_work() makes things much worse.
But I think it's actually goes beyond just the ordered work queues.
Process A:
btrfs_bio_wq_end_io() -> kmalloc a end_io_wq struct at address P
submit bio
end bio
btrfs_queue_work(endio_write_workers)
worker thread jumps in
end_workqueue_fn()
-> kfree(end_io_wq)
^^^^^ right here end_io_wq can be reused,
but the worker thread is still processing this work item
Process B:
btrfs_bio_wq_end() -> kmalloc an end_io_wq struct, reuse P
submit bio
end bio ... sometimes this is really fast
btrfs_queue_work(endio_workers) // lets do a read
->process_one_work()
-> find_worker_executing_work()
^^^^^ now we get in trouble. our struct P is still
active and so find_worker_executing_work() is going
to queue up this read completion on the end of the
scheduled list for this worker in the generic code.
The end result is we can have read IO completions
queued up behind write IO completions.
This example uses the bio end io code, but we probably have others. The
real solution is to have each btrfs workqueue provide its own worker
function, or each caller to btrfs_queue_work to send a unique worker
function down to the generic code.
That's true, personally I prefer the first one since it affects less
callers, but it seems to need more macro
hacks or somthing like it to generate different functions but they all
do the samething...
Thanks,
Qu
Thanks Liu, great job finding this.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
