[PATCH 0/2] Two fixes for loop devices · NeilBrown <hidden> · 2017-06-16
[PATCH 1/2] loop: use filp_close() rather than fput() · NeilBrown <hidden> · 2017-06-16
Re: [PATCH 1/2] loop: use filp_close() rather than fput() · Christoph Hellwig <hch@infradead.org> · 2017-06-16
Re: [PATCH 1/2] loop: use filp_close() rather than fput() · Al Viro <viro@ZenIV.linux.org.uk> · 2017-06-17
Re: [PATCH 1/2] loop: use filp_close() rather than fput() · NeilBrown <hidden> · 2017-06-18
[PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread. · NeilBrown <hidden> · 2017-06-16
Re: [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread. · Christoph Hellwig <hch@infradead.org> · 2017-06-16
Re: [PATCH 0/2] Two fixes for loop devices · Jens Axboe <axboe@fb.com> · 2017-06-16
Re: [PATCH 0/2] Two fixes for loop devices · NeilBrown <hidden> · 2017-06-18
Re: [PATCH 0/2] Two fixes for loop devices · Jens Axboe <axboe@kernel.dk> · 2017-06-18

Re: [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

From: Christoph Hellwig <hch@infradead.org>
Date: 2017-06-16 07:37:02
Also in: lkml

why isn't loop using kthread_create_worker()?  Why isn't the less
throttle a flag to kthread_create_worker()?  I hate all this open
coding..