From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <ebiederm@xmission.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<yukuai3@huawei.com>, Matthew Wilcox <willy@infradead.org>,
<bhe@redhat.com>, <bfoster@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
<kaleshsingh@google.com>
Subject: Re: [PATCH v4] proc: Fix a dentry lock race between release_task and lookup
Date: Tue, 12 Jul 2022 11:06:16 +0800 [thread overview]
Message-ID: <b7df85db-8e02-8a0f-000f-b36eccf4505e@huawei.com> (raw)
In-Reply-To: <6e47d9b8-6b6e-e350-d688-1576f68211ed@huawei.com>
在 2022/6/10 16:09, Zhihao Cheng 写道:
> 在 2022/6/1 14:23, Zhihao Cheng 写道:
ping again.
> friendly ping
>> Commit 7bc3e6e55acf06 ("proc: Use a list of inodes to flush from proc")
>> moved proc_flush_task() behind __exit_signal(). Then, process systemd
>> can take long period high cpu usage during releasing task in following
>> concurrent processes:
>>
>> systemd ps
>> kernel_waitid stat(/proc/tgid)
>> do_wait filename_lookup
>> wait_consider_task lookup_fast
>> release_task
>> __exit_signal
>> __unhash_process
>> detach_pid
>> __change_pid // remove task->pid_links
>> d_revalidate -> pid_revalidate
>> // 0
>> d_invalidate(/proc/tgid)
>> shrink_dcache_parent(/proc/tgid)
>> d_walk(/proc/tgid)
>>
>> spin_lock_nested(/proc/tgid/fd)
>> // iterating opened fd
>> proc_flush_pid |
>> d_invalidate (/proc/tgid/fd) |
>> shrink_dcache_parent(/proc/tgid/fd) |
>> shrink_dentry_list(subdirs) ↓
>> shrink_lock_dentry(/proc/tgid/fd) --> race on
>> dentry lock
>>
>> Function d_invalidate() will remove dentry from hash firstly, but why
>> does
>> proc_flush_pid() process dentry '/proc/tgid/fd' before dentry
>> '/proc/tgid'?
>> That's because proc_pid_make_inode() adds proc inode in reverse order by
>> invoking hlist_add_head_rcu(). But proc should not add any inodes under
>> '/proc/tgid' except '/proc/tgid/task/pid', fix it by adding inode into
>> 'pid->inodes' only if the inode is /proc/tgid or /proc/tgid/task/pid.
>>
>> Performance regression:
>> Create 200 tasks, each task open one file for 50,000 times. Kill all
>> tasks when opened files exceed 10,000,000 (cat /proc/sys/fs/file-nr).
>>
>
> .
next prev parent reply other threads:[~2022-07-12 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 6:23 Zhihao Cheng
2022-06-10 8:09 ` Zhihao Cheng
2022-07-12 3:06 ` Zhihao Cheng [this message]
2022-07-12 14:16 ` Brian Foster
2022-07-13 7:24 ` Zhihao Cheng
2022-07-13 12:41 ` Brian Foster
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=b7df85db-8e02-8a0f-000f-b36eccf4505e@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kaleshsingh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®