From: Andrew Morton <akpm@linux-foundation.org>
To: Feng zhou <zhoufeng.zf@bytedance.com>
Cc: adobriyan@gmail.com, rppt@kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
songmuchun@bytedance.com, zhouchengming@bytedance.com,
chenying.kernel@bytedance.com, zhengqi.arch@bytedance.com
Subject: Re: [PATCH v2] fs/proc/kcore.c: add mmap interface
Date: Tue, 1 Jun 2021 19:22:57 -0700 [thread overview]
Message-ID: <20210601192257.65a514606382f0a972f918c3@linux-foundation.org> (raw)
In-Reply-To: <20210601082241.13378-1-zhoufeng.zf@bytedance.com>
On Tue, 1 Jun 2021 16:22:41 +0800 Feng zhou <zhoufeng.zf@bytedance.com> wrote:
> From: ZHOUFENG <zhoufeng.zf@bytedance.com>
>
> When we do the kernel monitor, use the DRGN
> (https://github.com/osandov/drgn) access to kernel data structures,
> found that the system calls a lot. DRGN is implemented by reading
> /proc/kcore. After looking at the kcore code, it is found that kcore
> does not implement mmap, resulting in frequent context switching
> triggered by read. Therefore, we want to add mmap interface to optimize
> performance. Since vmalloc and module areas will change with allocation
> and release, consistency cannot be guaranteed, so mmap interface only
> maps KCORE_TEXT and KCORE_RAM.
>
> ...
>
> +static int mmap_kcore(struct file *file, struct vm_area_struct *vma)
> +{
> + size_t size = vma->vm_end - vma->vm_start;
> + u64 start, pfn;
> + int nphdr;
> + size_t data_offset;
> + size_t phdrs_len, notes_len;
> + struct kcore_list *m = NULL;
> + int ret = 0;
> +
> + down_read(&kclist_lock);
> +
> + get_kcore_size(&nphdr, &phdrs_len, ¬es_len, &data_offset);
> +
> + start = kc_offset_to_vaddr(((u64)vma->vm_pgoff << PAGE_SHIFT) -
> + ((data_offset >> PAGE_SHIFT) << PAGE_SHIFT));
> +
> + list_for_each_entry(m, &kclist_head, list) {
> + if (start >= m->addr && size <= m->size)
> + break;
> + }
> +
> + if (&m->list == &kclist_head) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
> + if (vma->vm_flags & (VM_WRITE | VM_EXEC)) {
> + ret = -EPERM;
> + goto out;
> + }
> +
> + vma->vm_flags &= ~(VM_MAYWRITE | VM_MAYEXEC);
> + vma->vm_flags |= VM_MIXEDMAP;
> + vma->vm_ops = &kcore_mmap_ops;
> +
> + if (kern_addr_valid(start)) {
> + if (m->type == KCORE_RAM || m->type == KCORE_REMAP)
KCORE_REMAP was removed by
https://lkml.kernel.org/r/20210526093041.8800-2-david@redhat.com
I did this:
--- a/fs/proc/kcore.c~fs-proc-kcorec-add-mmap-interface-fix
+++ a/fs/proc/kcore.c
@@ -660,7 +660,7 @@ static int mmap_kcore(struct file *file,
vma->vm_ops = &kcore_mmap_ops;
if (kern_addr_valid(start)) {
- if (m->type == KCORE_RAM || m->type == KCORE_REMAP)
+ if (m->type == KCORE_RAM)
pfn = __pa(start) >> PAGE_SHIFT;
else if (m->type == KCORE_TEXT)
pfn = __pa_symbol(start) >> PAGE_SHIFT;
next prev parent reply other threads:[~2021-06-02 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:22 [PATCH v2] fs/proc/kcore.c: add mmap interface Feng zhou
2021-06-02 2:22 ` Andrew Morton [this message]
2021-06-02 2:31 ` [External] " zhoufeng
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=20210601192257.65a514606382f0a972f918c3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=chenying.kernel@bytedance.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=zhengqi.arch@bytedance.com \
--cc=zhouchengming@bytedance.com \
--cc=zhoufeng.zf@bytedance.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).