From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: Nikolay Borisov <nborisov@suse.com>,
Omar Sandoval <osandov@osandov.com>,
linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: [PATCH v2] Btrfs: fix missing delayed iputs on unmount
Date: Thu, 1 Nov 2018 17:10:37 +0200 [thread overview]
Message-ID: <44d61374-3250-2cb5-b4f0-dd8f4d3678c6@gmail.com> (raw)
In-Reply-To: <a0a00740-6c97-7689-54dd-b381d4c8a2db@suse.com>
On 1.11.18 г. 16:35 ч., Nikolay Borisov wrote:
>
>
> On 31.10.18 г. 19:06 ч., Omar Sandoval wrote:
>> From: Omar Sandoval <osandov@fb.com>
>>
>> There's a race between close_ctree() and cleaner_kthread().
>> close_ctree() sets btrfs_fs_closing(), and the cleaner stops when it
>> sees it set, but this is racy; the cleaner might have already checked
>> the bit and could be cleaning stuff. In particular, if it deletes unused
>> block groups, it will create delayed iputs for the free space cache
>> inodes. As of "btrfs: don't run delayed_iputs in commit", we're no
>> longer running delayed iputs after a commit. Therefore, if the cleaner
>> creates more delayed iputs after delayed iputs are run in
>> btrfs_commit_super(), we will leak inodes on unmount and get a busy
>> inode crash from the VFS.
>>
>> Fix it by parking the cleaner before we actually close anything. Then,
>> any remaining delayed iputs will always be handled in
>> btrfs_commit_super(). This also ensures that the commit in close_ctree()
>> is really the last commit, so we can get rid of the commit in
>> cleaner_kthread().
>>
>> Fixes: 30928e9baac2 ("btrfs: don't run delayed_iputs in commit")
>> Signed-off-by: Omar Sandoval <osandov@fb.com>
>
> Also I believe this patch renders the wake_up_process in
> btrfs_commit_super a null op so it can also be removed, which leaves a
> single place that could wake up the cleaner - transaction_kthread.
>
> So can't we stop transaction and cleaner thread right after setting
> CLOSING_FS. And commit the transaction in close_ctree whenever we deem
> necessary (in btrfs_commit_super for example) ?
Ok, that won't work because commit_super is called in other contexts
where it can genuinely wake up the trans kthread, blimey. Why can't we
stop transaction kthread first thing in close_ctree ?
>
>> ---
>> Changes from v1:
>>
>> - Add a comment explaining why it needs to be a kthread_park(), not
>> kthread_stop()
>> - Update later comment now that the cleaner thread is definitely stopped
>>
>> fs/btrfs/disk-io.c | 51 ++++++++++++++--------------------------------
>> 1 file changed, 15 insertions(+), 36 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index b0ab41da91d1..40bcc45d827d 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -1664,9 +1664,8 @@ static int cleaner_kthread(void *arg)
>> struct btrfs_root *root = arg;
>> struct btrfs_fs_info *fs_info = root->fs_info;
>> int again;
>> - struct btrfs_trans_handle *trans;
>>
>> - do {
>> + while (1) {
>> again = 0;
>>
>> /* Make the cleaner go to sleep early. */
>> @@ -1715,42 +1714,16 @@ static int cleaner_kthread(void *arg)
>> */
>> btrfs_delete_unused_bgs(fs_info);
>> sleep:
>> + if (kthread_should_park())
>> + kthread_parkme();
>> + if (kthread_should_stop())
>> + return 0;
>> if (!again) {
>> set_current_state(TASK_INTERRUPTIBLE);
>> - if (!kthread_should_stop())
>> - schedule();
>> + schedule();
>> __set_current_state(TASK_RUNNING);
>> }
>> - } while (!kthread_should_stop());
>> -
>> - /*
>> - * Transaction kthread is stopped before us and wakes us up.
>> - * However we might have started a new transaction and COWed some
>> - * tree blocks when deleting unused block groups for example. So
>> - * make sure we commit the transaction we started to have a clean
>> - * shutdown when evicting the btree inode - if it has dirty pages
>> - * when we do the final iput() on it, eviction will trigger a
>> - * writeback for it which will fail with null pointer dereferences
>> - * since work queues and other resources were already released and
>> - * destroyed by the time the iput/eviction/writeback is made.
>> - */
>> - trans = btrfs_attach_transaction(root);
>> - if (IS_ERR(trans)) {
>> - if (PTR_ERR(trans) != -ENOENT)
>> - btrfs_err(fs_info,
>> - "cleaner transaction attach returned %ld",
>> - PTR_ERR(trans));
>> - } else {
>> - int ret;
>> -
>> - ret = btrfs_commit_transaction(trans);
>> - if (ret)
>> - btrfs_err(fs_info,
>> - "cleaner open transaction commit returned %d",
>> - ret);
>> }
>> -
>> - return 0;
>> }
>>
>> static int transaction_kthread(void *arg)
>> @@ -3931,6 +3904,13 @@ void close_ctree(struct btrfs_fs_info *fs_info)
>> int ret;
>>
>> set_bit(BTRFS_FS_CLOSING_START, &fs_info->flags);
>> + /*
>> + * We don't want the cleaner to start new transactions, add more delayed
>> + * iputs, etc. while we're closing. We can't use kthread_stop() yet
>> + * because that frees the task_struct, and the transaction kthread might
>> + * still try to wake up the cleaner.
>> + */
>> + kthread_park(fs_info->cleaner_kthread);
>>
>> /* wait for the qgroup rescan worker to stop */
>> btrfs_qgroup_wait_for_completion(fs_info, false);
>> @@ -3958,9 +3938,8 @@ void close_ctree(struct btrfs_fs_info *fs_info)
>>
>> if (!sb_rdonly(fs_info->sb)) {
>> /*
>> - * If the cleaner thread is stopped and there are
>> - * block groups queued for removal, the deletion will be
>> - * skipped when we quit the cleaner thread.
>> + * The cleaner kthread is stopped, so do one final pass over
>> + * unused block groups.
>> */
>> btrfs_delete_unused_bgs(fs_info);
>>
>>
next prev parent reply other threads:[~2018-11-01 15:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 17:06 [PATCH v2] Btrfs: fix missing delayed iputs on unmount Omar Sandoval
2018-11-01 10:15 ` David Sterba
2018-11-01 13:31 ` Chris Mason
2018-11-01 15:08 ` David Sterba
2018-11-01 15:22 ` David Sterba
2018-11-01 15:24 ` Omar Sandoval
2018-11-01 15:28 ` Omar Sandoval
2018-11-01 15:29 ` David Sterba
2018-11-01 16:00 ` Omar Sandoval
2018-11-01 16:44 ` David Sterba
2018-11-01 16:50 ` Nikolay Borisov
2018-11-01 17:15 ` David Sterba
2018-11-01 17:36 ` Chris Mason
2018-11-01 15:23 ` Omar Sandoval
2018-11-01 15:28 ` David Sterba
2018-11-01 14:35 ` Nikolay Borisov
2018-11-01 15:10 ` Nikolay Borisov [this message]
2018-11-07 16:01 ` David Sterba
2018-11-10 4:07 ` Omar Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44d61374-3250-2cb5-b4f0-dd8f4d3678c6@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=osandov@osandov.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).