From: Yang Shi <yang.shi@linux.alibaba.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: proc: use down_read_killable in proc_pid_cmdline_read()
Date: Fri, 23 Feb 2018 12:08:20 -0800 [thread overview]
Message-ID: <139a6862-ca1a-c291-3e03-8130e35b5fc0@linux.alibaba.com> (raw)
In-Reply-To: <20180223194547.GC5708@avx2>
On 2/23/18 11:45 AM, Alexey Dobriyan wrote:
> On Fri, Feb 23, 2018 at 11:42:34AM -0800, Yang Shi wrote:
>>
>> On 2/23/18 11:33 AM, Alexey Dobriyan wrote:
>>> On Wed, Feb 21, 2018 at 03:13:10PM -0800, Yang Shi wrote:
>>>
>>>>>>> 2) access_remote_vm() et al will do the same ->mmap_sem, and
>>>>>> Yes, it does. But, __access_remote_vm() is called by access_process_vm()
>>>>>> too, which is used by much more places, i.e. ptrace, so I was not sure
>>>>>> if it is preferred to convert to killable version. So, I leave it untouched.
>>>>> Yeah, but ->mmap_sem is taken 3 times per /proc/*/cmdline read
>>>>> and your scalability tests should trigger next backtrace right away.
>>>> Yes, however, I didn't run into it if mmap_sem is acquired earlier.
>>>>
>>>> How about defining a killable version, like
>>>> __access_remote_vm_killable() which use down_read_killable(), then the
>>>> killable version can be used by proc/*/cmdline? There might be other
>>>> users in the future.
>>> It would be a disaster as interfaces multiply.
>> Might be not that bad.
> Maybe.
>
> But you need to explain why there is no backtrace several lines later:
>
> access_remote_vm
> __access_remote_vm
> down_read(&mm->mmap_sem)
I think it might be because:
CPU A CPU B
read /proc/*/cmdline
get_mm
acquire mmap_sem
munmap(300G) try to acquire mmap_sem --> go to sleep
release mmap_sem
got mmap_sem
release mmap_sem
access_remote_vm
put_mm
The munmap might happen right before access_remote_vm(), but I just
didn't run into it for the time being. It may be hit on another machine
or with some changes to the test cases.
BTW, even the hung I met happened occassionally, not very often. So, the
access_remote_vm() hit sounds less often. But, I agree it is still
possible in theory.
Regards,
Yang
next prev parent reply other threads:[~2018-02-23 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 19:49 Yang Shi
2018-02-20 22:38 ` Alexey Dobriyan
2018-02-20 23:38 ` Yang Shi
2018-02-21 19:57 ` Alexey Dobriyan
2018-02-21 23:13 ` Yang Shi
2018-02-23 19:33 ` Alexey Dobriyan
2018-02-23 19:42 ` Yang Shi
2018-02-23 19:45 ` Alexey Dobriyan
2018-02-23 20:08 ` Yang Shi [this message]
2018-02-23 18:28 ` Yang Shi
2018-02-20 23:57 ` Yang Shi
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=139a6862-ca1a-c291-3e03-8130e35b5fc0@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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®