diff options
| author | Tejun Heo | 2014-09-08 08:04:00 +0900 |
|---|---|---|
| committer | Jens Axboe | 2014-09-08 10:00:41 -0600 |
| commit | 1a1e4530eacca37e85a4d66a164273c7dba9110c (patch) | |
| tree | ade41fb1306d5efdb2868e4998926a2845c3274f /scripts/rt-tester/t5-l4-pi-boost-deboost-setsched.tst | |
| parent | c0ea1c22bce63a27b47da90ad1ac49ce48e1a8aa (diff) | |
bdi: explain the dirty list transferring in bdi_destroy()
bdi_destroy() has code to transfer the remaining dirty inodes to the
default_backing_dev_info; however, given the shutdown sequence, it
isn't clear how such condition would happen. Also, it isn't a full
solution as the transferred inodes stlil point to the bdi which is
being destroyed. Operations on those inodes can end up accessing
already released fields such as the percpu stat fields.
Digging through the history, it seems that the code was added as a
quick workaround for a bug report without fully root-causing the
issue. We probably want to remove the code in time but for now let's
add a comment noting that it is a quick workaround.
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'scripts/rt-tester/t5-l4-pi-boost-deboost-setsched.tst')
0 files changed, 0 insertions, 0 deletions